From: Andi Kleen <ak@linux.intel.com>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: Andi Kleen <andi@firstfloor.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kgdb: Fix warning with !CONFIG_DEBUG_RODATA
Date: Fri, 21 Sep 2012 14:06:57 -0700 [thread overview]
Message-ID: <20120921210657.GD665@tassilo.jf.intel.com> (raw)
In-Reply-To: <505CD5C3.3020009@windriver.com>
On Fri, Sep 21, 2012 at 04:01:55PM -0500, Jason Wessel wrote:
> On 09/21/2012 03:59 PM, Andi Kleen wrote:
> > From: Andi Kleen <ak@linux.intel.com>
> >
> > Fixes
> >
> > arch/x86/kernel/kgdb.c: In function ‘kgdb_arch_set_breakpoint’:
> > arch/x86/kernel/kgdb.c:749:7: warning: unused variable ‘opc’ [-Wunused-variable]
> >
> > when CONFIG_DEBUG_RODATA is not defined.
> >
>
> This is already pending along with other fixes in kgdb-next / linux next for the 3.7 merge window.
Ok. This was broken in 3.5 too. Next time please fast track warning fixes.
It's about the only warning in my standard builds.
-Andi
prev parent reply other threads:[~2012-09-21 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 20:59 [PATCH] kgdb: Fix warning with !CONFIG_DEBUG_RODATA Andi Kleen
2012-09-21 21:01 ` Jason Wessel
2012-09-21 21:06 ` Andi Kleen [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=20120921210657.GD665@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=jason.wessel@windriver.com \
--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