linux-kernel - Re: [PATCH v4 19/20] USB: phy-mv-usb: use phy-pxa-usb

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 2 Dec 2018 11:07:13 -0800
From:   Olof Johansson <olof@...om.net>
To:     Pavel Machek <pavel@....cz>
Cc:     balbi@...nel.org, Lubomir Rintel <lkundrak@...sk>,
        ARM-SoC Maintainers <arm@...nel.org>,
        Arnd Bergmann <arnd@...db.de>,
        Eric Miao <eric.y.miao@...il.com>,
        Haojian Zhuang <haojian.zhuang@...il.com>,
        Russell King <linux@...linux.org.uk>,
        Robert Jarzmik <robert.jarzmik@...e.fr>,
        James Cameron <quozl@...top.org>,
        Linux ARM Mailing List <linux-arm-kernel@...ts.infradead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v4 19/20] USB: phy-mv-usb: use phy-pxa-usb

On Sat, Dec 1, 2018 at 5:10 AM Pavel Machek <pavel@....cz> wrote:
>
> On Fri 2018-11-30 15:42:05, Olof Johansson wrote:
> > On Wed, Nov 28, 2018 at 06:53:23PM +0100, Lubomir Rintel wrote:
> > > Use a proper PHY driver, instead of hooks to a board support package.
> > >
> > > Signed-off-by: Lubomir Rintel <lkundrak@...sk>
> > > Tested-by: Pavel Machek <pavel@....cz>
> >
> > These should have an ack from the USB PHY maintainer before we apply them.
> > I don't see him cc:d on these patches though (Felipe)?
>
> I put him into cc now.
>
> USB PHY LAYER
> M:      Felipe Balbi <balbi@...nel.org>
> L:      linux-usb@...r.kernel.org
> T:      git
> git://git.kernel.org/pub/scm/linux/kernel/git/balbi/usb.git
> S:      Maintained
> F:      drivers/usb/phy/
>
> I guess linux-usb list should be cc-ed, too...

Yeah, and depending on how his mail subscriptions work, he might just
get the above email and not the patch.

Lubo, I suggest resending the remaining patches and making sure that
the maintainers are on cc (and the corresponding lists). If you ask
for their ack instead of to pick up the patch, we can merge it through
our tree.


-Olof