devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Local user for Liviu Dudau <liviu.dudau@arm.com>,
	Robin Murphy <robin.murphy@arm.com>
Cc: devicetree@vger.kernel.org, lorenzo.pieralisi@arm.com,
	linux-arm-kernel@lists.infradead.org,
	Sudeep Holla <sudeep.holla@arm.com>
Subject: Re: [PATCH 3/3] arm64: dts: juno: Remove Motherboard USB node
Date: Wed, 18 Jan 2017 14:18:10 +0000	[thread overview]
Message-ID: <61d3b621-bb47-c59b-d89f-07636ef8408c@arm.com> (raw)
In-Reply-To: <20170118123802.GE995@e110455-lin.cambridge.arm.com>



On 18/01/17 12:38, Local user for Liviu Dudau wrote:
> Hi Robin,
> 
> On Wed, Jan 18, 2017 at 12:12:52PM +0000, Robin Murphy wrote:
>> The first batch of Juno boards included a discrete USB controller chip
>> as a contingency in case of issues with the USB 2.0 IP integrated into
>> the SoC. As it turned out, the latter was fine, and to the best of my
>> knowledge the motherboard USB was never even brought up and validated.
>>
>> Since this also isn't present on later boards, and uses a compatible
>> string undocumented and unmatched by any driver in the kernel, let's
>> just tidy it away for ever to avoid any confusion.
>>
>> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> 
> For all 3 patches:
> 
> Acked-by: Liviu Dudau <Liviu.Dudau@arm.com>
> 

Thanks Liviu (or/and Local user for Liviu Dudau :))

All 3 patches applied to [1]

-- 
Regards,
Sudeep

[1] git.kernel.org/sudeep.holla/linux/h/for-next/updates/juno

      reply	other threads:[~2017-01-18 14:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-18 12:12 [PATCH 1/3] arm64: dts: juno: Add dma-ranges property Robin Murphy
     [not found] ` <74595d6d866518db7cfabc39b4cf9b54d3be9bde.1484741104.git.robin.murphy-5wv7dgnIgG8@public.gmane.org>
2017-01-18 12:12   ` [PATCH 2/3] arm64: dts: juno: Add ETR SMMU power domain Robin Murphy
2017-01-18 12:12   ` [PATCH 3/3] arm64: dts: juno: Remove Motherboard USB node Robin Murphy
2017-01-18 12:38     ` Local user for Liviu Dudau
2017-01-18 14:18       ` Sudeep Holla [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=61d3b621-bb47-c59b-d89f-07636ef8408c@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=liviu.dudau@arm.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=robin.murphy@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).