From: Thomas Gleixner <tglx@linutronix.de>
To: kernel test robot <lkp@intel.com>, "Peter\,
Zijlstra\," <peterz@infradead.org>
Cc: LKP <lkp@lists.01.org>,
linux-kernel@vger.kernel.org, x86@kernel.org,
linux-kernel@vger.kernel.org, philip.li@intel.com
Subject: Re: b614345f52 ("x86/entry: Clarify irq_{enter,exit}_rcu()"): WARNING: CPU: 0 PID: 0 at kernel/locking/lockdep.c:3680 lockdep_hardirqs_on_prepare
Date: Wed, 03 Jun 2020 12:23:56 +0200 [thread overview]
Message-ID: <87v9k8fnwj.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <5ed39ad2.0a1dg5gg0oNfWJPp%lkp@intel.com>
kernel test robot <lkp@intel.com> writes:
> 0-DAY CI Kernel Test Service, Intel Corporation
> https://lists.01.org/hyperkitty/list/lkp@lists.01.org
> #!/bin/bash
>
> kernel=$1
> initrd=yocto-x86_64-trinity.cgz
>
> wget --no-clobber https://download.01.org/0day-ci/lkp-qemu/osimage/yocto/$initrd
That results in a 404. Still the same problem as months ago.
initrd=yocto-trinity-x86_64.cgz
works ....
next prev parent reply other threads:[~2020-06-03 10:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 11:53 kernel test robot
2020-06-03 10:23 ` Thomas Gleixner [this message]
2020-06-04 0:26 ` [LKP] " Rong Chen
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=87v9k8fnwj.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=peterz@infradead.org \
--cc=philip.li@intel.com \
--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
all inboxes | Powered by JetHome®