public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: kbuild test robot <lkp@intel.com>
To: allen <allen.chen@ite.com.tw>
Cc: kbuild-all@lists.01.org, Allen Chen <allen.chen@ite.com.tw>,
	Pi-Hsun Shih <pihsun@chromium.org>,
	Jau-Chih Tseng <Jau-Chih.Tseng@ite.com.tw>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <maxime.ripard@bootlin.com>,
	Sean Paul <sean@poorly.run>, David Airlie <airlied@linux.ie>,
	"open list:DRM DRIVERS" <dri-devel@lists.freedesktop.org>,
	open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/edid: fixup EDID 1.3 and 1.4 judge reduced-blanking timings logic
Date: Sun, 3 Nov 2019 15:51:00 +0800	[thread overview]
Message-ID: <201911031510.4s2wqcIN%lkp@intel.com> (raw)
In-Reply-To: <1572595463-30970-1-git-send-email-allen.chen@ite.com.tw>

Hi allen,

I love your patch! Perhaps something to improve:

[auto build test WARNING on linus/master]
[also build test WARNING on v5.4-rc5 next-20191031]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system. BTW, we also suggest to use '--base' option to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/allen/drm-edid-fixup-EDID-1-3-and-1-4-judge-reduced-blanking-timings-logic/20191102-200357
base:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git 1204c70d9dcba31164f78ad5d8c88c42335d51f8

If you fix the issue, kindly add following tag
Reported-by: kbuild test robot <lkp@intel.com>

smatch warnings:
drivers/gpu/drm/drm_edid.c:2042 drm_monitor_supports_rb() warn: always true condition '(closure.support_rb >= 0) => (0-255 >= 0)'

vim +2042 drivers/gpu/drm/drm_edid.c

  2030	
  2031	/* EDID 1.4 defines this explicitly.  For EDID 1.3, we guess, badly. */
  2032	static bool
  2033	drm_monitor_supports_rb(struct edid *edid)
  2034	{
  2035		struct edid_support_rb_closure closure = {
  2036			.edid = edid,
  2037			.support_rb = -1,
  2038		};
  2039	
  2040		if (edid->revision >= 4) {
  2041			drm_for_each_detailed_block((u8 *)edid, is_rb, &closure);
> 2042			if (closure.support_rb >= 0)
  2043				return closure.support_rb;
  2044		}
  2045	
  2046		return true;
  2047	}
  2048	

---
0-DAY kernel test infrastructure                Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all                   Intel Corporation

  reply	other threads:[~2019-11-03  7:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-01  8:04 [PATCH] drm/edid: fixup EDID 1.3 and 1.4 judge reduced-blanking timings logic allen
2019-11-03  7:51 ` kbuild test robot [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-04  8:42 allen
2019-11-07 15:42 ` Ville Syrjälä
2019-11-11  1:43   ` allen.chen
2019-11-11 13:54     ` Ville Syrjälä
2019-11-26  9:46 allen
2019-11-27 10:29 ` Jani Nikula
     [not found]   ` <e2486891920843798e9af97209464833@ite.com.tw>
2019-12-03  8:02     ` Jani Nikula
2019-12-10 11:10 ` Jani Nikula
2019-12-11  3:47   ` allen.chen

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=201911031510.4s2wqcIN%lkp@intel.com \
    --to=lkp@intel.com \
    --cc=Jau-Chih.Tseng@ite.com.tw \
    --cc=airlied@linux.ie \
    --cc=allen.chen@ite.com.tw \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=pihsun@chromium.org \
    --cc=sean@poorly.run \
    /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