From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net-next v1 0/4] ice: transmit improvement series
Date: Wed, 27 Oct 2021 12:46:07 -0700 [thread overview]
Message-ID: <850d2742-2191-9cec-e585-dbbb1d796510@intel.com> (raw)
In-Reply-To: <7afd99cc66d66f81ce68e9bd9e9cc116cefab1eb.camel@intel.com>
On 10/26/2021 9:21 AM, Nguyen, Anthony L wrote:
>> Jesse Brandeburg (4):
>> ? ice: update to newer kernel API
>> ? ice: use prefetch methods
>> ? ice: tighter control over VSI_DOWN state
>> ? ice: use modern kernel API for kick
>
> It looks like patch 2 never made it to the list [1]. Seems like the
> email issues may be further reaching than kernel.org.
>
> Thanks,
> Tony
>
> [1] https://patchwork.ozlabs.org/project/intel-wired-
> lan/list/?series=268871
Thanks for letting me know!
The issue was root caused to a typo in the To:email address on my end,
and I attempted to resend the patch with a correct reply-to, it seems to
have failed to do what I wanted (but did show up on patchwork now) so
please let me know if you want me to resend the whole series as a v2.
prev parent reply other threads:[~2021-10-27 19:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-26 0:08 [Intel-wired-lan] [PATCH net-next v1 0/4] ice: transmit improvement series Jesse Brandeburg
2021-10-26 0:08 ` [Intel-wired-lan] [PATCH net-next v1 1/4] ice: update to newer kernel API Jesse Brandeburg
2021-11-05 9:10 ` G, GurucharanX
2021-10-26 0:08 ` [Intel-wired-lan] [PATCH net-next v1 3/4] ice: tighter control over VSI_DOWN state Jesse Brandeburg
2021-11-05 9:10 ` G, GurucharanX
2021-10-26 0:08 ` [Intel-wired-lan] [PATCH net-next v1 4/4] ice: use modern kernel API for kick Jesse Brandeburg
2021-11-05 9:11 ` G, GurucharanX
2021-10-26 16:21 ` [Intel-wired-lan] [PATCH net-next v1 0/4] ice: transmit improvement series Nguyen, Anthony L
2021-10-27 19:46 ` Jesse Brandeburg [this message]
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=850d2742-2191-9cec-e585-dbbb1d796510@intel.com \
--to=jesse.brandeburg@intel.com \
--cc=intel-wired-lan@osuosl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox