All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 219198] usb on Dell WD19TB Thunderbolt Dock stop working
Date: Tue, 27 Aug 2024 09:19:59 +0000	[thread overview]
Message-ID: <bug-219198-208809-mrE0Cwrj0A@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219198-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=219198

--- Comment #9 from Markus Rathgeb (maggu2810@gmail.com) ---
Does a git bisect help you to identify the problematic change(s)

I am currently in the progress...

$ git bisect log
git bisect start
# status: waiting for both good and bad commits
# bad: [8400291e289ee6b2bf9779ff1c83a291501f017b] Linux 6.11-rc1
git bisect bad 8400291e289ee6b2bf9779ff1c83a291501f017b
# status: waiting for good commit(s), bad commit known
# good: [7ba498d9d1bb67bcbc2a79f19a9054cdc8b95098] Linux 6.10.6
git bisect good 7ba498d9d1bb67bcbc2a79f19a9054cdc8b95098
# good: [0c3836482481200ead7b416ca80c68a29cfdaabd] Linux 6.10
git bisect good 0c3836482481200ead7b416ca80c68a29cfdaabd
# good: [280e36f0d5b997173d014c07484c03a7f7750668] nsfs: use cleanup guard
git bisect good 280e36f0d5b997173d014c07484c03a7f7750668

But if you already know what related changes has been done, I could cancel it.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-08-27  9:20 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-26  8:49 [Bug 219198] New: usb on Dell WD19TB Thunderbolt Dock stop working bugzilla-daemon
2024-08-26  8:50 ` [Bug 219198] " bugzilla-daemon
2024-08-26  9:12 ` bugzilla-daemon
2024-08-26 11:17 ` bugzilla-daemon
2024-08-26 18:35 ` bugzilla-daemon
2024-08-26 19:06 ` bugzilla-daemon
2024-08-26 19:07 ` bugzilla-daemon
2024-08-26 19:07 ` bugzilla-daemon
2024-08-26 20:32 ` bugzilla-daemon
2024-08-27  9:19 ` bugzilla-daemon [this message]
2024-08-27  9:56 ` bugzilla-daemon
2024-08-27 15:22 ` bugzilla-daemon
2024-08-27 15:41 ` bugzilla-daemon
2024-08-27 18:56 ` bugzilla-daemon
2024-08-27 20:20 ` bugzilla-daemon
2024-08-28  9:39 ` bugzilla-daemon
2024-08-28 10:09 ` bugzilla-daemon
2024-08-28 10:12 ` bugzilla-daemon
2024-08-28 10:46 ` bugzilla-daemon
2024-08-28 17:51 ` bugzilla-daemon
2024-08-28 17:57 ` bugzilla-daemon
2024-08-28 18:05 ` bugzilla-daemon
2024-08-28 19:11 ` bugzilla-daemon
2024-08-28 19:14 ` bugzilla-daemon
2024-08-28 19:18 ` bugzilla-daemon
2024-08-28 19:19 ` bugzilla-daemon
2024-08-29  7:06 ` bugzilla-daemon
2024-08-29  8:36 ` bugzilla-daemon
2024-09-03 23:40 ` bugzilla-daemon
2024-09-04  5:42 ` bugzilla-daemon
2024-09-04  5:44 ` bugzilla-daemon

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=bug-219198-208809-mrE0Cwrj0A@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@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 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.