linux-kernel - Re: [alsa-devel] [PATCH] MAINTAINERS: Add maintainer for maxim codecs

Open Source and information security mailing list archives

Date:	Tue, 24 Mar 2015 08:07:25 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	anish <yesanishhere@...il.com>
Cc:	linux-kernel@...r.kernel.org, akpm@...ux-foundation.org,
	gregkh@...uxfoundation.org,
	Linux-ALSA <alsa-devel@...a-project.org>
Subject: Re: [alsa-devel] [PATCH] MAINTAINERS: Add maintainer for maxim codecs

At Mon, 23 Mar 2015 23:39:28 -0700,
anish wrote:
> 
> On Mon, Mar 23, 2015 at 11:32 PM, Takashi Iwai <tiwai@...e.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@...il.com> wrote:
> >> > This patch adds maintainer for maxim audio codecs.
> >> > Signed-off-by: Anish Kumar <yesanishhere@...il.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@...il.com>
> >> > +L:     alsa-devel@...a-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@...emloft.net>
> >> >  L:     sparclinux@...r.kernel.org
> >> > --
> >> > 1.9.3
> >> >
> >> _______________________________________________
> >> Alsa-devel mailing list
> >> Alsa-devel@...a-project.org
> >> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
> >>
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives