From: Greg KH <gregkh@linuxfoundation.org>
To: Laurentiu Tudor <laurentiu.tudor@nxp.com>
Cc: "stuyoder@gmail.com" <stuyoder@gmail.com>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"agraf@suse.de" <agraf@suse.de>, "arnd@arndb.de" <arnd@arndb.de>,
Ioana Ciornei <ioana.ciornei@nxp.com>,
Ruxandra Ioana Radulescu <ruxandra.radulescu@nxp.com>,
Bharat Bhushan <bharat.bhushan@nxp.com>,
Catalin Horghidan <catalin.horghidan@nxp.com>,
Leo Li <leoyang.li@nxp.com>, Roy Pledge <roy.pledge@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>
Subject: Re: [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging
Date: Tue, 6 Jun 2017 16:20:14 +0200 [thread overview]
Message-ID: <20170606142014.GA19404@kroah.com> (raw)
In-Reply-To: <VI1PR0401MB1856DBA58830206CC7DFC18DECCB0@VI1PR0401MB1856.eurprd04.prod.outlook.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 :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-06 14:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-31 10:58 [PATCH v6 00/10] staging: fsl-mc: move bus driver out of staging laurentiu.tudor
2017-05-31 10:58 ` [PATCH 01/10] staging: fsl-mc: enclose macro params in parens laurentiu.tudor
2017-06-03 8:41 ` Greg KH
2017-06-06 12:03 ` Laurentiu Tudor
2017-05-31 10:58 ` [PATCH 02/10] staging: fsl-mc: fix macros with possible side effects laurentiu.tudor
2017-05-31 10:58 ` [PATCH 03/10] staging: fsl-mc: simplify couple of deallocations laurentiu.tudor
2017-05-31 10:58 ` [PATCH 04/10] staging: fsl-mc: drop a few useless #includes laurentiu.tudor
2017-05-31 10:58 ` [PATCH 05/10] staging: fsl-mc: remove extra blank line laurentiu.tudor
2017-05-31 10:58 ` [PATCH 06/10] staging: fsl-mc: drop unused forward declaration laurentiu.tudor
2017-05-31 10:58 ` [PATCH v2 07/10] staging: fsl-mc: add binding path to MAINTAINERS laurentiu.tudor
2017-05-31 10:58 ` [PATCH 08/10] staging: fsl-mc: drop reference to restool laurentiu.tudor
2017-05-31 10:58 ` [PATCH 09/10] staging: fsl-mc: add reference to mc-bus DT binding laurentiu.tudor
2017-05-31 10:58 ` [PATCH v4 10/10] staging: fsl-mc: move bus driver out of staging laurentiu.tudor
2017-05-31 11:15 ` Marc Zyngier
2017-05-31 11:31 ` Laurentiu Tudor
2017-06-03 8:40 ` Greg KH
2017-06-06 14:03 ` Laurentiu Tudor
2017-06-06 14:20 ` Greg KH [this message]
2017-06-06 14:23 ` Laurentiu Tudor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170606142014.GA19404@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agraf@suse.de \
--cc=arnd@arndb.de \
--cc=bharat.bhushan@nxp.com \
--cc=catalin.horghidan@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=ioana.ciornei@nxp.com \
--cc=jason@lakedaemon.net \
--cc=laurentiu.tudor@nxp.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.zyngier@arm.com \
--cc=roy.pledge@nxp.com \
--cc=ruxandra.radulescu@nxp.com \
--cc=stuyoder@gmail.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox