linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] arm64: Juno: Add support for PCIe or R1 board
Date: Tue, 27 Oct 2015 08:55:05 +0900	[thread overview]
Message-ID: <20151026235505.GA13221@localhost> (raw)
In-Reply-To: <20151026101256.GF963@e106497-lin.cambridge.arm.com>

Hi,

On Mon, Oct 26, 2015 at 10:12:57AM +0000, Liviu Dudau wrote:
> On Fri, Oct 23, 2015 at 10:42:53PM +0200, Arnd Bergmann wrote:
> > On Wednesday 21 October 2015 12:36:29 Liviu Dudau wrote:
> > > The following changes since commit 25cb62b76430a91cc6195f902e61c2cb84ade622:
> > > 
> > >   Linux 4.3-rc5 (2015-10-11 11:09:45 -0700)
> > > 
> > > are available in the git repository at:
> > > 
> > > 
> > 
> > Not pulled.
> > 
> > All our branches are based on -rc4 or earlier, and we'd like to avoid
> > backmerges from mainline if at all possible.
> > 
> > Can you rebase this to -rc4 and send again?
> > 
> > 	Arnd
> 
> Sure, I've rebased the branch on top of -rc4 now, so here is the new request.
> 
> Many thanks,
> Liviu
> 
> The following changes since commit 049e6dde7e57f0054fdc49102e7ef4830c698b46:
> 
>   Linux 4.3-rc4 (2015-10-04 16:57:17 +0100)
> 
> are available in the git repository at:
> 
>   git://linux-arm.org/linux-ld for-upstream/juno-pcie

This is showing up late by now, but Juno also isn't a high-volume platform
so exposure to regressions are limited.

That being said, I really hope we won't have to pick up any fixes for
this due to lack of exposure to -next after the merge window.


Merged into next/arm64.


Thanks,

-Olof

  reply	other threads:[~2015-10-26 23:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-21 11:36 [GIT PULL] arm64: Juno: Add support for PCIe or R1 board Liviu Dudau
2015-10-23 20:42 ` Arnd Bergmann
2015-10-26 10:12   ` Liviu Dudau
2015-10-26 23:55     ` Olof Johansson [this message]
2015-10-27 10:12       ` Liviu Dudau
2015-10-29  9:21         ` Kevin Hilman
2015-10-29  9:44           ` Liviu Dudau

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=20151026235505.GA13221@localhost \
    --to=olof@lixom.net \
    --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 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).