From: Shuah Khan <skhan@linuxfoundation.org>
To: Madhur Kumar <madhurkumar004@gmail.com>,
aconole@redhat.com, echaudro@redhat.com, i.maximets@ovn.org,
shuah@kernel.org
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, netdev@vger.kernel.org,
dev@openvswitch.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH] print: fix spelling error in message
Date: Thu, 14 Aug 2025 09:30:36 -0600 [thread overview]
Message-ID: <08a4b41b-fdcc-4104-b02c-ec28078ae80a@linuxfoundation.org> (raw)
In-Reply-To: <20250814144916.338054-1-madhurkumar004@gmail.com>
On 8/14/25 08:49, Madhur Kumar wrote:
Missing changelog - commit summary log is missing the subsystem
details - selftests/net: ------
> Signed-off-by: Madhur Kumar <madhurkumar004@gmail.com>
> ---
> tools/testing/selftests/net/openvswitch/ovs-dpctl.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/selftests/net/openvswitch/ovs-dpctl.py b/tools/testing/selftests/net/openvswitch/ovs-dpctl.py
> index 8a0396bfa..b521e0dea 100644
> --- a/tools/testing/selftests/net/openvswitch/ovs-dpctl.py
> +++ b/tools/testing/selftests/net/openvswitch/ovs-dpctl.py
> @@ -1877,7 +1877,7 @@ class OvsPacket(GenericNetlinkSocket):
> elif msg["cmd"] == OvsPacket.OVS_PACKET_CMD_EXECUTE:
> up.execute(msg)
> else:
> - print("Unkonwn cmd: %d" % msg["cmd"])
> + print("Unknown cmd: %d" % msg["cmd"])
> except NetlinkError as ne:
> raise ne
>
Look at the submitting patches documentation to learn how to write
commit summary, logs, and how to submit patches in general.
thanks,
-- Shuah
prev parent reply other threads:[~2025-08-14 15:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-14 14:49 [PATCH] print: fix spelling error in message Madhur Kumar
2025-08-14 15:30 ` Shuah Khan [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=08a4b41b-fdcc-4104-b02c-ec28078ae80a@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=aconole@redhat.com \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=echaudro@redhat.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=i.maximets@ovn.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=madhurkumar004@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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