From: "naamax.meir" <naamax.meir@linux.intel.com>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>,
Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Jesper Dangaard Brouer <hawk@kernel.org>
Cc: intel-wired-lan@lists.osuosl.org
Subject: Re: [Intel-wired-lan] [PATCH iwl-next 1/2] igc: Simplify setting flags in the TX data descriptor
Date: Wed, 18 Oct 2023 21:41:40 +0300 [thread overview]
Message-ID: <2f85eb35-7f95-424b-ad66-e34dbad13279@linux.intel.com> (raw)
In-Reply-To: <20230921-igc-multiple-tstamp-vclock-v2-v1-1-aa0971cb0fe9@intel.com>
On 9/22/2023 04:40, Vinicius Costa Gomes wrote:
> We can re-use the IGC_SET_FLAG() macro to simplify setting some values
> in the TX data descriptor. With the macro it's easier to get the
> meaning of the operations.
>
> Signed-off-by: Vinicius Costa Gomes <vinicius.gomes@intel.com>
> ---
> drivers/net/ethernet/intel/igc/igc_main.c | 10 ++++------
> 1 file changed, 4 insertions(+), 6 deletions(-)
Tested-by: Naama Meir <naamax.meir@linux.intel.com>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-10-18 18:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 1:40 [Intel-wired-lan] [PATCH iwl-next 0/2] igc: Add support for physical + free-running timers Vinicius Costa Gomes
2023-09-22 1:40 ` [Intel-wired-lan] [PATCH iwl-next 1/2] igc: Simplify setting flags in the TX data descriptor Vinicius Costa Gomes
2023-10-18 18:41 ` naamax.meir [this message]
2023-09-22 1:40 ` [Intel-wired-lan] [PATCH iwl-next 2/2] igc: Add support for PTP .getcyclesx64() Vinicius Costa Gomes
2023-10-22 13:46 ` naamax.meir
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=2f85eb35-7f95-424b-ad66-e34dbad13279@linux.intel.com \
--to=naamax.meir@linux.intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.com \
--cc=vinicius.gomes@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 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.