[GIT,PULL] ARM: actions: dt64 for v4.14

Message ID 20170905223252.9478-2-afaerber@suse.de
State New
Headers show
Series
  • [GIT,PULL] ARM: actions: dt64 for v4.14
Related show

Pull-request

git://git.kernel.org/pub/scm/linux/kernel/git/afaerber/linux-actions.git tags/actions-arm64-dt-for-4.14

Message

Andreas Färber Sept. 5, 2017, 10:32 p.m.
Hi Olof and Arnd,

Here's a (late) dt64 pull for Actions Semi.
This clock node is needed to make use of the new full serial driver.

Regards,
Andreas

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/afaerber/linux-actions.git tags/actions-arm64-dt-for-4.14

for you to fetch changes up to f0e12dd55384d5ef53c6e15673d39133dfca5f0a:

  arm64: dts: actions: s900-bubblegum-96: Add fake uart5 clock (2017-09-06 00:14:38 +0200)

----------------------------------------------------------------
Actions Semi ARM64 based SoC DT for 4.14

This updates the Bubblegum-64 DT with a clock node for the debug UART.

----------------------------------------------------------------
Andreas Färber (1):
      arm64: dts: actions: s900-bubblegum-96: Add fake uart5 clock

 arch/arm64/boot/dts/actions/s900-bubblegum-96.dts | 7 +++++++
 1 file changed, 7 insertions(+)

Comments

Olof Johansson Sept. 15, 2017, 9:58 p.m. | #1
On Tue, Sep 5, 2017 at 3:32 PM, Andreas Färber <afaerber@suse.de> wrote:
> Hi Olof and Arnd,
>
> Here's a (late) dt64 pull for Actions Semi.
> This clock node is needed to make use of the new full serial driver.
>
> Regards,
> Andreas
>
> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>
>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>
> are available in the git repository at:
>
>   git://git.kernel.org/pub/scm/linux/kernel/git/afaerber/linux-actions.git tags/actions-arm64-dt-for-4.14
>
> for you to fetch changes up to f0e12dd55384d5ef53c6e15673d39133dfca5f0a:
>
>   arm64: dts: actions: s900-bubblegum-96: Add fake uart5 clock (2017-09-06 00:14:38 +0200)

Merged into next/late. Thanks!


-Olof
Andreas Färber Nov. 4, 2017, 9:34 a.m. | #2
Hi Olof,

Am 16.09.2017 um 05:58 schrieb Olof Johansson:
> On Tue, Sep 5, 2017 at 3:32 PM, Andreas Färber <afaerber@suse.de> wrote:
>> Hi Olof and Arnd,
>>
>> Here's a (late) dt64 pull for Actions Semi.
>> This clock node is needed to make use of the new full serial driver.
>>
>> Regards,
>> Andreas
>>
>> The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:
>>
>>   Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/afaerber/linux-actions.git tags/actions-arm64-dt-for-4.14
>>
>> for you to fetch changes up to f0e12dd55384d5ef53c6e15673d39133dfca5f0a:
>>
>>   arm64: dts: actions: s900-bubblegum-96: Add fake uart5 clock (2017-09-06 00:14:38 +0200)
> 
> Merged into next/late. Thanks!

Hmm, this has still not shown up in linux.git and disappeared in
linux-next.git - did this get lost? Do I need to resubmit this for 4.15?

Same issue with 32-bit dt pull.

Holding back three 4.15 pulls due to this.

Regards,
Andreas
Andreas Färber Nov. 4, 2017, 12:06 p.m. | #3
Am 04.11.2017 um 17:49 schrieb Arnd Bergmann:
> On Nov 4, 2017 10:34, "Andreas Färber" <afaerber@suse.de
> <mailto:afaerber@suse.de>> wrote:
> 
>     Hi Olof,
> 
>     Am 16.09.2017 um 05:58 schrieb Olof Johansson:
>     > On Tue, Sep 5, 2017 at 3:32 PM, Andreas Färber <afaerber@suse.de
>     <mailto:afaerber@suse.de>> wrote:
>     >> Hi Olof and Arnd,
>     >>
>     >> Here's a (late) dt64 pull for Actions Semi.
>     >> This clock node is needed to make use of the new full serial driver.
> 
> 
> 
> Please let us know earlier when you see problems. It missed the 4.14
> window since that late branch ended up being too late for us. We should
> have communicated this better, but we expected you to resend the
> contents for 4.15  early on. 

Sorry, when I read "merged" I consider that contents out of my hands -
and for 4.13 Linus complained about our elaborate drivers->soc merge.

Also I'm five weeks out of the office this merge window and it's been as
surprising as Christmas to see an -rc7 tagged already. ;)

> Also, don't hold back new content while you wait for other stuff to get
> merges, just keep the pull requests coming so we know what's going on.

Well, that didn't quite apply here, branches based on v4.14-rc1 vs.
v4.13-rc1 would cause merge conflicts. When based on the same tag, sure.

> If you send the full set of pull requests now and we get an -rc8
> tomorrow, we might still merge it all for 4.15, otherwise please resend
> it for 4.16 after the merge window.
Understood. I've updated for-next and sent out 4.15 pulls for Actions
(and Realtek) as good as I could from my hotel. If they don't make
v4.15-rc1 I'll rebase them and send immediate 4.16 pulls, with any
regular 4.16 contents going into a second round then.

I've tried to avoid sending you single-patch pulls, but on the other
hand waiting for the full patches to finish review for inclusion has not
been working well either.

Regards,
Andreas