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 <linux-serial@vger.kernel.org>,
	Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 0/3] serial: Add uart_xmit_advance() + fixes part (of a larger patch series)
Date: Thu, 1 Sep 2022 16:33:55 +0200	[thread overview]
Message-ID: <YxDC08w4sFu/RYzA@kroah.com> (raw)
In-Reply-To: <30e3b86f-c349-d2b7-d6d3-aeec24efb4f5@linux.intel.com>

On Thu, Sep 01, 2022 at 05:15:11PM +0300, Ilpo Järvinen wrote:
> On Thu, 1 Sep 2022, Greg Kroah-Hartman wrote:
> 
> > On Tue, Aug 30, 2022 at 04:19:40PM +0300, Ilpo Järvinen wrote:
> > > On Tue, 30 Aug 2022, Ilpo Järvinen wrote:
> > > 
> > > > Add uart_xmit_advance() helper to handle circular xmit buffer
> > > > advancement + accounting of Tx'ed bytes. Use it to fix a few drivers
> > > > that previously lacked to accounting for DMA Tx.
> > > > 
> > > > Greg,
> > > > I've a another series on top this which is tty-next material making the
> > > > rest of the drivers to use uart_xmit_advance(). That series obviously
> > > > depends on the patch 1/3 of this series so if you end up putting these
> > > > 3 patches into tty-linus, I'll need it to be merged into tty-next at
> > > > some point (I'm not in a big hurry with this so if you choose to delay
> > > > the merge, it's not a big deal).
> > > 
> > > This merge, btw, is no longer that important because I agreed with Jiri to 
> > > wait for his tx loop rewrite series.
> > 
> > Ok, I'll drop this series for now.
> 
> It's not what I meant.
> 
> I've a follow-up series on top of this which depeds on uart_xmit_advance() 
> being available (thus I'd have need it in tty-next). However, now I'm 
> postponing the follow-up series while Jiri sorts out the tx loops.
> 
> This first part of the series and Jiri's tx loop series don't even touch 
> the same files.
> 
> I guess I should resend these if you dropped these from your queue?

Yes please, sorry, I was confused.

greg k-h

      reply	other threads:[~2022-09-01 14:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-30 13:13 [PATCH v2 0/3] serial: Add uart_xmit_advance() + fixes part (of a larger patch series) Ilpo Järvinen
2022-08-30 13:13 ` [PATCH v2 1/3] serial: Create uart_xmit_advance() Ilpo Järvinen
2022-08-30 13:13 ` [PATCH v2 2/3] serial: tegra: Use uart_xmit_advance(), fixes icount.tx accounting Ilpo Järvinen
2022-08-30 13:13 ` [PATCH v2 3/3] serial: tegra-tcu: " Ilpo Järvinen
2022-09-15 12:26   ` Thierry Reding
2022-08-30 13:19 ` [PATCH v2 0/3] serial: Add uart_xmit_advance() + fixes part (of a larger patch series) Ilpo Järvinen
2022-09-01 14:00   ` Greg Kroah-Hartman
2022-09-01 14:15     ` Ilpo Järvinen
2022-09-01 14:33       ` Greg Kroah-Hartman [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=YxDC08w4sFu/RYzA@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=ilpo.jarvinen@linux.intel.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