[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJKOXPdmSUqs+d3CuJ9px=vWPPdgP0scAZvKJkKDrs5O+sw6yA@mail.gmail.com>
Date: Tue, 22 Mar 2022 18:05:49 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Jung Daehwan <dh10.jung@...sung.com>,
Mathias Nyman <mathias.nyman@...el.com>,
"open list:USB XHCI DRIVER" <linux-usb@...r.kernel.org>,
open list <linux-kernel@...r.kernel.org>,
Howard Yen <howardyen@...gle.com>,
Jack Pham <jackp@...eaurora.org>,
Puma Hsu <pumahsu@...gle.com>,
"J . Avila" <elavila@...gle.com>, sc.suh@...sung.com
Subject: Re: [PATCH v3 0/4] support USB offload feature
On Mon, 21 Mar 2022 at 11:16, Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> >
> > [v3, 0/4] add xhci-exynos driver
> >
> > This patchset is for support xhci-exynos driver....
> > ....
> >
> > usb: host: export symbols for xhci-exynos to use xhci hooks
> > usb: host: add xhci hooks for xhci-exynos
> > usb: host: add some to xhci overrides for xhci-exynos
> > usb: host: add xhci-exynos driver
>
> Yes, that makes much more sense. What would you want to see if you had
> to review such a series?
Unfortunately it might not make more sense, because last time
xhci-exynos driver was a fake driver, not for submission. It did not
compile, it did not work in mainline.
That driver was not even sent to proper mailing lists, as pointed out
by get_maintainers.pl, maybe because it was not developed on the
mainline kernel, so there is no MAINTAINERS file?
Best regards,
Krzysztof
Powered by blists - more mailing lists