From: Dawid Osuchowski <dawid.osuchowski@linux.intel.com>
To: Tony Nguyen <anthony.l.nguyen@intel.com>,
intel-wired-lan@lists.osuosl.org
Cc: netdev@vger.kernel.org, Konrad Knitter <konrad.knitter@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] ice: add E835 device IDs
Date: Mon, 19 May 2025 13:08:49 +0200 [thread overview]
Message-ID: <870e9fd3-0b09-4da7-97fe-cca386fa2ca2@linux.intel.com> (raw)
In-Reply-To: <31f29ba7-7731-487c-9738-1beab56b727f@intel.com>
On 2025-05-16 7:30 PM, Tony Nguyen wrote:
> On 5/14/2025 3:46 AM, Dawid Osuchowski wrote:
>> diff --git a/drivers/net/ethernet/intel/ice/ice_devids.h b/drivers/
>> net/ethernet/intel/ice/ice_devids.h
>> index 34fd604132f5..7761c3501174 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_devids.h
>> +++ b/drivers/net/ethernet/intel/ice/ice_devids.h
>> @@ -36,6 +36,24 @@
>> #define ICE_DEV_ID_E830_XXV_QSFP 0x12DD
>> /* Intel(R) Ethernet Controller E830-XXV for SFP */
>> #define ICE_DEV_ID_E830_XXV_SFP 0x12DE
>> +/* Intel(R) Ethernet Controller E835-CC for backplane */
>> +#define ICE_DEV_ID_E835CC_BACKPLANE 0x1248
>> +/* Intel(R) Ethernet Controller E835-CC for QSFP */
>> +#define ICE_DEV_ID_E835CC_QSFP56 0x1249
>> +/* Intel(R) Ethernet Controller E835-CC for SFP */
>> +#define ICE_DEV_ID_E835CC_SFP 0x124A
>> +/* Intel(R) Ethernet Controller E835-C for backplane */
>> +#define ICE_DEV_ID_E835C_BACKPLANE 0x1261
>> +/* Intel(R) Ethernet Controller E835-C for QSFP */
>> +#define ICE_DEV_ID_E835C_QSFP 0x1262
>> +/* Intel(R) Ethernet Controller E835-C for SFP */
>> +#define ICE_DEV_ID_E835C_SFP 0x1263
>> +/* Intel(R) Ethernet Controller E835-L for backplane */
>> +#define ICE_DEV_ID_E835_L_BACKPLANE 0x1265
>> +/* Intel(R) Ethernet Controller E835-L for QSFP */
>> +#define ICE_DEV_ID_E835_L_QSFP 0x1266
>> +/* Intel(R) Ethernet Controller E835-L for SFP */
>> +#define ICE_DEV_ID_E835_L_SFP 0x1267
>> /* Intel(R) Ethernet Controller E810-C for backplane */
>> #define ICE_DEV_ID_E810C_BACKPLANE 0x1591
>
> For the most part this file is sorted by device id, could you move these
> to the corresponding spot?
Sure, will send v2.
Best regards,
Dawid
>
> Thanks,
> Tony
next prev parent reply other threads:[~2025-05-19 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 10:46 [PATCH iwl-next] ice: add E835 device IDs Dawid Osuchowski
2025-05-15 20:02 ` Simon Horman
2025-05-16 17:30 ` [Intel-wired-lan] " Tony Nguyen
2025-05-19 11:08 ` Dawid Osuchowski [this message]
2025-05-16 20:57 ` Paul Menzel
2025-05-19 11:11 ` Dawid Osuchowski
2025-05-22 7:01 ` Paul Menzel
2025-05-22 7:58 ` Dawid Osuchowski
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=870e9fd3-0b09-4da7-97fe-cca386fa2ca2@linux.intel.com \
--to=dawid.osuchowski@linux.intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=konrad.knitter@intel.com \
--cc=netdev@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).