From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Lukas Wunner <lukas@wunner.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org,
Philipp Rosenberger <p.rosenberger@kunbus.com>,
Zhi Han <hanzhi09@gmail.com>
Subject: Re: [PATCH net-next] net: enc28j60: Use threaded interrupt instead of workqueue
Date: Wed, 10 May 2023 19:05:17 -0700 [thread overview]
Message-ID: <20230510190517.26f11d4a@kernel.org> (raw)
In-Reply-To: <20230509135613.GP38143@unreal>
On Tue, 9 May 2023 16:56:13 +0300 Leon Romanovsky wrote:
> > > This is part of changelog which doesn't belong to commit message. The
> > > examples which you can find in git log, for such format like you used,
> > > are usually reserved to maintainers when they apply the patch.
> >
> > Is that a new rule?
>
> No, this rule always existed, just some of the maintainers didn't care
> about it.
>
> >
> > Honestly I think it's important to mention changes applied to
> > someone else's patch, if only to let it be known who's to blame
> > for any mistakes.
>
> Right, this is why maintainers use this notation when they apply
> patches. In your case, you are submitter, patch is not applied yet
> and all changes can be easily seen through lore web interface.
>
> >
> > I'm seeing plenty of recent precedent in the git history where
> > non-committers fixed up patches and made their changes known in
> > this way, e.g.:
>
> It doesn't make it correct.
> Documentation/maintainer/modifying-patches.rst
TBH I'm not sure if this is the correct reading of this doc.
I don't see any problem with Lukas using the common notation.
It makes it quite obvious what he changed and the changes are
not invasive enough to warrant a major rewrite of the commit msg.
next prev parent reply other threads:[~2023-05-11 2:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 4:28 [PATCH net-next] net: enc28j60: Use threaded interrupt instead of workqueue Lukas Wunner
2023-05-09 8:06 ` Leon Romanovsky
2023-05-09 13:36 ` Lukas Wunner
2023-05-09 13:56 ` Leon Romanovsky
2023-05-11 2:05 ` Jakub Kicinski [this message]
2023-05-11 6:36 ` Paolo Abeni
2023-05-11 6:59 ` Leon Romanovsky
2023-05-11 15:51 ` Jakub Kicinski
2023-05-11 18:48 ` Leon Romanovsky
2023-05-09 9:22 ` Piotr Raczynski
2023-05-12 1:10 ` 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=20230510190517.26f11d4a@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hanzhi09@gmail.com \
--cc=leon@kernel.org \
--cc=lukas@wunner.de \
--cc=netdev@vger.kernel.org \
--cc=p.rosenberger@kunbus.com \
--cc=pabeni@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.