linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: robh@kernel.org, kernel@puri.sm, Anson.Huang@nxp.com,
	devicetree@vger.kernel.org, shawnguo@kernel.org,
	s.hauer@pengutronix.de, angus@akkea.ca,
	linux-kernel@vger.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 2/2] MAINTAINERS: Add Purism Librem 5 section to the list
Date: Wed, 27 May 2020 21:40:04 +0200	[thread overview]
Message-ID: <b4a75f90-2e79-415b-4e96-e1ca317bae3c@puri.sm> (raw)
In-Reply-To: <20200527094014.nn4cupjrvcceo5lv@pengutronix.de>

On 27.05.20 11:40, Marco Felsch wrote:
> On 20-05-14 17:57, Martin Kepplinger wrote:
>> Add development information for the devicetree files for hardware
>> by Purism SPC.
>>
>> Signed-off-by: Martin Kepplinger <martin.kepplinger@puri.sm>
>> ---
>>  MAINTAINERS | 8 ++++++++
>>  1 file changed, 8 insertions(+)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 0abba1aff1ae..176efec31010 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -13775,6 +13775,14 @@ 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>
>> +S:	Supported
>> +B:	https://source.puri.sm/Librem5/linux-next/issues
>> +T:	https://source.puri.sm/Librem5/linux-next
>> +F:	arch/arm64/boot/dts/freescale/imx8mq-librem5-devkit.dts
>> +F:	arch/arm64/boot/dts/freescale/imx8mq-librem5.dts
> 
> Is it okay to take care of all imx8mq-librem5* files? 
> 
> F:	arch/arm64/boot/dts/freescale/imx8mq-librem5*
> 
> Regards,
>   Marco
> 

hi Marco

it is. I'll change it for a next revision. thanks a lot for taking the
time to review this!

                    martin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-05-27 19:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-14 15:57 [PATCH 1/2] arm64: dts: Add a device tree for the Librem5 phone Martin Kepplinger
2020-05-14 15:57 ` [PATCH 2/2] MAINTAINERS: Add Purism Librem 5 section to the list Martin Kepplinger
2020-05-27  9:40   ` Marco Felsch
2020-05-27 19:40     ` Martin Kepplinger [this message]
2020-05-25  8:47 ` [PATCH 1/2] arm64: dts: Add a device tree for the Librem5 phone Martin Kepplinger
2020-05-26 11:39 ` Daniel Baluta
2020-05-27  9:35 ` Marco Felsch
2020-06-02 15:44   ` Martin Kepplinger
2020-05-29 16:28 ` Pavel Machek
2020-05-29 18:07   ` Pavel Machek
2020-05-29 18:20     ` Martin Kepplinger
2020-05-31 15:36   ` Guido Günther

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=b4a75f90-2e79-415b-4e96-e1ca317bae3c@puri.sm \
    --to=martin.kepplinger@puri.sm \
    --cc=Anson.Huang@nxp.com \
    --cc=agx@sigxcpu.org \
    --cc=angus@akkea.ca \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.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=m.felsch@pengutronix.de \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.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;
as well as URLs for NNTP newsgroup(s).