linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Timur Tabi <timur@codeaurora.org>
To: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-next@vger.kernel.org,
	Gregory CLEMENT <gregory.clement@free-electrons.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will.deacon@arm.com>, Arnd Bergmann <arnd@arndb.de>
Cc: timur@codeaurora.org
Subject: [PATCH 0/9] [v3] [RESEND] arm64: defconfig: enable several options useful for ARM64 server platforms
Date: Wed,  3 May 2017 11:17:51 -0500	[thread overview]
Message-ID: <1493828280-6620-1-git-send-email-timur@codeaurora.org> (raw)

ACPI-based ARM64 server platforms based, like the Qualcomm Datacenter
Technologies QDF2400, need several features and drivers enabled for
full functionality.  This patchset enables many of those features.

The first patch, "resynchronize the defconfig" refreshes the ARM64
defconfig so that it's aligned with savedefconfig.  This needs to be
done periodically, so that new patches avoid merge conflicts.  

If the first patch does not apply cleanly, I ask the maintainer to 
refresh it himself manually, following the instructions in the commit
message.  The remaining 8 patches should apply cleanly on top of that.

Timur Tabi (9):
  [v3] arm64: defconfig: resynchronize the defconfig
  arm64: defconfig: enable ACPI_CPPC_CPUFREQ
  arm64: defconfig: enable BLK_DEV_NVME
  [v2] arm64: defconfig: enable EFI_CAPSULE_LOADER
  arm64: defconfig: enable support for PCIe hotplug
  arm64: defconfig: enable APEI and GHES features
  [v2] arm64: defconfig: enable EDAC options
  arm64: defconfig: enable QCOM_L2_PMU and QCOM_L3_PMU
  arm64: defconfig: enable the Qualcomm Technologies EMAC Ethernet
    driver

 arch/arm64/configs/defconfig | 116 ++++++++++++++++++++-----------------------
 1 file changed, 55 insertions(+), 61 deletions(-)

-- 
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm
Technologies, Inc.  Qualcomm Technologies, Inc. is a member of the
Code Aurora Forum, a Linux Foundation Collaborative Project.

             reply	other threads:[~2017-05-03 16:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-03 16:17 Timur Tabi [this message]
2017-05-03 16:17 ` [PATCH 1/9] [v3] arm64: defconfig: resynchronize the defconfig Timur Tabi
2017-05-09 14:12   ` Timur Tabi
2017-05-03 16:17 ` [PATCH 2/9] arm64: defconfig: enable ACPI_CPPC_CPUFREQ Timur Tabi
2017-05-03 16:17 ` [PATCH 3/9] arm64: defconfig: enable BLK_DEV_NVME Timur Tabi
2017-05-03 16:17 ` [PATCH 4/9] [v2] arm64: defconfig: enable EFI_CAPSULE_LOADER Timur Tabi
2017-05-03 16:17 ` [PATCH 5/9] arm64: defconfig: enable support for PCIe hotplug Timur Tabi
2017-05-03 16:17 ` [PATCH 6/9] arm64: defconfig: enable APEI and GHES features Timur Tabi
2017-05-03 16:17 ` [PATCH 7/9] [v2] arm64: defconfig: enable EDAC options Timur Tabi
2017-05-03 16:17 ` [PATCH 8/9] arm64: defconfig: enable QCOM_L2_PMU and QCOM_L3_PMU Timur Tabi
2017-05-03 16:18 ` [PATCH 9/9] arm64: defconfig: enable the Qualcomm Technologies EMAC Ethernet driver Timur Tabi

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=1493828280-6620-1-git-send-email-timur@codeaurora.org \
    --to=timur@codeaurora.org \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=catalin.marinas@arm.com \
    --cc=gregory.clement@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=will.deacon@arm.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;
as well as URLs for NNTP newsgroup(s).