From: Philip Li <philip.li@intel.com>
To: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Cc: "kernel test robot" <lkp@intel.com>,
"Yujie Liu" <yujie.liu@intel.com>,
oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev,
"Alex Gaynor" <alex.gaynor@gmail.com>,
"Wedson Almeida Filho" <wedsonaf@gmail.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Gary Guo" <gary@garyguo.net>,
"Björn Roy Baron" <bjorn3_gh@protonmail.com>
Subject: Re: [PATCH 4/5] rust: types: implement `ForeignOwnable` for the unit type
Date: Sat, 21 Jan 2023 10:42:57 +0800 [thread overview]
Message-ID: <Y8tRMZAwcl6rb6Jd@rli9-mobl> (raw)
In-Reply-To: <CANiq72=UD2Wnx4WgJSeKyL6WGytadG9p0Dt8YHL2cD-0zhsc4Q@mail.gmail.com>
On Fri, Jan 20, 2023 at 10:41:39PM +0100, Miguel Ojeda wrote:
> Hi kernel test robot, Yujie,
>
> On Fri, Jan 20, 2023 at 9:15 AM kernel test robot <lkp@intel.com> wrote:
> >
> > config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20230120/202301201612.50oSpQHu-lkp@intel.com/config)
>
> Could you please disable `CONFIG_RETPOLINE` and
> `CONFIG_X86_KERNEL_IBT` for the Rust config? (e.g. like in KernelCI
Got it Miguel, we will disable them for rust related configs.
> https://github.com/kernelci/kernelci-core/blob/main/config/core/build-configs.yaml#L410)
>
> We are discussing whether to add a `depends on !` or other approaches
> on the kernel side, which may make that redundant, but meanwhile it
> would be great if you could update the config.
thanks, we will do it asap.
>
> Thanks!
>
> Cheers,
> Miguel
>
next prev parent reply other threads:[~2023-01-21 2:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 8:14 [PATCH 4/5] rust: types: implement `ForeignOwnable` for the unit type kernel test robot
2023-01-20 21:41 ` Miguel Ojeda
2023-01-21 2:42 ` Philip Li [this message]
2023-01-21 11:15 ` Miguel Ojeda
2023-01-21 12:55 ` Philip Li
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=Y8tRMZAwcl6rb6Jd@rli9-mobl \
--to=philip.li@intel.com \
--cc=alex.gaynor@gmail.com \
--cc=bjorn3_gh@protonmail.com \
--cc=boqun.feng@gmail.com \
--cc=gary@garyguo.net \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=wedsonaf@gmail.com \
--cc=yujie.liu@intel.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