From: Hans Ulli Kroll <ulli.kroll@googlemail.com>
To: Christophe Jaillet <christophe.jaillet@wanadoo.fr>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH 0/4] usb: gadget: fotg210-udc: Fixes and cleanup
Date: Sat, 17 Feb 2018 11:50:16 +0100 (CET) [thread overview]
Message-ID: <alpine.LNX.2.00.1802171142240.10047@T420s> (raw)
In-Reply-To: <p5sksu$4pc$1@blaine.gmane.org>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 950 bytes --]
Hi Christophe
On Mon, 12 Feb 2018, Christophe Jaillet wrote:
> Le 12/02/2018 à 09:48, Felipe Balbi a écrit :
> >
[..]
> > way around :-) First fixes, then cleanups. The reason is that fixes can
> > get accepted during -rc cycle, but cleanups must wait until the next
> > merge window.
> >
> > Please fix up your patches, otherwise I'll have to apply the entire
> > series for v4.17
> >
>
> I agree with you. I will be more careful in the future.
> However, I will not re-send an updated version. Development on this driver
> does not seem to be very active.
... not quite right.
This driver and the fotg210-hcd is *currently* under my observation, I
want to add a phy/otg driber on top of these.
Feel free to CC me if you want to resend these patches.
With "not very active" makes me happy, so I don't break not much.
And if anyone ask, I have some devices to test, of cource ;-)
Greetings
Hans Ulli Kroll
prev parent reply other threads:[~2018-02-17 10:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 21:41 Christophe JAILLET
2018-01-12 21:44 ` [PATCH 1/4] usb: gadget: fotg210-udc: Remove a useless Christophe JAILLET
2018-01-12 21:44 ` [PATCH 2/4] usb: gadget: fotg210-udc: Fix a memory leak Christophe JAILLET
2018-01-12 21:44 ` [PATCH 3/4] usb: gadget: fotg210-udc: Simplify code Christophe JAILLET
2018-01-12 21:44 ` [PATCH 4/4] usb: gadget: fotg210-udc: Fix a potential invalid pointer dereference Christophe JAILLET
2018-02-12 8:48 ` [PATCH 0/4] usb: gadget: fotg210-udc: Fixes and cleanup Felipe Balbi
2018-02-12 18:05 ` Christophe Jaillet
2018-02-17 10:50 ` Hans Ulli Kroll [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=alpine.LNX.2.00.1802171142240.10047@T420s \
--to=ulli.kroll@googlemail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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®