From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: defconfig for v4.5 (#2)
Date: Fri, 11 Dec 2015 15:21:42 +0100 [thread overview]
Message-ID: <87io456p6x.fsf@free-electrons.com> (raw)
Hi,
Here is the second pull request for defconfig for mvebu for v4.5.
Gregory
The following changes since commit a0638365f6850855728a5ef5caf2aeab82a58035:
ARM: mvebu: add Kirkwood cpuidle to defconfig (2015-11-30 15:26:45 +0100)
are available in the git repository at:
git://git.infradead.org/linux-mvebu.git tags/mvebu-defconfig-4.5-2
for you to fetch changes up to ab8d80eb5dfd7f4f57364392d746a7700a891e68:
ARM: mvebu: update v5 defconfig for Orion5x machines (2015-12-08 10:55:20 +0100)
----------------------------------------------------------------
mvebu defconfig for 4.5 (part 2)
- Reenable DSA in mvebu_v5_defconfig
- Update multi_v5_defconfig after adding Orion5x to multiarch
----------------------------------------------------------------
Andrew Lunn (5):
ARM: config: Regenerate multi_v5_defconfig
ARM: config: Reenable DSA in multi_v5_defconfig
ARM: config: Add orion5x to multi_v5_defconfig
ARM: mvebu: Reenable DSA in mvebu_v5_defconfig
ARM: mvebu: update v5 defconfig for Orion5x machines
arch/arm/configs/multi_v5_defconfig | 43 +++++++++++++++++++++++++++----------
arch/arm/configs/mvebu_v5_defconfig | 31 +++++++++++++++++++++++++-
2 files changed, 62 insertions(+), 12 deletions(-)
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next reply other threads:[~2015-12-11 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-11 14:21 Gregory CLEMENT [this message]
2015-12-15 16:45 ` [GIT PULL] ARM: mvebu: defconfig for v4.5 (#2) 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=87io456p6x.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;
as well as URLs for NNTP newsgroup(s).