All of lore.kernel.org
 help / color / mirror / Atom feed
From: xuwei5@hisilicon.com (Wei Xu)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL]arm64: dts: hisilicon: hi6220 updates for 4.8(#2)
Date: Thu, 14 Jul 2016 16:04:26 +0100	[thread overview]
Message-ID: <5787A9FA.9060704@hisilicon.com> (raw)
In-Reply-To: <4529903.blvXMCdknS@wuerfel>

Hi Arnd,

On 14/07/2016 14:58, Arnd Bergmann wrote:
> On Thursday, July 7, 2016 2:51:44 PM CEST Wei Xu wrote:
>> Hi Arnd, Hi Olof, Hi Kevin,
>>
>> I know the walkaround for this kind of patch is still under discussion.
>> Could you please consider to pull the following changes?
>>
>> This depends on the change in clk tree (clk-hi6220-rtc)
>> which is already in the clk-next.
>>
>> And for easier grepping through history, below is the pull request
>> for the dts specific change (no clk commits):
>>
> 
> Pulled into next/late, thanks!

Thanks!

Best Regards,
Wei

> 
> 	Arnd
> 
> 
> .
> 

      reply	other threads:[~2016-07-14 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-07 13:51 [GIT PULL]arm64: dts: hisilicon: hi6220 updates for 4.8(#2) Wei Xu
2016-07-07 14:04 ` Arnd Bergmann
2016-07-07 14:20   ` Wei Xu
2016-07-14 13:58 ` Arnd Bergmann
2016-07-14 15:04   ` Wei Xu [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=5787A9FA.9060704@hisilicon.com \
    --to=xuwei5@hisilicon.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.