From: Mark Brown <broonie@kernel.org>
To: Nariman Poushin <nariman@opensource.wolfsonmicro.com>
Cc: oder_chiou@realtek.com, brian.austin@cirrus.com,
laurent.pinchart+renesas@ideasonboard.com, sameo@linux.intel.com,
support.opensource@diasemi.com, airlied@linux.ie,
gregkh@linuxfoundation.org, dmitry.torokhov@gmail.com,
alsa-devel@alsa-project.org, dri-devel@lists.freedesktop.org,
lgirdwood@gmail.com, peter.ujfalusi@ti.com, tony@atomide.com,
lars@metafoo.de, Paul.Handrigan@cirrus.com,
patches@opensource.wolfsonmicro.com, bardliao@realtek.com,
linux-omap@vger.kernel.org, lee.jones@linaro.org,
linux-kernel@vger.kernel.org, dmurphy@ti.com
Subject: Re: [PATCH 1/2] V4 regmap: Use reg_sequence for multi_reg_write / register_patch
Date: Thu, 16 Jul 2015 21:48:08 +0100 [thread overview]
Message-ID: <20150716204808.GB1602@sirena.org.uk> (raw)
In-Reply-To: <20150716154525.GB21939@opensource.wolfsonmicro.com>
[-- Attachment #1.1: Type: text/plain, Size: 305 bytes --]
On Thu, Jul 16, 2015 at 04:45:25PM +0100, Nariman Poushin wrote:
> I will resend with a cover letter explaining the change from the previous
> patch set if that is the right thing to do.
No, that's fine. If you want to fix something like that just reply to
the cover letter with the extra information.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2015-07-16 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 14:45 [PATCH 1/2] V4 regmap: Use reg_sequence for multi_reg_write / register_patch Nariman Poushin
2015-07-14 14:45 ` [PATCH 2/2] V4 regmap: Apply optional delay in multi_reg_write/register_patch Nariman Poushin
2015-07-16 13:12 ` [alsa-devel] " Takashi Iwai
2015-07-16 12:52 ` [PATCH 1/2] V4 regmap: Use reg_sequence for multi_reg_write / register_patch Mark Brown
2015-07-16 15:45 ` [alsa-devel] " Nariman Poushin
2015-07-16 20:48 ` Mark Brown [this message]
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=20150716204808.GB1602@sirena.org.uk \
--to=broonie@kernel.org \
--cc=Paul.Handrigan@cirrus.com \
--cc=airlied@linux.ie \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=brian.austin@cirrus.com \
--cc=dmitry.torokhov@gmail.com \
--cc=dmurphy@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=lars@metafoo.de \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=lee.jones@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=nariman@opensource.wolfsonmicro.com \
--cc=oder_chiou@realtek.com \
--cc=patches@opensource.wolfsonmicro.com \
--cc=peter.ujfalusi@ti.com \
--cc=sameo@linux.intel.com \
--cc=support.opensource@diasemi.com \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).