From: David Miller <davem@davemloft.net>
To: ecree@solarflare.com
Cc: linux-net-drivers@solarflare.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] sfc: misc. fixes
Date: Fri, 17 Feb 2017 15:29:58 -0500 (EST) [thread overview]
Message-ID: <20170217.152958.1189664741143995910.davem@davemloft.net> (raw)
In-Reply-To: <f49743cd-3227-4d30-9d6d-bd2f8400df62@solarflare.com>
From: Edward Cree <ecree@solarflare.com>
Date: Fri, 17 Feb 2017 15:47:32 +0000
> Three largely unrelated fixes to increase robustness in rare edge cases.
Series applied, thanks.
prev parent reply other threads:[~2017-02-17 20:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 15:47 [PATCH net-next 0/3] sfc: misc. fixes Edward Cree
2017-02-17 15:49 ` [PATCH net-next 1/3] sfc: fix filter_id misinterpretation in edge case Edward Cree
2017-02-17 15:50 ` [PATCH net-next 2/3] sfc: forget filters from sw table if hw replies ENOENT on removing them Edward Cree
2017-02-17 15:50 ` [PATCH net-next 3/3] sfc: do not device_attach if a reset is pending Edward Cree
2017-02-17 20:29 ` David Miller [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=20170217.152958.1189664741143995910.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ecree@solarflare.com \
--cc=linux-net-drivers@solarflare.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 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).