linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: linux-arm-kernel <linux-arm-kernel@lists.infradead.org>
Cc: linux-efi <linux-efi@vger.kernel.org>
Subject: Re: [Issue] EFI runtime-wrapper is broken #forregzbot
Date: Wed, 9 Nov 2022 16:45:30 +0100	[thread overview]
Message-ID: <00c9d729-b287-eee4-315c-235837faf2e4@leemhuis.info> (raw)
In-Reply-To: <CAMj1kXFtitTuxVSBsxX0j_NHxwnX2oVupip4xy7TKqe-rja_Vw@mail.gmail.com>

[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]

On 08.11.22 14:57, Ard Biesheuvel wrote:
>> I ask because I have this on the list of tracked regression -- and I
>> noticed there is another report about problems caused by d3549a938b73
>> now from Alexandru Elisei:
>> https://lore.kernel.org/lkml/Y2lAB508TrrjpDPi@monolith.localdoman/
> Yes, this is essentially the exact same problem, only on a different
> type of Ampere hardware
> 
> I have an idea how to fix this more comprehensively - I'll work with
> Alexandru to converge on a fix and get it queued up.

In that case:

#regzbot dup-of:
https://lore.kernel.org/lkml/Y2lAB508TrrjpDPi@monolith.localdoman/


_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-11-09 15:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d799b60c-ff4e-44ae-84be-d9ade761ec6d@redhat.com>
2022-10-28  9:21 ` [Issue] EFI runtime-wrapper is broken Ard Biesheuvel
2022-10-28  9:38   ` Gavin Shan
2022-10-28  9:39     ` Ard Biesheuvel
2022-11-08 12:26       ` Thorsten Leemhuis
2022-11-08 13:57         ` Ard Biesheuvel
2022-11-09 15:45           ` Thorsten Leemhuis [this message]
2022-11-13 18:31         ` [Issue] EFI runtime-wrapper is broken #forregzbot Thorsten Leemhuis
2022-10-28  9:45   ` [Issue] EFI runtime-wrapper is broken Ard Biesheuvel
2022-10-30 16:49   ` [Issue] EFI runtime-wrapper is broken #forregzbot Thorsten Leemhuis

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=00c9d729-b287-eee4-315c-235837faf2e4@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-efi@vger.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 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).