Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1656814 > unrolled thread

Re: [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Re: [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging Greg KH <gregkh@linuxfoundation.org> - 2017-06-03 16:10 +0200
    RE: [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging Laurentiu Tudor <laurentiu.tudor@nxp.com> - 2017-06-06 16:10 +0200
      RE: [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging Laurentiu Tudor <laurentiu.tudor@nxp.com> - 2017-06-06 16:30 +0200
      Re: [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging Greg KH <gregkh@linuxfoundation.org> - 2017-06-06 16:30 +0200

#1656814 — Re: [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging

On Wed, May 31, 2017 at 01:58:52PM +0300, laurentiu.tudor@nxp.com wrote:
> From: Stuart Yoder <stuart.yoder@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'!

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?

thanks,

greg k-h

[toc] | [next] | [standalone]

#1658794

Hi Greg, 

> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Saturday, June 03, 2017 11:40 AM
> 
> On Wed, May 31, 2017 at 01:58:52PM +0300, laurentiu.tudor@nxp.com wrote:
> > From: Stuart Yoder <stuart.yoder@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.
 
> 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)?

---
Thanks & Best Regards, Laurentiu

[toc] | [prev] | [next] | [standalone]

#1658802

> -----Original Message-----
> From: Greg KH [mailto:gregkh@linuxfoundation.org]
> Sent: Tuesday, June 06, 2017 5:20 PM
> To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
> 
> On Tue, Jun 06, 2017 at 02:03:44PM +0000, Laurentiu Tudor wrote:
> > Hi Greg,
> >
> > > -----Original Message-----
> > > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > > Sent: Saturday, June 03, 2017 11:40 AM
> > >
> > > On Wed, May 31, 2017 at 01:58:52PM +0300, laurentiu.tudor@nxp.com
> wrote:
> > > > From: Stuart Yoder <stuart.yoder@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 :)
> 

Ok, finally got it. :-) Will do so in the next spin.

---
Thanks & Best Regards, Laurentiu

[toc] | [prev] | [next] | [standalone]

#1658806

On Tue, Jun 06, 2017 at 02:03:44PM +0000, Laurentiu Tudor wrote:
> Hi Greg, 
> 
> > -----Original Message-----
> > From: Greg KH [mailto:gregkh@linuxfoundation.org]
> > Sent: Saturday, June 03, 2017 11:40 AM
> > 
> > On Wed, May 31, 2017 at 01:58:52PM +0300, laurentiu.tudor@nxp.com wrote:
> > > From: Stuart Yoder <stuart.yoder@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

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web