From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Trevor Woerner <twoerner@gmail.com>
Cc: loongarch@lists.linux.dev, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v3 3/4] arch/mips/configs/*_defconfig cleanup
Date: Wed, 23 Aug 2023 09:22:24 +0200 [thread overview]
Message-ID: <ZOWzsAHxuHQLGsEa@alpha.franken.de> (raw)
In-Reply-To: <20230817115017.35663-4-twoerner@gmail.com>
On Thu, Aug 17, 2023 at 07:50:13AM -0400, Trevor Woerner wrote:
> Drop CONFIG_IP_NF_TARGET_CLUSTERIP from any remaining mips defconfigs as it
> was removed in commit 9db5d918e2c0 ("netfilter: ip_tables: remove clusterip
> target").
>
> Signed-off-by: Trevor Woerner <twoerner@gmail.com>
> ---
> arch/mips/configs/ip22_defconfig | 1 -
> arch/mips/configs/malta_defconfig | 1 -
> arch/mips/configs/malta_kvm_defconfig | 1 -
> arch/mips/configs/maltaup_xpa_defconfig | 1 -
> arch/mips/configs/rm200_defconfig | 1 -
> 5 files changed, 5 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2023-08-23 8:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 11:50 [PATCH v3 0/4] general defconfig cleanups Trevor Woerner
2023-08-17 11:50 ` [PATCH v3 1/4] arch/arm/configs/*_defconfig cleanup Trevor Woerner
2023-08-17 11:50 ` [PATCH v3 2/4] arch/loongarch/configs/*_defconfig cleanup Trevor Woerner
2023-08-24 6:02 ` WANG Xuerui
2023-08-17 11:50 ` [PATCH v3 3/4] arch/mips/configs/*_defconfig cleanup Trevor Woerner
2023-08-17 15:43 ` Philippe Mathieu-Daudé
2023-08-23 7:22 ` Thomas Bogendoerfer [this message]
2023-08-17 11:50 ` [PATCH v3 4/4] arch/powerpc/configs/*_defconfig cleanup Trevor Woerner
2023-08-23 11:55 ` (subset) [PATCH v3 0/4] general defconfig cleanups Michael Ellerman
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=ZOWzsAHxuHQLGsEa@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=loongarch@lists.linux.dev \
--cc=twoerner@gmail.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).