From: Denis Benato <benato.denis96@gmail.com>
To: Simon Horman <horms@kernel.org>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Paolo Abeni <pabeni@redhat.com>, Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew+netdev@lunn.ch>
Subject: Re: [PATCH] eth: fealnx: fix typo in comment
Date: Sat, 4 Oct 2025 22:16:54 +0200 [thread overview]
Message-ID: <0d7f5ada-9e8e-4869-9daf-bf67f364b70b@gmail.com> (raw)
In-Reply-To: <20251004160858.GD3060232@horms.kernel.org>
On 10/4/25 18:08, Simon Horman wrote:
> On Sat, Oct 04, 2025 at 02:59:42PM +0200, Denis Benato wrote:
>> There is a typo in a comment containing "avilable":
>> replace it with "available".
>>
>> Signed-off-by: Denis Benato <benato.denis96@gmail.com>
> Thanks Denis,
Hello Simon,
>
> I agree this is a good change, but could you also
> fix the spelling of mutlicast in this file?
>
Sure thing! I didn't noticed it, I was fixing another driver, so I
searched for that misspell and found this, so I simply quickly changed that
without looking or touching anything else.
> Please do consider tagging patches for Networking for their target tree.
> In this case I assume net-next, as this doesn't seem to be a bugfix for net.
>
> Also, net-next is currently closed for hte merge window.
> And will reopen once v6.18-rc1 has been released, I expect on or after
> the 13th October. So please post any patches for net-next after then.
>
> See: https://docs.kernel.org/process/maintainer-netdev.html
>
Thank you for the guidance! I am pretty new to all of this.
prev parent reply other threads:[~2025-10-04 20:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 12:59 Denis Benato
2025-10-04 16:08 ` Simon Horman
2025-10-04 20:16 ` Denis Benato [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=0d7f5ada-9e8e-4869-9daf-bf67f364b70b@gmail.com \
--to=benato.denis96@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®