From: Bastien Nocera <hadess@hadess.net>
To: Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Subject: Re: [PATCH v2 0/6] Add Apple MFi fastcharge USB device driver
Date: Tue, 15 Oct 2019 16:29:17 +0200 [thread overview]
Message-ID: <a30df988f8b338c7ad04feeb747936aa0baeba24.camel@hadess.net> (raw)
In-Reply-To: <16edde941e06216fa26477b9e1c121ffbb88a0b4.camel@hadess.net>
On Tue, 2019-10-15 at 16:27 +0200, Bastien Nocera wrote:
> This is version 2 of the patch set.
>
> - checkpatch.pl is now quiet
> - fallback to the generic driver when driver ->probe() fails
And I'll send a v3 because all the patches got mangled by my mail
client.
next prev parent reply other threads:[~2019-10-15 14:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-15 14:27 [PATCH v2 0/6] Add Apple MFi fastcharge USB device driver Bastien Nocera
2019-10-15 14:29 ` Bastien Nocera [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-10-15 14:31 Bastien Nocera
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=a30df988f8b338c7ad04feeb747936aa0baeba24.camel@hadess.net \
--to=hadess@hadess.net \
--cc=benjamin.tissoires@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.edu \
/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).