Linux-PHY Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Stanley Chang[昌育德]" <stanley_chang@realtek.com>
Cc: "Vinod Koul" <vkoul@kernel.org>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	"Johan Hovold" <johan+linaro@kernel.org>,
	"Geert Uytterhoeven" <geert+renesas@glider.be>,
	"Rob Herring" <robh@kernel.org>,
	"Jinjie Ruan" <ruanjinjie@huawei.com>,
	"Alan Stern" <stern@rowland.harvard.edu>,
	"Roy Luo" <royluo@google.com>,
	"Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
	"Flavio Suligoi" <f.suligoi@asem.it>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-phy@lists.infradead.org" <linux-phy@lists.infradead.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH v4 4/4] usb: core: add phy notify connect and disconnect
Date: Tue, 9 Jan 2024 12:44:56 +0100	[thread overview]
Message-ID: <2024010925-splendid-thorn-3221@gregkh> (raw)
In-Reply-To: <bdb2c10798124e228b8562576d73b881@realtek.com>

On Tue, Jan 09, 2024 at 02:08:57AM +0000, Stanley Chang[昌育德] wrote:
> Hi Greg,
> 
> Please help review these series of patches.

I was hoping that someone else would review these, which didn't seem to
happen at all, which is odd for something that I thought many others
wanted to see merged.

It will have to wait until after 6.8-rc1 is out.  To also help this out,
please help review other changes that are submitted to the lists as that
will reduce the maintainer load here.

And again, if anyone else cares to see these merged, please help review
them, the Cc: list here is very long...

thanks,

greg k-h

-- 
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy

           reply	other threads:[~2024-01-09 11:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <bdb2c10798124e228b8562576d73b881@realtek.com>]

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=2024010925-splendid-thorn-3221@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=f.suligoi@asem.it \
    --cc=geert+renesas@glider.be \
    --cc=johan+linaro@kernel.org \
    --cc=kishon@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ricardo.canuelo@collabora.com \
    --cc=robh@kernel.org \
    --cc=royluo@google.com \
    --cc=ruanjinjie@huawei.com \
    --cc=stanley_chang@realtek.com \
    --cc=stern@rowland.harvard.edu \
    --cc=vkoul@kernel.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