From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@mail.com>,
patches@opensource.wolfsonmicro.com, linux-input@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Remove wm97xx entry
Date: Sun, 4 Oct 2015 13:50:41 +0100 [thread overview]
Message-ID: <20151004125041.GA21528@ck-lbox> (raw)
In-Reply-To: <1443805758-27153-1-git-send-email-broonie@kernel.org>
On Fri, Oct 02, 2015 at 06:09:18PM +0100, Mark Brown wrote:
> Neither myself or Liam is especially interested in this driver any more
> and the devices are already covered by the general ex-Wolfson entry so
> just remove this.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Acked-by: Liam Girdwood <liam.r.girdwood@linux.intel.com>
> ---
Acked-by: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Thanks,
Charles
prev parent reply other threads:[~2015-10-04 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 17:09 [PATCH] MAINTAINERS: Remove wm97xx entry Mark Brown
2015-10-04 12:50 ` Charles Keepax [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=20151004125041.GA21528@ck-lbox \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@mail.com \
--cc=linux-input@vger.kernel.org \
--cc=patches@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).