mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: anish <yesanishhere@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	gregkh@linuxfoundation.org,
	Linux-ALSA <alsa-devel@alsa-project.org>
Subject: Re: [alsa-devel] [PATCH] MAINTAINERS: Add maintainer for maxim codecs
Date: Tue, 24 Mar 2015 08:07:25 +0100	[thread overview]
Message-ID: <s5h4mpalvpu.wl-tiwai@suse.de> (raw)
In-Reply-To: <CABCoZhAKWL-qm2PMNNZx49HiBn_BO4Pb568n5H4goOfA0uN3CQ@mail.gmail.com>

At Mon, 23 Mar 2015 23:39:28 -0700,
anish wrote:
> 
> On Mon, Mar 23, 2015 at 11:32 PM, Takashi Iwai <tiwai@suse.de> wrote:
> > At Mon, 23 Mar 2015 17:04:26 -0700,
> > anish wrote:
> >>
> >> Hello,
> >>
> >> I was wondering if this patch is in any of the queue?
> >
> > I guess it's not.  One of the reasons is that you don't know whom to
> > reach; it's a problem as a subsystem maintainer.
> >
> > Also, you never seem to appear in the commit history of these codes.
> > Have you been involved with the development?  If so, it'd be better to
> > have Acks from people who actually wrote/committed the codes of these
> > codec drivers.
> 
> The reason for this change is that we want to monitor the codec drivers
> related to maxim chip as we saw couple of changes which shouldn't have
> been taken and since we were not involved when the review was being
> done we couldn't contribute our opinion.
> 
> What is the best way to go about this? We have given maxim driver
> code to our various clients and some of the clients contributed the
> code to linux kernel. I will try to get acks from them anyway.

How about start contributing by sending fix patches in a proper
manner, if anything should be fixed?  The maintainership is given
mostly per trust in open source world.  Sending patches and
communicating with other community members are the best way to gain a
trust in Linux kernel development.


thanks,

Takashi

> 
> Thanks,
> >
> >
> > thanks,
> >
> > Takashi
> >
> >>
> >> 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
> >> >
> >> _______________________________________________
> >> Alsa-devel mailing list
> >> Alsa-devel@alsa-project.org
> >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >>
> 

      reply	other threads:[~2015-03-24  7:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 23:16 Anish Kumar
2015-03-12 23:35 ` anish
2015-03-24  0:04 ` anish
2015-03-24  6:32   ` [alsa-devel] " Takashi Iwai
2015-03-24  6:39     ` anish
2015-03-24  7:07       ` Takashi Iwai [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=s5h4mpalvpu.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yesanishhere@gmail.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

all inboxes | Powered by JetHome®