All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregory.clement@free-electrons.com (Gregory CLEMENT)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: arm for v4.18 (#1)
Date: Thu, 17 May 2018 14:59:42 +0200	[thread overview]
Message-ID: <87603m1lq9.fsf@bootlin.com> (raw)

Hi,

Here is the first pull request for arm for mvebu for v4.18.

As I feared, there were (trivial) merge issues due to the defconfig
update in linux-next. The best place to solve them is in your tree, so
as soon as you will pull this, I will remove from my mvebu/for-next
branch.

Gregory

The following changes since commit 60cc43fc888428bb2f18f08997432d426a243338:

  Linux 4.17-rc1 (2018-04-15 18:24:20 -0700)

are available in the Git repository at:

  git://git.infradead.org/linux-mvebu.git tags/mvebu-arm-4.18-1

for you to fetch changes up to 95fbfe2f63d0838fed56d2f93604f205719bc51c:

  ARM: multi_v7_defconfig: Add Marvell NAND controller support (2018-05-16 19:38:34 +0200)

----------------------------------------------------------------
mvebu arm for 4.18 (part 1)

Updating multi_v7_defconfig and adding marvell NAND controller
support.

----------------------------------------------------------------
Gregory CLEMENT (2):
      ARM: multi_v7_defconfig: Update with current configuration
      ARM: multi_v7_defconfig: Add Marvell NAND controller support

 arch/arm/configs/multi_v7_defconfig | 369 +++++++++++++++---------------------
 1 file changed, 153 insertions(+), 216 deletions(-)

             reply	other threads:[~2018-05-17 12:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 12:59 Gregory CLEMENT [this message]
2018-05-25 11:57 ` [GIT PULL] ARM: mvebu: arm for v4.18 (#1) Olof Johansson
2018-05-28 15:13   ` Gregory CLEMENT

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=87603m1lq9.fsf@bootlin.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.