On Wed, Dec 07, 2005 at 03:13:32PM -0200, Eduardo Pereira Habkost wrote: > I have a small question: in my view, this patch series is a small > step towards implementing the usb-serial drivers The Right Way, as it > removes a a bit of duplicated code.
It doesn't remove any "duplicated code", it only changes a spinlock to an atomic_t for one single value (which I personally do not think is the best thing to do, and based on the number of comments on this thread, I think others also feel this way.) > If we start to do The Big Change to serial_core , probably we would > make further refactorings on these parts, going towards The Right Way > to implement the drivers. Sure, that's the way kernel development is done. > My question would be: where would the small refactorings belong, while > the big change to serial_core is work in progress? I would like them > to go to some tree for testing, while the work is being done, instead > of pushing lots of changes later, but I don't know if there is someone > who we could send them. The "normal" way of doing work like this is, do it somewhere, and then break it all down into a series of steps, after you have figured out exactly where you are going to end up. Feel free to send me any patches that you feel should be applied that work toward this end goal. thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
