From: Michael Ellerman <patch-notifications@ellerman.id.au>
To: Sam Bobroff <sbobroff@linux.ibm.com>, linuxppc-dev@lists.ozlabs.org
Cc: Nathan Lynch <nathanl@linux.ibm.com>,
Oliver O'Halloran <oohall@gmail.com>
Subject: Re: [PATCH v4 0/2] powerpc/eeh: Release EEH device state synchronously
Date: Wed, 20 May 2020 21:00:11 +1000 (AEST) [thread overview]
Message-ID: <158997214111.943180.7534452185720129130.b4-ty@ellerman.id.au> (raw)
In-Reply-To: <cover.1588045502.git.sbobroff@linux.ibm.com>
On Tue, 28 Apr 2020 13:45:04 +1000, Sam Bobroff wrote:
> Here are some fixes and cleanups that have come from other work but that I
> think stand on their own.
>
> Only one patch ("Release EEH device state synchronously", suggested by Oliver
> O'Halloran) is a significant change: it moves the cleanup of some EEH device
> data out of the (possibly asynchronous) device release handler and into the
> (synchronously called) bus notifier. This is useful for future work as it makes
> it easier to reason about the lifetimes of EEH structures.
>
> [...]
Applied to powerpc/next.
[1/2] powerpc/eeh: Fix pseries_eeh_configure_bridge()
https://git.kernel.org/powerpc/c/6fa13640aea7bb0760846981aa2da4245307bd26
[2/2] powerpc/eeh: Release EEH device state synchronously
https://git.kernel.org/powerpc/c/466381ecdc741b1767d980e10b1ec49f6bde56f3
cheers
prev parent reply other threads:[~2020-05-20 11:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 3:45 [PATCH v4 0/2] powerpc/eeh: Release EEH device state synchronously Sam Bobroff
2020-04-28 3:45 ` [PATCH v4 1/2] powerpc/eeh: fix pseries_eeh_configure_bridge() Sam Bobroff
2020-05-06 14:55 ` Nathan Lynch
2020-04-28 3:45 ` [PATCH v4 2/2] powerpc/eeh: Release EEH device state synchronously Sam Bobroff
2020-05-20 11:00 ` Michael Ellerman [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=158997214111.943180.7534452185720129130.b4-ty@ellerman.id.au \
--to=patch-notifications@ellerman.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=nathanl@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=sbobroff@linux.ibm.com \
/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).