linux-kernel - Re: [PATCH v9 1/3] serial: sc16is7xx: announce support of SER_RS485_RTS_ON

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] [day] [month] [year] [list]

Message-ID: <CAHp75VeQyZ-WQ3D=T4wLQ46=oQYQPBXg9+8nj6AsXgEop8txgA@mail.gmail.com>
Date: Fri, 26 Apr 2024 18:10:16 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: "Konstantin P." <ria.freelander@...il.com>
Cc: Andy Shevchenko <andy@...nel.org>, Konstantin Pugin <rilian.la.te@...ru>, krzk@...nel.org, 
	conor@...nel.org, lkp@...el.com, vz@...ia.com, robh@...nel.org, 
	jcmvbkbc@...il.com, nicolas.ferre@...rochip.com, manikanta.guntupalli@....com, 
	corbet@....net, ychuang3@...oton.com, u.kleine-koenig@...gutronix.de, 
	Maarten.Brock@...ls.nl, Hugo Villeneuve <hvilleneuve@...onoff.com>, 
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Jiri Slaby <jirislaby@...nel.org>, 
	Lech Perczak <lech.perczak@...lingroup.com>, 
	Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>, 
	linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org
Subject: Re: [PATCH v9 1/3] serial: sc16is7xx: announce support of SER_RS485_RTS_ON_SEND

On Fri, Apr 26, 2024 at 6:06 PM Andy Shevchenko
<andy.shevchenko@...il.com> wrote:
> On Fri, Apr 26, 2024 at 6:00 PM Konstantin P. <ria.freelander@...il.com> wrote:
> > On Fri, Apr 26, 2024 at 5:36 PM Andy Shevchenko <andy@...nel.org> wrote:
> > > On Thu, Apr 25, 2024 at 09:32:33PM +0300, Konstantin Pugin wrote:

..

> > > Greg KH, who is maintainer of TTY/serial subsystem, usually asks to separate
> > > fixes from new features. So, sending this patch separately may not only help
> > > him, but let's move forward with your stuff.
> >
> > Do I need to increase the version number in split send?
>
> Nope, the opposite, i.e. drop it to v1 (and mention in the comments
> area, that's after the cutter '---' line, that it's a split from this
> series).
>
> >  And if I need
> > to do so, then how I should do it? Only on new driver? Or only on fix?
> > Should I CC linux-stable in fix patch?
>
> Everything else is documented:
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html

Just to be crystal clear:
- the split of the fix goes as v1
- the rest as v10 (or what is the number of the next revision?) after
you address all review comments, confirmed testing, etc.

-- 
With Best Regards,
Andy Shevchenko