From: Christoph Hellwig <hch@lst.de>
To: Philip Li <philip.li@intel.com>
Cc: Christoph Hellwig <hch@lst.de>, kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev
Subject: Re: [hch-misc:block-error-injection 3/4] block/blk-core.c:141:33: sparse: sparse: cast to restricted blk_opf_t
Date: Wed, 10 Jun 2026 13:59:10 +0200 [thread overview]
Message-ID: <20260610115910.GC19624@lst.de> (raw)
In-Reply-To: <ailRL3E4dtN6/mUE@rli9-mobl>
On Wed, Jun 10, 2026 at 07:57:35PM +0800, Philip Li wrote:
> On Wed, Jun 10, 2026 at 01:37:57PM +0200, Christoph Hellwig wrote:
> > On Wed, Jun 10, 2026 at 07:22:03PM +0800, kernel test robot wrote:
> > > 139 for (i = 0; i < ARRAY_SIZE(blk_op_name); i++)
> > > 140 if (blk_op_name[i] && !strcmp(blk_op_name[i], op))
> > > > 141 return (enum req_op)i;
> >
> > My spare on x86 and varous cross builds is perfectly fine with it.
> > What sparese version is installed on the microblaze build box?
>
> The version used is
>
> sparse: v0.6.5-rc1
That's pretty current. No idea why this generates a warning on
microblaze, but not elsewhere.
prev parent reply other threads:[~2026-06-10 11:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 11:22 [hch-misc:block-error-injection 3/4] block/blk-core.c:141:33: sparse: sparse: cast to restricted blk_opf_t kernel test robot
2026-06-10 11:37 ` Christoph Hellwig
2026-06-10 11:57 ` Philip Li
2026-06-10 11:59 ` Christoph Hellwig [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=20260610115910.GC19624@lst.de \
--to=hch@lst.de \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philip.li@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.