From: Simona Vetter <simona.vetter@ffwll.ch>
To: "Raphaël Gallais-Pou" <rgallaispou@gmail.com>
Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm: of: fix documentation reference
Date: Mon, 14 Jul 2025 14:27:01 +0200 [thread overview]
Message-ID: <aHT3lW9WlM-fB_Nb@phenom.ffwll.local> (raw)
In-Reply-To: <11d29a7e-d36b-42e4-abe0-9f72a478c5c6@gmail.com>
On Sun, Jul 13, 2025 at 03:51:56PM +0200, Raphaël Gallais-Pou wrote:
>
> Le 09/06/2025 à 15:35, Raphael Gallais-Pou a écrit :
> > Documentation/devicetree/bindings/graph.txt content has move directly to
> > the dt-schema repo.
> >
> > Point to the YAML of the official repo instead of the old file.
> >
> > Signed-off-by: Raphael Gallais-Pou <rgallaispou@gmail.com>
>
> Hi,
>
> Gentle ping !
Applied to drm-misc-next, thanks for your patch. For next time around
might help if you include a reference to the upstream commit that moved
the dt file out-of-tree.
Thanks, Sima
>
> Best regards,
> Raphaël
> > ---
> > drivers/gpu/drm/drm_of.c | 7 +++++--
> > 1 file changed, 5 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_of.c b/drivers/gpu/drm/drm_of.c
> > index d0183dea770308e77f05da364ffe087d53f3be36..4f65ce729a473ec372bd76a60ac11a40ffb5df97 100644
> > --- a/drivers/gpu/drm/drm_of.c
> > +++ b/drivers/gpu/drm/drm_of.c
> > @@ -55,7 +55,8 @@ EXPORT_SYMBOL(drm_of_crtc_port_mask);
> > * and generate the DRM mask of CRTCs which may be attached to this
> > * encoder.
> > *
> > - * See Documentation/devicetree/bindings/graph.txt for the bindings.
> > + * See https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/graph.yaml
> > + * for the bindings.
> > */
> > uint32_t drm_of_find_possible_crtcs(struct drm_device *dev,
> > struct device_node *port)
> > @@ -106,7 +107,9 @@ EXPORT_SYMBOL_GPL(drm_of_component_match_add);
> > * Parse the platform device OF node and bind all the components associated
> > * with the master. Interface ports are added before the encoders in order to
> > * satisfy their .bind requirements
> > - * See Documentation/devicetree/bindings/graph.txt for the bindings.
> > + *
> > + * See https://github.com/devicetree-org/dt-schema/blob/main/dtschema/schemas/graph.yaml
> > + * for the bindings.
> > *
> > * Returns zero if successful, or one of the standard error codes if it fails.
> > */
> >
> > ---
> > base-commit: 6f392f37165008cfb3f89d723aa019e372ee79b9
> > change-id: 20250609-drm-misc-next-2f4dd8f88bb9
> >
> > Best regards,
>
--
Simona Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
next prev parent reply other threads:[~2025-07-14 12:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 13:35 Raphael Gallais-Pou
2025-07-13 13:51 ` Raphaël Gallais-Pou
2025-07-14 12:27 ` Simona Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-28 11:41 Raphael Gallais-Pou
2025-03-28 14:15 ` Maxime Ripard
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=aHT3lW9WlM-fB_Nb@phenom.ffwll.local \
--to=simona.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=rgallaispou@gmail.com \
--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®