linux-kernel - Re: [PATCH v16 1/3] usb: typec: tcpci: move tcpci.h to include/linux/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:   Wed, 13 Jul 2022 14:28:45 +0800
From:   Xin Ji <xji@...logixsemi.com>
To:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Guenter Roeck <linux@...ck-us.net>
Cc:     Heikki Krogerus <heikki.krogerus@...ux.intel.com>,
        Matthias Brugger <matthias.bgg@...il.com>,
        bliang@...logixsemi.com, qwen@...logixsemi.com,
        jli@...logixsemi.com, linux-usb@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH v16 1/3] usb: typec: tcpci: move tcpci.h to
 include/linux/usb/

On Tue, Jul 12, 2022 at 03:43:48PM +0200, Greg Kroah-Hartman wrote:
> On Tue, Jul 12, 2022 at 06:31:22AM -0700, Guenter Roeck wrote:
> > On 7/12/22 02:05, Xin Ji wrote:
> > > USB PD controllers which consisting of a microcontroller (acting as the TCPM)
> > > and a port controller (TCPC) - may require that the driver for the PD
> > > controller accesses directly also the on-chip port controller in some cases.
> > > 
> > > Move tcpci.h to include/linux/usb/ is convenience access TCPC registers.
> > > 
> > > Reviewed-by: Guenter Roeck <linux@...ck-us.net>
> > > Reviewed-by: Heikki Krogerus <heikki.krogerus@...ux.intel.com>
> > > Signed-off-by: Xin Ji <xji@...logixsemi.com>
> > > 
> > > ---
> > > V9 -> V10: Rebase on the latest code
> > > V8 -> V9 : Add more commit message
> > > V7 -> V8 : Fix Guanter's comment, remove unnecessary explain
> > 
> > We are now at v16. The change log has not been updated since v10,
> > making it all but worthless.
> 
> It's also already in my tree for a while, so I have no idea what this is
> being generated against :(
Hi all, I'm little confused, do I need update change log from v11 to
v16? There is no changes since v10.
Thanks,
Xin