All of lore.kernel.org
 help / color / mirror / Atom feed
From: Javier Martinez Canillas <javierm@redhat.com>
To: Melissa Wen <mwen@igalia.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Emma Anholt <emma@anholt.net>,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement
Date: Fri, 10 Jun 2022 14:13:33 +0200	[thread overview]
Message-ID: <0ac368d9-efe6-ab98-a695-292bca8febf8@redhat.com> (raw)
In-Reply-To: <20220610110556.63mddbye7vxq6mzb@mail.igalia.com>

Hello Melissa,

On 6/10/22 13:05, Melissa Wen wrote:
> On 06/08, Javier Martinez Canillas wrote:

[snip]

> 
> Hi Javier,
> 
> Thanks for waiting a little.
> 
> Stefan guided me to the missing part and I'm okay on this serie.
>

No worries and thanks for the testing.
 
> If there's any r-b missing for drm/v3d, you can add mine:
> Reviewed-by: Melissa Wen <mwen@igalia.com>
> 
> But if you prefer that I applied them, just let me know.
> 

If you can apply them that's even better since you are more involved
with this driver. I was just trying to be helpful and that's why I
volunteered to push, to prevent this effort to get stalled :)

-- 
Best regards,

Javier Martinez Canillas
Linux Engineering
Red Hat


WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javierm@redhat.com>
To: Melissa Wen <mwen@igalia.com>
Cc: Stefan Wahren <stefan.wahren@i2se.com>,
	devicetree@vger.kernel.org,
	Florian Fainelli <f.fainelli@gmail.com>,
	Emma Anholt <emma@anholt.net>, Arnd Bergmann <arnd@arndb.de>,
	David Airlie <airlied@linux.ie>,
	Catalin Marinas <catalin.marinas@arm.com>,
	dri-devel@lists.freedesktop.org, Rob Herring <robh+dt@kernel.org>,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	bcm-kernel-feedback-list@broadcom.com,
	Peter Robinson <pbrobinson@gmail.com>,
	maxime@cerno.tech, Will Deacon <will@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement
Date: Fri, 10 Jun 2022 14:13:33 +0200	[thread overview]
Message-ID: <0ac368d9-efe6-ab98-a695-292bca8febf8@redhat.com> (raw)
In-Reply-To: <20220610110556.63mddbye7vxq6mzb@mail.igalia.com>

Hello Melissa,

On 6/10/22 13:05, Melissa Wen wrote:
> On 06/08, Javier Martinez Canillas wrote:

[snip]

> 
> Hi Javier,
> 
> Thanks for waiting a little.
> 
> Stefan guided me to the missing part and I'm okay on this serie.
>

No worries and thanks for the testing.
 
> If there's any r-b missing for drm/v3d, you can add mine:
> Reviewed-by: Melissa Wen <mwen@igalia.com>
> 
> But if you prefer that I applied them, just let me know.
> 

If you can apply them that's even better since you are more involved
with this driver. I was just trying to be helpful and that's why I
volunteered to push, to prevent this effort to get stalled :)

-- 
Best regards,

Javier Martinez Canillas
Linux Engineering
Red Hat


WARNING: multiple messages have this Message-ID (diff)
From: Javier Martinez Canillas <javierm@redhat.com>
To: Melissa Wen <mwen@igalia.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Peter Robinson <pbrobinson@gmail.com>,
	Arnd Bergmann <arnd@arndb.de>,
	bcm-kernel-feedback-list@broadcom.com,
	Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
	devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Emma Anholt <emma@anholt.net>,
	linux-arm-kernel@lists.infradead.org,
	linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
	Nicolas Saenz Julienne <nsaenz@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>
Subject: Re: [PATCH v6 0/6] Raspberry PI 4 V3D enablement
Date: Fri, 10 Jun 2022 14:13:33 +0200	[thread overview]
Message-ID: <0ac368d9-efe6-ab98-a695-292bca8febf8@redhat.com> (raw)
In-Reply-To: <20220610110556.63mddbye7vxq6mzb@mail.igalia.com>

Hello Melissa,

