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>,
Andy Gross <agross@codeaurora.org>,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH 1/9] [v3] arm64: defconfig: resynchronize the defconfig
Date: Tue, 9 May 2017 09:12:41 -0500 [thread overview]
Message-ID: <a92fa867-d9ec-f209-ed75-1e1c9cb28308@codeaurora.org> (raw)
In-Reply-To: <1493828280-6620-2-git-send-email-timur@codeaurora.org>
On 05/03/2017 11:17 AM, Timur Tabi wrote:
> Defconfig files become unsynchronized over time as Kconfig entries are
> added, removed, or changed. Making specific changes to the defconfig
> becomes difficult as unrelated differences can interfere. This problem
> is easily remedied:
>
> make defconfig
> make savedefconfig
> cp defconfig arch/arm64/configs/defconfig
> git add arch/arm64/configs/defconfig
> git commit -s <sha>
>
> Signed-off-by: Timur Tabi <timur@codeaurora.org>
At the very least, could SOMEONE please clean up the defconfig in time for
4.12, so that future merges are easier? Like I said earlier, it's very much
out of sync.
I will re-sumbit my defconfig changes for 4.13, but it would be a lot easier
for me to do so if the defconfig is in sync by then.
Thanks.
--
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.
next prev parent reply other threads:[~2017-05-09 14:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 16:17 [PATCH 0/9] [v3] [RESEND] arm64: defconfig: enable several options useful for ARM64 server platforms Timur Tabi
2017-05-03 16:17 ` [PATCH 1/9] [v3] arm64: defconfig: resynchronize the defconfig Timur Tabi
2017-05-09 14:12 ` Timur Tabi [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2017-04-28 21:05 [PATCH 0/9] [v3] arm64: defconfig: enable several options useful for ARM64 server platforms Timur Tabi
2017-04-28 21:05 ` [PATCH 1/9] [v3] arm64: defconfig: resynchronize the defconfig 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=a92fa867-d9ec-f209-ed75-1e1c9cb28308@codeaurora.org \
--to=timur@codeaurora.org \
--cc=agross@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=linux@arm.linux.org.uk \
--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).