Re: iio/…: Use common error handling code

2017-12-10 Thread Jonathan Cameron
On Sun, 10 Dec 2017 17:43:34 +0100 SF Markus Elfring wrote: > > Hi Markus, I've accepted the ones that I think made an improvement > > outweighing the inherent small costs of making any change. > > Does such a kind of feedback mean that you reconsidered any places > where you expressed a rejec

Re: iio/…: Use common error handling code

2017-12-10 Thread SF Markus Elfring
> Hi Markus, I've accepted the ones that I think made an improvement > outweighing the inherent small costs of making any change. Does such a kind of feedback mean that you reconsidered any places where you expressed a rejection initially? > We also need to avoid code constructs that are unusual

Re: iio/…: Use common error handling code

2017-12-10 Thread Jonathan Cameron
On Sun, 10 Dec 2017 13:33:01 +0100 SF Markus Elfring wrote: > > Again, a general kernel development rule is to float only one > > patch of a given type until you have had feedback on it. > > A few weeks later … > > > > As I said in one of the other patches, I always reply to all > > patches

Re: iio/…: Use common error handling code

2017-12-10 Thread SF Markus Elfring
> Again, a general kernel development rule is to float only one > patch of a given type until you have had feedback on it. A few weeks later … > As I said in one of the other patches, I always reply to all > patches I am rejecting so that anyone coming across them later > on their own from an ar