From: Neelesh Gupta <neelegup@linux.vnet.ibm.com>
To: Anshuman Khandual <khandual@linux.vnet.ibm.com>,
mpe@ellerman.id.au, linuxppc-dev@lists.ozlabs.org,
benh@kernel.crashing.org
Subject: Re: [PATCH 2/2] opal: Add message notifier unregister function
Date: Thu, 12 Feb 2015 16:40:49 +0530 [thread overview]
Message-ID: <54DC8A39.3070401@linux.vnet.ibm.com> (raw)
In-Reply-To: <54DB35A7.8030609@linux.vnet.ibm.com>
On 02/11/2015 04:27 PM, Anshuman Khandual wrote:
> On 02/11/2015 11:57 AM, Neelesh Gupta wrote:
>> Provide an unregister interface for the opal message notifiers
>> to be called when not needed like during driver unload/remove.
> Why only for unload/remove, you can also use it in cases where you need
> to abort because of any other error soon after successful registration
> for an OPAL message.
I didn't mean *only* driver unload/remove.. gave a simple use case of why do
we need this change.
Neelesh.
>
next prev parent reply other threads:[~2015-02-12 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-11 6:27 [PATCH v2 1/2] opal: Fix the overflow of message notifiers head array Neelesh Gupta
2015-02-11 6:27 ` [PATCH 2/2] opal: Add message notifier unregister function Neelesh Gupta
2015-02-11 10:57 ` Anshuman Khandual
2015-02-12 11:10 ` Neelesh Gupta [this message]
2015-02-11 10:53 ` [PATCH v2 1/2] opal: Fix the overflow of message notifiers head array Anshuman Khandual
-- strict thread matches above, loose matches on Subject: below --
2015-02-10 17:14 [PATCH " Neelesh Gupta
2015-02-10 17:15 ` [PATCH 2/2] opal: Add message notifier unregister function Neelesh Gupta
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=54DC8A39.3070401@linux.vnet.ibm.com \
--to=neelegup@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=khandual@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
/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).