All of lore.kernel.org
 help / color / mirror / Atom feed
From: Iago Toral <itoral@igalia.com>
To: Stefan Wahren <wahrenst@gmx.net>, Maira Canal <mcanal@igalia.com>,
	 dri-devel@lists.freedesktop.org
Cc: Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Emma Anholt <emma@anholt.net>, Melissa Wen <mwen@igalia.com>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v2 3/4] dt-bindings: gpu: v3d: Add BCM2712's compatible
Date: Mon, 30 Oct 2023 11:18:38 +0100	[thread overview]
Message-ID: <641b573516a2d22dfe082b1c25b26e4e68d6a68b.camel@igalia.com> (raw)
In-Reply-To: <1d926740-74d8-4114-85c7-30b2e986ba8a@gmx.net>

El lun, 30-10-2023 a las 10:57 +0100, Stefan Wahren escribió:
> Hi Iago,
> 
> Am 30.10.23 um 09:28 schrieb Iago Toral Quiroga:
> > BCM2712, Raspberry Pi 5's SoC, contains a V3D core. So add its
> > specific
> > compatible to the bindings.
> > 
> > v2: new, requested by Stefan Wahren.
> Thanks for sending this but the line above belongs below --- since
> it's
> not relevant after the patch has been applied.
> > 
> > Signed-off-by: Iago Toral Quiroga <itoral@igalia.com>
> Unfortunately this patch will be ignored because the relevant
> devicetree
> people are missing to give their Ack.
> 
> Please use scripts/get_maintainers.pl
> 

Sorry about that, my bad, should I resend the patch (as part of a v3)
or is it enough to add the relevant maintainers in a reply to the
original v2 patch?

Iago

> Best regards
> > ---
> >   Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml | 1 +
> >   1 file changed, 1 insertion(+)
> > 
> > diff --git a/Documentation/devicetree/bindings/gpu/brcm,bcm-
> > v3d.yaml b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
> > index dae55b8a267b..dc078ceeca9a 100644
> > --- a/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
> > +++ b/Documentation/devicetree/bindings/gpu/brcm,bcm-v3d.yaml
> > @@ -17,6 +17,7 @@ properties:
> >     compatible:
> >       enum:
> >         - brcm,2711-v3d
> > +      - brcm,2712-v3d
> >         - brcm,7268-v3d
> >         - brcm,7278-v3d
> > 
> 
> 


  reply	other threads:[~2023-10-30 10:18 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-30  8:28 [PATCH v2 0/4] V3D module changes for Pi5 Iago Toral Quiroga
2023-10-30  8:28 ` [PATCH v2 1/4] drm/v3d: update UAPI to match user-space for V3D 7.x Iago Toral Quiroga
2023-10-30  8:28 ` [PATCH v2 2/4] drm/v3d: fix up register addresses " Iago Toral Quiroga
2023-10-30  9:58   ` Stefan Wahren
2023-10-30 10:14     ` Iago Toral
2023-10-30 10:28       ` Stefan Wahren
2023-10-30 10:30         ` Iago Toral
2023-10-30  8:28 ` [PATCH v2 3/4] dt-bindings: gpu: v3d: Add BCM2712's compatible Iago Toral Quiroga
2023-10-30  9:57   ` Stefan Wahren
2023-10-30 10:18     ` Iago Toral [this message]
2023-10-30 10:23       ` Stefan Wahren
2023-10-30 14:39   ` Krzysztof Kozlowski
2023-10-30  8:28 ` [PATCH v2 4/4] drm/v3d: add brcm,2712-v3d as a compatible V3D device Iago Toral Quiroga
2023-10-30 10:01   ` Stefan Wahren
2023-10-30 12:26 ` [PATCH v2 0/4] V3D module changes for Pi5 Maira Canal

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=641b573516a2d22dfe082b1c25b26e4e68d6a68b.camel@igalia.com \
    --to=itoral@igalia.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=mcanal@igalia.com \
    --cc=mwen@igalia.com \
    --cc=nsaenz@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=wahrenst@gmx.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.