From: Anatolii Gerasymenko <anatolii.gerasymenko@intel.com>
To: Paul Menzel <pmenzel@molgen.mpg.de>
Cc: intel-wired-lan@lists.osuosl.org,
Jesse Brandeburg <jesse.brandeburg@intel.com>
Subject: Re: [Intel-wired-lan] Patches not threaded below the cover letter (was: [PATCH net-next 0/2] ice: FCS/CRC stripping control)
Date: Thu, 30 Jun 2022 08:22:11 +0200 [thread overview]
Message-ID: <0ec8de81-2aaa-8084-f927-89f0f72114f7@intel.com> (raw)
In-Reply-To: <f1bc6014-1743-ec50-a719-639890ed6649@molgen.mpg.de>
On 28.06.2022 12:49, Paul Menzel wrote:
> Dear Anatolii,
>
>
> Thank you for the patches.
>
> Am 28.06.22 um 12:43 schrieb Anatolii Gerasymenko:
>> Implement possibility to change FCS/CRC stripping feature using
>> ethtool command.
>>
>> Having FCS/CRC could be useful for:
>> - network sniffers to inspect FCS/CRC correctness
>> - for benchmarking use cases
>> - XDP programs
>>
>> Anatolii Gerasymenko (1):
>> ice: Implement FCS/CRC and VLAN stripping co-existence policy
>>
>> Jesse Brandeburg (1):
>> ice: Implement control of FCS/CRC stripping
>
> […]
>
> For some reason the two patches are not threaded below the cover letter although you use git-send-email:
>
> X-Mailer: git-send-email 2.25.1
>
> Can you please check you setup?
>
Yes, that is strange. I will check.
Thank you, Paul.
>
> Kind regards,
>
> Paul
_______________________________________________
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:[~2022-06-30 6:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-28 10:43 [Intel-wired-lan] [PATCH net-next 0/2] ice: FCS/CRC stripping control Anatolii Gerasymenko
2022-06-28 10:49 ` [Intel-wired-lan] Patches not threaded below the cover letter (was: [PATCH net-next 0/2] ice: FCS/CRC stripping control) Paul Menzel
2022-06-30 6:22 ` Anatolii Gerasymenko [this message]
2022-06-28 20:36 ` [Intel-wired-lan] [PATCH net-next 0/2] ice: FCS/CRC stripping control Zvi Effron
2022-06-30 6:26 ` Anatolii Gerasymenko
2022-07-20 5:23 ` Mekala, SunithaX D
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=0ec8de81-2aaa-8084-f927-89f0f72114f7@intel.com \
--to=anatolii.gerasymenko@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=pmenzel@molgen.mpg.de \
/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