From: Mark Brown <broonie@kernel•org>
To: Charles Keepax <ckeepax@opensource•wolfsonmicro.com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Nariman Poushin <nariman@opensource•wolfsonmicro.com>,
Lee Jones <lee.jones@linaro•org>,
Liam Girdwood <lgirdwood@gmail•com>,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
Richard Fitzgerald <rf@opensource•wolfsonmicro.com>
Subject: Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch
Date: Fri, 18 Sep 2015 11:25:24 +0100 [thread overview]
Message-ID: <20150918102524.GH12027@sirena.org.uk> (raw)
In-Reply-To: <20150918083336.GE7694@ck-lbox>
[-- Attachment #1: Type: text/plain, Size: 870 bytes --]
On Fri, Sep 18, 2015 at 09:33:36AM +0100, Charles Keepax wrote:
> On Fri, Sep 18, 2015 at 01:50:15PM +1000, Stephen Rothwell wrote:
> > It looks like that patch has been forgotten as I am still applying it
> > to the linux-next tree every day ...
> Apologies if I am a little out of my depth here, but are we in
> the situation where you are expecting this to go through the MFD
> tree and Lee is expecting it to go through your tree?
No, -next is a merge down of trees that will be sent to Linus rather
than a tree that is sent to Linus itself.
> Assuming this is the case, Lee could you perhaps pull this fix in
> fairly soon? As it is causing build warning for some configs, in
> Linus's tree at the moment. I am quite happy to resend it on
> Nariman's behalf if required (he is on holiday at the moment).
I'd recommend resending to make sure Lee has the patch.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-09-18 10:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-17 4:39 linux-next: build warnings after merge of the regmap tree Stephen Rothwell
2015-07-17 9:44 ` Nariman Poushin
2015-07-17 10:34 ` Mark Brown
2015-07-17 14:09 ` [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch Nariman Poushin
2015-07-17 17:57 ` Mark Brown
2015-07-20 1:59 ` Stephen Rothwell
2015-09-05 14:08 ` Geert Uytterhoeven
2015-09-18 3:50 ` Stephen Rothwell
2015-09-18 8:33 ` Charles Keepax
2015-09-18 10:25 ` Mark Brown [this message]
2015-07-17 14:11 ` [PATCH 2/2] ASoC: wm5110: Use reg_sequence for multi_reg_write/register_patch Nariman Poushin
2015-07-17 15:29 ` linux-next: build warnings after merge of the regmap tree Nariman Poushin
2015-07-17 16:45 ` Charles Keepax
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=20150918102524.GH12027@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=ckeepax@opensource$(echo .)wolfsonmicro.com \
--cc=lee.jones@linaro$(echo .)org \
--cc=lgirdwood@gmail$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=nariman@opensource$(echo .)wolfsonmicro.com \
--cc=rf@opensource$(echo .)wolfsonmicro.com \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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