From: Jacob Keller <jacob.e.keller@intel.com>
To: Michal Schmidt <mschmidt@redhat.com>, <intel-wired-lan@lists.osuosl.org>
Cc: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Richard Cochran <richardcochran@gmail.com>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Karol Kolacinski <karol.kolacinski@intel.com>,
<netdev@vger.kernel.org>
Subject: Re: [PATCH net-next 3/3] ice: fold ice_ptp_read_time into ice_ptp_gettimex64
Date: Mon, 26 Feb 2024 11:36:45 -0800 [thread overview]
Message-ID: <0ea688a3-f8ee-4383-b98e-82b84b791886@intel.com> (raw)
In-Reply-To: <20240226151125.45391-4-mschmidt@redhat.com>
On 2/26/2024 7:11 AM, Michal Schmidt wrote:
> This is a cleanup. It is unnecessary to have this function just to call
> another function.
>
> Signed-off-by: Michal Schmidt <mschmidt@redhat.com>
Obvious cleanup, thanks!
Reviewed-by: Jacob Keller <jacob.e.keller@intel.com>
next prev parent reply other threads:[~2024-02-26 19:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-26 15:11 [PATCH net-next 0/3] ice: lighter locking for PTP time reading Michal Schmidt
2024-02-26 15:11 ` [PATCH net-next 1/3] ice: add ice_adapter for shared data across PFs on the same NIC Michal Schmidt
2024-02-26 19:18 ` Jacob Keller
2024-02-27 7:05 ` Jiri Pirko
2024-02-27 8:11 ` Michal Schmidt
2024-02-28 2:35 ` Jakub Kicinski
2024-02-28 17:39 ` Keller, Jacob E
2024-02-26 15:11 ` [PATCH net-next 2/3] ice: avoid the PTP hardware semaphore in gettimex64 path Michal Schmidt
2024-02-26 19:36 ` Jacob Keller
2024-02-26 20:11 ` Michal Schmidt
2024-02-26 21:13 ` Jacob Keller
2024-02-26 15:11 ` [PATCH net-next 3/3] ice: fold ice_ptp_read_time into ice_ptp_gettimex64 Michal Schmidt
2024-02-26 19:36 ` Jacob Keller [this message]
2024-02-26 19:16 ` [PATCH net-next 0/3] ice: lighter locking for PTP time reading Jacob Keller
2024-02-26 20:01 ` Michal Schmidt
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=0ea688a3-f8ee-4383-b98e-82b84b791886@intel.com \
--to=jacob.e.keller@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=karol.kolacinski@intel.com \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=richardcochran@gmail.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).