From: David Miller <davem@davemloft.net>
To: mkalderon@marvell.com
Cc: michal.kalderon@cavium.com, ariel.elior@cavium.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/3] qed*: Error recovery process
Date: Sun, 27 Jan 2019 10:17:29 -0800 (PST) [thread overview]
Message-ID: <20190127.101729.1774234996114932306.davem@davemloft.net> (raw)
In-Reply-To: <BLUPR18MB0130E67F11EEE010B26933E3A1950@BLUPR18MB0130.namprd18.prod.outlook.com>
From: Michal Kalderon <mkalderon@marvell.com>
Date: Sun, 27 Jan 2019 13:42:35 +0000
>> From: David Miller <davem@davemloft.net>
>> Sent: Wednesday, January 23, 2019 3:37 AM
>>
>> > Parity errors might happen in the device's memories due to momentary
>> > bit flips which are caused by radiation.
>> > Errors that are not correctable initiate a process kill event, which
>> > blocks the device access towards the host and the network, and a
>> > recovery process is started in the management FW and in the driver.
>> >
>> > This series adds the support of this process in the qed core module
>> > and in the qede driver (patches 2 & 3).
>> > Patch 1 in the series revises the load sequence, to avoid PCI errors
>> > that might be observed during a recovery process.
>>
>> Series applied.
>
> Thanks Dave, though I don't see this in net-next, I noticed this was recently applied
> and reverted from net, should I resend to have it applied to net-next ?
Yes it was my mistake, please resubmit and please integrate the follow-up fix that
was posted as well.
https://patchwork.ozlabs.org/patch/1030545/
next prev parent reply other threads:[~2019-01-27 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-20 9:36 [PATCH net-next 0/3] qed*: Error recovery process Michal Kalderon
2019-01-20 9:36 ` [PATCH net-next 1/3] qed: Revise load sequence to avoid PCI errors Michal Kalderon
2019-01-20 9:36 ` [PATCH net-next 2/3] qed: Add infrastructure for error detection and recovery Michal Kalderon
2019-01-20 9:36 ` [PATCH net-next 3/3] qede: Error recovery process Michal Kalderon
2019-01-23 1:37 ` [PATCH net-next 0/3] qed*: " David Miller
2019-01-27 13:42 ` Michal Kalderon
2019-01-27 18:17 ` David Miller [this message]
2019-01-27 18:57 ` [EXT] " Michal Kalderon
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=20190127.101729.1774234996114932306.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=ariel.elior@cavium.com \
--cc=michal.kalderon@cavium.com \
--cc=mkalderon@marvell.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