linux-kernel - Re: [PATCH v2 0/3] serial: Add uart_xmit_advance() + fixes part (of a larger patch series)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 1 Sep 2022 17:15:11 +0300 (EEST)
From:   Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>
cc:     Jiri Slaby <jirislaby@...nel.org>,
        linux-serial <linux-serial@...r.kernel.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 0/3] serial: Add uart_xmit_advance() + fixes part (of
 a larger patch series)

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?


-- 
 i.