From: Florian Fainelli <f.fainelli@gmail.com>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Eric Anholt <eric@anholt.net>, Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@linux.ie>, Daniel Vetter <daniel@ffwll.ch>,
Rob Herring <robh+dt@kernel.org>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] drm/v3d: Minor improvements
Date: Wed, 23 Dec 2020 15:37:34 -0800 [thread overview]
Message-ID: <aa2781a4-b748-cb49-bf3d-52881ea66b37@gmail.com> (raw)
In-Reply-To: <2f9769da-f5b3-0c25-2f46-a0796da225ba@gmail.com>
On 12/23/2020 1:39 PM, Florian Fainelli wrote:
>
>
> On 12/23/2020 12:27 PM, Stefan Wahren wrote:
>> This small series of v3d patches is a preparation for the upcoming bcm2711
>> support. The bcm2711 support will be send separate, because it involves
>> bigger changes.
>>
>> I'm not sure that the schema conversion patch is sufficient.
>>
>> Patch 2,3 are directly taken from Raspberry Pi 4 vendor tree.
>>
>> Nicolas Saenz Julienne (1):
>> drm/v3d: Use platform_get_irq_optional() to get optional IRQs
>>
>> Phil Elwell (2):
>> drm/v3d: Set dma_mask as well as coherent_dma_mask
>> drm/v3d: Don't clear MMU control bits on exception
>
> You need to amend your Signed-off-by to all of those 3 patches that you
> did not author.
Looks like you fixed it in v2 about 10 minutes after, sorry for the noise.
--
Florian
prev parent reply other threads:[~2020-12-23 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 20:27 [PATCH 0/4] drm/v3d: Minor improvements Stefan Wahren
2020-12-23 20:27 ` [PATCH 1/4] drm/v3d: Use platform_get_irq_optional() to get optional IRQs Stefan Wahren
2020-12-23 20:27 ` [PATCH 2/4] drm/v3d: Set dma_mask as well as coherent_dma_mask Stefan Wahren
2020-12-23 20:27 ` [PATCH 3/4] drm/v3d: Don't clear MMU control bits on exception Stefan Wahren
2020-12-23 20:27 ` [PATCH 4/4] dt-bindings: gpu: Convert v3d to json-schema Stefan Wahren
2020-12-23 21:39 ` [PATCH 0/4] drm/v3d: Minor improvements Florian Fainelli
2020-12-23 23:37 ` Florian Fainelli [this message]
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=aa2781a4-b748-cb49-bf3d-52881ea66b37@gmail.com \
--to=f.fainelli@gmail.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mripard@kernel.org \
--cc=nsaenzjulienne@suse.de \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.com \
/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;
as well as URLs for NNTP newsgroup(s).