From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 00/12] Add support for Rx timestamping for both ice and iavf drivers.
Date: Thu, 28 Mar 2024 09:48:27 +0100 [thread overview]
Message-ID: <19acc560-4744-47e0-9d73-dc44ca6471c3@intel.com> (raw)
In-Reply-To: <20240327075015.7c13a71b@kernel.org>
On 3/27/2024 3:50 PM, Jakub Kicinski wrote:
> On Wed, 27 Mar 2024 09:25:31 -0400 Mateusz Polchlopek wrote:
>> v2:
>> - fixed warning related to wrong specifier to dev_err_once in
>> commit 7
>> - fixed warnings related to unused variables in commit 9
>
> You posted this yesterday and got no feedback.
> You're not posting to the list just to get the code build tested, right?
> There's a lot of code getting posted, give people more time to take
> a look. v2 feels a bit rushed.
You are right, it was a bit rush, sorry for that. I will remember for
the future
WARNING: multiple messages have this Message-ID (diff)
From: Mateusz Polchlopek <mateusz.polchlopek@intel.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next v2 00/12] Add support for Rx timestamping for both ice and iavf drivers.
Date: Thu, 28 Mar 2024 09:48:27 +0100 [thread overview]
Message-ID: <19acc560-4744-47e0-9d73-dc44ca6471c3@intel.com> (raw)
In-Reply-To: <20240327075015.7c13a71b@kernel.org>
On 3/27/2024 3:50 PM, Jakub Kicinski wrote:
> On Wed, 27 Mar 2024 09:25:31 -0400 Mateusz Polchlopek wrote:
>> v2:
>> - fixed warning related to wrong specifier to dev_err_once in
>> commit 7
>> - fixed warnings related to unused variables in commit 9
>
> You posted this yesterday and got no feedback.
> You're not posting to the list just to get the code build tested, right?
> There's a lot of code getting posted, give people more time to take
> a look. v2 feels a bit rushed.
You are right, it was a bit rush, sorry for that. I will remember for
the future
next prev parent reply other threads:[~2024-03-28 8:48 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-27 13:25 [Intel-wired-lan] [PATCH iwl-next v2 00/12] Add support for Rx timestamping for both ice and iavf drivers Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 01/12] virtchnl: add support for enabling PTP on iAVF Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 02/12] ice: support Rx timestamp on flex descriptor Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 03/12] virtchnl: add enumeration for the rxdid format Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 04/12] iavf: add support for negotiating flexible RXDID format Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 05/12] iavf: negotiate PTP capabilities Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 06/12] iavf: add initial framework for registering PTP clock Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 07/12] iavf: add support for indirect access to PHC time Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 08/12] iavf: periodically cache " Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 09/12] iavf: refactor iavf_clean_rx_irq to support legacy and flex descriptors Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-29 20:46 ` Tony Nguyen
2024-03-29 20:46 ` Tony Nguyen
2024-03-29 20:46 ` Tony Nguyen
2024-03-29 20:46 ` Tony Nguyen
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 10/12] iavf: Implement checking DD desc field Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 11/12] iavf: handle SIOCSHWTSTAMP and SIOCGHWTSTAMP Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 13:25 ` [Intel-wired-lan] [PATCH iwl-next v2 12/12] iavf: add support for Rx timestamps to hotpath Mateusz Polchlopek
2024-03-27 13:25 ` Mateusz Polchlopek
2024-03-27 14:50 ` [Intel-wired-lan] [PATCH iwl-next v2 00/12] Add support for Rx timestamping for both ice and iavf drivers Jakub Kicinski
2024-03-27 14:50 ` Jakub Kicinski
2024-03-28 8:48 ` Mateusz Polchlopek [this message]
2024-03-28 8:48 ` Mateusz Polchlopek
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=19acc560-4744-47e0-9d73-dc44ca6471c3@intel.com \
--to=mateusz.polchlopek@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kuba@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.