public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Ming Lei <ming.lei@canonical.com>
Cc: Sameer Nanda <snanda@chromium.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Ingo Molnar <mingo@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kernel/watchdog.c : fix smp_processor_id() warning
Date: Fri, 27 Jul 2012 10:37:15 -0400	[thread overview]
Message-ID: <20120727143715.GK5637@redhat.com> (raw)
In-Reply-To: <CACVXFVPdKzHXE=mV=FOx8xV4BLUEo_Ey9p6e9CkSOHxxYBfVgA@mail.gmail.com>

On Fri, Jul 27, 2012 at 08:38:21AM +0800, Ming Lei wrote:
> On Fri, Jul 27, 2012 at 3:43 AM, Don Zickus <dzickus@redhat.com> wrote:
> > On Wed, Jul 25, 2012 at 12:39:45PM +0800, Ming Lei wrote:
> >> Use raw_smp_processor_id in lockup_detector_bootcpu_resume()
> >> because it is enough when non-boot CPUs are offline.
> >>
> >> This patch fixes the following warning when DEBUG_PREEMPT
> >> is enabled.
> >
> > Is this patched on top of linux-next?
> 
> Yes.
> 
> The warning is introduced by the commit below:
> 
>       7fb860ff90ae970cf62cf676dfc1addcf8415674
>       (NMI watchdog: fix for lockup detector breakage on resume)

Ok, so I can respin this to give my SoB, if Andrew wants.  But at the same
time this patch will become obsolete (or broken) with tglx's hotplug
infrastructure changes.

Not sure what to do here.

Andrew?

Cheers,
Don

      reply	other threads:[~2012-07-27 14:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25  4:39 [PATCH] kernel/watchdog.c : fix smp_processor_id() warning Ming Lei
2012-07-26 19:43 ` Don Zickus
2012-07-27  0:38   ` Ming Lei
2012-07-27 14:37     ` Don Zickus [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=20120727143715.GK5637@redhat.com \
    --to=dzickus@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.lei@canonical.com \
    --cc=mingo@kernel.org \
    --cc=snanda@chromium.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