From: Simon Horman <horms@verge.net.au>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Geert Uytterhoeven" <geert@linux-m68k.org>,
"Kuninori Morimoto" <kuninori.morimoto.gx@renesas.com>,
"Magnus Damm" <magnus.damm@gmail.com>,
"USB list" <linux-usb@vger.kernel.org>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
Subject: Re: [PATCH v2 2/2] dt-bindings: usb: renesas_gen3: Rename bindings documentation file
Date: Thu, 1 Aug 2019 11:14:22 +0200 [thread overview]
Message-ID: <20190801091421.4gf3xggg3eko6wql@verge.net.au> (raw)
In-Reply-To: <TYAPR01MB4544A8358DE51BFB1193287CD8DD0@TYAPR01MB4544.jpnprd01.prod.outlook.com>
On Mon, Jul 29, 2019 at 08:25:24AM +0000, Yoshihiro Shimoda wrote:
> Hi Simon-san,
>
> > From: Simon Horman, Sent: Monday, July 29, 2019 5:15 PM
> <snip>
> > > > > > Unfortunately the previous version has already made it into usb-next
> > > > > > 23c46801d14cb647 dt-bindings: usb: renesas_gen3: Rename bindings
> > > > > > documentation file
> > > > >
> > > > > Ok, I guess we should go with that version.
> > > >
> > > > So can you resend this series based on 5.3-rc1 so I know what to apply?
> > >
> > > Since your usb-testing branch already has it which is merged from Felipe's usb-next branch,
> > > I don't think Simon has to resend this series.
> > >
> > > https://www.spinics.net/lists/linux-usb/msg182103.html
> >
> > Thanks and sorry for the confusion.
> >
> > In v5.2-rc1 we had:
> >
> > devicetree/bindings/usb/renesas_usb3.txt
> > devicetree/bindings/usb/renesas_usbhs.txt
> >
> >
> > In v5.3-rc1 we have:
> >
> > devicetree/bindings/usb/renesas,usb3.txt
> > devicetree/bindings/usb/renesas,usbhs.txt
> >
> > Which reflects v1 of this patchset. And I think this is an improvement.
> >
> > Shimoda-san, can you let me know if you would like me to rebase v2
> > on v5.3-rc1? That would would give us:
> >
> > devicetree/bindings/usb/renesas,usb3-peri.txt
> > devicetree/bindings/usb/renesas,usbhs.txt [unchanged]
>
> Thank you for the detail. I would like you to rebase v2 like that, if possible.
Thanks, I have posted this as:
[PATCH] dt-bindings: usb: renesas_gen3: Rename bindings documentation file to reflect IP block
prev parent reply other threads:[~2019-08-01 9:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 8:35 [PATCH v2 0/2] dt-bindings: usb: renease_{usbhs,gen3} Rename bindings documentation files Simon Horman
2019-07-03 8:35 ` [PATCH v2 1/2] dt-bindings: usb: renesas_usbhs: Rename bindings documentation file Simon Horman
2019-07-03 8:35 ` [PATCH v2 2/2] dt-bindings: usb: renesas_gen3: " Simon Horman
2019-07-03 12:28 ` Geert Uytterhoeven
2019-07-11 8:03 ` Simon Horman
2019-07-25 9:09 ` Greg Kroah-Hartman
2019-07-26 1:22 ` Yoshihiro Shimoda
2019-07-29 8:14 ` Simon Horman
2019-07-29 8:25 ` Yoshihiro Shimoda
2019-08-01 9:14 ` Simon Horman [this message]
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=20190801091421.4gf3xggg3eko6wql@verge.net.au \
--to=horms@verge.net.au \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mark.rutland@arm.com \
--cc=niklas.soderlund+renesas@ragnatech.se \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.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).