From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>,
<lgirdwood@gmail.com>, <patches@opensource.wolfsonmicro.com>,
<alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] regulator: arizona: add support for WM8998 and WM1814
Date: Thu, 1 Oct 2015 08:51:02 +0100 [thread overview]
Message-ID: <20151001075102.GL5432@ck-lbox> (raw)
In-Reply-To: <20150930181601.GS15635@sirena.org.uk>
On Wed, Sep 30, 2015 at 07:16:01PM +0100, Mark Brown wrote:
> On Mon, Sep 28, 2015 at 02:01:07PM +0100, Richard Fitzgerald wrote:
> > Signed-off-by: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
> > Acked-by: Mark Brown <broonie@kernel.org>
>
> So if I've acked this rather than applying it presumably there are MFD
> dependencies somewhere we're waiting for? If there aren't why did this
> not go in with the MFD?
>
> Please don't resend me my own ack on code that it looks like I'm
> expected to apply, it's confusing :(
Afraid Richard is on holiday at the moment, apologies for any
confusion. The MFD changes went in ages ago, but the other
changes in the series weren't applied, I am can't remember
exactly why. So all the supporting MFD stuff is already in
your trees and you can safely apply these ones.
Thanks,
Charles
next prev parent reply other threads:[~2015-10-01 8:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 13:01 [PATCH v2 0/3] Add support for Wolfson Micro WM8998 codec Richard Fitzgerald
2015-09-28 13:01 ` [PATCH v2 1/3] regulator: arizona: add support for WM8998 and WM1814 Richard Fitzgerald
2015-09-30 18:16 ` Mark Brown
2015-10-01 7:51 ` Charles Keepax [this message]
2015-09-28 13:01 ` [PATCH v2 2/3] ASoC: arizona: add defines for single-input gain control Richard Fitzgerald
2015-09-28 13:01 ` [PATCH v2 3/3] ASoC: wm8998: Initial WM8998 codec driver Richard Fitzgerald
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=20151001075102.GL5432@ck-lbox \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=rf@opensource.wolfsonmicro.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).