From: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
To: Juerg Haefliger <juerg.haefliger@canonical.com>
Cc: airlied@gmail.com, daniel@ffwll.ch,
dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
joel@joelfernandes.org, johan+linaro@kernel.org,
konrad.dybcio@linaro.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, quic_abhinavk@quicinc.com,
quic_akhilpo@quicinc.com, ribalda@chromium.org,
robdclark@gmail.com, sean@poorly.run
Subject: Re: [PATCH v2] drm/msm/adreno: Add missing MODULE_FIRMWARE macros
Date: Thu, 22 Jun 2023 21:44:25 +0300 [thread overview]
Message-ID: <b0460532-b5f1-7efc-49af-8d4feecc1085@linaro.org> (raw)
In-Reply-To: <20230620054031.1203960-1-juerg.haefliger@canonical.com>
On 20/06/2023 08:40, Juerg Haefliger wrote:
> The driver references some firmware files that don't have corresponding
> MODULE_FIRMWARE macros and thus won't be listed via modinfo. Fix that.
>
> Signed-off-by: Juerg Haefliger <juerg.haefliger@canonical.com>
>
> ---
> v2:
> - Drop addition and removal of zap files (needs more discussion)
> - Add new a690_gmu.bin
> - Update commit subject and message accordingly
> ---
> drivers/gpu/drm/msm/adreno/adreno_device.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
--
With best wishes
Dmitry
next prev parent reply other threads:[~2023-06-22 18:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-16 12:28 [PATCH] drm/msm/adreno: Update " Juerg Haefliger
2023-06-16 15:23 ` Brian Masney
2023-06-16 15:55 ` Akhil P Oommen
2023-06-17 0:43 ` Dmitry Baryshkov
2023-06-20 5:08 ` Juerg Haefliger
2023-06-20 5:40 ` [PATCH v2] drm/msm/adreno: Add missing " Juerg Haefliger
2023-06-22 18:44 ` Dmitry Baryshkov [this message]
2023-08-15 11:52 ` Juerg Haefliger
2023-08-15 14:48 ` Joel Fernandes
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=b0460532-b5f1-7efc-49af-8d4feecc1085@linaro.org \
--to=dmitry.baryshkov@linaro.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=joel@joelfernandes.org \
--cc=johan+linaro@kernel.org \
--cc=juerg.haefliger@canonical.com \
--cc=konrad.dybcio@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_abhinavk@quicinc.com \
--cc=quic_akhilpo@quicinc.com \
--cc=ribalda@chromium.org \
--cc=robdclark@gmail.com \
--cc=sean@poorly.run \
/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®