From: Michael Ellerman <mpe@ellerman.id.au>
To: Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH] Support resetting WARN_ONCE for all architectures
Date: Wed, 08 Nov 2017 20:40:57 +1100 [thread overview]
Message-ID: <87r2t92jme.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <20171106213654.GW2482@two.firstfloor.org>
Andi Kleen <andi@firstfloor.org> writes:
>>
>> And this is getting a bit nutty:
>>
>> support-resetting-warn_once.patch
>> support-resetting-warn_once-checkpatch-fixes.patch
>> support-resetting-warn_once-for-all-architectures.patch
>> support-resetting-warn_once-for-all-architectures-v2.patch
>> support-resetting-warn_once-for-all-architectures-v2-fix.patch
>> support-resetting-warn_once-for-all-architectures-v2-fix-fix.patch
>> support-resetting-warn_once-for-all-architectures-v2-fix-fix-fix.patch
>>
>> I'll push all this at Stephen later today. Someone please tell me
>> whether this code actually works!
>
> Sorry for the trash! Yes this was harder than originally expected.
>
> The original x86 patch was tested. I see Michael now tested
> the PPC version too. So everything should be good and hopefully
> don't need any more fixes.
Yep, I tested next-20171107 and that works for me, if you like:
Tested-by: Michael Ellerman <mpe@ellerman.id.au>
cheers
next prev parent reply other threads:[~2017-11-08 9:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-19 20:46 Andi Kleen
2017-11-03 9:38 ` Michael Ellerman
2017-11-03 17:47 ` Andrew Morton
2017-11-06 0:18 ` Michael Ellerman
2017-11-06 21:36 ` Andi Kleen
2017-11-08 9:40 ` Michael Ellerman [this message]
2017-10-20 17:06 Andi Kleen
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=87r2t92jme.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®