linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Christoph Niedermaier <cniedermaier@dh-electronics.com>,
	linux-arm-kernel@lists.infradead.org, soc@kernel.org,
	Marek Vasut <marex@denx.de>,
	kernel@dh-electronics.com, linux-kernel@vger.kernel.org,
	NXP Linux Team <linux-imx@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH] MAINTAINERS: Add DHCOR to the DH electronic i.MX6 board support
Date: Tue, 22 Nov 2022 11:57:16 +0800	[thread overview]
Message-ID: <20221122035715.GA25470@T480> (raw)
In-Reply-To: <cf1c2f76-a724-4609-8263-a5cf997895be@app.fastmail.com>

On Mon, Nov 21, 2022 at 09:43:06PM +0100, Arnd Bergmann wrote:
> On Thu, Nov 17, 2022, at 11:51, Christoph Niedermaier wrote:
> > Add DHCOR to the DH electronic i.MX6 board support to cover the
> > DHCOR i.MX6ULL SoM. It is a solderable SoM.
> >
> > Signed-off-by: Christoph Niedermaier <cniedermaier@dh-electronics.com>
> 
> The patch looks good to me, and while I could apply it directly to the
> soc tree, the normal way is to send this to the i.MX maintainers
> (added to Cc here).
> 
> Shawn, let me know if you want me to apply this directly,
> otherwise I assume it will be part of you next pull request. 

Hi Arnd,

Feel free to pick it up, as I do not plan to send you another PR for
6.2 merge window, unless there are something really urgent coming.

Shawn

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

  reply	other threads:[~2022-11-22  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-17 10:51 [PATCH] MAINTAINERS: Add DHCOR to the DH electronic i.MX6 board support Christoph Niedermaier
2022-11-21 20:43 ` Arnd Bergmann
2022-11-22  3:57   ` Shawn Guo [this message]
2022-11-22  8:16     ` Arnd Bergmann

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=20221122035715.GA25470@T480 \
    --to=shawnguo@kernel.org \
    --cc=arnd@arndb.de \
    --cc=cniedermaier@dh-electronics.com \
    --cc=festevam@gmail.com \
    --cc=kernel@dh-electronics.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marex@denx.de \
    --cc=s.hauer@pengutronix.de \
    --cc=soc@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).