From: Mark Brown <broonie@kernel.org>
To: "Opensource [Steve Twiss]" <stwiss.opensource@diasemi.com>
Cc: Lee Jones <lee.jones@linaro.org>,
LINUXKERNEL <linux-kernel@vger.kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Samuel Ortiz <sameo@linux.intel.com>,
David Dajun Chen <david.chen@diasemi.com>,
Support Opensource <Support.Opensource@diasemi.com>
Subject: Re: [PATCH V1 0/2] Add DA9021 support to the existing DA9052/53 driver
Date: Mon, 12 Oct 2015 17:42:18 +0100 [thread overview]
Message-ID: <20151012164218.GI4238@sirena.org.uk> (raw)
In-Reply-To: <6ED8E3B22081A4459DAC7699F3695FB70173D1AB31@SW-EX-MBX02.diasemi.com>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Fri, Oct 09, 2015 at 12:52:00PM +0000, Opensource [Steve Twiss] wrote:
> On 09 October 2015 12:36 Mark Brown wrote:
> > Are there any dependencies between the two patches?
> Nope.
> I just thought because they were for MFD and regulators I would separate them.
> Do you want me to merge them into a single patch and re-send?
No, the point is that if you send a series the assumption will normally
be that later patches depend on earlier patches so a cross tree merge or
carrying things in a non-default tree is required to get everything
integrated.
If there are no dependencies it's clearer to just send each patch
individually.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-10-12 16:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-08 15:17 Steve Twiss
2015-10-08 15:17 ` [PATCH V1 1/2] mfd: da9053: Addition of extra registers for GPIOs 8-13 Steve Twiss
2015-10-13 7:31 ` Lee Jones
2015-10-13 8:21 ` Opensource [Steve Twiss]
2015-10-08 15:17 ` [PATCH V1 2/2] regulator: da9053: Add regulator support for DA9053 BB silicon Steve Twiss
2015-10-09 11:36 ` [PATCH V1 0/2] Add DA9021 support to the existing DA9052/53 driver Mark Brown
2015-10-09 12:52 ` Opensource [Steve Twiss]
2015-10-12 7:57 ` Opensource [Steve Twiss]
2015-10-12 16:42 ` Mark Brown [this message]
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=20151012164218.GI4238@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Support.Opensource@diasemi.com \
--cc=david.chen@diasemi.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sameo@linux.intel.com \
--cc=stwiss.opensource@diasemi.com \
/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
all inboxes | Powered by JetHome®