From: Simon Horman <horms@kernel.org>
To: Tatyana Nikolova <tatyana.e.nikolova@intel.com>
Cc: jgg@nvidia.com, leon@kernel.org,
intel-wired-lan@lists.osuosl.org, linux-rdma@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [iwl-next v5 4/5] ice: Replace ice specific DSCP mapping num with a kernel define
Date: Thu, 17 Apr 2025 12:21:56 +0100 [thread overview]
Message-ID: <20250417112156.GF2430521@horms.kernel.org> (raw)
In-Reply-To: <20250416021549.606-5-tatyana.e.nikolova@intel.com>
On Tue, Apr 15, 2025 at 09:15:48PM -0500, Tatyana Nikolova wrote:
> Replace ice driver specific DSCP mapping number defines
> ICE_DSCP_NUM_VAL and IIDC_MAX_DSCP_MAPPING with
> an equivalent kernel define DSCP_MAX.
>
> Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> Signed-off-by: Tatyana Nikolova <tatyana.e.nikolova@intel.com>
> Signed-off-by: Dave Ertman <david.m.ertman@intel.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2025-04-17 11:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 2:15 [iwl-next v5 0/5] Refactor to prepare for Intel IPU E2000 (GEN3) Tatyana Nikolova
2025-04-16 2:15 ` [iwl-next v5 1/5] iidc/ice/irdma: Rename IDC header file Tatyana Nikolova
2025-04-16 2:15 ` [iwl-next v5 2/5] iidc/ice/irdma: Rename to iidc_* convention Tatyana Nikolova
2025-04-16 2:15 ` [iwl-next v5 3/5] iidc/ice/irdma: Break iidc.h into two headers Tatyana Nikolova
2025-04-16 2:15 ` [iwl-next v5 4/5] ice: Replace ice specific DSCP mapping num with a kernel define Tatyana Nikolova
2025-04-17 11:21 ` Simon Horman [this message]
2025-04-16 2:15 ` [iwl-next v5 5/5] iidc/ice/irdma: Update IDC to support multiple consumers Tatyana Nikolova
2025-04-17 11:21 ` Simon Horman
2025-04-18 17:14 ` [Intel-wired-lan] " Ertman, David M
2025-04-23 16:14 ` Simon Horman
2025-04-24 15:58 ` [iwl-next v5 0/5] Refactor to prepare for Intel IPU E2000 (GEN3) Nikolova, Tatyana E
2025-04-24 21:51 ` Jakub Kicinski
2025-04-28 20:29 ` Nikolova, Tatyana E
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=20250417112156.GF2430521@horms.kernel.org \
--to=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tatyana.e.nikolova@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 NNTP newsgroup(s).