From: David Miller <davem@davemloft.net>
To: magnus.karlsson@intel.com
Cc: bjorn.topel@intel.com, intel-wired-lan@lists.osuosl.org,
maciej.fijalkowski@intel.com, maciejromanfijalkowski@gmail.com,
netdev@vger.kernel.org, jeffrey.t.kirsher@intel.com
Subject: Re: [PATCH net 1/2] i40e: need_wakeup flag might not be set for Tx
Date: Fri, 08 Nov 2019 14:11:26 -0800 (PST) [thread overview]
Message-ID: <20191108.141126.499156209602458565.davem@davemloft.net> (raw)
In-Reply-To: <1573243090-2721-1-git-send-email-magnus.karlsson@intel.com>
Jeff, please pick these up.
Thanks.
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH net 1/2] i40e: need_wakeup flag might not be set for Tx
Date: Fri, 08 Nov 2019 14:11:26 -0800 (PST) [thread overview]
Message-ID: <20191108.141126.499156209602458565.davem@davemloft.net> (raw)
In-Reply-To: <1573243090-2721-1-git-send-email-magnus.karlsson@intel.com>
Jeff, please pick these up.
Thanks.
next prev parent reply other threads:[~2019-11-08 22:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-08 19:58 [PATCH net 1/2] i40e: need_wakeup flag might not be set for Tx Magnus Karlsson
2019-11-08 19:58 ` [Intel-wired-lan] " Magnus Karlsson
2019-11-08 19:58 ` [PATCH net 2/2] ixgbe: " Magnus Karlsson
2019-11-08 19:58 ` [Intel-wired-lan] " Magnus Karlsson
2019-11-09 0:02 ` Bowers, AndrewX
2019-11-09 0:02 ` Bowers, AndrewX
2019-11-08 22:11 ` David Miller [this message]
2019-11-08 22:11 ` [Intel-wired-lan] [PATCH net 1/2] i40e: " David Miller
2019-11-08 22:46 ` Jeff Kirsher
2019-11-08 22:46 ` [Intel-wired-lan] " Jeff Kirsher
2019-11-09 0:01 ` Bowers, AndrewX
2019-11-09 0:01 ` Bowers, AndrewX
2019-11-25 15:24 ` Maxim Mikityanskiy
2019-11-25 15:24 ` [Intel-wired-lan] " Maxim Mikityanskiy
2019-11-25 16:44 ` Magnus Karlsson
2019-11-25 16:44 ` Magnus Karlsson
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=20191108.141126.499156209602458565.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bjorn.topel@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=maciej.fijalkowski@intel.com \
--cc=maciejromanfijalkowski@gmail.com \
--cc=magnus.karlsson@intel.com \
--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.