From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Doug Anderson <dianders@chromium.org>
Cc: Matthias Kaehlcke <mka@chromium.org>,
Alan Stern <stern@rowland.harvard.edu>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
Mathias Nyman <mathias.nyman@intel.com>,
Felipe Balbi <balbi@kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Krzysztof Kozlowski <krzk@kernel.org>,
Stephen Boyd <swboyd@chromium.org>,
Peter Chen <peter.chen@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Roger Quadros <rogerq@kernel.org>,
Michal Simek <michal.simek@xilinx.com>,
Linux USB List <linux-usb@vger.kernel.org>,
Bastien Nocera <hadess@hadess.net>,
Ravi Chandra Sadineni <ravisadineni@chromium.org>,
Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v20 5/5] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub
Date: Tue, 15 Feb 2022 19:55:17 +0100 [thread overview]
Message-ID: <Ygv3FSDS/fq1oePy@kroah.com> (raw)
In-Reply-To: <CAD=FV=WMP8M5HTRNv9_scvrytbpE0iBdUack=XaHoypGNLJeVA@mail.gmail.com>
On Tue, Feb 15, 2022 at 09:54:54AM -0800, Doug Anderson wrote:
> Hi,
>
> On Tue, Feb 8, 2022 at 11:21 AM Matthias Kaehlcke <mka@chromium.org> wrote:
> >
> > On Tue, Feb 08, 2022 at 11:57:20AM +0100, Greg Kroah-Hartman wrote:
> > > On Wed, Jan 19, 2022 at 12:43:45PM -0800, Matthias Kaehlcke wrote:
> > > > Add nodes for the onboard USB hub on trogdor devices. Remove the
> > > > 'always-on' property from the hub regulator, since the regulator
> > > > is now managed by the onboard_usb_hub driver.
> > > >
> > > > Signed-off-by: Matthias Kaehlcke <mka@chromium.org>
> > > > Reviewed-by: Stephen Boyd <swboyd@chromium.org>
> > > > Reviewed-by: Douglas Anderson <dianders@chromium.org>
> > > > ---
> > >
> > > No DT maintainer approval yet? :(
> >
> > Bjorn usually just picks DT changes into the QCOM tree when they are
> > ready, so I wouldn't interpret anything into the lack of an explicit
> > Ack.
>
> Right, so the expectation is that this patch wouldn't land through the
> USB tree but would instead land through the Qualcomm tree, probably a
> revision after the code lands in the USB tree to avoid dependency
> problems.
But our tools pick up the whole series. I can't just do "i will pick
patches 1-4 only" easily, and neither can any other maintainer.
Why not just get their ack so that I know it can come through the USB
tree? That's what normally happens for other changes like this where a
driver change is required first.
thanks,
greg k-h
next prev parent reply other threads:[~2022-02-15 18:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-19 20:43 [PATCH v20 0/5] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2022-01-19 20:43 ` [PATCH v20 1/5] of/platform: Add stubs for of_platform_device_create/destroy() Matthias Kaehlcke
2022-01-19 20:43 ` [PATCH v20 2/5] driver core: Export device_is_bound() Matthias Kaehlcke
2022-01-20 7:29 ` Christoph Hellwig
2022-01-20 7:45 ` Greg Kroah-Hartman
2022-01-20 15:25 ` Matthias Kaehlcke
2022-01-20 15:36 ` Greg Kroah-Hartman
2022-02-08 0:38 ` Doug Anderson
2022-01-19 20:43 ` [PATCH v20 3/5] usb: misc: Add onboard_usb_hub driver Matthias Kaehlcke
2022-02-08 10:47 ` Greg Kroah-Hartman
2022-02-08 10:56 ` Greg Kroah-Hartman
2022-02-08 19:17 ` Matthias Kaehlcke
2022-02-15 18:02 ` Doug Anderson
2022-01-19 20:43 ` [PATCH v20 4/5] usb: core: hcd: Create platform devices for onboard hubs in probe() Matthias Kaehlcke
2022-01-19 20:43 ` [PATCH v20 5/5] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub Matthias Kaehlcke
2022-02-08 10:57 ` Greg Kroah-Hartman
2022-02-08 19:21 ` Matthias Kaehlcke
2022-02-15 17:54 ` Doug Anderson
2022-02-15 18:55 ` Greg Kroah-Hartman [this message]
2022-02-15 19:03 ` Doug Anderson
2022-02-16 7:36 ` Krzysztof Kozlowski
2022-02-16 19:45 ` Bjorn Andersson
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=Ygv3FSDS/fq1oePy@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=agross@kernel.org \
--cc=balbi@kernel.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=frowand.list@gmail.com \
--cc=hadess@hadess.net \
--cc=krzk@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=michal.simek@xilinx.com \
--cc=mka@chromium.org \
--cc=peter.chen@kernel.org \
--cc=ravisadineni@chromium.org \
--cc=robh+dt@kernel.org \
--cc=rogerq@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=swboyd@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).