From: Richard Genoud <richard.genoud@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: Codrin.Ciubotariu@microchip.com, linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
alexandre.belloni@bootlin.com, Ludovic.Desroches@microchip.com,
jslaby@suse.com
Subject: Re: [PATCH] tty/serial: atmel: RS485 & ISO7816: wait for TXRDY before sending data
Date: Thu, 9 Jan 2020 09:52:30 +0100 [thread overview]
Message-ID: <0ea33918-2845-a750-faa7-fec729976136@gmail.com> (raw)
In-Reply-To: <20200109073305.yn5y6sgomjniwwj6@pengutronix.de>
Le 09/01/2020 à 08:33, Uwe Kleine-König a écrit :
> Hello,
>
> On Wed, Jan 08, 2020 at 02:45:05PM +0100, Richard Genoud wrote:
>> NB: MS exchange has added some =3D and =20 here and there, but git am
>> doesn't seems to be bothered by them.
>
> Unless I missed something I cannot confirm. In mutt I don't see any =3D
> or =20.
It's strange indeed. I double check under thunderbird and directly on my
webmail (posteo.de), there're =3D lying around in the message source.
But not on the other patches from linux-serial.
weird...
>
> Best regards
> Uwe
>
WARNING: multiple messages have this Message-ID (diff)
From: Richard Genoud <richard.genoud@gmail.com>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
Cc: alexandre.belloni@bootlin.com, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, Ludovic.Desroches@microchip.com,
linux-serial@vger.kernel.org, jslaby@suse.com,
Codrin.Ciubotariu@microchip.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] tty/serial: atmel: RS485 & ISO7816: wait for TXRDY before sending data
Date: Thu, 9 Jan 2020 09:52:30 +0100 [thread overview]
Message-ID: <0ea33918-2845-a750-faa7-fec729976136@gmail.com> (raw)
In-Reply-To: <20200109073305.yn5y6sgomjniwwj6@pengutronix.de>
Le 09/01/2020 à 08:33, Uwe Kleine-König a écrit :
> Hello,
>
> On Wed, Jan 08, 2020 at 02:45:05PM +0100, Richard Genoud wrote:
>> NB: MS exchange has added some =3D and =20 here and there, but git am
>> doesn't seems to be bothered by them.
>
> Unless I missed something I cannot confirm. In mutt I don't see any =3D
> or =20.
It's strange indeed. I double check under thunderbird and directly on my
webmail (posteo.de), there're =3D lying around in the message source.
But not on the other patches from linux-serial.
weird...
>
> Best regards
> Uwe
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-01-09 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 11:17 [PATCH] tty/serial: atmel: RS485 & ISO7816: wait for TXRDY before sending data Codrin.Ciubotariu
2020-01-07 11:17 ` Codrin.Ciubotariu
2020-01-08 13:45 ` Richard Genoud
2020-01-08 13:45 ` Richard Genoud
2020-01-08 16:03 ` Codrin.Ciubotariu
2020-01-08 16:03 ` Codrin.Ciubotariu
2020-01-09 7:33 ` Uwe Kleine-König
2020-01-09 7:33 ` Uwe Kleine-König
2020-01-09 8:52 ` Richard Genoud [this message]
2020-01-09 8:52 ` Richard Genoud
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=0ea33918-2845-a750-faa7-fec729976136@gmail.com \
--to=richard.genoud@gmail.com \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=u.kleine-koenig@pengutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.