public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tomasz.figa@gmail.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: "'Doug Anderson'" <dianders@chromium.org>,
	"'Stephen Rothwell'" <sfr@canb.auug.org.au>,
	"'linux-samsung-soc'" <linux-samsung-soc@vger.kernel.org>,
	"'Linus Walleij'" <linus.walleij@linaro.org>,
	"'Olof Johansson'" <olof@lixom.net>,
	"'Mauro Carvalho Chehab'" <mchehab@redhat.com>,
	"'Andrew Morton'" <akpm@linux-foundation.org>,
	"'Cesar Eduardo Barros'" <cesarb@cesarb.net>,
	"'David S. Miller'" <davem@davemloft.net>,
	"'Hans Verkuil'" <hans.verkuil@cisco.com>,
	linux-kernel@vger.kernel.org,
	"'Thomas Abraham'" <thomas.abraham@linaro.org>
Subject: Re: [PATCH] MAINTAINERS: Add Samsung pinctrl entries
Date: Fri, 14 Jun 2013 00:32:23 +0200	[thread overview]
Message-ID: <26381641.c4KnMQ8aS6@flatron> (raw)
In-Reply-To: <15cf01ce6884$8c073f20$a415bd60$%kim@samsung.com>

On Friday 14 of June 2013 07:22:53 Kukjin Kim wrote:
> Tomasz Figa wrote:
> > On Thursday 13 of June 2013 10:25:02 Doug Anderson wrote:
> > > Tomasz,
> > > 
> > > On Thu, Jun 13, 2013 at 10:13 AM, Tomasz Figa
> > > <tomasz.figa@gmail.com>
> > 
> > wrote:
> > > > On Thursday 13 of June 2013 10:05:44 Doug Anderson wrote:
> > > >> It's convenient if get_maintainer suggests sending samsung/exynos
> > > >> pinctrl changes to linux-samsung-soc and to Kukjin.  Add an entry
> > > >> for
> > > >> that.
> > > > 
> > > > Well, if we are already at it, we could list the actual
> > > > maintainers of
> > > > the driver.
> > > > 
> > > > The original maintainer was Thomas Abraham
> > > > <thomas.abraham@linaro.org>
> > > > (added to CC) and after joining to development of this driver last
> > > > year I have become a de facto maintainer as well, so...
> > > > 
> > > >> Signed-off-by: Doug Anderson <dianders@chromium.org>
> > > >> ---
> > > >> 
> > > >>  MAINTAINERS | 10 ++++++++++
> > > >>  1 file changed, 10 insertions(+)
> > > >> 
> > > >> diff --git a/MAINTAINERS b/MAINTAINERS
> > > >> index 8d97b3e..d026e38 100644
> > > >> --- a/MAINTAINERS
> > > >> +++ b/MAINTAINERS
> > > >> @@ -6284,6 +6284,16 @@ L:    
> > > >> linux-arm-kernel@lists.infradead.org
> > > >> (moderated for non-subscribers) S:    Maintained
> > > >> 
> > > >>  F:   drivers/pinctrl/pinctrl-at91.c
> > > >> 
> > > >> +PIN CONTROLLER - SAMSUNG
> > > >> +M:   Linus Walleij <linus.walleij@linaro.org>
> > > >> +M:   Kukjin Kim <kgene.kim@samsung.com>
> > > > 
> > > > So actually this would be:
> > > > M:      Thomas Abraham <thomas.abraham@linaro.org>
> > > > M:      Tomasz Figa <t.figa@samsung.com>
> > > > 
> > > > Thomas, do you agree on this?
> > > 
> > > Ah.  Wasn't sure where the official maintainership should lie.  ;) 
> > > If
> > > Thomas is happy with this then I'll spin and re-send.  Shall I
> > > remove
> > > Kukjin and Linus, then?  It's convenient to have Linus on the list
> > > since he tends to be the one applying the patches...
> > 
> > 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.

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

> > DRM DRIVERS FOR EXYNOS
> > M:      Inki Dae <inki.dae@samsung.com>
> > M:      Joonyoung Shim <jy0922.shim@samsung.com>
> > M:      Seung-Woo Kim <sw0312.kim@samsung.com>
> > M:      Kyungmin Park <kyungmin.park@samsung.com>
> > L:      dri-devel@lists.freedesktop.org
> > T:      git git://git.kernel.org/pub/scm/linux/kernel/git/daeinki/drm-
> > exynos.git
> > S:      Supported
> > F:      drivers/gpu/drm/exynos
> > F:      include/drm/exynos*
> > F:      include/uapi/drm/exynos*
> > 
> > EXYNOS DP DRIVER
> > M:      Jingoo Han <jg1.han@samsung.com>
> > L:      linux-fbdev@vger.kernel.org
> > S:      Maintained
> > F:      drivers/video/exynos/exynos_dp*
> > F:      include/video/exynos_dp*
> > 
> > EXYNOS MIPI DISPLAY DRIVERS
> > M:      Inki Dae <inki.dae@samsung.com>
> > M:      Donghwa Lee <dh09.lee@samsung.com>
> > M:      Kyungmin Park <kyungmin.park@samsung.com>
> > L:      linux-fbdev@vger.kernel.org
> > S:      Maintained
> > F:      drivers/video/exynos/exynos_mipi*
> > F:      include/video/exynos_mipi*
> > 
> > ARM/SAMSUNG S5P SERIES 2D GRAPHICS ACCELERATION (G2D) SUPPORT
> > M:      Kyungmin Park <kyungmin.park@samsung.com>
> > M:      Kamil Debski <k.debski@samsung.com>
> > L:      linux-arm-kernel@lists.infradead.org
> > L:      linux-media@vger.kernel.org
> > S:      Maintained
> > F:      drivers/media/platform/s5p-g2d/
> 
> 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.

Best regards,
Tomasz

> > and so on.
> > 
> > So I think, based on this precedent, we can do the same for pinctrl.
> > Let's wait to see Thomas' view on this.

  reply	other threads:[~2013-06-13 22:32 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-13 17:05 [PATCH] MAINTAINERS: Add Samsung pinctrl entries Doug Anderson
2013-06-13 17:13 ` Tomasz Figa
2013-06-13 17:25   ` Doug Anderson
2013-06-13 17:32     ` Tomasz Figa
2013-06-13 17:46       ` Joe Perches
2013-06-13 22:22       ` Kukjin Kim
2013-06-13 22:32         ` Tomasz Figa [this message]
2013-06-13 22:59           ` Kukjin Kim
2013-06-13 23:02           ` Kukjin Kim
2013-06-13 22:49         ` Tomasz Figa
2013-06-13 23:09           ` Tomasz Figa
2013-06-13 18:25     ` Linus Walleij
2013-06-13 22:47   ` Kukjin Kim
2013-06-13 23:03     ` Tomasz Figa
2013-06-16 12:47       ` Linus Walleij
2013-06-16 22:17 ` [PATCH v2 1/2] " Doug Anderson
2013-06-16 22:17   ` [PATCH v2 2/2] MAINTAINERS: Add exynos filename match to ARM/S5P EXYNOS ARM ARCHITECTURES Doug Anderson
2013-06-17 15:37     ` Kukjin Kim
2013-06-17 15:48       ` Doug Anderson
2013-06-17 15:55         ` Kukjin Kim
2013-06-17  3:35   ` [PATCH v2 1/2] MAINTAINERS: Add Samsung pinctrl entries Kyungmin Park
2013-06-17  3:43     ` Olof Johansson
2013-06-17 15:37       ` Kukjin Kim
2013-06-17 15:50         ` Doug Anderson
2013-06-17 16:35   ` Linus Walleij

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=26381641.c4KnMQ8aS6@flatron \
    --to=tomasz.figa@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=cesarb@cesarb.net \
    --cc=davem@davemloft.net \
    --cc=dianders@chromium.org \
    --cc=hans.verkuil@cisco.com \
    --cc=kgene.kim@samsung.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --cc=mchehab@redhat.com \
    --cc=olof@lixom.net \
    --cc=sfr@canb.auug.org.au \
    --cc=thomas.abraham@linaro.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