From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Karol Kolacinski <karol.kolacinski@intel.com>,
<intel-wired-lan@lists.osuosl.org>
Cc: netdev@vger.kernel.org
Subject: Re: [Intel-wired-lan] [PATCH v8 iwl-next 00/12] Introduce ETH56G PHY model for E825C products
Date: Tue, 16 Apr 2024 16:46:33 -0700 [thread overview]
Message-ID: <0471f360-3305-b58e-3cd4-6bcb78f73bec@intel.com> (raw)
In-Reply-To: <20240412131104.322851-14-karol.kolacinski@intel.com>
On 4/12/2024 6:06 AM, Karol Kolacinski wrote:
> E825C products have a different PHY model than E822, E823 and E810 products.
> This PHY is ETH56G and its support is necessary to have functional PTP stack
> for E825C products.
Can you clean up the new kernel-doc (-Wall) issues that these patches
are introducing?
Thanks,
Tony
prev parent reply other threads:[~2024-04-16 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 13:06 [Intel-wired-lan] [PATCH v8 iwl-next 00/12] Introduce ETH56G PHY model for E825C products Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 01/12] ice: Introduce ice_ptp_hw struct Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 02/12] ice: Introduce helper to get tmr_cmd_reg values Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 03/12] ice: Implement Tx interrupt enablement functions Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 04/12] ice: Add PHY OFFSET_READY register clearing Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 05/12] ice: Move CGU block Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 06/12] ice: Introduce ice_get_base_incval() helper Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 07/12] ice: Introduce ETH56G PHY model for E825C products Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 08/12] ice: Change CGU regs struct to anonymous Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 09/12] ice: Add support for E825-C TS PLL handling Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 10/12] ice: Add NAC Topology device capability parser Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 11/12] ice: Support 2XNAC configuration using auxbus Karol Kolacinski
2024-04-12 13:06 ` [Intel-wired-lan] [PATCH v8 iwl-next 12/12] ice: Adjust PTP init for 2x50G E825C devices Karol Kolacinski
2024-04-16 23:46 ` Tony Nguyen [this message]
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=0471f360-3305-b58e-3cd4-6bcb78f73bec@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=karol.kolacinski@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 read-only IMAP folder(s) and NNTP newsgroup(s).