From: Florian Fainelli <f.fainelli@gmail.com>
To: bcm-kernel-feedback-list@broadcom.com,
linux-arm-kernel@lists.infradead.org
Cc: Justin Chen <justinpopo6@gmail.com>,
Russell King <linux@armlinux.org.uk>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ARM: brcmstb: Add debug UART entry for 7216
Date: Fri, 20 Dec 2019 10:54:06 -0800 [thread overview]
Message-ID: <20191220185406.1886-1-f.fainelli@gmail.com> (raw)
In-Reply-To: <20191210224859.30899-1-f.fainelli@gmail.com>
On Tue, 10 Dec 2019 14:48:56 -0800, Florian Fainelli <f.fainelli@gmail.com> wrote:
> From: Justin Chen <justinpopo6@gmail.com>
>
> 7216 has the same memory map as 7278 and the same physical address for
> the UART, alias the definition accordingly.
>
> Signed-off-by: Justin Chen <justinpopo6@gmail.com>
> [florian: expand commit message]
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
Applied to soc/next, thanks!
--
Florian
prev parent reply other threads:[~2019-12-20 18:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 22:48 [PATCH] ARM: brcmstb: Add debug UART entry for 7216 Florian Fainelli
2019-12-20 18:54 ` Florian Fainelli [this message]
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=20191220185406.1886-1-f.fainelli@gmail.com \
--to=f.fainelli@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=justinpopo6@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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).