From: "Andreas Färber" <afaerber@suse.de>
To: Mark Brown <broonie@kernel.org>, Ben Whitten <ben.whitten@gmail.com>
Cc: Ben Whitten <ben.whitten@lairdtech.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 RESEND] regmap: Add regmap_noinc_write API
Date: Fri, 19 Oct 2018 13:59:07 +0200 [thread overview]
Message-ID: <6dc0a6f0-7bb9-4ad0-73ef-f3527da6894e@suse.de> (raw)
In-Reply-To: <20181019115652.GD5895@sirena.org.uk>
Am 19.10.18 um 13:56 schrieb Mark Brown:
> On Fri, Oct 19, 2018 at 10:33:50AM +0100, Ben Whitten wrote:
>> The regmap API had a noinc_read function added for instances where devices
>> supported returning data from an internal FIFO in a single read.
>
> The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
>
> Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
>
> are available in the Git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-noinc-write
>
> for you to fetch changes up to cdf6b11daa77d4b55ddf0530842a551cc5562a93:
>
> regmap: Add regmap_noinc_write API (2018-10-19 12:51:19 +0100)
You two forgot my Reviewed-by... oh well.
Thanks anyway,
Andreas
>
> ----------------------------------------------------------------
> regmap: Add noinc write support
>
> Mirroring the read support
>
> ----------------------------------------------------------------
> Ben Whitten (1):
> regmap: Add regmap_noinc_write API
>
> drivers/base/regmap/internal.h | 3 ++
> drivers/base/regmap/regmap.c | 77 ++++++++++++++++++++++++++++++++++++++++++
> include/linux/regmap.h | 19 +++++++++++
> 3 files changed, 99 insertions(+)
>
--
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
next prev parent reply other threads:[~2018-10-19 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 9:33 Ben Whitten
2018-10-19 11:56 ` Mark Brown
2018-10-19 11:59 ` Andreas Färber [this message]
2018-10-19 12:02 ` Mark Brown
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=6dc0a6f0-7bb9-4ad0-73ef-f3527da6894e@suse.de \
--to=afaerber@suse.de \
--cc=ben.whitten@gmail.com \
--cc=ben.whitten@lairdtech.com \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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
all inboxes | Powered by JetHome®