From: Jakub Kicinski <kuba@kernel.org>
To: Leon Romanovsky <leon@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>, Lukas Wunner <lukas@wunner.de>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.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: Thu, 11 May 2023 08:51:28 -0700 [thread overview]
Message-ID: <20230511085128.3eb887e3@kernel.org> (raw)
In-Reply-To: <20230511065917.GT38143@unreal>
On Thu, 11 May 2023 09:59:17 +0300 Leon Romanovsky wrote:
> And this is mainly the issue here. Lukas changes are not different from
> what many of us doing when we submit internal patches. We change/update/rewrite
> patches which make them different from internal variant.
>
> Once the patches are public, they will have relevant changelog section.
>
> I don't see how modifying-patches.rst can be seen differently.
>
> BTW, Regarding know-to-blame reasoning, everyone who added his
> Signed-off-by to the patch is immediately suspicious.
Right, modifying-patches.rst does not apply to corpo patches.
Maybe the analogy from US law would be helpful to show how I think
about it -- corporation (especially working on its own product)
is one "legal person", Philipp and Lukas are separate "human persons".
IOW patch circulation and attribution within a corporation is naturally
different than between community members.
next prev parent reply other threads:[~2023-05-11 15:51 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
2023-05-11 6:36 ` Paolo Abeni
2023-05-11 6:59 ` Leon Romanovsky
2023-05-11 15:51 ` Jakub Kicinski [this message]
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=20230511085128.3eb887e3@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.