From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: linux@armlinux.org.uk, linux-arm-kernel@lists.infradead.org,
linuxppc-dev@lists.ozlabs.org, linux-kbuild@vger.kernel.org
Cc: f.fainelli@gmail.com, linux-kernel@vger.kernel.org,
yamada.masahiro@socionext.com,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Subject: [PATCH 0/2] ARM: Introduce multi_v7_lpae_defconfig
Date: Mon, 3 Feb 2020 19:48:17 +0100 [thread overview]
Message-ID: <20200203184820.4433-1-nsaenzjulienne@suse.de> (raw)
This series introduces a new configuration target,
multi_v7_lpae_defconfig, built by merging the config fragment
lpae.config with mult_v7_defconfig. Ultimately needed in order for
Raspberry Pi 4's PCIe bus to work on arm builds, but which may benefit
other boards out there.
---
Changes since RFC:
- Move merge function into the scripts directory.
Nicolas Saenz Julienne (2):
kbuild: Add config fragment merge functionality
ARM: add multi_v7_lpae_defconfig
arch/arm/Makefile | 4 ++++
arch/arm/configs/lpae.config | 1 +
arch/powerpc/Makefile | 12 +-----------
scripts/Makefile.defconf | 15 +++++++++++++++
4 files changed, 21 insertions(+), 11 deletions(-)
create mode 100644 arch/arm/configs/lpae.config
create mode 100644 scripts/Makefile.defconf
--
2.25.0
next reply other threads:[~2020-02-03 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 18:48 Nicolas Saenz Julienne [this message]
2020-02-03 18:48 ` [PATCH 1/2] kbuild: Add config fragment merge functionality Nicolas Saenz Julienne
2020-02-03 18:48 ` [PATCH 2/2] ARM: add multi_v7_lpae_defconfig Nicolas Saenz Julienne
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=20200203184820.4433-1-nsaenzjulienne@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=yamada.masahiro@socionext.com \
/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