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

[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]

On Thu, 15 May 2025, Lukas Wunner wrote:

> On Thu, May 15, 2025 at 05:43:46PM +0900, Krzysztof Wilczy??ski wrote:
> > Done.  Squashed with the first commit from Ilpo, see:

Thanks Krzysztof for handling this, I should have put the note about 
squashing it to the resubmission but I forgot (this time I didn't do 
the diff against the previous version before sending it which I normally 
do).

> >   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.)

I'm a pdx86 maintainer so I do have an account, yes. I actually had the 
patchwork page listing my PCI patches already open, but I just hadn't hit 
"update" button yet.

I've done those two changes now.

I'm a bit hesitant to mark "Accepted" state though, I did it this time 
but in general I feel I might be overstepping my authority even if I know 
some patches have been accepted.

> 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.


-- 
 i.

  reply	other threads:[~2025-05-15 12:21 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
2025-05-15 12:21         ` Ilpo Järvinen [this message]
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=98fa31e7-db86-35f0-a71c-a1ebf27f93f0@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=bhelgaas@google.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lukas@wunner.de \
    --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