From: Ingo Molnar <mingo@elte.hu>
To: Nikanth Karthikesan <knikanth@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fix unused variable without softlock detection and highmem
Date: Mon, 23 Feb 2009 15:59:25 +0100 [thread overview]
Message-ID: <20090223145925.GD3377@elte.hu> (raw)
In-Reply-To: <200902231739.51863.knikanth@suse.de>
* Nikanth Karthikesan <knikanth@suse.de> wrote:
> When both CONFIG_DETECT_SOFTLOCKUP and CONFIG_HIGHMEM are not
> defined avoid defining the constant for one fixing the 'define
> but not used' warning.
>
> Signed-off-by: Nikanth Karthikesan <knikanth@suse.de>
A variant of this is already fixed a bit differently in
tip:core/softlockup:
9f8d979: softlockup: move 'one' to the softlockup section in sysctl.c
Ingo
prev parent reply other threads:[~2009-02-23 15:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-23 12:09 [PATCH] fix unused variable without softlock detection and highmem Nikanth Karthikesan
2009-02-23 14:59 ` Ingo Molnar [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=20090223145925.GD3377@elte.hu \
--to=mingo@elte.hu \
--cc=knikanth@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.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