public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Albert Wang <albertccwang@google.com>
Cc: mathias.nyman@intel.com, badhri@google.com, howardyen@google.com,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@google.com>
Subject: Re: [PATCH 2/3] usb: xhci-plat: add xhci_plat_priv_overwrite
Date: Thu, 27 Oct 2022 08:23:41 +0200	[thread overview]
Message-ID: <Y1oj7TlC93oOKyB7@kroah.com> (raw)
In-Reply-To: <20221027004050.4192111-3-albertccwang@google.com>

On Thu, Oct 27, 2022 at 08:40:49AM +0800, Albert Wang wrote:
> From: Howard Yen <howardyen@google.com>
> 
> Add an overwrite to platform specific callback for setting up the
> xhci_offload_ops, allow vendor to store the xhci_offload_ops and
> overwrite them when xhci_plat_probe invoked.
> 
> Signed-off-by: Howard Yen <howardyen@google.com>
> Link: https://lore.kernel.org/r/20210119101044.1637023-1-howardyen@google.com
> Signed-off-by: Greg Kroah-Hartman <gregkh@google.com>

Again, no, I do NOT sign off on this submission.

Also, you did not sign off on it, yet you forwarded it on.  That's not
allowed either, and makes this whole series not even able to be
accepted, if it were a valid set of changes :(

Please fix.

thanks,

greg k-h

  reply	other threads:[~2022-10-27  6:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  0:40 [PATCH 0/3] add xhci hooks for USB offload Albert Wang
2022-10-27  0:40 ` [PATCH 1/3] usb: host: " Albert Wang
2022-10-27  6:20   ` Greg KH
2022-11-03  1:25   ` kernel test robot
2022-10-27  0:40 ` [PATCH 2/3] usb: xhci-plat: add xhci_plat_priv_overwrite Albert Wang
2022-10-27  6:23   ` Greg KH [this message]
2022-11-03 14:12     ` Albert Wang
2022-10-27  0:40 ` [PATCH 3/3] usb: host: add the xhci offload hooks implementations Albert Wang
2022-10-27  6:22   ` Greg KH
2022-10-27  6:18 ` [PATCH 0/3] add xhci hooks for USB offload Greg KH

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=Y1oj7TlC93oOKyB7@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=albertccwang@google.com \
    --cc=badhri@google.com \
    --cc=gregkh@google.com \
    --cc=howardyen@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mathias.nyman@intel.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