From: "Michel Dänzer" <michel-otUistvHUpPR7s880joybQ@public.gmane.org>
To: "Deucher, Alexander" <Alexander.Deucher-5C7GfCeVMHo@public.gmane.org>
Cc: "amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org"
<amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org>
Subject: Re: Bug#921004: downgrade to firmware-amd-graphics_20180825-1_all.deb
Date: Thu, 31 Jan 2019 18:08:49 +0100 [thread overview]
Message-ID: <342b46fe-d8ad-a3b4-7931-86e531a30bde@daenzer.net> (raw)
In-Reply-To: <BN6PR12MB18093C89D32B548DFD16268AF7910-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
On 2019-01-31 6:01 p.m., Deucher, Alexander wrote:
> Is there a big report?
Yeah, 921004@bugs.debian.org => https://bugs.debian.org/921004 . Doesn't
have any more information currently though, we'd have to get in touch
with the reporter.
> I haven't heard of any other issues and these updates have been upstream
> in linux-firmware for over a month now.
It entered Debian sid about two weeks ago, so might have only entered
Debian testing this week.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Mesa and X developer
_______________________________________________
amd-gfx mailing list
amd-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2019-01-31 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1c2b5af4-ea57-0b07-723d-cb4ccb760219@free.fr>
[not found] ` <2e69cb23-06ee-5bcd-4feb-0eb88c0f4143@free.fr>
[not found] ` <2e69cb23-06ee-5bcd-4feb-0eb88c0f4143-GANU6spQydw@public.gmane.org>
2019-01-31 16:02 ` Fwd: Bug#921004: downgrade to firmware-amd-graphics_20180825-1_all.deb Michel Dänzer
[not found] ` <4808c53d-927e-71a7-62fb-af46f9e87efc-otUistvHUpPR7s880joybQ@public.gmane.org>
2019-01-31 17:01 ` Deucher, Alexander
[not found] ` <BN6PR12MB18093C89D32B548DFD16268AF7910-/b2+HYfkarSEx6ez0IUAagdYzm3356FpvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-01-31 17:08 ` Michel Dänzer [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=342b46fe-d8ad-a3b4-7931-86e531a30bde@daenzer.net \
--to=michel-otuistvhuppr7s880joybq@public.gmane.org \
--cc=Alexander.Deucher-5C7GfCeVMHo@public.gmane.org \
--cc=amd-gfx-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.