From: kernel test robot <lkp@intel.com>
To: Lyude Paul <lyude@redhat.com>
Cc: kbuild-all@lists.01.org,
Linux Memory Management List <linux-mm@kvack.org>,
Ilia Mirkin <imirkin@alum.mit.edu>
Subject: [linux-next:master 3518/6356] drivers/gpu/drm/drm_edid.o: warning: objtool: do_cvt_mode() falls through to next function drm_mode_detailed.isra.0()
Date: Mon, 16 Nov 2020 20:35:01 +0800 [thread overview]
Message-ID: <202011162058.sbMm3BZD-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 034307507118f7e1b18f8403c85af2216da2dc94
commit: 991fcb77f490390bcad89fa67d95763c58cdc04c [3518/6356] drm/edid: Fix uninitialized variable in drm_cvt_modes()
config: x86_64-randconfig-r036-20201116 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-15) 9.3.0
reproduce (this is a W=1 build):
# https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/?id=991fcb77f490390bcad89fa67d95763c58cdc04c
git remote add linux-next https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
git fetch --no-tags linux-next master
git checkout 991fcb77f490390bcad89fa67d95763c58cdc04c
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> drivers/gpu/drm/drm_edid.o: warning: objtool: do_cvt_mode() falls through to next function drm_mode_detailed.isra.0()
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 35205 bytes --]
reply other threads:[~2020-11-16 12:35 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=202011162058.sbMm3BZD-lkp@intel.com \
--to=lkp@intel.com \
--cc=imirkin@alum.mit.edu \
--cc=kbuild-all@lists.01.org \
--cc=linux-mm@kvack.org \
--cc=lyude@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).