devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: linux-usb-owner@vger.kernel.org, Rob Herring <robh@kernel.org>
Cc: pengbo.mu@nxp.com, Mark Rutland <mark.rutland@arm.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-usb@vger.kernel.org,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>,
	Ran Wang <ran.wang_1@nxp.com>
Subject: Re: [PATCH v6 3/4] arm64: dts: dwc3: description of incr burst type
Date: Tue, 02 Oct 2018 10:40:56 +0300	[thread overview]
Message-ID: <877ej0aj93.fsf@linux.intel.com> (raw)
In-Reply-To: <CADRPPNQQE1ESJ5WkMxySstxpaQir-w5XOdiwDe3qTTQ_cim5Xw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 795 bytes --]


Hi,

linux-usb-owner@vger.kernel.org writes:

> On Tue, Jul 24, 2018 at 6:23 PM Rob Herring <robh@kernel.org> wrote:
>>
>> On Mon, Jul 23, 2018 at 06:32:38PM +0800, Pengbo Mu wrote:
>> > Add description of 'snps,incr-burst-type-adjustment' to binding
>> > so that configuring devicetree.
>> >
>> > Signed-off-by: Ran Wang <ran.wang_1@nxp.com>
>> > Signed-off-by: Pengbo Mu <pengbo.mu@nxp.com>
>> > ---
>> >  Documentation/devicetree/bindings/usb/dwc3.txt | 6 ++++++
>> >  1 file changed, 6 insertions(+)
>>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>
> Hi Felipe,
>
> What do you think about this patch?  The patch title prefix should be
> updated from "arm64: dts: dwc3" to "dt-bindings: usb: dwc3" though.

Can you resend the series so I can apply?

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2018-10-02  7:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-23 10:32 [PATCH v6 1/4] usb: dwc3: add global soc bus configuration reg0 Pengbo Mu
2018-07-23 10:32 ` [PATCH v6 2/4] usb: dwc3: Enable undefined length INCR burst type Pengbo Mu
2018-07-23 10:32 ` [PATCH v6 3/4] arm64: dts: dwc3: description of incr " Pengbo Mu
2018-07-24 23:20   ` Rob Herring
2018-09-05 20:52     ` Yang Li
2018-10-02  7:40       ` Felipe Balbi [this message]
2018-07-23 10:32 ` [PATCH v6 4/4] arm: arm64: dts: add property snps incr burst type adjustment Pengbo Mu
2018-07-26 11:10   ` Felipe Balbi
2018-07-31  2:46     ` Pengbo Mu
  -- strict thread matches above, loose matches on Subject: below --
2018-07-23  3:11 [PATCH v6 1/4] usb: dwc3: add global soc bus configuration reg0 Pengbo Mu
2018-07-23  3:11 ` [PATCH v6 3/4] arm64: dts: dwc3: description of incr burst type Pengbo Mu
2018-07-23  3:06 [PATCH v6 1/4] usb: dwc3: add global soc bus configuration reg0 Pengbo Mu
2018-07-23  3:06 ` [PATCH v6 3/4] arm64: dts: dwc3: description of incr burst type Pengbo Mu

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=877ej0aj93.fsf@linux.intel.com \
    --to=balbi@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-owner@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=pengbo.mu@nxp.com \
    --cc=ran.wang_1@nxp.com \
    --cc=robh@kernel.org \
    --cc=will.deacon@arm.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).