From: Mark Brown <broonie@kernel.org>
To: Steve Twiss <stwiss.opensource@diasemi.com>
Cc: LINUX-KERNEL <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
DEVICETREE <devicetree@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Eduardo Valentin <edubezval@gmail.com>,
Guenter Roeck <linux@roeck-us.net>,
LINUX-INPUT <linux-input@vger.kernel.org>,
LINUX-PM <linux-pm@vger.kernel.org>,
LINUX-WATCHDOG <linux-watchdog@vger.kernel.org>,
Lee Jones <lee.jones@linaro.org>,
Mark Rutland <mark.rutland@arm.com>,
Rob Herring <robh+dt@kernel.org>,
Support Opensource <Support.Opensource@diasemi.com>,
Wim Van Sebroeck <wim@iguana.be>, Zhang Rui <rui.zhang@intel.com>
Subject: Re: [RESEND PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator driver
Date: Wed, 7 Jun 2017 16:42:06 +0100 [thread overview]
Message-ID: <20170607154206.3mcozi3fmue3dsuw@sirena.org.uk> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB7018CD927CE@SW-EX-MBX02.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On Wed, Jun 07, 2017 at 02:09:56PM +0000, Steve Twiss wrote:
> On 07 June 2017 10:42, Mark Brown wrote:
> > I'm missing the other patches in this series and the cover letter, what
> > are the dependencies here?
> My apologies Mark. I didn't re-send the cover letter because this regulator
> patch is the last one and I assumed it would not add anything.
> Am I confusing you here by not renaming the patch and leaving its subject
> as [PATCH V7 5/7]?
Yes, you are confusing things. You're missing the point of numbering
patches in a series, it's so that when working with a set of patches
that have been posted pople know what order to apply them in. The
numbering only means anything in a given posting of the series, if
something is resent it doesn't matter if it was posted before the
numbering should reflect what's being posted at the current time.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-06-07 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1496823229.git.stwiss.opensource@diasemi.com>
2017-06-07 8:13 ` [RESEND PATCH V7 5/7] regulator: da9061: BUCK and LDO regulator driver Steve Twiss
2017-06-07 9:41 ` Mark Brown
2017-06-07 14:09 ` Steve Twiss
2017-06-07 15:42 ` Mark Brown [this message]
[not found] <cover.1495546845.git.stwiss.opensource@diasemi.com>
[not found] ` <cover.1495546845.git.stwiss.opensource-WBD+wuPFNBhBDgjK7y7TUQ@public.gmane.org>
2017-05-23 13:40 ` Steve Twiss
2017-05-23 17:17 ` Mark Brown
2017-05-24 8:12 ` Steve Twiss
[not found] ` <6ED8E3B22081A4459DAC7699F3695FB7018CD8D651-68WUHU125fLzLL1Oxlh9IgLouzNaz+3S@public.gmane.org>
2017-05-24 8:40 ` Lee Jones
[not found] ` <20170523171721.lpqjhakaawnz4prz-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-05-24 8:32 ` Lee Jones
2017-05-24 10:10 ` Mark Brown
[not found] ` <20170524101057.v2fqwki4fopx5k7y-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2017-05-30 9:17 ` Lee Jones
2017-06-06 19:02 ` 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=20170607154206.3mcozi3fmue3dsuw@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Support.Opensource@diasemi.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=edubezval@gmail.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=rui.zhang@intel.com \
--cc=stwiss.opensource@diasemi.com \
--cc=wim@iguana.be \
/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