All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel test robot <lkp@intel.com>
Cc: oe-kbuild-all@lists.linux.dev, llvm@lists.linux.dev
Subject: [broonie-spi:for-6.6 14/42] vmlinux.o: warning: objtool: amd_spi_host_transfer() falls through to next function amd_spi_max_transfer_size()
Date: Sat, 12 Aug 2023 03:21:38 +0800	[thread overview]
Message-ID: <202308120329.no6VNiTY-lkp@intel.com> (raw)

CC: linux-spi@vger.kernel.org
TO: Yang Yingliang <yangyingliang@huawei.com>
CC: Mark Brown <broonie@kernel.org>

Hi Yang,

FYI, the error/warning was bisected to this commit, please ignore it if it's irrelevant.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-6.6
head:   ddaec4e44d4e2a556b51159d48788a85ff67179d
commit: e9759d403baaeda9ea4d61d64c3151e214561217 [14/42] spi: amd: switch to use modern name
config: x86_64-randconfig-r033-20230811 (https://download.01.org/0day-ci/archive/20230812/202308120329.no6VNiTY-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce: (https://download.01.org/0day-ci/archive/20230812/202308120329.no6VNiTY-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/202308120329.no6VNiTY-lkp@intel.com/

All warnings (new ones prefixed by >>):

   vmlinux.o: warning: objtool: jffs2_erase_pending_blocks() falls through to next function jffs2_free_jeb_node_refs()
>> vmlinux.o: warning: objtool: amd_spi_host_transfer() falls through to next function amd_spi_max_transfer_size()

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

                 reply	other threads:[~2023-08-11 19: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=202308120329.no6VNiTY-lkp@intel.com \
    --to=lkp@intel.com \
    --cc=llvm@lists.linux.dev \
    --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.