From: Trevor Woerner <twoerner@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: soc@kernel.org, linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/1] ARM: defconfig: cleanup orphaned CONFIGs
Date: Tue, 19 Sep 2023 08:51:10 -0400 [thread overview]
Message-ID: <20230919125112.15515-1-twoerner@gmail.com> (raw)
Drop CONFIG_ options from defconfigs whose code has been removed.
v4:
Re-submit the ARM patch (alone) with a better subject line and CC'ing the
correct people to help ensure it gets picked up. v4 drops the patches for
mips, powerpc, and loongarch which have already been applied.
v3:
While reorganizing the patches, I put the wrong commit message with the
CONFIG_IP_NF_TARGET_CLUSTERIP option.
v2:
Generate arch-specific patches. In v1 I organized the patches by
CONFIG_ option which caused some of the patches to cross architectural
lines. This requires cross-arch consensus before they can be applied.
Therefore organize the changes by architecture so each one can apply them
independently (or not).
Trevor Woerner (1):
ARM: defconfig: cleanup orphaned CONFIGs
arch/arm/configs/keystone_defconfig | 1 -
arch/arm/configs/multi_v7_defconfig | 1 -
arch/arm/configs/omap2plus_defconfig | 8 --------
3 files changed, 10 deletions(-)
--
2.41.0.327.gaa9166bcc0ba
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-09-19 12:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-19 12:51 Trevor Woerner [this message]
2023-09-19 12:51 ` [PATCH v4 1/1] ARM: defconfig: cleanup orphaned CONFIGs Trevor Woerner
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=20230919125112.15515-1-twoerner@gmail.com \
--to=twoerner@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=soc@kernel.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;
as well as URLs for NNTP newsgroup(s).