Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Krzysztof Wilczy??ski <kwilczynski@kernel.org>
Cc: "Bjorn Helgaas" <bhelgaas@google.com>,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] PCI/bwctrl: Remove also pcie_bwctrl_lbms_rwsem
Date: Thu, 15 May 2025 14:09:25 +0200	[thread overview]
Message-ID: <aCXZdfOA8bme-qra@wunner.de> (raw)
In-Reply-To: <20250515084346.GA51912@rocinante>

On Thu, May 15, 2025 at 05:43:46PM +0900, Krzysztof Wilczy??ski wrote:
> Done.  Squashed with the first commit from Ilpo, see:
> 
>   https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git/commit/?h=bwctrl&id=2389d8dc38fee18176c49e9c4804f5ecc55807fa

Awesome, thank you!

> Let me know if there is anything else needed.

Actually, two small things:

- That patch on the pci/bwctrl topic branch is still marked "New"
  in patchwork, even though it's been applied:
  https://patchwork.kernel.org/project/linux-pci/patch/20250422115548.1483-1-ilpo.jarvinen@linux.intel.com/

- Version 1 of the same patch is likewise marked "New", even though
  it's been superseded:
  https://patchwork.kernel.org/project/linux-pci/patch/20250417124633.11470-1-ilpo.jarvinen@linux.intel.com/

Unfortunately I can't update it myself because I'm not the submitter.
(Ilpo could do it if he has a patchwork.kernel.org account.)


Something unrelated (only if you feel like doing it):

On the pci/enumeration branch, Bjorn queued up a revert which was
waiting to be ack'ed by AMD IOMMU maintainers:
https://lore.kernel.org/r/20250425163259.GA546441@bhelgaas/

In the meantime the ack has arrived:
https://lore.kernel.org/r/aCLv7cN_s1Z4abEl@8bytes.org/

So the remaining housekeeping items are:

- Add Jörg's Acked-by to commit e86c7278eba8 on pci/enumeration
- Remove the "XXX" marker from the subject line
- Remove "Needs AMD IOMMU ack" from the commit message

Again, only if you feel like doing it.  No urgency.

Thanks,

Lukas

  reply	other threads:[~2025-05-15 12:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-08  9:00 [PATCH 1/1] PCI/bwctrl: Remove also pcie_bwctrl_lbms_rwsem Ilpo Järvinen
2025-05-08 15:14 ` Paul E. McKenney
2025-05-14 17:28 ` Krzysztof Wilczyński
2025-05-14 19:42   ` Lukas Wunner
2025-05-15  8:43     ` Krzysztof Wilczyński
2025-05-15 12:09       ` Lukas Wunner [this message]
2025-05-15 12:21         ` Ilpo Järvinen
2025-05-15 12:33           ` Lukas Wunner
2025-05-15 14:00             ` Krzysztof Wilczy??ski
2025-05-15 14:05               ` Krzysztof Wilczy??ski
2025-05-15 13:54           ` Krzysztof Wilczy??ski
2025-05-15 13:51         ` Krzysztof Wilczy??ski

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=aCXZdfOA8bme-qra@wunner.de \
    --to=lukas@wunner.de \
    --cc=bhelgaas@google.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=paulmck@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