From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Jozsef Kadlecsik <kadlec@netfilter.org>,
Heiko Carstens <hca@linux.ibm.com>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Florian Westphal <fw@strlen.de>,
"D . Wythe" <alibuda@linux.alibaba.com>,
Dust Li <dust.li@linux.alibaba.com>,
Sidraya Jayagond <sidraya@linux.ibm.com>,
Wenjia Zhang <wenjia@linux.ibm.com>,
Alexandra Winter <wintera@linux.ibm.com>,
Thorsten Winkler <twinkler@linux.ibm.com>,
netdev@vger.kernel.org, Julian Anastasov <ja@ssi.bg>
Subject: Re: [PATCH net-next] net: Remove KMSG_COMPONENT macro
Date: Fri, 28 Nov 2025 11:53:40 +0000 [thread overview]
Message-ID: <aSmNRDG8RAHVoC7C@chamomile> (raw)
In-Reply-To: <20251127181127.5f89447b@kernel.org>
Hi Jakub,
On Thu, Nov 27, 2025 at 06:11:27PM -0800, Jakub Kicinski wrote:
> On Wed, 26 Nov 2025 15:07:05 +0100 Heiko Carstens wrote:
> > net/iucv/af_iucv.c | 3 +--
> > net/iucv/iucv.c | 3 +--
> > net/netfilter/ipvs/ip_vs_app.c | 3 +--
> > net/netfilter/ipvs/ip_vs_conn.c | 3 +--
>
> Jozsef, Pablo, should we ask the author to split this up or just apply as is?
Patch looks trivial, and not so large for a tree wide.
But I'm Cc'ing Julian Anastasov so he has a chance to ack the IPVS bits.
next prev parent reply other threads:[~2025-11-28 11:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 14:07 [PATCH net-next] net: Remove KMSG_COMPONENT macro Heiko Carstens
2025-11-26 16:05 ` Alexandra Winter
2025-11-28 2:11 ` Jakub Kicinski
2025-11-28 11:53 ` Pablo Neira Ayuso [this message]
2025-11-28 18:51 ` Jakub Kicinski
2025-11-28 14:47 ` Julian Anastasov
2025-11-28 15:54 ` Sidraya Jayagond
2025-11-29 3:51 ` patchwork-bot+netdevbpf
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=aSmNRDG8RAHVoC7C@chamomile \
--to=pablo@netfilter.org \
--cc=alibuda@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=dust.li@linux.alibaba.com \
--cc=edumazet@google.com \
--cc=fw@strlen.de \
--cc=hca@linux.ibm.com \
--cc=horms@kernel.org \
--cc=ja@ssi.bg \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sidraya@linux.ibm.com \
--cc=twinkler@linux.ibm.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.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).