From: Mario Limonciello <mario.limonciello@amd.com>
To: Hamza Mahfooz <hamza.mahfooz@amd.com>,
Josh Boyer <jwboyer@kernel.org>,
Wayne.Lin@amd.com,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-firmware@kernel.org, alexander.deucher@amd.com,
chandan.vurdigerenataraj@amd.com, deepak.sharma@amd.com
Subject: Re: Update of amdgpu DMCUB firmware (2023-08-25)
Date: Mon, 28 Aug 2023 09:38:03 -0500 [thread overview]
Message-ID: <dd01d36b-2ff1-4889-a409-e6fcec60af68@amd.com> (raw)
In-Reply-To: <12e4c4eb-df91-4a7a-9072-ccfac8679c85@amd.com>
On 8/28/2023 06:47, Hamza Mahfooz wrote:
> On 8/28/23 07:12, Josh Boyer wrote:
>> On Fri, Aug 25, 2023 at 4:20 PM Hamza Mahfooz <hamza.mahfooz@amd.com>
>> wrote:
>>>
>>> The following changes since commit
>>> a33f8f1abd1df344798188807de4b4397d7484d3:
>>>
>>> amdgpu: update DMCUB to 0.0.181.0 for various AMDGPU ASICs
>>> (2023-08-25 15:25:00 -0400)
>>>
>>> are available in the Git repository at:
>>>
>>> git@gitlab.freedesktop.org:drm/firmware.git tags/amd-2023-08-25
>>
>> Does this replace Wayne Lin's pull request for tags/amd-2023-08-18?
>
> No, that is updating a different ASIC's fw. So, it's still needed.
But in this case the tags are sequential and from the same branch. So I
think pulling the newer one will be sufficient.
>
>>
>> I can't get to gitlab.freedesktop.org at all right now, so I can't
>> pull either.
+bentiss
Presumably you're aware FDO gitlab is down already, right?
>>
>> josh
>>
>>>
>>> for you to fetch changes up to a33f8f1abd1df344798188807de4b4397d7484d3:
>>>
>>> amdgpu: update DMCUB to 0.0.181.0 for various AMDGPU ASICs
>>> (2023-08-25 15:25:00 -0400)
>>>
>>> ----------------------------------------------------------------
next prev parent reply other threads:[~2023-08-28 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 20:20 Update of amdgpu DMCUB firmware (2023-08-25) Hamza Mahfooz
2023-08-28 11:12 ` Josh Boyer
2023-08-28 11:47 ` Hamza Mahfooz
2023-08-28 14:38 ` Mario Limonciello [this message]
2023-08-28 14:40 ` Benjamin Tissoires
2023-08-28 19:19 ` Mario Limonciello
2023-08-29 11:28 ` Josh Boyer
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=dd01d36b-2ff1-4889-a409-e6fcec60af68@amd.com \
--to=mario.limonciello@amd.com \
--cc=Wayne.Lin@amd.com \
--cc=alexander.deucher@amd.com \
--cc=benjamin.tissoires@redhat.com \
--cc=chandan.vurdigerenataraj@amd.com \
--cc=deepak.sharma@amd.com \
--cc=hamza.mahfooz@amd.com \
--cc=jwboyer@kernel.org \
--cc=linux-firmware@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.