From: Jakub Kicinski <kuba@kernel.org>
To: Jakub Raczynski <j.raczynski@samsung.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-janitors@vger.kernel.org
Subject: Re: [PATCH net-next v3] net/sun: Fix multiple typos in comments
Date: Wed, 3 Jun 2026 19:21:29 -0700 [thread overview]
Message-ID: <20260603192129.53f9ca9b@kernel.org> (raw)
In-Reply-To: <20260601163727.554364-1-j.raczynski@samsung.com>
On Mon, 1 Jun 2026 18:37:27 +0200 Jakub Raczynski wrote:
> there is no reason not to fix them.
Time needed to process these patches (you are at v3?!) and space in git
history are two reasons that come to mind. These are ancient drivers.
The most action these files will see in the future is git rm..
I'll apply but please try to adjust the compass a little more towards
actively used code.
next prev parent reply other threads:[~2026-06-04 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260601163737eucas1p19d7a2bf830568053314738a191cbd591@eucas1p1.samsung.com>
2026-06-01 16:37 ` [PATCH net-next v3] net/sun: Fix multiple typos in comments Jakub Raczynski
2026-06-04 2:21 ` Jakub Kicinski [this message]
2026-06-04 2:30 ` 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=20260603192129.53f9ca9b@kernel.org \
--to=kuba@kernel.org \
--cc=j.raczynski@samsung.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.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