From: Cyril Hrubis <chrubis@suse.cz>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: kernel test robot <oliver.sang@intel.com>,
Niklas Cassel <niklas.cassel@wdc.com>,
lkp@intel.com, "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-kernel@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, Christoph Hellwig <hch@lst.de>,
ltp@lists.linux.it
Subject: Re: [LTP] [linux-next:master] [scsi] eca2040972: ltp.ioprio_set03.fail
Date: Wed, 21 Jun 2023 14:47:43 +0200 [thread overview]
Message-ID: <ZJLxbwCno-it2xBB@yuki> (raw)
In-Reply-To: <61f22c1d-6b04-d193-57c9-8cad1c555e4b@kernel.org>
Hi!
> > kernel test robot noticed "ltp.ioprio_set03.fail" on:
>
> LTP maintainers,
>
> Patches have been submitted to fix this issue. Were these patches applied ?
Looks like they are in, at least these two:
ioprio: use ioprio.h kernel header if it exists
ioprio: Use IOPRIO_PRIO_NUM to check prio range
And there does not seem to be anything ioprio related haning in the LTP
patchwork.
--
Cyril Hrubis
chrubis@suse.cz
WARNING: multiple messages have this Message-ID (diff)
From: Cyril Hrubis <chrubis@suse.cz>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: Niklas Cassel <niklas.cassel@wdc.com>,
lkp@intel.com, "Martin K. Petersen" <martin.petersen@oracle.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
Linux Memory Management List <linux-mm@kvack.org>,
kernel test robot <oliver.sang@intel.com>,
Hannes Reinecke <hare@suse.de>,
oe-lkp@lists.linux.dev, Christoph Hellwig <hch@lst.de>,
ltp@lists.linux.it
Subject: Re: [LTP] [linux-next:master] [scsi] eca2040972: ltp.ioprio_set03.fail
Date: Wed, 21 Jun 2023 14:47:43 +0200 [thread overview]
Message-ID: <ZJLxbwCno-it2xBB@yuki> (raw)
In-Reply-To: <61f22c1d-6b04-d193-57c9-8cad1c555e4b@kernel.org>
Hi!
> > kernel test robot noticed "ltp.ioprio_set03.fail" on:
>
> LTP maintainers,
>
> Patches have been submitted to fix this issue. Were these patches applied ?
Looks like they are in, at least these two:
ioprio: use ioprio.h kernel header if it exists
ioprio: Use IOPRIO_PRIO_NUM to check prio range
And there does not seem to be anything ioprio related haning in the LTP
patchwork.
--
Cyril Hrubis
chrubis@suse.cz
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-06-21 12:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 5:58 [LTP] [linux-next:master] [scsi] eca2040972: ltp.ioprio_set03.fail kernel test robot
2023-06-20 5:58 ` kernel test robot
2023-06-20 7:42 ` Damien Le Moal
2023-06-20 7:42 ` [LTP] " Damien Le Moal
2023-06-21 12:47 ` Cyril Hrubis [this message]
2023-06-21 12:47 ` Cyril Hrubis
2023-06-21 15:33 ` Niklas Cassel
2023-06-21 15:33 ` Niklas Cassel via ltp
2023-06-22 7:32 ` Petr Vorel
2023-06-22 7:32 ` Petr Vorel
2023-06-22 8:30 ` Damien Le Moal
2023-06-22 8:30 ` Damien Le Moal
2023-06-22 8:00 ` Cyril Hrubis
2023-06-22 8:00 ` Cyril Hrubis
2023-07-05 8:36 ` Liu, Yujie
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=ZJLxbwCno-it2xBB@yuki \
--to=chrubis@suse.cz \
--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=niklas.cassel@wdc.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@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 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.