From: Guenter Roeck <linux@roeck-us.net>
To: Xin Ji <xji@analogixsemi.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
bliang@analogixsemi.com, qwen@analogixsemi.com,
jli@analogixsemi.com, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH v16 1/3] usb: typec: tcpci: move tcpci.h to include/linux/usb/
Date: Wed, 13 Jul 2022 08:56:13 -0700 [thread overview]
Message-ID: <20220713155613.GA2194204@roeck-us.net> (raw)
In-Reply-To: <20220713064818.GA2789090@anxtwsw-Precision-3640-Tower>
On Wed, Jul 13, 2022 at 02:48:18PM +0800, Xin Ji wrote:
> On Wed, Jul 13, 2022 at 08:36:53AM +0200, Greg Kroah-Hartman wrote:
> > On Wed, Jul 13, 2022 at 02:28:45PM +0800, Xin Ji wrote:
> > > 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@roeck-us.net>
> > > > > > Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> > > > > > Signed-off-by: Xin Ji <xji@analogixsemi.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.
> >
> > I'm confused, why are you sending a patch over that is already in my
> > tree and in linux-next? You got an email saying it was merged, see
> > commit 7963d4d71011 ("usb: typec: tcpci: move tcpci.h to
> > include/linux/usb/").
> >
> > thanks,
> >
> > greg k-h
> Hi greg k-h, sorry for that, this serial has 3 patches, so I just think
> need update all 3 patches in each upstream.
If you resend patches as part of a series, please explain in the change
log that this patch was unchanged.
Guenter
prev parent reply other threads:[~2022-07-13 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 9:05 [PATCH v16 1/3] usb: typec: tcpci: move tcpci.h to include/linux/usb/ Xin Ji
2022-07-12 13:31 ` Guenter Roeck
2022-07-12 13:43 ` Greg Kroah-Hartman
2022-07-13 6:28 ` Xin Ji
2022-07-13 6:36 ` Greg Kroah-Hartman
2022-07-13 6:48 ` Xin Ji
2022-07-13 15:56 ` Guenter Roeck [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=20220713155613.GA2194204@roeck-us.net \
--to=linux@roeck-us.net \
--cc=bliang@analogixsemi.com \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jli@analogixsemi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=qwen@analogixsemi.com \
--cc=xji@analogixsemi.com \
/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