[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LFD.2.21.1905010255070.30973@eddie.linux-mips.org>
Date: Wed, 1 May 2019 03:20:37 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Greg KH <gregkh@...uxfoundation.org>
cc: "Enrico Weigelt, metux IT consult" <lkml@...ux.net>,
"Enrico Weigelt, metux IT consult" <info@...ux.net>,
linux-kernel@...r.kernel.org, andrew@...id.au,
andriy.shevchenko@...ux.intel.com, vz@...ia.com,
slemieux.tyco@...il.com, khilman@...libre.com, liviu.dudau@....com,
sudeep.holla@....com, lorenzo.pieralisi@....com,
"David S. Miller" <davem@...emloft.net>, jacmet@...site.dk,
linux@...sktech.co.nz, matthias.bgg@...il.com,
linux-mips@...r.kernel.org, linux-serial@...r.kernel.org,
linux-ia64@...r.kernel.org, linux-amlogic@...ts.infradead.org,
linuxppc-dev@...ts.ozlabs.org, sparclinux@...r.kernel.org
Subject: Re: [PATCH 01/41] drivers: tty: serial: dz: use dev_err() instead
of printk()
On Mon, 29 Apr 2019, Greg KH wrote:
> > >> drivers/tty/serial/dz.c | 8 ++++----
> > >
> > > Do you have this hardware to test any of these changes with?
> >
> > Unfortunately not :(
>
> Then I can take the "basic" types of patches for the driver (like this
> one), but not any others, sorry.
I can verify changes to dz.c, sb1250-duart.c and zs.c with real hardware,
but regrettably not right away: the hardware is in a remote location and
while I have it wired for remote operation unfortunately its connectivity
has been cut off by an unfriendly ISP.
I'm not sure if all the changes make sense though: if there is a compiler
warning or a usability issue, then a patch is surely welcome, otherwise:
"If it ain't broke, don't fix it".
Maciej
Powered by blists - more mailing lists