From: Vinod Koul <vkoul@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Heiko Stuebner <heiko@sntech.de>,
Yifeng Zhao <yifeng.zhao@rock-chips.com>,
Johan Jonker <jbx6244@gmail.com>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>,
Michael Riesch <michael.riesch@wolfvision.net>,
Rob Herring <robh@kernel.org>,
devicetree <devicetree@vger.kernel.org>,
arm-mail-list <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v4 1/8] dt-bindings: soc: grf: fix rk3568 usb definitions
Date: Wed, 2 Mar 2022 19:52:33 +0530 [thread overview]
Message-ID: <Yh99qVeALFN3X9te@matsya> (raw)
In-Reply-To: <CAMdYzYrkDbr5mHYmAbqBoJJEKH8A5xXfRNuTiTn8q40vRJeCgA@mail.gmail.com>
On 02-03-22, 07:18, Peter Geis wrote:
> On Wed, Mar 2, 2022 at 3:16 AM Vinod Koul <vkoul@kernel.org> wrote:
> >
> > On 01-03-22, 09:52, Peter Geis wrote:
> > > Good Morning,
> > >
> > > Would it be possible to pull this patch individually, to fix the
> > > current error reported by Rob?
> >
> > This does not apply for me on phy-next. What was this based on..?
>
> This is based on linux-next, which the applicable patch was accepted on 24 Feb.
> The original patch was correct, but it seems a merge error happened
> and these two lines were moved into an incorrect location.
> This patch corrects that, but I see on the original patch chain you
> are discussing reverting and reapplying to fix it.
Ok let me revert than so that it is easy for everyone to fix up
Thanks
--
~Vinod
next prev parent reply other threads:[~2022-03-02 14:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-28 13:56 [PATCH v4 0/8] enable usb support on rk356x Peter Geis
2022-02-28 13:56 ` [PATCH v4 1/8] dt-bindings: soc: grf: fix rk3568 usb definitions Peter Geis
2022-03-01 14:52 ` Peter Geis
2022-03-02 8:16 ` Vinod Koul
2022-03-02 12:18 ` Peter Geis
2022-03-02 14:22 ` Vinod Koul [this message]
2022-02-28 13:56 ` [PATCH v4 2/8] dt-bindings: soc: grf: add rk3566-pipe-grf compatible Peter Geis
2022-03-07 23:10 ` Rob Herring
2022-02-28 13:56 ` [PATCH v4 3/8] dt-bindings: usb: add rk3568 compatible to rockchip, dwc3 Peter Geis
2022-03-07 23:10 ` Rob Herring
2022-02-28 13:56 ` [PATCH v4 4/8] soc: rockchip: set dwc3 clock for rk3566 Peter Geis
2022-02-28 13:56 ` [PATCH v4 5/8] usb: dwc3: core: do not use 3.0 clock when operating in 2.0 mode Peter Geis
2022-02-28 13:56 ` [PATCH v4 6/8] arm64: dts: rockchip: add rk356x dwc3 usb3 nodes Peter Geis
2022-03-03 16:05 ` Aw: " Frank Wunderlich
2022-02-28 13:56 ` [PATCH v4 7/8] arm64: dts: rockchip: enable dwc3 on quartz64-a Peter Geis
2022-02-28 13:56 ` [PATCH v4 8/8] arm64: dts: rockchip: add usb3 support to rk3568-evb1-v10 Peter Geis
2022-03-01 14:30 ` [PATCH v4 0/8] enable usb support on rk356x Michael Riesch
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=Yh99qVeALFN3X9te@matsya \
--to=vkoul@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jbx6244@gmail.com \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=yifeng.zhao@rock-chips.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;
as well as URLs for NNTP newsgroup(s).