From: Marek Vasut <marek.vasut@mailbox.org>
To: dri-devel@lists.freedesktop.org
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Simona Vetter <simona@ffwll.ch>,
Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Luca Ceresoli <luca.ceresoli@bootlin.com>
Subject: Re: [PATCH] drm: of: Fix drm_of_get_data_lanes_count_ep() return value documentation
Date: Mon, 2 Mar 2026 22:36:23 +0100 [thread overview]
Message-ID: <6f172d61-e421-44dc-b160-d885ef023e67@mailbox.org> (raw)
In-Reply-To: <bd453972-529b-42bc-8b8d-41afd1f5008d@mailbox.org>
On 2/6/26 12:49 PM, Marek Vasut wrote:
> On 1/15/26 3:45 AM, Marek Vasut wrote:
>> Update drm_of_get_data_lanes_count_ep() return value documentation
>> to match the drm_of_get_data_lanes_count() return value documentation.
>> The drm_of_get_data_lanes_count_ep() is only a wrapper around the
>> drm_of_get_data_lanes_count() and therefore returns the same error
>> codes.
>>
>> Fixes: fc801750b197 ("drm: of: Add drm_of_get_data_lanes_count and
>> drm_of_get_data_lanes_ep")
>> Reported-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org>
>> ---
>> Cc: David Airlie <airlied@gmail.com>
>> Cc: Geert Uytterhoeven <geert+renesas@glider.be>
>> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> Cc: Maxime Ripard <mripard@kernel.org>
>> Cc: Simona Vetter <simona@ffwll.ch>
>> Cc: Thomas Zimmermann <tzimmermann@suse.de>
>> Cc: dri-devel@lists.freedesktop.org
>> Cc: linux-kernel@vger.kernel.org
>> Cc: linux-renesas-soc@vger.kernel.org
>> ---
>> drivers/gpu/drm/drm_of.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/drivers/gpu/drm/drm_of.c b/drivers/gpu/drm/drm_of.c
>> index 4f65ce729a473..cfd0518174de8 100644
>> --- a/drivers/gpu/drm/drm_of.c
>> +++ b/drivers/gpu/drm/drm_of.c
>> @@ -539,8 +539,8 @@ EXPORT_SYMBOL_GPL(drm_of_get_data_lanes_count);
>> *
>> * Return:
>> * * min..max - positive integer count of "data-lanes" elements
>> - * * -EINVAL - the "data-mapping" property is unsupported
>> - * * -ENODEV - the "data-mapping" property is missing
>> + * * -ve - the "data-lanes" property is missing or invalid
>> + * * -EINVAL - the "data-lanes" property is unsupported
>> */
>> int drm_of_get_data_lanes_count_ep(const struct device_node *port,
>> int port_reg, int reg,
>
>
> Is anything missing here or can this be applied ?
Can this be applied now ?
next prev parent reply other threads:[~2026-03-02 21:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 2:45 Marek Vasut
2026-02-06 11:49 ` Marek Vasut
2026-03-02 21:36 ` Marek Vasut [this message]
2026-03-03 8:07 ` Maxime Ripard
2026-03-03 8:14 ` Geert Uytterhoeven
2026-03-03 8:39 ` Maxime Ripard
2026-03-03 13:46 ` Luca Ceresoli
2026-03-03 20:57 ` Marek Vasut
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=6f172d61-e421-44dc-b160-d885ef023e67@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--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
all inboxes | Powered by JetHome®