From: Sam James <sam@gentoo.org>
To: aros@gmx.com
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
kernel@gentoo.org, mpagano@gentoo.org, gyakovlev@gentoo.org
Subject: Re: Very bad bad firmware loading reporting situation
Date: Sun, 30 Jul 2023 14:33:35 +0100 [thread overview]
Message-ID: <87a5vd34k4.fsf@gentoo.org> (raw)
In-Reply-To: <16a44663-808c-2eb4-ea6e-66f51a66f7cf@gmx.com>
Yes, we've been applying a patch for this downstream in Gentoo for a little while
now:
* https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=d3ba9963dbecff37c7b0d46913519cc22bc877c0
* https://gitweb.gentoo.org/proj/linux-patches.git/commit/?id=181caad4a8ad9f6a2ead5b4d596e6e83f123bb05
I think we did send it (or a previous variant) upstream at some point
but I can't find the link right now.
prev parent reply other threads:[~2023-07-30 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 13:30 Very bad bad firmware loading reporting situation Artem S. Tashkinov
2023-07-30 13:33 ` Sam James [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=87a5vd34k4.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=aros@gmx.com \
--cc=gyakovlev@gentoo.org \
--cc=kernel@gentoo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpagano@gentoo.org \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox