From: Shawn Guo <shawnguo@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Martin Kepplinger <martin.kepplinger@puri.sm>,
robh@kernel.org, kernel@puri.sm, s.hauer@pengutronix.de,
kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com,
mchehab@kernel.org, Anson.Huang@nxp.com, agx@sigxcpu.org,
angus@akkea.ca, broonie@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 2/3] MAINTAINERS: Add Purism Librem 5 section to the list
Date: Mon, 31 Aug 2020 09:19:07 +0800 [thread overview]
Message-ID: <20200831011906.GB4488@dragon> (raw)
In-Reply-To: <1d7c6ef2794bedca7e3164e5435f46864eacddfa.camel@perches.com>
On Sun, Aug 30, 2020 at 08:32:01AM -0700, Joe Perches wrote:
> On Sun, 2020-08-30 at 21:15 +0800, Shawn Guo wrote:
> > On Fri, Aug 21, 2020 at 02:17:54PM +0200, Martin Kepplinger wrote:
> > > Add development information for the devicetree files for hardware
> > > by Purism SPC.
> > >
> > > Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
> >
> > I decided to drop this patch from my queue, as I took the suggestion
> > from Joe and sent a patch to have get_maintainer report email address
> > in the dts file.
>
> It's OK to find maintainers in files, but what about the
> B: bug reporting and T: source code repository location lines,
>
> Those seem useful.
Hmm, I doubt they are practically useful for just a number of dts files.
They are more used for out-of-tree Librem5 kernel drivers, I guess.
Shawn
>
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > > @@ -14061,6 +14061,13 @@ T: git git://linuxtv.org/media_tree.git
> > > F: Documentation/admin-guide/media/pulse8-cec.rst
> > > F: drivers/media/cec/usb/pulse8/
> > >
> > > +PURISM LIBREM 5
> > > +M: Purism Kernel Team <kernel@puri.sm>
>
> People feel like their mails go into a void when no
> responses happen after sending to nameless addresses.
>
> It's better to have a named individual as a maintainer
> rather than an unspecified exploder address.
>
> It's OK to have both, but just the exploder doesn't
> really have that much value as it's faceless.
>
> > > +S: Supported
> > > +B: https://source.puri.sm/Librem5/linux-next/issues
> > > +T: https://source.puri.sm/Librem5/linux-next
>
> This T: line should be something else.
>
> Perhaps
> W; https://source.puri.sm/Librem5/linux-next
> T: git https://source.puri.sm/Librem5/linux-next.git
>
> > > +F: arch/arm64/boot/dts/freescale/imx8mq-librem5*
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Joe Perches <joe@perches.com>
Cc: Martin Kepplinger <martin.kepplinger@puri.sm>,
kernel@puri.sm, Anson.Huang@nxp.com, robh@kernel.org,
s.hauer@pengutronix.de, angus@akkea.ca,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
broonie@kernel.org, linux-imx@nxp.com, kernel@pengutronix.de,
mchehab@kernel.org, festevam@gmail.com, agx@sigxcpu.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v6 2/3] MAINTAINERS: Add Purism Librem 5 section to the list
Date: Mon, 31 Aug 2020 09:19:07 +0800 [thread overview]
Message-ID: <20200831011906.GB4488@dragon> (raw)
In-Reply-To: <1d7c6ef2794bedca7e3164e5435f46864eacddfa.camel@perches.com>
On Sun, Aug 30, 2020 at 08:32:01AM -0700, Joe Perches wrote:
> On Sun, 2020-08-30 at 21:15 +0800, Shawn Guo wrote:
> > On Fri, Aug 21, 2020 at 02:17:54PM +0200, Martin Kepplinger wrote:
> > > Add development information for the devicetree files for hardware
> > > by Purism SPC.
> > >
> > > Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
> >
> > I decided to drop this patch from my queue, as I took the suggestion
> > from Joe and sent a patch to have get_maintainer report email address
> > in the dts file.
>
> It's OK to find maintainers in files, but what about the
> B: bug reporting and T: source code repository location lines,
>
> Those seem useful.
Hmm, I doubt they are practically useful for just a number of dts files.
They are more used for out-of-tree Librem5 kernel drivers, I guess.
Shawn
>
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> []
> > > @@ -14061,6 +14061,13 @@ T: git git://linuxtv.org/media_tree.git
> > > F: Documentation/admin-guide/media/pulse8-cec.rst
> > > F: drivers/media/cec/usb/pulse8/
> > >
> > > +PURISM LIBREM 5
> > > +M: Purism Kernel Team <kernel@puri.sm>
>
> People feel like their mails go into a void when no
> responses happen after sending to nameless addresses.
>
> It's better to have a named individual as a maintainer
> rather than an unspecified exploder address.
>
> It's OK to have both, but just the exploder doesn't
> really have that much value as it's faceless.
>
> > > +S: Supported
> > > +B: https://source.puri.sm/Librem5/linux-next/issues
> > > +T: https://source.puri.sm/Librem5/linux-next
>
> This T: line should be something else.
>
> Perhaps
> W; https://source.puri.sm/Librem5/linux-next
> T: git https://source.puri.sm/Librem5/linux-next.git
>
> > > +F: arch/arm64/boot/dts/freescale/imx8mq-librem5*
>
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-08-31 1:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 12:17 [PATCH v6 1/3] arm64: dts: Add a device tree for the Librem 5 phone Martin Kepplinger
2020-08-21 12:17 ` Martin Kepplinger
2020-08-21 12:17 ` [PATCH v6 2/3] MAINTAINERS: Add Purism Librem 5 section to the list Martin Kepplinger
2020-08-21 12:17 ` Martin Kepplinger
2020-08-30 13:15 ` Shawn Guo
2020-08-30 13:15 ` Shawn Guo
2020-08-30 15:32 ` Joe Perches
2020-08-30 15:32 ` Joe Perches
2020-08-31 1:19 ` Shawn Guo [this message]
2020-08-31 1:19 ` Shawn Guo
2020-09-30 10:50 ` Krzysztof Kozlowski
2020-09-30 10:50 ` Krzysztof Kozlowski
2020-09-30 15:30 ` Joe Perches
2020-09-30 15:30 ` Joe Perches
2020-08-21 12:17 ` [PATCH v6 3/3] dt-bindings: arm: fsl: Add the librem 5 phone Martin Kepplinger
2020-08-21 12:17 ` Martin Kepplinger
2020-08-23 3:02 ` [PATCH v6 1/3] arm64: dts: Add a device tree for the Librem " Shawn Guo
2020-08-23 3:02 ` Shawn Guo
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=20200831011906.GB4488@dragon \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=agx@sigxcpu.org \
--cc=angus@akkea.ca \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=joe@perches.com \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.kepplinger@puri.sm \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.