On Tue, Jun 06, 2017 at 02:03:44PM +0000, Laurentiu Tudor wrote: > Hi Greg, > > > -----Original Message----- > > From: Greg KH [mailto:gre...@linuxfoundation.org] > > Sent: Saturday, June 03, 2017 11:40 AM > > > > On Wed, May 31, 2017 at 01:58:52PM +0300, laurentiu.tu...@nxp.com wrote: > > > From: Stuart Yoder <stuart.yo...@nxp.com> > > > > Your subject says 'v4' yet the other patches here in the series do not, > > they say > > nothing, or 'v2', and the 0/10 patch says 'v6'! > > I'm tracking the patch versions individually and use the cover letter version > (v6 currently) > to reflect the version of the patch series as a whole. There are a bunch of > patches that are either newly > introduced in this series or didn't had multiple versions so I didn't tagged > them with a version tag. > The patch [10/10] didn't changed since v4 so I left the version unchanged. > The only change was in patch [07/10] > for which I added a commit message so I bumped the version to v2.
And that's totally crazy. What do you expect me, or anyone else, to know what to do with that. Heck, I can't even sort them by proper order in which to apply them in, if I wanted to. You are keeping me from actually using your work :( > > Please fix up and do this correctly. The _whole_ patch series is versioned, > > otherwise how can I sort them to apply them in the correct order? > > Want me to tag all the patches with the same version (that is, v7 for > the next respin)? Yes, like everyone else does please :) thanks, greg k-h _______________________________________________ devel mailing list de...@linuxdriverproject.org http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
