From: Jakub Kicinski <kuba@kernel.org>
To: Lee Trager <lee@trager.us>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Alexander Duyck <alexanderduyck@fb.com>,
kernel-team@meta.com, Shinas Rasheed <srasheed@marvell.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
Phani Burra <phani.r.burra@intel.com>,
Joshua Hay <joshua.a.hay@intel.com>,
Sanman Pradhan <sanmanpradhan@meta.com>,
Sridhar Samudrala <sridhar.samudrala@intel.com>,
Alan Brady <alan.brady@intel.com>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] eth: fbnic: Add devlink firmware version info
Date: Tue, 10 Sep 2024 15:47:11 -0700 [thread overview]
Message-ID: <20240910154711.57c6557a@kernel.org> (raw)
In-Reply-To: <20240905233820.1713043-1-lee@trager.us>
On Thu, 5 Sep 2024 16:37:51 -0700 Lee Trager wrote:
> This adds support to show firmware version information for both stored and
> running firmware versions. The version and commit is displayed separately
> to aid monitoring tools which only care about the version.
I don't see a reply from the bots, so FTR Paolo applied this to net-next
as commit 0246388b9b79 ("eth: fbnic: Add devlink firmware version info").
Thank you!
next prev parent reply other threads:[~2024-09-10 22:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-05 23:37 [PATCH net-next] eth: fbnic: Add devlink firmware version info Lee Trager
2024-09-07 1:29 ` Jakub Kicinski
2024-09-10 22:47 ` Jakub Kicinski [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-09-04 19:48 Lee Trager
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=20240910154711.57c6557a@kernel.org \
--to=kuba@kernel.org \
--cc=alan.brady@intel.com \
--cc=alexanderduyck@fb.com \
--cc=anthony.l.nguyen@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=joshua.a.hay@intel.com \
--cc=kernel-team@meta.com \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=phani.r.burra@intel.com \
--cc=sanmanpradhan@meta.com \
--cc=srasheed@marvell.com \
--cc=sridhar.samudrala@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.