From: Simon Horman <horms@kernel.org>
To: Anil Samal <anil.samal@intel.com>
Cc: intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
leszek.pepiak@intel.com, przemyslaw.kitszel@intel.com,
lukasz.czapnik@intel.com,
Anthony L Nguyen <anthony.l.nguyen@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [PATCH iwl-next v2 1/3] ice: Extend Sideband Queue command to support dynamic flag
Date: Sat, 11 May 2024 17:57:35 +0100 [thread overview]
Message-ID: <20240511165735.GQ2347895@kernel.org> (raw)
In-Reply-To: <20240510065243.906877-2-anil.samal@intel.com>
[ Fixed CC list by dropping '--cc=' from start of addresses. ]
On Thu, May 09, 2024 at 11:50:40PM -0700, Anil Samal wrote:
> Current driver implementation for Sideband Queue supports a
> fixed flag (ICE_AQ_FLAG_RD). To retrieve FEC statistics from
> firmware, Sideband Queue command is used with a different flag.
>
> Extend API for Sideband Queue command to use 'flag' as input
> argument.
>
> Reviewed-by: Anthony L Nguyen <anthony.l.nguyen@intel.com>
> Reviewed-by: Jesse Brandeburg <jesse.brandeburg@intel.com>
> Signed-off-by: Anil Samal <anil.samal@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-05-11 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-10 6:50 [PATCH iwl-next v2 0/3] ice:Support to dump PHY config, FEC Anil Samal
2024-05-10 6:50 ` [PATCH iwl-next v2 1/3] ice: Extend Sideband Queue command to support dynamic flag Anil Samal
2024-05-11 16:57 ` Simon Horman [this message]
2024-05-10 6:50 ` [PATCH iwl-next v2 2/3] ice: Implement driver functionality to dump fec statistics Anil Samal
2024-05-11 16:57 ` Simon Horman
2024-05-10 6:50 ` [PATCH iwl-next v2 3/3] ice: Implement driver functionality to dump serdes equalizer values Anil Samal
2024-05-11 16:56 ` Simon Horman
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=20240511165735.GQ2347895@kernel.org \
--to=horms@kernel.org \
--cc=anil.samal@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=leszek.pepiak@intel.com \
--cc=lukasz.czapnik@intel.com \
--cc=netdev@vger.kernel.org \
--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 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 read-only IMAP folder(s) and NNTP newsgroup(s).