mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexander Gruhlke <gruhlke@mailbox.org>
To: lukas@wunner.de
Cc: bhelgaas@google.com, rafael@kernel.org, alex@shazbot.org,
	hui.wang@canonical.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: [PATCH 2/2] PCI: Wait for readiness after FLR even with Immediate Readiness
Date: Sun, 11 Oct 2026 10:25:15 +0200	[thread overview]
Message-ID: <20261011082515.18546-1-gruhlke@mailbox.org> (raw)
In-Reply-To: <asp7HDfhDSjNtx5p@wunner.de>

On Sat, Oct 10, 2026 at 07:51:24PM +0200, Lukas Wunner wrote:
> The device is incorrectly advertising Immediate Readiness, so I suggest
> clearing dev->imm_ready from a DECLARE_PCI_FIXUP_FINAL() quirk and
> emitting a message with KERN_INFO severity with something like
> "Ignoring incorrectly advertised Immediate Readiness support".

Makes sense, I'll do that in v2.

Thanks,
Alexander

  reply	other threads:[~2026-10-11  8:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-10 16:05 [PATCH 0/2] PCI: Wait after FLR for devices that don't honor " Alexander Gruhlke
2026-10-10 16:05 ` [PATCH 1/2] PCI: Don't treat ~0 as ready in pci_dev_wait() with RRS SV Alexander Gruhlke
2026-10-10 18:36   ` Lukas Wunner
2026-10-11  8:24     ` Alexander Gruhlke
2026-10-11 15:14       ` Lukas Wunner
2026-10-10 16:05 ` [PATCH 2/2] PCI: Wait for readiness after FLR even with Immediate Readiness Alexander Gruhlke
2026-10-10 17:51   ` Lukas Wunner
2026-10-11  8:25     ` Alexander Gruhlke [this message]
2026-10-11 16:38 ` [PATCH 0/2] PCI: Wait after FLR for devices that don't honor " Alexander Gruhlke

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=20261011082515.18546-1-gruhlke@mailbox.org \
    --to=gruhlke@mailbox.org \
    --cc=alex@shazbot.org \
    --cc=bhelgaas@google.com \
    --cc=hui.wang@canonical.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=rafael@kernel.org \
    --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®