linux-kernel - Re: [PATCH v1 00/13] serial: 8250

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]

Message-ID: <ZjPL5z7ah-Qkct6l@smile.fi.intel.com>
Date: Thu, 2 May 2024 20:22:47 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Parker Newman <parker@...est.io>
Cc: Parker Newman <pnewman@...necttech.com>, linux-kernel@...r.kernel.org,
	linux-serial@...r.kernel.org,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Jiri Slaby <jirislaby@...nel.org>
Subject: Re: [PATCH v1 00/13] serial: 8250_exar: Clean up the driver

On Thu, May 02, 2024 at 12:08:40PM -0400, Parker Newman wrote:
> On Thu, 2 May 2024 19:01:01 +0300
> Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> > On Thu, May 02, 2024 at 11:46:45AM -0400, Parker Newman wrote:
> > > On Thu,  2 May 2024 17:43:54 +0300
> > > Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:
> > >
> > > > After a rework for CONNTECH was done, the driver may need a bit of
> > > > love in order to become less verbose (in terms of indentation and
> > > > code duplication) and hence easier to read.
> > > >
> > > > This clean up series fixes a couple of (not so critical) issues and
> > > > cleans up the recently added code. No functional change indented by
> > > > the cleaning up part.
> > >
> > > Just an FYI I submitted a patch series that fixed several of these issues but I
> > > think it fell through the cracks (I know everyone is very busy!).
> > >
> > > Link: https://lore.kernel.org/linux-serial/cover.1713533298.git.pnewman@connecttech.com/
> > >
> > > I believe my previous patch series is no longer required. This one fixes
> > > everything.
> >
> > I haven't noticed that, if it contains duplicated patches, I may replace mine
> > with yours if you insist.
> >
> > In any case it's better to reply there that you prefer this series to be
> > applied, so Greg will not pick it up.
> >
> 
> I do not have a preference. I am fine with using yours if it is easier on
> the maintainers.

Up to you, there is no issue to take your patches in case they are the same
(or quite similar) as mine. I can pick them up, just tell me if you want this
to happen with a list of the patches (as mail Message-Id).

> I will send a reply on my previous series that it is not needed and link
> to this. I am new to the mailing lists so I didn't know what the procedure
> is for this situation.

It's not about mailing lists, it's just a common sense.

> Thanks for the fixes :),

You are welcome!

-- 
With Best Regards,
Andy Shevchenko