[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZiEqXkw_IvavCPVS@smile.fi.intel.com>
Date: Thu, 18 Apr 2024 17:12:46 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Konstantin Pugin <rilian.la.te@...ru>
Cc: Konstantin Pugin <ria.freelander@...il.com>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jirislaby@...nel.org>,
Hugo Villeneuve <hvilleneuve@...onoff.com>,
Lech Perczak <lech.perczak@...lingroup.com>,
Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>, linux-kernel@...r.kernel.org,
linux-serial@...r.kernel.org
Subject: Re: [PATCH v2 1/3] serial: sc16is7xx: announce support of
SER_RS485_RTS_ON_SEND
On Thu, Apr 18, 2024 at 04:57:32PM +0300, Konstantin Pugin wrote:
> From: Konstantin Pugin <ria.freelander@...il.com>
>
> Hardware supports both modes, but after
The hardware
"both"? Please elaborate, like
"The hardware supports both (A and B) modes, ..."
> commit 4afeced55baa ("serial: core: fix sanitizing check for RTS settings")
the commit
> we always end up with SER_RS485_RTS_AFTER_SEND and always write in
write to
> register SC16IS7XX_EFCR_RTS_INVERT_BIT,
the register
> which breaks some hardware using these chips,
Please, rewrap these lines to be approximately same width. Yes, you may split
commit over the lines in the body of the commit message, but tags (like Fixes).
Also it seems you forgot to add Vladimir's tags. It's your responsibility
to do that if you send a new version with only cosmetic changes done.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists