From: Mark Brown <broonie@kernel•org>
To: Nariman Poushin <nariman@opensource•wolfsonmicro.com>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
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: Fri, 17 Jul 2015 18:57:04 +0100 [thread overview]
Message-ID: <20150717175704.GR11162@sirena.org.uk> (raw)
In-Reply-To: <20150717140926.GG21939@opensource.wolfsonmicro.com>
[-- Attachment #1: Type: text/plain, Size: 2430 bytes --]
On Fri, Jul 17, 2015 at 03:09:26PM +0100, Nariman Poushin wrote:
> Introduced by:
> commit 8019ff6cfc04
> ("regmap: Use reg_sequence for multi_reg_write / register_patch")
Lee, feel free to pull the request below in to get the API update or let
me know if you want me to merge some MFD changes instead:
The following changes since commit d770e558e21961ad6cfdf0ff7df0eb5d7d4f0754:
Linux 4.2-rc1 (2015-07-05 11:01:52 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-seq-delay-api
for you to fetch changes up to 8019ff6cfc0440415fcfb6352c58c3951e6ab053:
regmap: Use reg_sequence for multi_reg_write / register_patch (2015-07-16 22:02:55 +0100)
----------------------------------------------------------------
regmap: Create a new struct reg_sequence for register sequences
In order to allow us to start adding extra annotations for sequences
without bloating register default tables duplicate the structure under
the new name reg_sequence and update the APIs to use that instead of
reg_default.
----------------------------------------------------------------
Nariman Poushin (1):
regmap: Use reg_sequence for multi_reg_write / register_patch
drivers/base/regmap/internal.h | 2 +-
drivers/base/regmap/regmap.c | 22 +++++++++++-----------
drivers/gpu/drm/i2c/adv7511.c | 2 +-
drivers/input/misc/drv260x.c | 6 +++---
drivers/input/misc/drv2665.c | 2 +-
drivers/input/misc/drv2667.c | 4 ++--
drivers/mfd/arizona-core.c | 2 +-
drivers/mfd/twl6040.c | 2 +-
drivers/mfd/wm5102-tables.c | 6 +++---
drivers/mfd/wm5110-tables.c | 6 +++---
drivers/mfd/wm8994-core.c | 8 ++++----
drivers/mfd/wm8997-tables.c | 2 +-
include/linux/regmap.h | 17 ++++++++++++++---
sound/soc/codecs/arizona.c | 2 +-
sound/soc/codecs/cs35l32.c | 2 +-
sound/soc/codecs/cs42l52.c | 2 +-
sound/soc/codecs/da7210.c | 4 ++--
sound/soc/codecs/rt5640.c | 2 +-
sound/soc/codecs/rt5645.c | 4 ++--
sound/soc/codecs/rt5651.c | 2 +-
sound/soc/codecs/rt5670.c | 2 +-
sound/soc/codecs/rt5677.c | 2 +-
sound/soc/codecs/tlv320aic3x.c | 2 +-
sound/soc/codecs/wm2200.c | 2 +-
sound/soc/codecs/wm5100.c | 2 +-
sound/soc/codecs/wm8962.c | 2 +-
sound/soc/codecs/wm8993.c | 2 +-
27 files changed, 62 insertions(+), 51 deletions(-)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-07-17 17:57 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 [this message]
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
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=20150717175704.GR11162@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