From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: fixes for v4.10 (#1)
Date: Thu, 02 Feb 2017 18:46:26 +0100 [thread overview]
Message-ID: <87shnwwknh.fsf@free-electrons.com> (raw)
In-Reply-To: <87y3xrz5ir.fsf@free-electrons.com> (Gregory CLEMENT's message of "Tue, 31 Jan 2017 15:08:12 +0100")
Hi Arnd,
On mar., janv. 31 2017, Gregory CLEMENT <gregory.clement@free-electrons.com> wrote:
> Hi,
>
> Here is the first pull request for fixes for mvebu for v4.10.
>
> Initially I applied them on mvebu/dt byt finally they looked more
> appropriate for fixes.
>
> Gregory
>
> The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:
>
> Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)
>
> are available in the git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-4.10-1
>
> for you to fetch changes up to 6cfd3cd8d8365cf78db1d25cd276d3d900eb8541:
>
> ARM: dts: orion5x-lschl: More consistent naming on linkstation series (2017-01-31 12:19:33 +0100)
>
> ----------------------------------------------------------------
> mvebu fixes for 4.10 (part 1)
>
> More consistent naming for some orion5x based boards helping the
> switch to device tree for debian users.
>
> ----------------------------------------------------------------
> Roger Shimizu (2):
> ARM: dts: orion5x-lschl: Fix model name
> ARM: dts: orion5x-lschl: More consistent naming on linkstation series
>
> .../arm/boot/dts/{orion5x-lschl.dts => orion5x-linkstation-lschl.dts} | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> rename arch/arm/boot/dts/{orion5x-lschl.dts => orion5x-linkstation-lschl.dts} (98%)
As requested this is a new version of first pull request for fixes for
mvebu for v4.10.
Gregory
The following changes since commit 0c744ea4f77d72b3dcebb7a8f2684633ec79be88:
Linux 4.10-rc2 (2017-01-01 14:31:53 -0800)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/mvebu-fixes-4.10-1
for you to fetch changes up to 1a902f6b70c55171ca2419d946b85274e35c9757:
ARM: orion5x: fix Makefile for linkstation-lschl.dtb (2017-02-02 18:40:04 +0100)
----------------------------------------------------------------
mvebu fixes for 4.10 (part 1)
More consistent naming for some orion5x based boards helping the
switch to device tree for debian users.
----------------------------------------------------------------
Arnd Bergmann (1):
ARM: orion5x: fix Makefile for linkstation-lschl.dtb
Roger Shimizu (2):
ARM: dts: orion5x-lschl: Fix model name
ARM: dts: orion5x-lschl: More consistent naming on linkstation series
arch/arm/boot/dts/Makefile | 2 +-
.../arm/boot/dts/{orion5x-lschl.dts => orion5x-linkstation-lschl.dts} | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
rename arch/arm/boot/dts/{orion5x-lschl.dts => orion5x-linkstation-lschl.dts} (98%)
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2017-02-02 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 14:08 [GIT PULL] ARM: mvebu: fixes for v4.10 (#1) Gregory CLEMENT
2017-02-02 17:46 ` Gregory CLEMENT [this message]
2017-02-06 16:36 ` Arnd Bergmann
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=87shnwwknh.fsf@free-electrons.com \
--to=gregory.clement@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox