From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: joaomboni <joaoboni017@gmail.com>,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH] e1000: Adicionado const para melhorar a segurança do código
Date: Mon, 3 Mar 2025 15:31:21 -0800 [thread overview]
Message-ID: <20250303153121.7c730c7c@kernel.org> (raw)
In-Reply-To: <de6bcb17-964e-475d-b535-ce153760d9dc@lunn.ch>
On Mon, 3 Mar 2025 14:48:46 +0100 Andrew Lunn wrote:
> Sorry, but the Subject: line needs to be in English.
>
> And the name in Signed-off-by: needs to be a real name.
>
> The code change itself looks sensible.
If only we were also LLMs, not just humans, we could read commits
in any language!
WARNING: multiple messages have this Message-ID (diff)
From: Jakub Kicinski <kuba@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: joaomboni <joaoboni017@gmail.com>,
anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, intel-wired-lan@lists.osuosl.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] e1000: Adicionado const para melhorar a segurança do código
Date: Mon, 3 Mar 2025 15:31:21 -0800 [thread overview]
Message-ID: <20250303153121.7c730c7c@kernel.org> (raw)
In-Reply-To: <de6bcb17-964e-475d-b535-ce153760d9dc@lunn.ch>
On Mon, 3 Mar 2025 14:48:46 +0100 Andrew Lunn wrote:
> Sorry, but the Subject: line needs to be in English.
>
> And the name in Signed-off-by: needs to be a real name.
>
> The code change itself looks sensible.
If only we were also LLMs, not just humans, we could read commits
in any language!
next prev parent reply other threads:[~2025-03-03 23:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-03 13:11 [Intel-wired-lan] [PATCH] e1000: Adicionado const para melhorar a segurança do código joaomboni
2025-03-03 13:11 ` joaomboni
2025-03-03 13:48 ` [Intel-wired-lan] " Andrew Lunn
2025-03-03 13:48 ` Andrew Lunn
2025-03-03 23:31 ` Jakub Kicinski [this message]
2025-03-03 23:31 ` Jakub Kicinski
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=20250303153121.7c730c7c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=joaoboni017@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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.