From: Jakub Kicinski <kuba@kernel.org>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
Victor Nogueira <victor@mojatatu.com>,
netdev@vger.kernel.org, Jiri Pirko <jiri@resnulli.us>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>,
Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH net-next v2] net/sched: em_text: pad the text pattern in the ematch dump
Date: Sat, 21 Nov 2026 15:50:28 -0800 [thread overview]
Message-ID: <20261121155028.44552d14@kernel.org> (raw)
In-Reply-To: <CAM0EoMm5jkHBnkdxKq_TDs9uwBWiJSqrJLXc_CWOOoT+_+X6mw@mail.gmail.com>
On Tue, 17 Nov 2026 17:54:28 -0500 Jamal Hadi Salim wrote:
> What is the problem? This is the standard format sashiko likes:
> 1) you describe how you came across the problem,
> 2) you describe what the issue being resolved is
> 3) you describe what the fix is
> 4) you provide any extra context
> 5) you describe what the conditions are to recreate the issue.
>
> If you leave any of those you will end up in version 5 in no time. In
> fact you will immediately get a note from Jakub's bot to ask you to
> explain #1
> Where do you see the sumarization/shortening happening?
Fun fact, if maintainers read all the commit messages for patches
coming it, and it would take them 2 minutes to go thru this slop
we'd spend 8 hours a day just reading this garbage.
How is it not reasonable to expect the submitter to look over
the commit msg and trim it.
next prev parent reply other threads:[~2026-11-21 23:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 19:10 [PATCH net-next v2] net/sched: em_text: pad the text pattern in the ematch dump Victor Nogueira
2026-11-17 19:59 ` netdev-bot+sashiko
2026-11-19 13:37 ` Simon Horman
2026-11-19 20:19 ` Jamal Hadi Salim
2026-11-19 20:26 ` Jamal Hadi Salim
2026-11-17 22:16 ` Stephen Hemminger
2026-11-17 22:54 ` Jamal Hadi Salim
2026-11-21 23:50 ` Jakub Kicinski [this message]
2026-11-21 23:50 ` 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=20261121155028.44552d14@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=horms@kernel.org \
--cc=jhs@mojatatu.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sashiko-bot@kernel.org \
--cc=stephen@networkplumber.org \
--cc=victor@mojatatu.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