mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mario Limonciello <mario.limonciello@amd.com>
To: Linux kernel regressions list <regressions@lists.linux.dev>,
	o-takashi@sakamocchi.jp
Cc: a.mark.broadworth@gmail.com, matthias.schrumpf@freenet.de,
	LKML <linux-kernel@vger.kernel.org>,
	aros@gmx.com, bagasdotme@gmail.com
Subject: Regression from dcadfd7f7c74ef9ee415e072a19bdf6c085159eb
Date: Mon, 6 Nov 2023 14:14:39 -0600	[thread overview]
Message-ID: <f878b188-3fe4-420c-9bcb-b431ac6088dd@amd.com> (raw)

Hi,

I recently came across a kernel bugzilla that bisected a boot problem 
[1] introduced in kernel 6.5 to this change.

commit dcadfd7f7c74ef9ee415e072a19bdf6c085159eb (HEAD -> dcadfd7f7c7)
Author: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Date:   Tue May 30 08:12:40 2023 +0900

     firewire: core: use union for callback of transaction completion

Removing the firewire card from the system fixes it for both reporters 
(CC'ed)

As the author of this issue can you please take a look at it?

Thanks,

[1] https://bugzilla.kernel.org/show_bug.cgi?id=217993

             reply	other threads:[~2023-11-06 20:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-06 20:14 Mario Limonciello [this message]
2023-11-07  7:02 ` Bagas Sanjaya
2024-01-19 14:08   ` Linux regression tracking #update (Thorsten Leemhuis)
2023-11-07 12:17 ` Takashi Sakamoto
2023-11-07 21:27   ` Mario Limonciello
2023-11-08  5:16     ` Takashi Sakamoto
2023-11-20  5:41       ` Linux regression tracking (Thorsten Leemhuis)
2023-11-28  5:24       ` Takashi Sakamoto
2023-11-28  6:09         ` Mario Limonciello
2023-12-03 12:29           ` Takashi Sakamoto
2023-12-05 20:04             ` Mario Limonciello
2023-12-10  8:02               ` Takashi Sakamoto
2024-01-16  1:49 ` Takashi Sakamoto

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=f878b188-3fe4-420c-9bcb-b431ac6088dd@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=a.mark.broadworth@gmail.com \
    --cc=aros@gmx.com \
    --cc=bagasdotme@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.schrumpf@freenet.de \
    --cc=o-takashi@sakamocchi.jp \
    --cc=regressions@lists.linux.dev \
    /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®