From: Jakub Kicinski <kuba@kernel.org>
To: Shannon Nelson <snelson@pensando.io>
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [PATCH net-next 0/6] ionic error recovery fixes
Date: Thu, 19 Mar 2020 20:46:40 -0700 [thread overview]
Message-ID: <20200319204640.36626901@kicinski-fedora-PC1C0HJN> (raw)
In-Reply-To: <20200320023153.48655-1-snelson@pensando.io>
On Thu, 19 Mar 2020 19:31:47 -0700 Shannon Nelson wrote:
> These are a few little patches to make error recovery a little
> more safe and successful.
Patches looks good to me, FWIW. Thanks for dropping the controversial
one. I think this should have been v2 since we seen most if not all of
these.
I'm not sure why most of them have a Fixes tag, though. The
AUTOSEL bot is quite likely to pull them into the stable trees once
they land. Is this some intentional strategy on your part?
next prev parent reply other threads:[~2020-03-20 3:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 2:31 [PATCH net-next 0/6] ionic error recovery fixes Shannon Nelson
2020-03-20 2:31 ` [PATCH net-next 1/6] ionic: add timeout error checking for queue disable Shannon Nelson
2020-03-20 2:31 ` [PATCH net-next 2/6] ionic: leave dev cmd request contents alone on FW timeout Shannon Nelson
2020-03-20 2:31 ` [PATCH net-next 3/6] ionic: only save good lif dentry Shannon Nelson
2020-03-20 2:31 ` [PATCH net-next 4/6] ionic: ignore eexist on rx filter add Shannon Nelson
2020-03-20 3:43 ` Jakub Kicinski
2020-03-20 5:21 ` Shannon Nelson
2020-03-20 17:16 ` Jakub Kicinski
2020-03-20 2:31 ` [PATCH net-next 5/6] ionic: clean irq affinity on queue deinit Shannon Nelson
2020-03-20 2:31 ` [PATCH net-next 6/6] ionic: check for NULL structs on teardown Shannon Nelson
2020-03-20 3:46 ` Jakub Kicinski [this message]
2020-03-20 5:21 ` [PATCH net-next 0/6] ionic error recovery fixes Shannon Nelson
2020-03-22 2:56 ` David Miller
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=20200319204640.36626901@kicinski-fedora-PC1C0HJN \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=snelson@pensando.io \
/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