From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: devicetree@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Li Yang <leoyang.li@nxp.com>
Subject: Re: [PATCH] arm64: dts: freescale: sl28: enable LPUART1
Date: Wed, 20 May 2020 09:14:12 +0800 [thread overview]
Message-ID: <20200520011411.GH11739@dragon> (raw)
In-Reply-To: <20200505150037.32573-1-michael@walle.cc>
On Tue, May 05, 2020 at 05:00:37PM +0200, Michael Walle wrote:
> Now that the LPUART has support for the LS1028A SoC, also enable it on
> our board.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
>
> Hi Shawn,
>
> After adding/fixing the LPUART support for the LS1028A I've forgot to send
> this patch to actually enable the LPUART on our boards. It would be great
> if this could make it into the fixes queue for the -rc. If not its also ok.
We only take critical bug fixes at this point. Applied it for -next.
Shawn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Michael Walle <michael@walle.cc>
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Li Yang <leoyang.li@nxp.com>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH] arm64: dts: freescale: sl28: enable LPUART1
Date: Wed, 20 May 2020 09:14:12 +0800 [thread overview]
Message-ID: <20200520011411.GH11739@dragon> (raw)
In-Reply-To: <20200505150037.32573-1-michael@walle.cc>
On Tue, May 05, 2020 at 05:00:37PM +0200, Michael Walle wrote:
> Now that the LPUART has support for the LS1028A SoC, also enable it on
> our board.
>
> Signed-off-by: Michael Walle <michael@walle.cc>
> ---
>
> Hi Shawn,
>
> After adding/fixing the LPUART support for the LS1028A I've forgot to send
> this patch to actually enable the LPUART on our boards. It would be great
> if this could make it into the fixes queue for the -rc. If not its also ok.
We only take critical bug fixes at this point. Applied it for -next.
Shawn
next prev parent reply other threads:[~2020-05-20 1:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 15:00 [PATCH] arm64: dts: freescale: sl28: enable LPUART1 Michael Walle
2020-05-05 15:00 ` Michael Walle
2020-05-20 1:14 ` Shawn Guo [this message]
2020-05-20 1:14 ` 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=20200520011411.GH11739@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=robh+dt@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 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.