All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
To: Christoph Hellwig <hch@lst.de>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [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 19:22:03 +0800	[thread overview]
Message-ID: <202606101953.PdmBi8go-lkp@intel.com> (raw)

tree:   git://git.infradead.org/users/hch/misc.git block-error-injection
head:   5976bb2f6894c34ac87cd38acf150423724c4628
commit: 7979d56135777d83ac77af6854484aa7a4c8c871 [3/4] block: add a str_to_blk_op helper
config: microblaze-randconfig-r113-20260610 (https://download.01.org/0day-ci/archive/20260610/202606101953.PdmBi8go-lkp@intel.com/config)
compiler: microblaze-linux-gcc (GCC) 10.5.0
sparse: v0.6.5-rc1
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260610/202606101953.PdmBi8go-lkp@intel.com/reproduce)

If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202606101953.PdmBi8go-lkp@intel.com/

sparse warnings: (new ones prefixed by >>)
>> block/blk-core.c:141:33: sparse: sparse: cast to restricted blk_opf_t

vim +141 block/blk-core.c

   134	
   135	enum req_op str_to_blk_op(const char *op)
   136	{
   137		int i;
   138	
   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;
   142		return REQ_OP_LAST;
   143	}
   144	

--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki

             reply	other threads:[~2026-06-10 11:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 11:22 kernel test robot [this message]
2026-06-10 11:37 ` [hch-misc:block-error-injection 3/4] block/blk-core.c:141:33: sparse: sparse: cast to restricted blk_opf_t Christoph Hellwig
2026-06-10 11:57   ` Philip Li
2026-06-10 11:59     ` Christoph Hellwig

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=202606101953.PdmBi8go-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=hch@lst.de \
    --cc=oe-kbuild-all@lists.linux.dev \
    /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.