On 6/10/22 13:05, Melissa Wen wrote:
> On 06/08, Javier Martinez Canillas wrote:

[snip]

> 
> Hi Javier,
> 
> Thanks for waiting a little.
> 
> Stefan guided me to the missing part and I'm okay on this serie.
>

No worries and thanks for the testing.
 
> If there's any r-b missing for drm/v3d, you can add mine:
> Reviewed-by: Melissa Wen <mwen@igalia.com>
> 
> But if you prefer that I applied them, just let me know.
> 

If you can apply them that's even better since you are more involved
with this driver. I was just trying to be helpful and that's why I
volunteered to push, to prevent this effort to get stalled :)

-- 
Best regards,

Javier Martinez Canillas
Linux Engineering
Red Hat


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-06-10 12:13 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  9:26 [PATCH v6 0/6] Raspberry PI 4 V3D enablement Peter Robinson
2022-06-03  9:26 ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 2/6] drm/v3d: Get rid of pm code Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03 11:29   ` Melissa Wen
2022-06-03 11:29     ` Melissa Wen
2022-06-03 11:29     ` Melissa Wen
2022-06-03  9:26 ` [PATCH v6 3/6] drm/v3d: Add support for bcm2711 Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26 ` [PATCH v6 4/6] ARM: dts: bcm2711: Enable V3D Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:07   ` Florian Fainelli
2022-06-13 17:07     ` Florian Fainelli
2022-06-03  9:26 ` [PATCH v6 5/6] ARM: configs: Enable DRM_V3D Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:08   ` Florian Fainelli
2022-06-13 17:08     ` Florian Fainelli
2022-06-03  9:26 ` [PATCH v6 6/6] arm64: config: " Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-03  9:26   ` Peter Robinson
2022-06-13 17:08   ` Florian Fainelli
2022-06-13 17:08     ` Florian Fainelli
2022-06-08  9:26 ` [PATCH v6 0/6] Raspberry PI 4 V3D enablement Florian Fainelli
2022-06-08  9:26   ` Florian Fainelli
2022-06-08 12:23   ` Javier Martinez Canillas
2022-06-08 12:23     ` Javier Martinez Canillas
2022-06-08 15:51     ` Melissa Wen
2022-06-08 15:51       ` Melissa Wen
2022-06-08 15:51       ` Melissa Wen
2022-06-08 16:48       ` Javier Martinez Canillas
2022-06-08 16:48         ` Javier Martinez Canillas
2022-06-08 16:48         ` Javier Martinez Canillas
2022-06-10 11:05         ` Melissa Wen
2022-06-10 11:05           ` Melissa Wen
2022-06-10 11:05           ` Melissa Wen
2022-06-10 12:13           ` Javier Martinez Canillas [this message]
2022-06-10 12:13             ` Javier Martinez Canillas
2022-06-10 12:13             ` Javier Martinez Canillas
2022-06-13  9:30             ` Melissa Wen
2022-06-13  9:30               ` Melissa Wen
2022-06-13  9:30               ` Melissa Wen
2022-06-08 12:51 ` Melissa Wen
2022-06-08 12:51   ` Melissa Wen
2022-06-08 12:51   ` Melissa Wen
2022-06-08 22:35   ` Stefan Wahren
2022-06-08 22:35     ` Stefan Wahren
2022-06-08 22:35     ` Stefan Wahren
2022-06-10 10:39     ` Melissa Wen
2022-06-10 10:39       ` Melissa Wen
2022-06-10 10:39       ` Melissa Wen

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=0ac368d9-efe6-ab98-a695-292bca8febf8@redhat.com \
    --to=javierm@redhat.com \
    --cc=airlied@linux.ie \
    --cc=arnd@arndb.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=catalin.marinas@arm.com \
    --cc=daniel@ffwll.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=emma@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rpi-kernel@lists.infradead.org \
    --cc=maxime@cerno.tech \
    --cc=mwen@igalia.com \
    --cc=nsaenz@kernel.org \
    --cc=pbrobinson@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=stefan.wahren@i2se.com \
    --cc=will@kernel.org \
    /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.