From: Thomas Gleixner <tglx@linutronix.de>
To: Bandan Das <bsd@redhat.com>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, linux-kernel@vger.kernel.org,
tipbuild@zytor.com
Subject: Re: [tip:x86/urgent 3/3] arch/x86/kernel/apic/apic.c:1182:6: warning: the address of 'x2apic_enabled' will always evaluate as 'true'
Date: Tue, 27 Aug 2019 08:50:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1908270849540.1939@nanos.tec.linutronix.de> (raw)
In-Reply-To: <jpgwoezgldx.fsf@linux.bootlegged.copy>
On Tue, 27 Aug 2019, Bandan Das wrote:
> kbuild test robot <lkp@intel.com> writes:
>
> > tree: https://kernel.googlesource.com/pub/scm/linux/kernel/git/tip/tip.git x86/urgent
> > head: cfa16294b1c5b320c0a0e1cac37c784b92366c87
> > commit: cfa16294b1c5b320c0a0e1cac37c784b92366c87 [3/3] x86/apic: Include the LDR when clearing out APIC registers
> > config: i386-defconfig (attached as .config)
> > compiler: gcc-7 (Debian 7.4.0-10) 7.4.0
> > reproduce:
> > git checkout cfa16294b1c5b320c0a0e1cac37c784b92366c87
> > # save the attached .config to linux build tree
> > make ARCH=i386
> >
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> >
> > All warnings (new ones prefixed by >>):
> >
> > arch/x86/kernel/apic/apic.c: In function 'clear_local_APIC':
> >>> arch/x86/kernel/apic/apic.c:1182:6: warning: the address of 'x2apic_enabled' will always evaluate as 'true' [-Waddress]
> > if (!x2apic_enabled) {
> > ^
> Thomas, I apologize for the typo here. This is the x2apic_enabled() function.
> Should I respin ?
https://lkml.kernel.org/r/156684295076.23440.2192639697586451635.tip-bot2@tip-bot2
You have that mail in your inbox ..
next prev parent reply other threads:[~2019-08-27 6:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-26 16:30 kbuild test robot
2019-08-27 6:42 ` Bandan Das
2019-08-27 6:50 ` Thomas Gleixner [this message]
2019-08-27 6:58 ` Bandan Das
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=alpine.DEB.2.21.1908270849540.1939@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=bsd@redhat.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=tipbuild@zytor.com \
/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®