mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Xin Ji <xji@analogixsemi.com>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	bliang@analogixsemi.com, qwen@analogixsemi.com,
	jli@analogixsemi.com, kernel test robot <lkp@intel.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 2/2] usb: typec: anx7411: Add Analogix PD ANX7411 support
Date: Thu, 20 Jan 2022 12:55:27 +0100	[thread overview]
Message-ID: <YelNrzuYajCZ7agG@kroah.com> (raw)
In-Reply-To: <20220120103137.GA2026944@anxtwsw-Precision-3640-Tower>

On Thu, Jan 20, 2022 at 06:31:37PM +0800, Xin Ji wrote:
> On Thu, Jan 20, 2022 at 10:58:17AM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Jan 20, 2022 at 05:36:15PM +0800, Xin Ji wrote:
> > > Add driver for analogix ANX7411 USB Type-C DRP port controller.
> > > 
> > > Reported-by: kernel test robot <lkp@intel.com>
> > 
> > The test robot did not report this to ask for a new driver :(
> Hi Greg, test robot ask me to fix the compile warning issue,
> https://patchwork.kernel.org/project/linux-usb/patch/20220119110141.1020452-2-xji@analogixsemi.com/
> so I think need upstream v2 after fixed the issue. I'll remove the test
> robot tag in the next serial.
> 
> BTW, your robot ask me to add more log at commit message, do I need
> upstream v3 after do that?

Of course, I can't take this as-is.

thanks,

greg k-h

  reply	other threads:[~2022-01-20 11:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-20  9:36 [PATCH v2 1/2] dt-bindings: usb: Add analogix anx7411 PD binding Xin Ji
2022-01-20  9:36 ` [PATCH v2 2/2] usb: typec: anx7411: Add Analogix PD ANX7411 support Xin Ji
2022-01-20  9:57   ` Greg Kroah-Hartman
2022-01-20  9:58   ` Greg Kroah-Hartman
2022-01-20 10:31     ` Xin Ji
2022-01-20 11:55       ` Greg Kroah-Hartman [this message]
2022-01-21  3:05         ` Xin Ji

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=YelNrzuYajCZ7agG@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bliang@analogixsemi.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=jli@analogixsemi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lkp@intel.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
Powered by JetHome