From: Jakub Kicinski <kuba@kernel.org>
To: Damodharam Ammepalli <damodharam.ammepalli@broadcom.com>
Cc: Ido Schimmel <idosch@nvidia.com>,
netdev@vger.kernel.org, davem@davemloft.net, pabeni@redhat.com,
edumazet@google.com, horms@kernel.org, danieller@nvidia.com,
petrm@nvidia.com, andrew@lunn.ch, michael.chan@broadcom.com,
andrew.gospodarek@broadcom.com
Subject: Re: [PATCH net] ethtool: cmis_cdb: Fix incorrect read / write length extension
Date: Wed, 9 Apr 2025 16:42:14 -0700 [thread overview]
Message-ID: <20250409164214.6a19e340@kernel.org> (raw)
In-Reply-To: <CAKSYD4y5cTMdRmo97naYX=xE4k3jLBOBzptmyXi-YEimK4VmPw@mail.gmail.com>
On Wed, 9 Apr 2025 11:02:47 -0700 Damodharam Ammepalli wrote:
> This electronic communication and the information and any files transmitted
> with it, or attached to it, are confidential and are intended solely for
> the use of the individual or entity to whom it is addressed and may contain
> information that is confidential, legally privileged, protected by privacy
> laws, or otherwise restricted from disclosure to anyone else. If you are
> not the intended recipient or the person responsible for delivering the
> e-mail to the intended recipient, you are hereby notified that any use,
> copying, distributing, dissemination, forwarding, printing, or copying of
> this e-mail is strictly prohibited. If you received this e-mail in error,
> please return the e-mail to the sender, delete it from your computer, and
> destroy any printed copy of it.
Please fix your email setup.
--
pv-bot: trailer
next prev parent reply other threads:[~2025-04-09 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-09 11:24 [PATCH net] ethtool: cmis_cdb: Fix incorrect read / write length extension Ido Schimmel
2025-04-09 18:02 ` Damodharam Ammepalli
2025-04-09 23:42 ` Jakub Kicinski [this message]
2025-04-10 8:41 ` Petr Machata
2025-04-10 12:40 ` 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=20250409164214.6a19e340@kernel.org \
--to=kuba@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=andrew@lunn.ch \
--cc=damodharam.ammepalli@broadcom.com \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.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 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).