From: Randy Dunlap <rdunlap@infradead.org>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Rob Clark" <robdclark@gmail.com>
Cc: dri-devel@lists.freedesktop.org,
Rob Clark <robdclark@chromium.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/vblank: Simplify drm_dev_has_vblank()
Date: Mon, 3 Apr 2023 09:28:25 -0700 [thread overview]
Message-ID: <ef2ba536-a7ea-7cfb-7cf6-9e0c02aeba80@infradead.org> (raw)
In-Reply-To: <ZCr9jrhTyGuZA+Qt@intel.com>
On 4/3/23 09:23, Ville Syrjälä wrote:
> On Mon, Apr 03, 2023 at 09:07:35AM -0700, Rob Clark wrote:
>> From: Rob Clark <robdclark@chromium.org>
>>
>> What does vblank have to do with num_crtcs? Well, this was technically
>> correct, but you'd have to go look at where num_crtcs is initialized to
>> understand why. Lets just replace it with the simpler and more obvious
>> check.
>>
>> Signed-off-by: Rob Clark <robdclark@chromium.org>
>> ---
>> drivers/gpu/drm/drm_vblank.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/gpu/drm/drm_vblank.c b/drivers/gpu/drm/drm_vblank.c
>> index 877e2067534f..ad34c235d853 100644
>> --- a/drivers/gpu/drm/drm_vblank.c
>> +++ b/drivers/gpu/drm/drm_vblank.c
>> @@ -575,7 +575,7 @@ EXPORT_SYMBOL(drm_vblank_init);
>> */
>> bool drm_dev_has_vblank(const struct drm_device *dev)
>> {
>> - return dev->num_crtcs != 0;
>> + return !!dev->vblank;
>
> The compiler knows how to turn things into a boolean.
>> Or I guess if we want to be a bit more explicit we could
> write this as
> return dev->vblank != NULL;
> but IIRC that will make checkpatch complain because of
> someone's personal taste.
checkpatch isn't an absolute thing. :)
--
~Randy
next prev parent reply other threads:[~2023-04-03 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 16:07 Rob Clark
2023-04-03 16:23 ` Ville Syrjälä
2023-04-03 16:28 ` Randy Dunlap [this message]
2023-04-04 20:46 ` Daniel Vetter
2023-04-04 21:00 ` Ville Syrjälä
2023-04-05 8:10 ` Daniel Vetter
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=ef2ba536-a7ea-7cfb-7cf6-9e0c02aeba80@infradead.org \
--to=rdunlap@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@chromium.org \
--cc=robdclark@gmail.com \
--cc=tzimmermann@suse.de \
--cc=ville.syrjala@linux.intel.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®