From: Philip Li <philip.li@intel.com>
To: Borislav Petkov <bp@alien8.de>
Cc: kbuild test robot <lkp@intel.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
kbuild-all@01.org
Subject: Re: [kbuild-all] arch/x86/include/asm/cmpxchg.h:245:2: error: 'asm' operand has impossible constraints
Date: Tue, 22 Jan 2019 19:13:59 +0800 [thread overview]
Message-ID: <20190122111359.GA9888@intel.com> (raw)
In-Reply-To: <20190122100815.GA26587@zn.tnic>
On Tue, Jan 22, 2019 at 11:08:34AM +0100, Borislav Petkov wrote:
> On Tue, Jan 22, 2019 at 12:53:11PM +0800, kbuild test robot wrote:
> > Hi Ingo,
> >
> > FYI, the error/warning still remains.
>
> Guys,
>
> we already discussed this:
>
> https://lists.01.org/pipermail/kbuild-all/2018-December/056206.html
>
> but you keep reporting it.
>
> You need to fix your reported issues tracking or otherwise no one will
> bother anymore.
thanks for the feedback, we will blacklist this. So may i understand based on
the thread at https://lists.01.org/pipermail/kbuild-all/2018-December/056225.html,
this is gcc-4.9 problem?
>
> Thx.
>
> --
> Regards/Gruss,
> Boris.
>
> Good mailing practices for 400: avoid top-posting and trim the reply.
> _______________________________________________
> kbuild-all mailing list
> kbuild-all@lists.01.org
> https://lists.01.org/mailman/listinfo/kbuild-all
next prev parent reply other threads:[~2019-01-22 11:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201901221204.ZqZgxRnA%fengguang.wu@intel.com>
2019-01-22 10:08 ` arch/x86/include/asm/cmpxchg.h:245:2: error: 'asm' operand has impossible constraints Borislav Petkov
2019-01-22 11:13 ` Philip Li [this message]
2019-01-22 11:55 ` [kbuild-all] " Borislav Petkov
2019-01-30 3:28 ` Rong Chen
2019-01-30 11:15 ` Borislav Petkov
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=20190122111359.GA9888@intel.com \
--to=philip.li@intel.com \
--cc=bp@alien8.de \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mingo@kernel.org \
--cc=tglx@linutronix.de \
/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