2013/8/3 Gerhard Sittig <g...@denx.de>: > On Wed, Jul 31, 2013 at 11:21 +0400, Alexander Popov wrote: >> > You don't provide a lot of information to those you want to > receive feedback from. You should keep a history and list the > changes between versions. And you may want to somehow link this > v3 to its predecessor -- especially when you only send part of > the series and assume that reviewers may know where to find the > remainder. > > Please help those persons you want to get help from.
Thanks. Now I see how to collaborate via mailing lists properly. > I think it's unfortunate to attribute the "will access > peripheral" to the channel instead of the transfer job, and to > set the flag from within the device control callback, and to > nevery clear the flag (what will happen if a channel gets freed > and reallocated by some other client?). > > I think that the peripheral access is an attribute of the > transfer job, and should be setup in the prep routines (both set > and cleared, depending on what gets setup). This would be more > robust and more readable (read: maintainable) in my eyes. Yes. I agree, I will implement it and offer differences from RFC v2 in the initial topic. Best regards, Alexander. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
