From: Johan Hovold <johan@kernel.org>
To: Karoly Pados <pados@pados.hu>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Loic Poulain <loic.poulain@linaro.org>
Subject: Re: [PATCH v5] USB: serial: ftdi_sio: implement GPIO support for FT-X devices
Date: Mon, 24 Sep 2018 14:37:36 +0200 [thread overview]
Message-ID: <20180924123736.GJ5101@localhost> (raw)
In-Reply-To: <48c673281bec5fbb4b8b84ed884c000a@pados.hu>
On Mon, Sep 24, 2018 at 11:52:38AM +0000, Karoly Pados wrote:
> Oops, I sent v4 again, so it had no changes at all. Can't I just
> resend v5 instead of calling it v6?
No, you should label it v6 so that it can be told apart from the
incorrect v5.
Thanks,
Johan
prev parent reply other threads:[~2018-09-24 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-23 16:03 [PATCH v5] USB: serial: ftdi_sio: implement GPIO support for FT-X devices Karoly Pados
2018-09-24 8:47 ` Johan Hovold
2018-09-24 11:52 ` Karoly Pados
2018-09-24 12:37 ` Johan Hovold [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=20180924123736.GJ5101@localhost \
--to=johan@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=pados@pados.hu \
/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;
as well as URLs for NNTP newsgroup(s).