All of lore.kernel.org
 help / color / mirror / Atom feed
From: sudeep.holla@arm.com (Sudeep Holla)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: dts: vexpress: fixes for v4.6
Date: Mon, 14 Mar 2016 09:46:12 +0000	[thread overview]
Message-ID: <56E68864.7020206@arm.com> (raw)
In-Reply-To: <20160313012756.GB5883@localhost>



On 13/03/16 01:27, Olof Johansson wrote:
> On Tue, Mar 08, 2016 at 04:49:02PM +0000, Sudeep Holla wrote:

[...]

>> Update for ARM VExpress platforms
>>
>> Just one update to fix node name unit-address presence/absence mismatch
>> warnings in all the Vexpress device trees.
>
> These kidn of changes can really wait until the next cycle when they
> come in this late; there's already discussion on whether the dtc uprev
> was the right thing to do or not at this time.
>

Ah OK, I was not sure if that will be dropped, hence sent this change.

> So, I'll hold off on this one since there's no other material in this branch.

Sure, I will post this after v4.6 merge window.

-- 
Regards,
Sudeep

      reply	other threads:[~2016-03-14  9:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 16:49 [GIT PULL] ARM: dts: vexpress: fixes for v4.6 Sudeep Holla
2016-03-13  1:27 ` Olof Johansson
2016-03-14  9:46   ` 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=56E68864.7020206@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.