public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Singh, Balbir" <sblbir@amazon.com>
To: "lkp@intel.com" <lkp@intel.com>
Cc: "kbuild-all@lists.01.org" <kbuild-all@lists.01.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"x86@kernel.org" <x86@kernel.org>
Subject: Re:  [tip:x86/pti 4/5] arch/x86/mm/tlb.c:319:6: warning: variable 'cpu' set but not used
Date: Wed, 20 Jan 2021 10:37:38 +0000	[thread overview]
Message-ID: <71f2a4567f0853b26048918ec1afff24ae87e5be.camel@amazon.com> (raw)
In-Reply-To: <202101161129.TiX15hOi-lkp@intel.com>

On Sat, 2021-01-16 at 11:21 +0800, kernel test robot wrote:
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86/pti
> head:   767d46ab566dd489733666efe48732d523c8c332
> commit: b6724f118d44606fddde391ba7527526b3cad211 [4/5] prctl: Hook L1D flushing in via prctl
> config: i386-randconfig-r026-20210115 (attached as .config)
> compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
> reproduce (this is a W=1 build):
>         # https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?id=b6724f118d44606fddde391ba7527526b3cad211
>         git remote add tip https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
>         git fetch --no-tags tip x86/pti
>         git checkout b6724f118d44606fddde391ba7527526b3cad211
>         # save the attached .config to linux build tree
>         make W=1 ARCH=i386
>

There is a newer revision of the patches posted at 
 https://lore.kernel.org/lkml/20210108121056.21940-1-sblbir@amazon.com/T/

which should not have this problem/issue.

Balbir Singh.

      reply	other threads:[~2021-01-20 11:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-16  3:21 [tip:x86/pti 4/5] arch/x86/mm/tlb.c:319:6: warning: variable 'cpu' set but not used kernel test robot
2021-01-20 10:37 ` Singh, Balbir [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=71f2a4567f0853b26048918ec1afff24ae87e5be.camel@amazon.com \
    --to=sblbir@amazon.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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