All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: Timur Tabi <timur@tabi.org>, Mark Brown <broonie@kernel.org>
Cc: Brian Austin <brian.austin@cirrus.com>,
	linaro-kernel@lists.linaro.org,
	alsa-devel mailing list <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@linaro.org>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Paul Handrigan <Paul.Handrigan@cirrus.com>
Subject: Re: [PATCH] MAINTAINERS: Add entry for Cirrus CODEC drivers
Date: Thu, 13 Feb 2014 11:25:20 +0100	[thread overview]
Message-ID: <52FC9D90.4060305@zonque.org> (raw)
In-Reply-To: <CAOZdJXUtv_rB2rn+s18mLw6p8TkjDQMnFN03=RL24phWcneKeQ@mail.gmail.com>

On 02/11/2014 05:45 AM, Timur Tabi wrote:
> On Tue, Feb 4, 2014 at 2:30 PM, Mark Brown <broonie@kernel.org> wrote:
>> From: Mark Brown <broonie@linaro.org>
>>
>> I noticed that some recent patches hadn't been CCed to the Cirrus people
>> - add an entry in MAINTAINERS to help make that happen.
>>
>> Signed-off-by: Mark Brown <broonie@linaro.org>
>> ---
>>
>> Brian, Paul - are you OK with this?
> 
> Go ahead and remove me as maintainer of the CS4270 driver, if you guys
> want.  I don't have access to that hardware any more, and so I really
> can't maintain it.

I do have hardware, but it will take me some time to test more intrusive
patches. If nobody else volunteers, I'd take it.


Thanks,
Daniel

  reply	other threads:[~2014-02-13 10:25 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-04 20:30 [PATCH] MAINTAINERS: Add entry for Cirrus CODEC drivers Mark Brown
2014-02-04 20:41 ` Austin, Brian
2014-02-04 21:18 ` Handrigan, Paul
2014-02-11  4:45 ` Timur Tabi
2014-02-13 10:25   ` Daniel Mack [this message]
2014-02-13 14:30     ` Handrigan, Paul
2014-02-13 16:01       ` Mark Brown
2014-02-13 16:15         ` Timur Tabi
2014-02-13 18:09           ` Mark Brown
2014-02-14  1:08             ` Daniel Mack

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=52FC9D90.4060305@zonque.org \
    --to=daniel@zonque.org \
    --cc=Paul.Handrigan@cirrus.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=brian.austin@cirrus.com \
    --cc=broonie@kernel.org \
    --cc=broonie@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linaro-kernel@lists.linaro.org \
    --cc=timur@tabi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.