From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Nuno Gonçalves" <nunojpg@gmail.com>,
"Tomasz Mon" <tomasz.mon@camlingroup.com>,
"Lukas Wunner" <lukas@wunner.de>,
linux-serial <linux-serial@vger.kernel.org>
Subject: Re: [PATCH v2] serial: pl011: UPSTAT_AUTORTS requires .throttle/unthrottle
Date: Fri, 29 Apr 2022 15:33:00 +0300 (EEST) [thread overview]
Message-ID: <3f44e8d-3d2d-db4e-6cfc-67ec5824c289@linux.intel.com> (raw)
In-Reply-To: <YmvWFQultpccovgb@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1220 bytes --]
On Fri, 29 Apr 2022, Greg KH wrote:
> On Fri, Apr 29, 2022 at 02:57:16PM +0300, Ilpo Järvinen wrote:
> > The driver must provide throttle and unthrottle in uart_ops when it
> > sets UPSTAT_AUTORTS. Add them using existing stop_rx &
> > enable_interrupts functions.
> >
> > Compile tested (w/o linking).
>
> That shouldn't be here at all, put it below the --- line if its needed.
>
>
> >
> > Reported-by: Nuno Gonçalves <nunojpg@gmail.com>
> > Fixes: 2a76fa283098 (serial: pl011: Adopt generic flag to store auto
> > RTS status)
>
> Nit, this should be all in one line.
>
> > Cc: Lukas Wunner <lukas@wunner.de>
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
>
> Any reason why you are not cc:ing all the needed people as per
> scripts/get_maintainer.pl?
Yes there is ;-). Around here I'm being told that I should generally
avoid as much as possible bugging you unnecessarily. ...Or sending garbage
to you which I feel a compile tested patch for hw I'm not particularly
familiar with surely could be. After all this should be tested first and
then I'd be resending another version with Tested-by: xx Cc'ing you
and you would avoid all those intermediate garbage versions :-).
--
i.
next prev parent reply other threads:[~2022-04-29 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-29 11:57 [PATCH v2] serial: pl011: UPSTAT_AUTORTS requires .throttle/unthrottle Ilpo Järvinen
2022-04-29 12:12 ` Greg KH
2022-04-29 12:33 ` Ilpo Järvinen [this message]
2022-05-05 20:24 ` Greg KH
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=3f44e8d-3d2d-db4e-6cfc-67ec5824c289@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=nunojpg@gmail.com \
--cc=tomasz.mon@camlingroup.com \
/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