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]
Date:   Fri, 27 Oct 2023 18:36:09 +0200
From:   Lino Sanfilippo <LinoSanfilippo@....de>
To:     Greg KH <gregkh@...uxfoundation.org>,
        Lino Sanfilippo <l.sanfilippo@...bus.com>
Cc:     jirislaby@...nel.org, ilpo.jarvinen@...ux.intel.com,
        u.kleine-koenig@...gutronix.de, shawnguo@...nel.org,
        s.hauer@...gutronix.de, mcoquelin.stm32@...il.com,
        alexandre.torgue@...s.st.com, cniedermaier@...electronics.com,
        linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
        lukas@...ner.de, p.rosenberger@...bus.com
Subject: Re: [PATCH v4 0/7] Fixes and improvements for RS485


On 27.10.23 13:03, Greg KH wrote:
> On Wed, Oct 18, 2023 at 07:48:33PM +0200, Lino Sanfilippo wrote:
>> The following series includes some fixes and improvements around RS485 in
>> the serial core and UART drivers:
>>
>> Patch 1: Do not hold the port lock when setting rx-during-tx GPIO
>> Patch 2: set missing supported flag for RX during TX GPIO
>> Patch 3: fix sanitizing check for RTS settings
>> Patch 4: make sure RS485 is cannot be enabled when it is not supported
>> Patch 5: imx: do not set RS485 enabled if it is not supported
>> Patch 6: omap: do not override settings for rs485 support
>> Patch 7: exar: set missing RS485 supported flag
>>
>> Changes in v4:
>> - add comment for function uart_set_rs485_gpios after hint from Hugo
>> - correct commit message as pointed out by Hugo
>> - rephrase commit messages
>> - add patch 7 after discussion with Ilpo
>
> There's a lot of fuzz for this series against my current tree, so much
> so I don't feel comfortable taking it right now.  Can you resend it
> after 6.7-rc1 is out and you have rebased it against that?  If these
> really are all bugfixes, we can still get them into 6.7-final then.
Yes, no problem, will do so.

BR,
Lino

Powered by blists - more mailing lists