From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Alex Nemirovsky <Alex.Nemirovsky@cortina-access.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
Jason Li <jason.li@cortina-access.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>
Subject: Re: [PATCH 1/3] tty: serial: Add UART driver for Cortina-Access platform
Date: Wed, 24 Mar 2021 07:04:14 +0100 [thread overview]
Message-ID: <YFrWXtYKnBCYMnYd@kroah.com> (raw)
In-Reply-To: <04208957-55F9-47E8-A20A-4DEB2A35040E@cortina-access.com>
On Tue, Mar 23, 2021 at 07:28:51PM +0000, Alex Nemirovsky wrote:
>
>
> > On Mar 23, 2021, at 2:22 AM, Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
> >
> > On Thu, Feb 18, 2021 at 06:42:09PM -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>
> >> ---
> >> MAINTAINERS | 5 +
> >> drivers/tty/serial/Kconfig | 19 +
> >> drivers/tty/serial/Makefile | 1 +
> >> drivers/tty/serial/serial_cortina-access.c | 798 +++++++++++++++++++++++++++++
> >> include/uapi/linux/serial_core.h | 3 +
> >> 5 files changed, 826 insertions(+)
> >> create mode 100644 drivers/tty/serial/serial_cortina-access.c
> >>
> >> Change log
> >> drivers/tty/serial/serial_cortina-access.c
> >> v3:
> >> - Remove usage of uintptr_t. Change to pointer to driver's private
> >> structure instead.
> >
> > Is this really a "v3"? The subject lines do not show that, so I'm
> > totally confused as to what to review and what has been reviewed here.
> >
> > Please fix this up and submit a "v4" so we know what is going on :)
>
> Could you recommend a method or a tool to update the commit subject id with a version prefix?
> Currently we are doing a git format-patch and the subject line is automatically created without a
> version number. Do you just go in manual and edit the resulting patch contents file or do you use a
> tool to assist in this?
This is only 3 patches, they are easy to edit by hand... :)
Anyway 'git format-patch' can do this automatically for you if you want,
see the -v or --reroll-count option.
thanks,
greg k-h
next prev parent reply other threads:[~2021-03-24 6:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1613702532-5096-1-git-send-email-alex.nemirovsky@cortina-access.com>
2021-03-23 9:22 ` [PATCH 1/3] tty: serial: Add UART driver for Cortina-Access platform Greg Kroah-Hartman
2021-03-23 19:28 ` Alex Nemirovsky
2021-03-24 6:04 ` Greg Kroah-Hartman [this message]
2021-03-23 9:24 ` Greg Kroah-Hartman
2021-03-23 19:25 ` Alex Nemirovsky
2021-03-24 6:02 ` Greg Kroah-Hartman
[not found] <1612425530-20483-1-git-send-email-alex.nemirovsky@cortina-access.com>
2021-02-04 15:48 ` Greg Kroah-Hartman
2021-02-04 15:49 ` Greg Kroah-Hartman
2021-02-04 22:22 ` Alex Nemirovsky
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=YFrWXtYKnBCYMnYd@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Alex.Nemirovsky@cortina-access.com \
--cc=jason.li@cortina-access.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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