linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Benson Leung <bleung@chromium.org>
Cc: Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Enric Balletbo i Serra <enric.balletbo@collabora.com>,
	Prashant Malani <pmalani@chromium.org>,
	"open list:USB SUBSYSTEM" <linux-usb@vger.kernel.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Kyle Tso <kyletso@google.com>
Subject: Re: [PATCH v2] platform/chrome: cros_ec_typec: Fix call to typec_partner_set_pd_revision
Date: Tue, 2 Feb 2021 19:30:06 +0100	[thread overview]
Message-ID: <YBmaLi5hhEj1zy8J@kroah.com> (raw)
In-Reply-To: <CANLzEkuFgLK9saqHhHdrKhOjsiG001d1N9EYXsnohoMPHsAPGg@mail.gmail.com>

On Tue, Feb 02, 2021 at 09:52:13AM -0800, Benson Leung wrote:
> Hi Greg,
> 
> On Tue, Feb 2, 2021 at 9:02 AM Greg KH <gregkh@linuxfoundation.org> wrote:
> >
> > On Tue, Feb 02, 2021 at 08:45:31AM -0800, Benson Leung wrote:
> > > typec_partner_set_pd_revision returns void now.
> > >
> > > Fixes: cefc011f8daf ("platform/chrome: cros_ec_typec: Set Partner PD revision from status")
> > > Signed-off-by: Benson Leung <bleung@chromium.org>
> > > ---
> > >  drivers/platform/chrome/cros_ec_typec.c | 6 +-----
> > >  1 file changed, 1 insertion(+), 5 deletions(-)
> >
> > What changed from "v1"?
> >
> 
> Just the "Fixes" line in the commit message.

That should always go below the --- line, remember, some of us deal with
hundreds of patches a day :)

I'll go take this...

thanks,

greg k-h

  reply	other threads:[~2021-02-02 18:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-02 16:45 [PATCH v2] platform/chrome: cros_ec_typec: Fix call to typec_partner_set_pd_revision Benson Leung
2021-02-02 17:02 ` Greg KH
2021-02-02 17:52   ` Benson Leung
2021-02-02 18:30     ` Greg KH [this message]
2021-02-02 19:44       ` Benson Leung

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=YBmaLi5hhEj1zy8J@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=bleung@chromium.org \
    --cc=enric.balletbo@collabora.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=kyletso@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=pmalani@chromium.org \
    /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;
as well as URLs for NNTP newsgroup(s).