From: Florian Westphal <fw@strlen.de>
To: Soham Metha <sohammetha01@gmail.com>
Cc: linux-kselftest@vger.kernel.org, shuah@kernel.org,
skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
netdev@vger.kernel.org
Subject: Re: [PATCH 2/6] setftests: net: netfilter: fix spelling mistakes in output
Date: Fri, 15 Aug 2025 08:14:07 +0200 [thread overview]
Message-ID: <aJ7QL0BHj7xJNqPw@strlen.de> (raw)
In-Reply-To: <20250815001803.112924-1-sohammetha01@gmail.com>
Soham Metha <sohammetha01@gmail.com> wrote:
> found/fixed following typos
>
> - add add -> add
> - cannnot -> cannot
> - fowarded -> forwarded
OK, but what tree are you targetting?
In case netdev maintainers or someone else wants to take it:
Acked-by: Florian Westphal <fw@strlen.de>
Else we can route it via nf-next in the coming week.
prev parent reply other threads:[~2025-08-15 6:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 0:08 [PATCH 0/6] Kselftests: fix spelling mistakes Soham Metha
2025-08-15 0:08 ` [PATCH 1/6] selftests: filesystems: statmout: fix spelling mistake in output Soham Metha
2025-08-15 0:17 ` [PATCH 2/6] setftests: net: netfilter: fix spelling mistakes " Soham Metha
2025-08-15 0:18 ` [PATCH 3/6] selftests: ublk: fixed spelling mistake " Soham Metha
2025-08-15 6:08 ` Ming Lei
2025-08-15 0:18 ` [PATCH 4/6] selftests: kvm: riscv: fix spelling mistakes in comments Soham Metha
2025-08-15 0:18 ` [PATCH 5/6] selftests: kvm: s390: fixed spelling mistake in output Soham Metha
2025-08-18 9:56 ` David Hildenbrand
2025-08-15 0:18 ` [PATCH 6/6] selftests: net: tcp_ao: fix spelling mistake in comments Soham Metha
2025-08-15 6:14 ` Florian Westphal [this message]
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=aJ7QL0BHj7xJNqPw@strlen.de \
--to=fw@strlen.de \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=shuah@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=sohammetha01@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