> [..] > > Put it in drivers/staging/sdfat/. > > > > But really we want someone from Samsung to say that they will treat > > the staging version as upstream. It doesn't work when people apply > > fixes to their version and a year later back port the fixes into > > staging. The staging tree is going to have tons and tons of white space > > fixes so backports are a pain. All development needs to be upstream > > first where the staging driver is upstream. Otherwise we should just > > wait for Samsung to get it read to be merged in fs/ and not through the > > staging tree. > Quite frankly, > This whole thing came as a huge-huge surprise to us, we did not initiate > upstreaming of exfat/sdfat code and, as of this moment, I'm not exactly > sure that we are prepared for any immediate radical changes to our internal > development process which people all of a sudden want from us. I need to > discuss with related people on internal thread. > please wait a while:) We decide to contribute sdfat directly and treat upstream exfat. Perhaps more time is needed for patch preparation(exfat rename + vfat removal + clean-up) and internal processes. After contributing sdfat v2.2.0 as the base, We will also provide change-set of sdfat v2.3.0 later. Thanks! > > Thanks! > > > > regards, > > dan carpenter > > _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
