From: gregory.clement@free-electrons•com (Gregory CLEMENT)
To: linux-arm-kernel@lists•infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes for v4.12 (#1)
Date: Fri, 02 Jun 2017 11:18:44 +0200 [thread overview]
Message-ID: <878tlarbm3.fsf@free-electrons.com> (raw)
In-Reply-To: <20170601235745.GF13314@localhost> (Olof Johansson's message of "Thu, 1 Jun 2017 16:57:45 -0700")
Hi Olof,
On ven., juin 02 2017, Olof Johansson <olof@lixom•net> wrote:
> On Thu, Jun 01, 2017 at 05:06:35PM +0200, Gregory CLEMENT wrote:
>> Hi,
>>
>> Here is the first pull request for fixes for mvebu for v4.12.
>>
>> Gregory
>>
>> The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d:
>>
>> Linux 4.12-rc2 (2017-05-21 19:30:23 -0700)
>>
>> are available in the git repository at:
>>
>> git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-4.12-1
>
> So, it's really appreciated from our side if you take a look at our tree to see
> what the base for our own fixes branch is, and pick the same or older base for
> your contents.
>
> In this case, we're still at -rc1 and you're on -rc2, so this included
> a backmerge of -rc2 into our branch. It's nice to avoid if we can, but it's
> also not a huge deal.
I used the rc2 as a base because some mvebu related patches I sent close
to the opening of the 4.12 merge windows were merged in 4.12-rc2.
I wanted to avoid future potential conflict on hte fixes branch.
Thanks,
Gregory
>
>
> Merged to fixes.
>
>
> -Olof
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2017-06-02 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:06 [GIT PULL] ARM: mvebu: fixes for v4.12 (#1) Gregory CLEMENT
2017-06-01 23:57 ` Olof Johansson
2017-06-02 9:18 ` Gregory CLEMENT [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=878tlarbm3.fsf@free-electrons.com \
--to=gregory.clement@free-electrons$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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