All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
	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: Mon, 6 Nov 2017 13:36:55 -0800	[thread overview]
Message-ID: <20171106213654.GW2482@two.firstfloor.org> (raw)
In-Reply-To: <20171103104755.0fa2dba59f48df43d5bffb25@linux-foundation.org>

> 
> 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.

Thanks,

-Andi

  parent reply	other threads:[~2017-11-06 21:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-19 20:46 [PATCH] Support resetting WARN_ONCE for all architectures 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 [this message]
2017-11-08  9:40       ` Michael Ellerman
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=20171106213654.GW2482@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=ak@linux.intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.