From: Jacob Keller <jacob.e.keller@intel.com>
To: Alexander Lobakin <aleksander.lobakin@intel.com>,
Karol Kolacinski <karol.kolacinski@intel.com>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
<anthony.l.nguyen@intel.com>, <przemyslaw.kitszel@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH v3 iwl-next 4/4] ice: combine cross timestamp functions for E82x and E830
Date: Fri, 26 Jul 2024 16:16:21 -0700 [thread overview]
Message-ID: <68ddd3e9-e8de-48d8-9d32-7de6a18bf245@intel.com> (raw)
In-Reply-To: <ad94e165-ea7f-4216-b43d-b035c443a914@intel.com>
On 7/26/2024 6:37 AM, Alexander Lobakin wrote:
>> diff --git a/drivers/net/ethernet/intel/ice/ice_osdep.h b/drivers/net/ethernet/intel/ice/ice_osdep.h
>> index a2562f04267f..c03ab0207e0a 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_osdep.h
>> +++ b/drivers/net/ethernet/intel/ice/ice_osdep.h
>> @@ -23,6 +23,9 @@
>> #define wr64(a, reg, value) writeq((value), ((a)->hw_addr + (reg)))
>> #define rd64(a, reg) readq((a)->hw_addr + (reg))
>>
>> +#define rd32_poll_timeout(a, addr, val, cond, delay_us, timeout_us) \
>> + read_poll_timeout(rd32, val, cond, delay_us, timeout_us, false, a, addr)
>> +
>> #define ice_flush(a) rd32((a), GLGEN_STAT)
>> #define ICE_M(m, s) ((m ## U) << (s))
>>
>> diff --git a/drivers/net/ethernet/intel/ice/ice_ptp.c b/drivers/net/ethernet/intel/ice/ice_ptp.c
>> index 9f0eff040a95..ac3944fec2d3 100644
>> --- a/drivers/net/ethernet/intel/ice/ice_ptp.c
>> +++ b/drivers/net/ethernet/intel/ice/ice_ptp.c
>> @@ -1,6 +1,7 @@
>> // SPDX-License-Identifier: GPL-2.0
>> /* Copyright (C) 2021, Intel Corporation. */
>>
>> +#include <linux/iopoll.h>
>
> read_poll_timeout() is used in osdep.h, but you include it here.
> You should either define rd32_poll_timeout() here instead of the header
> or move this include to osdep.h.
>
Please move the include to ice_osdep.h, as there are some other places
where we will want to use rd32_poll_timeout (such as in ice_controlq.c,
and others).
Thanks,
Jake
next prev parent reply other threads:[~2024-07-26 23:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 9:34 [PATCH v3 iwl-next 0/4] ice: Implement PTP support for E830 devices Karol Kolacinski
2024-07-25 9:34 ` [PATCH v3 iwl-next 1/4] " Karol Kolacinski
2024-07-26 13:17 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-25 9:34 ` [PATCH v3 iwl-next 2/4] ice: Process TSYN IRQ in a separate function Karol Kolacinski
2024-07-26 13:22 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-25 9:34 ` [PATCH v3 iwl-next 3/4] ice: Add timestamp ready bitmap for E830 products Karol Kolacinski
2024-07-26 13:25 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-25 9:34 ` [PATCH v3 iwl-next 4/4] ice: combine cross timestamp functions for E82x and E830 Karol Kolacinski
2024-07-25 16:31 ` Jacob Keller
2024-07-26 13:37 ` [Intel-wired-lan] " Alexander Lobakin
2024-07-26 23:16 ` Jacob Keller [this message]
2024-08-05 16:21 ` Kolacinski, Karol
2024-08-07 13:54 ` Alexander Lobakin
2024-08-07 14:26 ` Kolacinski, Karol
2024-08-08 13:00 ` Alexander Lobakin
2024-08-08 14:20 ` Jakub Kicinski
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=68ddd3e9-e8de-48d8-9d32-7de6a18bf245@intel.com \
--to=jacob.e.keller@intel.com \
--cc=aleksander.lobakin@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=karol.kolacinski@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 NNTP newsgroup(s).