From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Nariman Poushin <nariman@opensource•wolfsonmicro.com>
Cc: Mark Brown <broonie@kernel•org>, 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>,
Charles Keepax <ckeepax@opensource•wolfsonmicro.com>
Subject: Re: [PATCH 1/2] mfd: Fixup clients of multi_reg_write/register_patch
Date: Mon, 20 Jul 2015 11:59:35 +1000 [thread overview]
Message-ID: <20150720115935.686b556e@canb.auug.org.au> (raw)
In-Reply-To: <20150717140926.GG21939@opensource.wolfsonmicro.com>
Hi Nariman,
On Fri, 17 Jul 2015 15:09:26 +0100 Nariman Poushin <nariman@opensource•wolfsonmicro.com> wrote:
>
> Introduced by:
> commit 8019ff6cfc04
> ("regmap: Use reg_sequence for multi_reg_write / register_patch")
>
> Interacting with:
> commit 561629755a21 ("mfd: arizona: Add support for WM8998 and WM1814")
> commit 81207880cef2 ("mfd: wm5110: Add register patch for rev E and above")
>
> Signed-off-by: Nariman Poushin <nariman@opensource•wolfsonmicro.com>
> ---
> drivers/mfd/wm5110-tables.c | 2 +-
> drivers/mfd/wm8998-tables.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
I will apply both these patches as merge fix patches in linux-next
today. Thanks.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
next prev parent reply other threads:[~2015-07-20 1:59 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 [this message]
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
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=20150720115935.686b556e@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=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 \
/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