From: Rob Herring <robh@kernel.org>
To: Pawel Laszczak <pawell@cadence.com>
Cc: devicetree@vger.kernel.org, gregkh@linuxfoundation.org,
felipe.balbi@linux.intel.com, mark.rutland@arm.com,
linux-usb@vger.kernel.org, hdegoede@redhat.com,
heikki.krogerus@linux.intel.com, andy.shevchenko@gmail.com,
robh+dt@kernel.org, rogerq@ti.com, linux-kernel@vger.kernel.org,
jbergsagel@ti.com, nsekhar@ti.com, nm@ti.com,
sureshp@cadence.com, peter.chen@nxp.com, kurahul@cadence.com,
Pawel Laszczak <pawell@cadence.com>
Subject: Re: [PATCH v4 1/6] dt-bindings: add binding for USBSS-DRD controller.
Date: Mon, 18 Feb 2019 10:46:09 -0600 [thread overview]
Message-ID: <20190218164609.GA2649@bogus> (raw)
In-Reply-To: <1550173514-23573-2-git-send-email-pawell@cadence.com>
On Thu, 14 Feb 2019 19:45:09 +0000, Pawel Laszczak wrote:
> This patch aim at documenting USB related dt-bindings for the
> Cadence USBSS-DRD controller.
>
> Signed-off-by: Pawel Laszczak <pawell@cadence.com>
> ---
> .../devicetree/bindings/usb/cdns-usb3.txt | 30 +++++++++++++++++++
> 1 file changed, 30 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/usb/cdns-usb3.txt
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2019-02-18 16:46 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 19:45 [PATCH v4 0/6] Introduced new Cadence USBSS DRD Driver Pawel Laszczak
2019-02-14 19:45 ` [PATCH v4 1/6] dt-bindings: add binding for USBSS-DRD controller Pawel Laszczak
2019-02-18 16:46 ` Rob Herring [this message]
2019-02-14 19:45 ` [PATCH v4 2/6] usb:common Separated decoding functions from dwc3 driver Pawel Laszczak
2019-02-19 13:14 ` Greg KH
2019-02-20 6:28 ` Pawel Laszczak
2019-02-14 19:45 ` [PATCH v4 3/6] usb:common Patch simplify usb_decode_set_clear_feature function Pawel Laszczak
2019-02-14 19:45 ` [PATCH v4 4/6] usb:common Simplify usb_decode_get_set_descriptor function Pawel Laszczak
2019-02-14 19:45 ` [PATCH v4 5/6] usb:cdns3 Add Cadence USB3 DRD Driver Pawel Laszczak
2019-02-15 9:57 ` Chunfeng Yun
2019-03-04 11:01 ` Pawel Laszczak
2019-03-04 12:46 ` Pawel Laszczak
2019-03-05 1:42 ` Chunfeng Yun
2019-02-19 13:24 ` Greg KH
2019-03-04 9:23 ` Pawel Laszczak
2019-02-20 13:04 ` Roger Quadros
2019-03-07 5:37 ` Pawel Laszczak
2019-03-11 11:53 ` Roger Quadros
2019-03-28 6:05 ` Pawel Laszczak
2019-02-21 9:22 ` Peter Chen
2019-03-07 9:52 ` Pawel Laszczak
2019-03-12 3:44 ` Peter Chen
2019-03-28 8:26 ` Pawel Laszczak
2019-02-14 19:45 ` [PATCH v4 6/6] usb:cdns3 Fix for stuck packets in on-chip OUT buffer Pawel Laszczak
2019-02-20 10:24 ` Roger Quadros
2019-02-20 11:18 ` Pawel Laszczak
2019-02-20 13:17 ` Roger Quadros
2019-02-20 15:50 ` Pawel Laszczak
2019-02-21 7:14 ` Felipe Balbi
2019-03-04 10:25 ` Roger Quadros
2019-03-07 7:06 ` Pawel Laszczak
2019-03-07 9:13 ` Roger Quadros
2019-03-11 8:15 ` Peter Chen
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=20190218164609.GA2649@bogus \
--to=robh@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=felipe.balbi@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=jbergsagel@ti.com \
--cc=kurahul@cadence.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=pawell@cadence.com \
--cc=peter.chen@nxp.com \
--cc=robh+dt@kernel.org \
--cc=rogerq@ti.com \
--cc=sureshp@cadence.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).