From: Alain Volmat <avolmat@me.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Kate Stewart <kstewart@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Russell King <linux@armlinux.org.uk>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Patrice CHOTARD <patrice.chotard@st.com>,
Olof Johansson <olof@lixom.net>,
Nathan Huckleberry <nhuck15@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Enrico Weigelt <info@metux.net>,
Claudiu Beznea <claudiu.beznea@microchip.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 0/2] arm: sti: LL_UART updates & STiH418 addition
Date: Fri, 18 Sep 2020 22:28:35 +0200 [thread overview]
Message-ID: <20200918202834.GA7621@gnbcxl0029.gnb.st.com> (raw)
In-Reply-To: <CACRpkdaMK8xkvGiSXx=kVjncB=BNy_jcvKsQNTCxRwSKGKJ8Lg@mail.gmail.com>
Hi Linus
On Sat, Sep 12, 2020 at 12:13:59PM +0200, Linus Walleij wrote:
> On Sun, Aug 30, 2020 at 9:58 PM Alain Volmat <avolmat@me.com> wrote:
>
> > This serie update the STi Platform LL_UART code to rely on
> > DEBUG_UART_PHYS & DEBUG_UART_VIRT and add the STiH418 SoC support.
> >
> > Alain Volmat (2):
> > arm: use DEBUG_UART_PHYS and DEBUG_UART_VIRT for sti LL_UART
> > arm: sti LL_UART: add STiH418 SBC UART0 support
>
> Both patches looks good to me:
> Reviewed-by: Linus Walleij <linus.walleij@linaro.org>
>
> I made some patches to the debug UARTs that are pending in Russell's
> patch tracker:
> https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9004/1
> https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9005/1
> https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=9006/1
>
> It doesn't look like these will conflict with your patches but please take
> a look just to make sure.
I confirm that they do not conflict with my two patches.
Alain
>
> Yours,
> Linus Walleij
_______________________________________________
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-09-18 20:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-30 19:57 [PATCH v2 0/2] arm: sti: LL_UART updates & STiH418 addition Alain Volmat
2020-08-30 19:57 ` [PATCH v2 1/2] arm: use DEBUG_UART_PHYS and DEBUG_UART_VIRT for sti LL_UART Alain Volmat
2020-10-06 7:06 ` Patrice CHOTARD
2020-08-30 19:57 ` [PATCH v2 2/2] arm: sti LL_UART: add STiH418 SBC UART0 support Alain Volmat
2020-10-06 7:07 ` Patrice CHOTARD
2020-09-12 10:13 ` [PATCH v2 0/2] arm: sti: LL_UART updates & STiH418 addition Linus Walleij
2020-09-18 20:28 ` Alain Volmat [this message]
2020-10-06 5:04 ` Alain Volmat
2020-10-06 8:29 ` Linus Walleij
2020-11-19 8:08 ` Patrice CHOTARD
2020-11-19 8:26 ` Linus Walleij
2020-11-19 9:57 ` Patrice CHOTARD
2020-11-19 10:23 ` Patrice CHOTARD
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=20200918202834.GA7621@gnbcxl0029.gnb.st.com \
--to=avolmat@me.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=info@metux.net \
--cc=kstewart@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=nhuck15@gmail.com \
--cc=olof@lixom.net \
--cc=patrice.chotard@st.com \
--cc=s.hauer@pengutronix.de \
--cc=tglx@linutronix.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 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).