From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android12-5.4-lts 16747/29903] htmldocs: ./fs/inode.c:1609: WARNING: Inline emphasis start-string without end-string.
Date: Sun, 29 Oct 2023 10:20:56 +0800 [thread overview]
Message-ID: <202310291024.lEvg3jPL-lkp@intel.com> (raw)
Hi Jaegeuk,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android12-5.4-lts
head: fcdc8d9a71cdda01c736bb52ad5d494e5b0937a3
commit: 7a42ec4d9dae843ce99a9ee771d13c67084f2435 [16747/29903] Revert "Revert "fs: Enable bmap() function to properly return errors""
reproduce: (https://download.01.org/0day-ci/archive/20231029/202310291024.lEvg3jPL-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/202310291024.lEvg3jPL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> ./fs/inode.c:1609: WARNING: Inline emphasis start-string without end-string.
vim +1609 ./fs/inode.c
1602
1603 #ifdef CONFIG_BLOCK
1604 /**
1605 * bmap - find a block number in a file
1606 * @inode: inode owning the block number being requested
1607 * @block: pointer containing the block to find
1608 *
> 1609 * Replaces the value in *block with the block number on the device holding
1610 * corresponding to the requested block number in the file.
1611 * That is, asked for block 4 of inode 1 the function will replace the
1612 * 4 in *block, with disk block relative to the disk start that holds that
1613 * block of the file.
1614 *
1615 * Returns -EINVAL in case of error, 0 otherwise. If mapping falls into a
1616 * hole, returns 0 and *block is also set to 0.
1617 */
1618 int bmap(struct inode *inode, sector_t *block)
1619 {
1620 if (!inode->i_mapping->a_ops->bmap)
1621 return -EINVAL;
1622
1623 *block = inode->i_mapping->a_ops->bmap(inode->i_mapping, *block);
1624 return 0;
1625 }
1626 EXPORT_SYMBOL(bmap);
1627 #endif
1628
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-10-29 2:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202310291024.lEvg3jPL-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--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.