Message ID | 87d1ansq6c.fsf@free-electrons.com |
---|---|
State | New |
Headers | show |
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. Merged to fixes. -Olof
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