public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Jiri Slaby <jirislaby@kernel.org>,
	linux-serial@vger.kernel.org, Stephen Warren <swarren@nvidia.com>,
	Alan Cox <alan@linux.intel.com>,
	Laxman Dewangan <ldewangan@nvidia.com>,
	Thierry Reding <treding@nvidia.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] serial: Create uart_xmit_advance()
Date: Tue, 30 Aug 2022 14:27:43 +0200	[thread overview]
Message-ID: <Yw4CP8y3b9E9XV0K@kroah.com> (raw)
In-Reply-To: <20220825091707.8112-2-ilpo.jarvinen@linux.intel.com>

On Thu, Aug 25, 2022 at 12:17:05PM +0300, Ilpo Järvinen wrote:
> A very common pattern in the drivers is to advance xmit tail
> index and do bookkeeping of Tx'ed characters. Create
> uart_xmit_advance() to handle it.
> 
> Fixes: e9ea096dd225 ("serial: tegra: add serial driver")
> Fixes: 2d908b38d409 ("serial: Add Tegra Combined UART driver")

This commit only adds a new function, it does not "Fix" anything :(


  reply	other threads:[~2022-08-30 12:27 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-25  9:17 [PATCH 0/3] serial: Add uart_xmit_advance() + fixes part (of a larger patch series) Ilpo Järvinen
2022-08-25  9:17 ` [PATCH 1/3] serial: Create uart_xmit_advance() Ilpo Järvinen
2022-08-30 12:27   ` Greg Kroah-Hartman [this message]
2022-08-30 12:38     ` Andy Shevchenko
2022-08-30 12:48       ` Greg Kroah-Hartman
2022-08-30 12:53         ` Andy Shevchenko
2022-08-25  9:17 ` [PATCH 2/3] serial: tegra: Use uart_xmit_advance(), fixes icount.tx accounting Ilpo Järvinen
2022-08-25  9:17 ` [PATCH 3/3] serial: tegra-tcu: " Ilpo Järvinen
2022-08-26 16:03 ` [PATCH 0/3] serial: Add uart_xmit_advance() + fixes part (of a larger patch series) Andy Shevchenko
2022-08-29  7:23 ` Jiri Slaby
2022-08-29  7:41   ` Ilpo Järvinen
2022-08-29  7:50     ` Jiri Slaby
2022-08-29  7:54       ` Ilpo Järvinen

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=Yw4CP8y3b9E9XV0K@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=alan@linux.intel.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=jirislaby@kernel.org \
    --cc=ldewangan@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=swarren@nvidia.com \
    --cc=treding@nvidia.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