From: Jakub Kicinski <kuba@kernel.org>
To: Alexey Nepomnyashih <sdl@nppct.ru>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
lvc-project@linuxtesting.org, stable@vger.kernel.org
Subject: Re: [PATCH] net: liquidio: fix overflow in octeon_init_instr_queue()
Date: Thu, 18 Sep 2025 07:32:32 -0700 [thread overview]
Message-ID: <20250918073232.6137a819@kernel.org> (raw)
In-Reply-To: <20250917153105.562563-1-sdl@nppct.ru>
On Wed, 17 Sep 2025 15:30:58 +0000 Alexey Nepomnyashih wrote:
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
No ads in the commit messages, please. Put the company / project in
the From line in the future. Quoting documentation:
From Line
^^^^^^^^^
The ``from`` line must be the very first line in the message body,
and has the form:
From: Patch Author <author@example.com>
The ``from`` line specifies who will be credited as the author of the
patch in the permanent changelog. If the ``from`` line is missing,
then the ``From:`` line from the email header will be used to determine
the patch author in the changelog.
The author may indicate their affiliation or the sponsor of the work
by adding the name of an organization to the ``from`` and ``SoB`` lines,
e.g.:
From: Patch Author (Company) <author@example.com>
See: https://www.kernel.org/doc/html/next/process/submitting-patches.html#the-canonical-patch-format
next prev parent reply other threads:[~2025-09-18 14:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 15:30 [PATCH] net: liquidio: fix overflow in octeon_init_instr_queue() Alexey Nepomnyashih
2025-09-18 14:32 ` Jakub Kicinski [this message]
2025-09-18 15:00 ` 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=20250918073232.6137a819@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sdl@nppct.ru \
--cc=stable@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;
as well as URLs for NNTP newsgroup(s).