From: kbuild test robot <lkp@intel.com>
To: Maciej Purski <m.purski@samsung.com>
Cc: kbuild-all@01.org, dri-devel@lists.freedesktop.org,
Archit Taneja <architt@codeaurora.org>,
Andrzej Hajda <a.hajda@samsung.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
David Airlie <airlied@linux.ie>,
Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
linux-kernel@vger.kernel.org,
Maciej Purski <m.purski@samsung.com>
Subject: Re: [PATCH] drm/bridge/sii8620: fix display modes validation
Date: Fri, 26 Jan 2018 07:27:52 +0800 [thread overview]
Message-ID: <201801260756.airFEko0%fengguang.wu@intel.com> (raw)
In-Reply-To: <1516706113-9016-1-git-send-email-m.purski@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 1992 bytes --]
Hi Maciej,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm/drm-next]
[also build test WARNING on next-20180119]
[cannot apply to v4.15-rc9]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system]
url: https://github.com/0day-ci/linux/commits/Maciej-Purski/drm-bridge-sii8620-fix-display-modes-validation/20180125-174703
base: git://people.freedesktop.org/~airlied/linux.git drm-next
config: i386-randconfig-sb0-01260635 (attached as .config)
compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4
reproduce:
# save the attached .config to linux build tree
make ARCH=i386
Note: it may well be a FALSE warning. FWIW you are at least aware of it now.
http://gcc.gnu.org/wiki/Better_Uninitialized_Warnings
All warnings (new ones prefixed by >>):
drivers/gpu/drm/bridge/sil-sii8620.c: In function 'sii8620_mode_valid':
>> drivers/gpu/drm/bridge/sil-sii8620.c:2242:2: warning: 'ret' may be used uninitialized in this function [-Wmaybe-uninitialized]
return ret;
^
vim +/ret +2242 drivers/gpu/drm/bridge/sil-sii8620.c
2220
2221 static enum drm_mode_status sii8620_mode_valid(struct drm_bridge *bridge,
2222 const struct drm_display_mode *mode)
2223 {
2224 enum drm_mode_status ret;
2225 struct sii8620 *ctx = bridge_to_sii8620(bridge);
2226 int pack_required = sii8620_is_packing_required(ctx, mode);
2227 bool can_pack = ctx->devcap[MHL_DCAP_VID_LINK_MODE] &
2228 MHL_DCAP_VID_LINK_PPIXEL;
2229
2230 switch (pack_required) {
2231 case -1:
2232 ret = MODE_CLOCK_HIGH;
2233 break;
2234 case 1:
2235 ret = (can_pack) ? MODE_OK : MODE_CLOCK_HIGH;
2236 break;
2237 case 0:
2238 ret = MODE_OK;
2239 break;
2240 }
2241
> 2242 return ret;
2243 }
2244
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 32004 bytes --]
prev parent reply other threads:[~2018-01-25 23:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20180123111523eucas1p2c4321e8ffc6425bec8725e2c60fec9e5@eucas1p2.samsung.com>
2018-01-23 11:15 ` Maciej Purski
2018-01-25 23:27 ` kbuild test robot [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=201801260756.airFEko0%fengguang.wu@intel.com \
--to=lkp@intel.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=architt@codeaurora.org \
--cc=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.purski@samsung.com \
--cc=m.szyprowski@samsung.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
all inboxes | Powered by JetHome®