From: Mark Brown <broonie@kernel.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Charles Keepax <ckeepax@opensource.cirrus.com>,
lee.jones@linaro.org, linus.walleij@linaro.org,
mturquette@baylibre.com, robh+dt@kernel.org,
mark.rutland@arm.com, lgirdwood@gmail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com, linux-clk@vger.kernel.org,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v2 3/5] clk: lochnagar: Add support for the Cirrus Logic Lochnagar
Date: Mon, 15 Oct 2018 17:55:28 +0100 [thread overview]
Message-ID: <20181015165528.GD12949@sirena.org.uk> (raw)
In-Reply-To: <153962159992.5275.9275448716859702011@swboyd.mtv.corp.google.com>
[-- Attachment #1: Type: text/plain, Size: 446 bytes --]
On Mon, Oct 15, 2018 at 09:39:59AM -0700, Stephen Boyd wrote:
> Ok if there's going to be read/volatile regs and defaults then it makes
> sense to leave the defines in some shared header file, which is
> unfortunate for the independent merge of driver bits. Either way, I
Kconfig dependencies take care of that pretty well - if there's a
dependency on the MFD then the function driver just won't get built
until the MFD gets merged.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-10-15 16:55 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-08 13:25 [PATCH v2 1/5] mfd: lochnagar: Add initial binding documentation Charles Keepax
2018-10-08 13:25 ` [PATCH v2 2/5] mfd: lochnagar: Add support for the Cirrus Logic Lochnagar Charles Keepax
2018-10-25 7:44 ` Lee Jones
2018-10-25 8:26 ` Charles Keepax
2018-10-25 9:28 ` Richard Fitzgerald
2018-10-25 10:12 ` Mark Brown
2018-10-25 10:56 ` Charles Keepax
2018-10-25 11:42 ` Lee Jones
2018-10-25 12:49 ` Charles Keepax
2018-10-25 13:20 ` Charles Keepax
2018-10-25 13:47 ` Richard Fitzgerald
2018-10-26 15:49 ` Mark Brown
2018-10-26 7:33 ` Lee Jones
2018-10-26 15:47 ` Mark Brown
2018-10-25 13:40 ` Richard Fitzgerald
2018-10-26 8:00 ` Lee Jones
2018-10-26 20:32 ` Mark Brown
2018-10-29 11:04 ` Lee Jones
2018-10-29 11:52 ` Richard Fitzgerald
2018-10-29 12:36 ` Richard Fitzgerald
2018-10-29 12:57 ` Mark Brown
2018-11-01 10:28 ` Charles Keepax
2018-11-01 11:40 ` Richard Fitzgerald
2018-11-01 12:04 ` Mark Brown
2018-11-01 12:01 ` Mark Brown
2018-11-01 14:17 ` Richard Fitzgerald
2018-10-08 13:25 ` [PATCH v2 3/5] clk: " Charles Keepax
2018-10-11 7:00 ` Stephen Boyd
2018-10-11 13:26 ` Charles Keepax
2018-10-12 15:59 ` Stephen Boyd
2018-10-15 10:49 ` Charles Keepax
2018-10-15 16:39 ` Stephen Boyd
2018-10-15 16:55 ` Mark Brown [this message]
2018-10-15 21:53 ` Stephen Boyd
2018-10-11 14:54 ` Mark Brown
2018-10-11 19:36 ` Stephen Boyd
2018-10-12 16:52 ` Mark Brown
2018-10-08 13:25 ` [PATCH v2 4/5] regulator: " Charles Keepax
2018-10-08 13:25 ` [PATCH v2 5/5] pinctrl: " Charles Keepax
2018-10-12 22:08 ` [PATCH v2 1/5] mfd: lochnagar: Add initial binding documentation Rob Herring
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=20181015165528.GD12949@sirena.org.uk \
--to=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--cc=devicetree@vger.kernel.org \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mturquette@baylibre.com \
--cc=patches@opensource.cirrus.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@kernel.org \
/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).