From: Cyril Hrubis <chrubis@suse.cz>
To: Niklas Cassel <Niklas.Cassel@wdc.com>
Cc: Damien Le Moal <dlemoal@kernel.org>,
kernel test robot <oliver.sang@intel.com>,
"lkp@intel.com" <lkp@intel.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Hannes Reinecke <hare@suse.de>,
"oe-lkp@lists.linux.dev" <oe-lkp@lists.linux.dev>,
Christoph Hellwig <hch@lst.de>,
"ltp@lists.linux.it" <ltp@lists.linux.it>,
Petr Vorel <pvorel@suse.cz>
Subject: Re: [LTP] [linux-next:master] [scsi] eca2040972: ltp.ioprio_set03.fail
Date: Thu, 22 Jun 2023 10:00:40 +0200 [thread overview]
Message-ID: <ZJP_qPeJ37H4qhEN@yuki> (raw)
In-Reply-To: <ZJMYP/CCVviG6IMq@x1-carbon>
Hi!
> But... shouldn't the installed uapi headers match the running kernel?
Genearlly this is tough nut to crack. It's nearly impossible for headers
to actually match the running kernel in testing environments, since
quite often the testsuite is compiled beforehand and only retrieved,
since recompiling for each testrun is wasting too many cycles. I would
say that the best we can have is that UAPI headers shouldn't be newer
than running kernel.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2023-06-22 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 5:58 kernel test robot
2023-06-20 7:42 ` Damien Le Moal
2023-06-21 12:47 ` [LTP] " Cyril Hrubis
2023-06-21 15:33 ` Niklas Cassel
2023-06-22 7:32 ` Petr Vorel
2023-06-22 8:30 ` Damien Le Moal
2023-06-22 8:00 ` Cyril Hrubis [this message]
2023-07-05 8:36 ` Liu, Yujie
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=ZJP_qPeJ37H4qhEN@yuki \
--to=chrubis@suse.cz \
--cc=Niklas.Cassel@wdc.com \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=martin.petersen@oracle.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
--cc=pvorel@suse.cz \
/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