From: Thomas Gleixner <tglx@linutronix.de>
To: Mukesh Ojha <mojha@codeaurora.org>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: Query on skip_onerr field in struct cpuhp_step
Date: Tue, 21 Aug 2018 15:57:41 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1808211557180.1535@nanos.tec.linutronix.de> (raw)
In-Reply-To: <c228c495-63fa-5af9-32ff-355410d78cc8@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 597 bytes --]
On Tue, 21 Aug 2018, Mukesh Ojha wrote:
> Hi All,
>
> This is about one of field in struct cpuhp_step
>
> * @skip_onerr: Do not invoke the functions on error rollback
> * Will go away once the notifiers are gone
> bool skip_onerr;
>
> Why this field was introduced, can anyone explain the history behind ? As i
> don't see it being set from anywhere
>
> If it is specifically was dependent on notifiers, did we missed to remove it
> as the notifiers are gone or the usecase still there?
As the comment says....
next prev parent reply other threads:[~2018-08-21 13:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-21 13:47 Query on skip_onerr field in struct cpuhp_step Mukesh Ojha
2018-08-21 13:57 ` Thomas Gleixner [this message]
2018-08-21 14:40 ` Mukesh Ojha
2018-08-25 18:27 ` Thomas Gleixner
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=alpine.DEB.2.21.1808211557180.1535@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mojha@codeaurora.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).