mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Zimmermann <tzimmermann@suse.de>
To: Ruben Wauters <rubenru09@aol.com>,
	Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	Maxime Ripard <mripard@kernel.org>,
	David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Cc: Dan Carpenter <dan.carpenter@linaro.org>,
	lkp@intel.com, oe-kbuild@lists.linux.dev,
	oe-kbuild-all@lists.linux.dev, dri-devel@lists.freedesktop.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/gud: fix accidentally deleted IS_ERR() check
Date: Tue, 23 Sep 2025 13:59:37 +0200	[thread overview]
Message-ID: <43972b5a-8bf7-4bfd-be14-45bd47a57d2c@suse.de> (raw)
In-Reply-To: <9625a9e34aee0157e57ca5b6a6bfeeeceba5ed38.camel@aol.com>

Hi

Am 23.09.25 um 11:38 schrieb Ruben Wauters:
> On Tue, 2025-09-23 at 09:57 +0200, Thomas Zimmermann wrote:
>> FYI I got the following warnings. I'll fix them when I merge the
>> patch.
>>
>> -:6: ERROR:GIT_COMMIT_ID: Please use git commit description style
>> 'commit <12+ chars of sha1> ("<title line>")' - ie: 'commit
>> 2d2f1dc74cfb
>> ("drm: gud: replace WARN_ON/WARN_ON_ONCE with drm versions")'
>> #6:
>> During conversion of WARN_ON_ONCE to drm_WARN_ON_ONCE in commit
> I'm not 100% sure why it's complaining about this one, the format
> matches. I assume it's a problem with the line break in it? but I'm not
> 100% sure.
>
>> -:15: WARNING:BAD_REPORTED_BY_LINK: Reported-by: should be
>> immediately
>> followed by Closes: with a URL to the report
>> #15:
>> Reported-by: kernel test robot <lkp@intel.com>
>> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
> I believe it's intentional to have two reported bys in a row, as both
> of them are followed by a Closes tag at the end.

Neither warning is really your fault. As you say the script doesn't like 
line breaks in certain places. It also only wants pairs of Closes/R-b tags.

Best regards
Thomas

>
> Thanks
>
>> Am 22.09.25 um 19:32 schrieb Ruben Wauters:
>>> During conversion of WARN_ON_ONCE to drm_WARN_ON_ONCE in commit
>>> 2d2f1dc74cfb ("drm: gud: replace WARN_ON/WARN_ON_ONCE with drm
>>> versions"), the IS_ERR check was accidentally removed, breaking the
>>> gud_connector_add_properties() function, as any valid pointer in
>>> state_val would produce an error.
>>>
>>> The warning was reported by kernel test robot, and is fixed in this
>>> patch.
>>>
>>> Fixes: 2d2f1dc74cfb ("drm: gud: replace WARN_ON/WARN_ON_ONCE with
>>> drm versions")
>>> Reported-by: kernel test robot <lkp@intel.com>
>>> Reported-by: Dan Carpenter <dan.carpenter@linaro.org>
>>> Closes:
>>> https://lore.kernel.org/r/202509212215.c8v3RKmL-lkp@intel.com/
>>> Signed-off-by: Ruben Wauters <rubenru09@aol.com>
>>> ---
>>>    drivers/gpu/drm/gud/gud_connector.c | 2 +-
>>>    1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> diff --git a/drivers/gpu/drm/gud/gud_connector.c
>>> b/drivers/gpu/drm/gud/gud_connector.c
>>> index 62e349b06dbe..1726a3fadff8 100644
>>> --- a/drivers/gpu/drm/gud/gud_connector.c
>>> +++ b/drivers/gpu/drm/gud/gud_connector.c
>>> @@ -593,7 +593,7 @@ int gud_connector_fill_properties(struct
>>> drm_connector_state *connector_state,
>>>    			unsigned int *state_val;
>>>    
>>>    			state_val =
>>> gud_connector_tv_state_val(prop, &connector_state->tv);
>>> -			if (drm_WARN_ON_ONCE(connector_state-
>>>> connector->dev, state_val))
>>> +			if (drm_WARN_ON_ONCE(connector_state-
>>>> connector->dev, IS_ERR(state_val)))
>>>    				return PTR_ERR(state_val);
>>>    
>>>    			val = *state_val;

-- 
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)



      reply	other threads:[~2025-09-23 11:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20250922173836.5608-1-rubenru09.ref@aol.com>
2025-09-22 17:32 ` Ruben Wauters
2025-09-23  6:38   ` Thomas Zimmermann
2025-09-23  7:57   ` Thomas Zimmermann
2025-09-23  8:29     ` Dan Carpenter
2025-09-23  9:38     ` Ruben Wauters
2025-09-23 11:59       ` Thomas Zimmermann [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=43972b5a-8bf7-4bfd-be14-45bd47a57d2c@suse.de \
    --to=tzimmermann@suse.de \
    --cc=airlied@gmail.com \
    --cc=dan.carpenter@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=oe-kbuild@lists.linux.dev \
    --cc=rubenru09@aol.com \
    --cc=simona@ffwll.ch \
    /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®