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
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Fri, 14 Jun 2013 07:59:24 +0900
From:	Kukjin Kim <kgene.kim@...sung.com>
To:	'Tomasz Figa' <tomasz.figa@...il.com>
Cc:	'Doug Anderson' <dianders@...omium.org>,
	'Stephen Rothwell' <sfr@...b.auug.org.au>,
	'linux-samsung-soc' <linux-samsung-soc@...r.kernel.org>,
	'Linus Walleij' <linus.walleij@...aro.org>,
	'Olof Johansson' <olof@...om.net>,
	'Mauro Carvalho Chehab' <mchehab@...hat.com>,
	'Andrew Morton' <akpm@...ux-foundation.org>,
	'Cesar Eduardo Barros' <cesarb@...arb.net>,
	"'David S. Miller'" <davem@...emloft.net>,
	'Hans Verkuil' <hans.verkuil@...co.com>,
	linux-kernel@...r.kernel.org,
	'Thomas Abraham' <thomas.abraham@...aro.org>
Subject: RE: [PATCH] MAINTAINERS: Add Samsung pinctrl entries

Tomasz Figa wrote:
> 

[...]

> > > From my understanding how it works, there is no need to list Linus in
> > > particular drivers, because he's already listed as a maintainer of the
> > > whole pinctrl subsystem and get-maintainer accounts for this.
> > >
> > > Similarly for Kukjin, he's listed as the main Samsung maintainer
> > > already,
> > If so, the directory like pinctrl should be added under Samsung ARM
> > Architectures like spi and sound for Samsung stuff...
> 
> I don't think so, because it's a part of the pin control subsystem.
> 
Yes right. I mean, pinctrl is clos

> > > but AFAIK in this case the script can't infer this based on directory
> >
> > > structure. Let's see how it's done for other Samsung drivers:
> > Well, I don't think so, because pinctrl has the close relationship with
> > exynos arch part and it's little bit different with following. Just in
> > my understanding.
> 
> I'm not really sure what you mean. Pin control is a separate kernel
> subsystem, which shouldn't have any dependencies on arch code.
> 
Yes, right. I have no objection about it is a subsystem. I meant just
relationship and it helps people find the overall architecture.

[...]

> > And I'm asking above all guys _really_ do review and maintaining the
> > file or directories? I don't think so.
> 
> I'm not really sure what makes you think they don't. I can see all of them
> involved in works on mentioned drivers.
> 
What's the role of maintainer? I mean, as you said, above guys are really do
it...

- Kukjin

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