From: Lino Sanfilippo <LinoSanfilippo@gmx.de>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: gregkh@linuxfoundation.org, jirislaby@kernel.org,
ilpo.jarvinen@linux.intel.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, vz@mleia.com,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
lukas@wunner.de, p.rosenberger@kunbus.com,
Lino Sanfilippo <l.sanfilippo@kunbus.com>
Subject: Re: [PATCH v4 0/8] Fixes and cleanup for RS485
Date: Sun, 10 Jul 2022 21:00:30 +0200 [thread overview]
Message-ID: <af8bf241-68c3-02fc-b2f2-6eba20c01b9a@gmx.de> (raw)
In-Reply-To: <YssdxGoKAt5Rx2DK@smile.fi.intel.com>
Hi,
On 10.07.22 20:43, Andy Shevchenko wrote:
> On Sun, Jul 10, 2022 at 06:44:34PM +0200, Lino Sanfilippo wrote:
>> From: Lino Sanfilippo <l.sanfilippo@kunbus.com>
>>
>> The following series includes cleanup and fixes around RS485 in the serial
>> core and uart drivers:
>>
>> Patch 1: ar933x: Fix check for RS485 support
>> Patch 2: Remove superfluous code in ar933x.
>> Patch 3: Set the rs485 termination GPIO in the serial core. This is needed
>> since if the gpio is only accessible in sleepable context. It also
>> is a further step to make the RS485 handling more generic.
>> Patch 4: Move sanitizing of RS485 delays into an own function. This is in
>> preparation of patch 4.
>> Patch 5: Sanitize RS485 delays read from device tree.
>> Patch 6: Correct RS485 delays in binding documentation.
>> Patch 7: Remove redundant code in 8250_dwlib.
>> Patch 8: Remove redundant code in 8250-lpc18xx.
>
>> Changes in v4:
>> - fixed logical error found by
>> - capitalize "uart" and "gpio" in commit messages
>
> Please, avoid sending sequential version of the series more often than once per
> a few days, recommended interval is one week.
>
sorry, this was due to the error found by the kernel test robot. I was not sure
if to wait, resend with the same version number or send the next version.
I guess waiting a few days would have been the best option. Will do so next
time.
Regards,
Lino
prev parent reply other threads:[~2022-07-10 19:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 16:44 Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 1/8] serial: ar933x: Fix check for RS485 support Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 2/8] serial: ar933x: Remove superfluous code in ar933x_config_rs485() Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 3/8] serial: core, 8250: set RS485 termination GPIO in serial core Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 4/8] serial: core: move sanitizing of RS485 delays into own function Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 5/8] serial: core: sanitize RS485 delays read from device tree Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 6/8] dt_bindings: rs485: Correct delay values Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 7/8] serial: 8250_dwlib: remove redundant sanity check for RS485 flags Lino Sanfilippo
2022-07-10 16:44 ` [PATCH v4 8/8] serial: 8250: lpc18xx: Remove " Lino Sanfilippo
2022-07-10 18:43 ` [PATCH v4 0/8] Fixes and cleanup for RS485 Andy Shevchenko
2022-07-10 19:00 ` Lino Sanfilippo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=af8bf241-68c3-02fc-b2f2-6eba20c01b9a@gmx.de \
--to=linosanfilippo@gmx.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=l.sanfilippo@kunbus.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=p.rosenberger@kunbus.com \
--cc=robh+dt@kernel.org \
--cc=vz@mleia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®