From: Philip Li <philip.li@intel.com>
To: kbuild-all@lists.01.org
Subject: Re: [tglx-devel:x86/entry 7/13] arch/x86/mm/fault.c:567:19: error: 'idt_descr' undeclared; did you mean
Date: Thu, 04 Jun 2020 15:42:39 +0800 [thread overview]
Message-ID: <20200604074239.GB7033@intel.com> (raw)
In-Reply-To: <87bllz8fj5.fsf@nanos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 1140 bytes --]
On Thu, Jun 04, 2020 at 09:18:54AM +0200, Thomas Gleixner wrote:
> kernel test robot <lkp@intel.com> writes:
> > tree: https://git.kernel.org/pub/scm/linux/kernel/git/tglx/devel.git x86/entry
> > head: 454d46254473cd0d626a82fe1cda7b20a5e359e2
> > commit: 2e02592ac802e13b5c22630cde0096553ba8b767 [7/13] x86/idt: Consolidate idt functionality
> > config: i386-randconfig-r013-20200603 (attached as .config)
> > compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
> > reproduce (this is a W=1 build):
> > git checkout 2e02592ac802e13b5c22630cde0096553ba8b767
> > # save the attached .config to linux build tree
> > make W=1 ARCH=i386
>
> This commit has been replaced on June 1st. Can you please stop walking a
> branch when the branch is not longer matching?
thanks for pointing out this, this is in our TODO but not yet implemented,
we will move this to higher priority. Sorry for the noise here.
>
> Thanks,
>
> tglx
> _______________________________________________
> kbuild-all mailing list -- kbuild-all(a)lists.01.org
> To unsubscribe send an email to kbuild-all-leave(a)lists.01.org
prev parent reply other threads:[~2020-06-04 7:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 0:43 [tglx-devel:x86/entry 7/13] arch/x86/mm/fault.c:567:19: error: 'idt_descr' undeclared; did you mean kernel test robot
2020-06-04 7:18 ` Thomas Gleixner
2020-06-04 7:42 ` Philip Li [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=20200604074239.GB7033@intel.com \
--to=philip.li@intel.com \
--cc=kbuild-all@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.