From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: mvebu: arm for v4.19 (#1)
Date: Sat, 14 Jul 2018 14:42:08 -0700 [thread overview]
Message-ID: <20180714214208.lns2fszqzm6m3q4g@localhost> (raw)
In-Reply-To: <87y3egbe7a.fsf@bootlin.com>
On Thu, Jul 12, 2018 at 06:39:53PM +0200, Gregory CLEMENT wrote:
> Hi,
>
> Here is the first pull request for arm for mvebu for v4.19.
>
> Gregory
>
> The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
>
> Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
>
> are available in the Git repository at:
>
> git://git.infradead.org/linux-mvebu.git tags/mvebu-arm-4.19-1
>
> for you to fetch changes up to 432c0254106a373bcc23b1bd3e0b7eb56929c0d9:
>
> ARM: mvebu_v7_defconfig: enable SFP support (2018-06-28 16:53:08 +0200)
>
> ----------------------------------------------------------------
> mvebu arm for 4.19 (part 1)
>
> defconfig update:
> - add NAND controller on multi_v7
> - add SFP support on mvebu_v7
> code improvement:
> - remove potential call from invalid context in boot_secondary
> - allow using CONFIG_FORTIFY_SOURCE in pmsu.c
Please separate out soc and defconfig changes to separate branches/pull
requests. If you look at our tree, you'll see that we queue them in
separate branches.
Also, note that we renoramlized the configs in 4.18-rc3, so you want to base
the DT contents on top of that when you send the new pull requests.
Thanks,
-Olof
next prev parent reply other threads:[~2018-07-14 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-12 16:39 [GIT PULL] ARM: mvebu: arm for v4.19 (#1) Gregory CLEMENT
2018-07-14 21:42 ` Olof Johansson [this message]
2018-07-18 15:02 ` Gregory CLEMENT
2018-07-18 15:38 ` Olof Johansson
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=20180714214208.lns2fszqzm6m3q4g@localhost \
--to=olof@lixom.net \
--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