From: Mark Brown <broonie@kernel.org>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
Cc: Linux-Kernel <linux-kernel@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
shiiba <naoya.shiiba.nx@renesas.com>
Subject: Re: [PATCH 0/4][RFC] regmap: add force write option
Date: Fri, 3 Jul 2015 13:48:44 +0100 [thread overview]
Message-ID: <20150703124844.GB1472@sirena.org.uk> (raw)
In-Reply-To: <87y4izkpkv.wl%kuninori.morimoto.gx@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 192 bytes --]
On Thu, Jul 02, 2015 at 07:07:15AM +0000, Kuninori Morimoto wrote:
> Can I have some feedback about these patches ?
Please do allow some time for review, especially during the merge
window.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-07-03 12:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-16 8:51 Kuninori Morimoto
2015-06-16 8:52 ` [PATCH 1/4][RFC] regmap: add force_write option on _regmap_update_bits() Kuninori Morimoto
2015-07-10 10:40 ` Applied "regmap: add force_write option on _regmap_update_bits()" to the regmap tree Mark Brown
2015-06-16 8:52 ` [PATCH 2/4][RFC] regmap: add regmap_write_bits() Kuninori Morimoto
2015-07-10 10:40 ` Applied "regmap: add regmap_write_bits()" to the regmap tree Mark Brown
2015-06-16 8:52 ` [PATCH 3/4][RFC] regmap: add regmap_fields_force_write() Kuninori Morimoto
2015-07-10 10:40 ` Applied "regmap: add regmap_fields_force_write()" to the regmap tree Mark Brown
2015-06-16 8:53 ` [PATCH 4/4][RFC] ASoC: rsnd: gen: add rsnd_force_write() Kuninori Morimoto
2015-07-02 7:07 ` [PATCH 0/4][RFC] regmap: add force write option Kuninori Morimoto
2015-07-03 12:48 ` Mark Brown [this message]
2015-07-08 0:52 ` Kuninori Morimoto
2015-07-02 7:46 ` Lars-Peter Clausen
2015-07-02 8:58 ` Kuninori Morimoto
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=20150703124844.GB1472@sirena.org.uk \
--to=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=naoya.shiiba.nx@renesas.com \
/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®