All of lore.kernel.org
 help / color / mirror / Atom feed
From: "The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot" <bugbot@kernel.org>
To: ulf.hansson@linaro.org, linux-mmc@vger.kernel.org
Subject: Re: sdhci_pci module is blocking low power s0ix sleep with GL9767
Date: Wed, 25 Sep 2024 13:40:06 +0000	[thread overview]
Message-ID: <20240925-b219284c2-aa94a203fbda@bugzilla.kernel.org> (raw)
In-Reply-To: <20240918-b219284c0-db72da0a4ac7@bugzilla.kernel.org>

The Linux kernel's regression tracker (Thorsten Leemhuis) writes via Kernel.org Bugzilla:

In case this is a regression (sounds like it's not!) please let me know.

Side note: reminder, there is a decent chance that your report here won't be seen by the developers; for details search for "bugzilla" in documents like https://docs.kernel.org/admin-guide/reporting-issues.html or https://linux-regtracking.leemhuis.info/post/frequent-reasons-why-linux-kernel-bug-reports-are-ignored/

View: https://bugzilla.kernel.org/show_bug.cgi?id=219284#c2
You can reply to this message to join the discussion.
-- 
Deet-doot-dot, I am a bot.
Kernel.org Bugzilla (bugspray 0.1-dev)


  parent reply	other threads:[~2024-09-25 13:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-18  9:50 sdhci_pci module is blocking low power s0ix sleep with GL9767 Georg Gottleuber via Bugspray Bot
2024-09-23 12:15 ` Georg Gottleuber via Bugspray Bot
2024-09-25 13:40 ` The Linux kernel's regression tracker (Thorsten Leemhuis) via Bugspray Bot [this message]
2024-09-30 12:55 ` Georg Gottleuber via Bugspray Bot
2024-12-16 20:05 ` GRbit via Bugspray Bot
2024-12-16 21:25 ` GRbit via Bugspray Bot
2024-12-16 21:25 ` GRbit via Bugspray Bot
  -- strict thread matches above, loose matches on Subject: below --
2024-09-26 15:31 Georg Gottleuber
2024-10-08 15:05 ` Ulf Hansson

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=20240925-b219284c2-aa94a203fbda@bugzilla.kernel.org \
    --to=bugbot@kernel.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=ulf.hansson@linaro.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.