From: Alex Nemirovsky <Alex.Nemirovsky@cortina-access.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Russell King <linux@armlinux.org.uk>,
Jason Li <jason.li@cortina-access.com>
Subject: Re: [PATCH 1/2] tty: serial: Add UART driver for Cortina-Access CAxxxx SoCs
Date: Fri, 15 Jan 2021 09:14:39 +0000 [thread overview]
Message-ID: <4E53F74B-5C07-4B91-AE51-E0332579B328@cortina-access.com> (raw)
In-Reply-To: <YAE5L8snkCNU/Lae@kroah.com>
ok.. that’s my bad. Jason had it split in two commits.
Thanks for all the feedback. “We will be back”. ;)
> On Jan 14, 2021, at 10:41 PM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> On Thu, Jan 14, 2021 at 05:11:52PM -0800, Alex Nemirovsky wrote:
>> From: Jason Li <jason.li@cortina-access.com>
>>
>> This driver supports Cortina Access UART IP integrated
>> in most all CAXXXX line of SoCs. Earlycom is also supported.
>>
>> Signed-off-by: Jason Li <jason.li@cortina-access.com>
>> Reviewed-by: Alex Nemirovsky <alex.nemirovsky@cortina-access.com>
>> ---
>> .../bindings/serial/cortina-access,serial.yaml | Bin 0 -> 836 bytes
>> .../devicetree/bindings/vendor-prefixes.yaml | 2 +
>
> Also, you need to split this up, with the DT-specific changes a separate
> patch, and cc: the device tree maintainers to get them to review it
> properly.
>
> thanks,
>
> greg k-h
prev parent reply other threads:[~2021-01-15 9:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1610673113-14503-1-git-send-email-alex.nemirovsky@cortina-access.com>
2021-01-15 6:40 ` [PATCH 1/2] tty: serial: Add UART driver for Cortina-Access CAxxxx SoCs Greg Kroah-Hartman
[not found] ` <4B59D43F-FEE9-4AA0-BEF6-DEE986609460@cortina-access.com>
2021-02-04 15:47 ` Greg Kroah-Hartman
2021-01-15 6:41 ` Greg Kroah-Hartman
2021-01-15 9:14 ` Alex Nemirovsky [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=4E53F74B-5C07-4B91-AE51-E0332579B328@cortina-access.com \
--to=alex.nemirovsky@cortina-access.com \
--cc=gregkh@linuxfoundation.org \
--cc=jason.li@cortina-access.com \
--cc=linux-serial@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).