linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: anish <yesanishhere@gmail.com>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
	Anish Kumar <yesanishhere@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: Add maintainer for maxim codecs
Date: Mon, 23 Mar 2015 17:04:26 -0700	[thread overview]
Message-ID: <CABCoZhD+pMPM3yazjh8R3s+8m1Sq7q3B81TBY0NKxJvgKBf4mw@mail.gmail.com> (raw)
In-Reply-To: <1425338170-30924-1-git-send-email-yesanishhere@gmail.com>

Hello,

I was wondering if this patch is in any of the queue?

On Mon, Mar 2, 2015 at 3:16 PM, Anish Kumar <yesanishhere@gmail.com> wrote:
> This patch adds maintainer for maxim audio codecs.
> Signed-off-by: Anish Kumar <yesanishhere@gmail.com>
> ---
>  MAINTAINERS | 7 +++++++
>  1 file changed, 7 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8bdd7a7..2128586 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -7387,6 +7387,13 @@ S:       Supported
>  F:     sound/soc/
>  F:     include/sound/soc*
>
> +MAXIM INTEGRATED SOC CODEC DRIVER
> +M:     Anish Kumar <yesanishhere@gmail.com>
> +L:     alsa-devel@alsa-project.org (moderated for non-subscribers)
> +S:     Maintained
> +F:     sound/soc/codecs/max*
> +F:     include/sound/max*
> +
>  SPARC + UltraSPARC (sparc/sparc64)
>  M:     "David S. Miller" <davem@davemloft.net>
>  L:     sparclinux@vger.kernel.org
> --
> 1.9.3
>

  parent reply	other threads:[~2015-03-24  0:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 23:16 [PATCH] MAINTAINERS: Add maintainer for maxim codecs Anish Kumar
2015-03-12 23:35 ` anish
2015-03-24  0:04 ` anish [this message]
2015-03-24  6:32   ` [alsa-devel] " Takashi Iwai
2015-03-24  6:39     ` anish
2015-03-24  7:07       ` Takashi Iwai

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=CABCoZhD+pMPM3yazjh8R3s+8m1Sq7q3B81TBY0NKxJvgKBf4mw@mail.gmail.com \
    --to=yesanishhere@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.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 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).