public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Slaby <jirislaby@kernel.org>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] firewire updates for 6.5-rc1
Date: Mon, 2 Oct 2023 12:42:09 +0200	[thread overview]
Message-ID: <9e335ce7-a4ac-45a0-afdf-9afca8a300d5@kernel.org> (raw)
In-Reply-To: <0ed4012a-83a7-4849-92c4-87a86e1bbb84@app.fastmail.com>

On 01. 10. 23, 7:15, Takashi Sakamoto wrote:
> Just now I installed openSUSE Tumbleweed, however I found no issue on my 1394 OHCI
> hardware. I would like to ask your current opinion for the issue?

Hi,

let's wait for the result of bisection. ATM, the cause appears to be one of:
147e9d3af34a firewire: cdev: code refactoring to operate event of response
39ce342c3a4b firewire: core: implement variations to send request and 
wait for response with time stamp
dcadfd7f7c74 firewire: core: use union for callback of transaction 
completion

I don't see the problem in them immediately. Do you?

My current bet is the last one. But why the heck the machine resets 
immediately?

thanks,
-- 
js
suse labs


  reply	other threads:[~2023-10-02 10:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04 12:18 [GIT PULL] firewire updates for 6.5-rc1 Takashi Sakamoto
2023-07-04 18:38 ` pr-tracker-bot
2023-09-26  9:11 ` Jiri Slaby
2023-09-26 14:09   ` Takashi Sakamoto
2023-09-27  5:03     ` Jiri Slaby
2023-10-01  5:15       ` Takashi Sakamoto
2023-10-02 10:42         ` Jiri Slaby [this message]
2023-10-04  0:24           ` Takashi Sakamoto
2023-10-04  8:33             ` Jiri Slaby
2023-10-16 15:56               ` Takashi Sakamoto
2023-10-17  7:36                 ` Jiri Slaby
2023-09-27 13:15   ` Linux regression tracking #adding (Thorsten Leemhuis)
2024-01-21 10:04     ` Linux regression tracking #update (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=9e335ce7-a4ac-45a0-afdf-9afca8a300d5@kernel.org \
    --to=jirislaby@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=o-takashi@sakamocchi.jp \
    /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