From: Jani Nikula <jani.nikula@linux.intel.com>
To: Maxime Ripard <mripard@kernel.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Javier Carrasco <javier.carrasco.cruz@gmail.com>
Cc: Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: (subset) [PATCH v2] drm/connector: document DRM_MODE_COLORIMETRY_COUNT
Date: Mon, 11 Sep 2023 13:23:34 +0300 [thread overview]
Message-ID: <87il8hf1p5.fsf@intel.com> (raw)
In-Reply-To: <169409716450.2201230.1132363284756871897.b4-ty@kernel.org>
On Thu, 07 Sep 2023, Maxime Ripard <mripard@kernel.org> wrote:
> On Wed, 06 Sep 2023 22:47:38 +0200, Javier Carrasco wrote:
>> The drm_colorspace enum member DRM_MODE_COLORIMETRY_COUNT has been
>> properly documented by moving the description out of the enum to the
>> member description list to get rid of an additional warning and improve
>> documentation clarity.
>>
>>
>
> Applied to drm/drm-misc (drm-misc-next).
After the fact, but adding /* private: */ would've been an alternative
approach. I think support for that for enums should be there.
Anyway, just for future reference, the merged patch is fine.
BR,
Jani.
>
> Thanks!
> Maxime
>
--
Jani Nikula, Intel Open Source Graphics Center
next prev parent reply other threads:[~2023-09-11 22:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 20:47 [PATCH v2] drm/connector: document DRM_MODE_COLORIMETRY_COUNT Javier Carrasco
2023-09-07 14:32 ` (subset) " Maxime Ripard
2023-09-11 10:23 ` Jani Nikula [this message]
2023-09-11 15:16 ` Randy Dunlap
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=87il8hf1p5.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=javier.carrasco.cruz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rdunlap@infradead.org \
--cc=tzimmermann@suse.de \
/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