From: Rob Herring <robh@kernel.org>
To: Gregory CLEMENT <gregory.clement@bootlin.com>
Cc: Cristian Birsan <cristian.birsan@microchip.com>,
Felipe Balbi <balbi@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
Ludovic Desroches <ludovic.desroches@microchip.com>,
linux-arm-kernel@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Gregory CLEMENT <gregory.clement@bootlin.com>
Subject: Re: [PATCH 2/3] dt-bindings: usb: atmel: Mark EP child node as deprecated
Date: Wed, 13 Nov 2019 19:30:57 -0600 [thread overview]
Message-ID: <20191114013057.GA20150@bogus> (raw)
In-Reply-To: <20191107153128.11038-3-gregory.clement@bootlin.com>
On Thu, 7 Nov 2019 16:31:27 +0100, Gregory CLEMENT wrote:
> There is no need to describe the end point in the deice tree. These
> properties won't be use anymore, so mark them as deprecated to keep
> the old device tree documented.
>
> Signed-off-by: Gregory CLEMENT <gregory.clement@bootlin.com>
> ---
> .../devicetree/bindings/usb/atmel-usb.txt | 56 +------------------
> 1 file changed, 3 insertions(+), 53 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-11-14 1:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-07 15:31 [PATCH 0/3] Remove the USB EP configuration from device tree Gregory CLEMENT
2019-11-07 15:31 ` [PATCH 1/3] usb: gadget: udc: atmel: Don't use DT to configure end point Gregory CLEMENT
2019-11-22 14:50 ` Gregory CLEMENT
2019-11-22 16:02 ` Cristian.Birsan
2019-11-07 15:31 ` [PATCH 2/3] dt-bindings: usb: atmel: Mark EP child node as deprecated Gregory CLEMENT
2019-11-14 1:30 ` Rob Herring [this message]
2019-11-07 15:31 ` [PATCH 3/3] ARM: dts: at91: Remove the USB EP child node Gregory CLEMENT
2019-11-22 17:22 ` Robin Murphy
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=20191114013057.GA20150@bogus \
--to=robh@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=balbi@kernel.org \
--cc=cristian.birsan@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=gregory.clement@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--cc=stern@rowland.harvard.edu \
--cc=thomas.petazzoni@bootlin.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).