From: Tony Lindgren <tony@atomide.com>
To: Trevor Woerner <twoerner@gmail.com>
Cc: linux-kernel@vger.kernel.org,
Russell King <linux@armlinux.org.uk>,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/4] arch/arm/configs/omap2plus_defconfig: drop removed options
Date: Wed, 9 Aug 2023 10:14:04 +0300 [thread overview]
Message-ID: <20230809071404.GA11676@atomide.com> (raw)
In-Reply-To: <20230803191821.36793-2-twoerner@gmail.com>
* Trevor Woerner <twoerner@gmail.com> [230803 19:18]:
> Drop CONFIG_NF_LOG_NETDEV as it was removed in commit 1510618e45cb
> ("netfilter: nf_log_netdev: merge with nf_log_syslog").
>
> Drop CONFIG_NFT_COUNTER as it was removed in commit 023223dfbfb3
> ("netfilter: nf_tables: make counter support built-in").
>
> Drop CONFIG_NF_FLOW_TABLE_IPV6 and CONFIG_NF_FLOW_TABLE_IPV4 as they were
> removed in commit c42ba4290b21 ("netfilter: flowtable: remove ipv4/ipv6
> modules").
>
> Drop CONFIG_NF_LOG_BRIDGE as it was removed in commit 77ccee96a674
> ("netfilter: nf_log_bridge: merge with nf_log_syslog").
All the changes look good to me in the series, what's the plan
for applying them?
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-08-09 7:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230803191821.36793-1-twoerner@gmail.com>
2023-08-03 19:18 ` [PATCH 1/4] arch/arm/configs/omap2plus_defconfig: drop removed options Trevor Woerner
2023-08-09 7:14 ` Tony Lindgren [this message]
2023-08-03 19:18 ` [PATCH 2/4] arch/*/configs/*_defconfig cleanup: drop CONFIG_IP_NF_TARGET_CLUSTERIP Trevor Woerner
2023-08-03 19:18 ` [PATCH 3/4] arch/arm/configs/*_defconfig cleanup: drop CONFIG_USB_MUSB_AM35X Trevor Woerner
2023-08-03 19:18 ` [PATCH 4/4] arch/*/configs/*_defconfig cleanup: drop CONFIG_NFT_OBJREF 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=20230809071404.GA11676@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--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).