From: Matt Porter <mporter@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Lee Jones <lee.jones@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Samuel Ortiz <sameo@linux.intel.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Christian Daudt <bcm@fixthebug.org>,
Devicetree List <devicetree@vger.kernel.org>,
Linux ARM Kernel List <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/5] mfd: add bcm590xx pmu driver
Date: Tue, 11 Mar 2014 20:57:48 -0400 [thread overview]
Message-ID: <20140312005748.GQ25092@beef> (raw)
In-Reply-To: <20140312004030.GH28112@sirena.org.uk>
[-- Attachment #1: Type: text/plain, Size: 742 bytes --]
On Wed, Mar 12, 2014 at 12:40:30AM +0000, Mark Brown wrote:
> On Tue, Mar 11, 2014 at 07:25:45PM -0400, Matt Porter wrote:
> > On Tue, Mar 11, 2014 at 10:45:17PM +0000, Lee Jones wrote:
>
> > > Are there any inter-patch dependencies in the set? If so, we should
> > > know about them so we can coordinate a sensible solution.
>
> > Yes, the regulator driver (3/5) that Mark applied is dependent on this
> > patch...the regulator driver includes include/linux/mfd/bcm590xx.h.
>
> There's no actual dependency though - the regulator driver can only be
> built if the MFD is enabled in Kconfig since it depends on it so until
> the MFD is present in the tree it won't get built.
Oh, right. Lee, no dependencies then.
-Matt
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-03-12 0:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 15:46 [PATCH v3 0/5] BCM59056 PMU regulator support Matt Porter
2014-03-11 15:46 ` [PATCH v3 1/5] mfd: add bcm590xx pmu DT binding Matt Porter
2014-03-11 15:46 ` [PATCH v3 2/5] mfd: add bcm590xx pmu driver Matt Porter
[not found] ` <1394552775-31264-3-git-send-email-mporter-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2014-03-11 16:08 ` Lee Jones
2014-03-11 22:19 ` Matt Porter
2014-03-11 22:45 ` Lee Jones
2014-03-11 23:25 ` Matt Porter
2014-03-12 0:40 ` Mark Brown
2014-03-12 0:57 ` Matt Porter [this message]
2014-03-12 9:23 ` Lee Jones
2014-03-12 9:35 ` Lee Jones
2014-03-11 15:46 ` [PATCH v3 3/5] regulator: add bcm590xx regulator driver Matt Porter
2014-03-11 18:52 ` Mark Brown
2014-03-11 15:46 ` [PATCH v3 4/5] ARM: configs: bcm_defconfig: enable bcm590xx regulator support Matt Porter
2014-03-11 15:46 ` [PATCH v3 5/5] ARM: dts: add bcm590xx pmu support and enable for bcm28155-ap Matt Porter
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=20140312005748.GQ25092@beef \
--to=mporter@linaro.org \
--cc=bcm@fixthebug.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sameo@linux.intel.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;
as well as URLs for NNTP newsgroup(s).