linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 218486] Linux warning `usb: port power management may be unreliable` on Dell OptiPlex 3620
Date: Wed, 21 Feb 2024 18:21:20 +0000	[thread overview]
Message-ID: <bug-218486-208809-j7dXPO2nUD@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-218486-208809@https.bugzilla.kernel.org/>

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

--- Comment #3 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
Created attachment 305902
  --> https://bugzilla.kernel.org/attachment.cgi?id=305902&action=edit
Linux 6.8-rc5+ messages with v2 patches (output of `dmesg`) with system
firmware 1.28.0

With Mathias’ patches (I just tested v2)

1. 
https://lore.kernel.org/all/20240220135946.4028553-1-mathias.nyman@linux.intel.com/
2. 
https://lore.kernel.org/all/20240220135946.4028553-2-mathias.nyman@linux.intel.com/

the warning is gone.

    $ git log --oneline --no-decorate -3
    b075462c1a037 usb: port: Don't try to peer unused USB ports based on
location
    c9b8f9ed3da92 usb: usb-acpi: Set port connect type of not connectable ports
correctly
    9fc1ccccfd8d5 Merge tag 'for-linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/rdma/rdma

-- 
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-02-21 18:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 12:58 [Bug 218486] New: Linux warning `usb: port power management may be unreliable` on Dell OptiPlex 3620 bugzilla-daemon
2024-02-13 12:59 ` [Bug 218486] " bugzilla-daemon
2024-02-13 17:46 ` bugzilla-daemon
2024-02-21 18:21 ` bugzilla-daemon [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=bug-218486-208809-j7dXPO2nUD@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 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).