From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ashish Jangam <Ashish.Jangam@kpitcummins.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Dajun <dajun.chen@diasemi.com>, "arnd@arndb.de" <arnd@arndb.de>,
"sameo@linux.intel.com" <sameo@linux.intel.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Anton Vorontsov <avorontsov@ru.mvista.com>
Subject: Re: [PATCH 02/06] MFD: DA9052/53 MFD core module v9 Added ADC support
Date: Tue, 10 Jan 2012 22:43:30 +0000 [thread overview]
Message-ID: <20120110224329.GM7164@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <C3AE124F08223B42BC95AEB82F0F6CED1FDB2D4E@KCHJEXMB02.kpit.com>
On Tue, Jan 10, 2012 at 05:50:30AM +0000, Ashish Jangam wrote:
> >>This is patch 2/6 - where are patches 1 and 3-6?
> Patch 1 and 3-6 are already ACK'ed and got merged.
> Since patch 2/6 was not merged therefore got re-submitted.
You're not understanding the purpose of the numbering at all here. The
numbering is there so that people know what order the patches being sent
together come in. If a patch has been sent before as part of a series
that's totally irrelevant to a further submission.
If you label the patch as part of a series like this then you're saying
that there's a patch 1 that this depends on and is needed for this to be
applied.
next prev parent reply other threads:[~2012-01-10 22:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 8:46 [PATCH 02/06] MFD: DA9052/53 MFD core module v9 Added ADC support Ashish Jangam
2012-01-09 22:37 ` Mark Brown
2012-01-10 5:50 ` Ashish Jangam
2012-01-10 22:43 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-09 14:16 Ashish Jangam
2011-12-12 4:52 ` Mark Brown
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=20120110224329.GM7164@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=Ashish.Jangam@kpitcummins.com \
--cc=arnd@arndb.de \
--cc=avorontsov@ru.mvista.com \
--cc=dajun.chen@diasemi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.