linux-kernel - Re: [PATCH 1/1] PCI/bwctrl: Remove also pcie_bwctrl_lbms

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250515140034.GC3596832@rocinante>
Date: Thu, 15 May 2025 23:00:34 +0900
From: Krzysztof Wilczy??ski <kwilczynski@...nel.org>
To: Lukas Wunner <lukas@...ner.de>
Cc: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	"Paul E. McKenney" <paulmck@...nel.org>, linux-pci@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/1] PCI/bwctrl: Remove also pcie_bwctrl_lbms_rwsem

Hello,

> > 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.
> 
> Bjorn has encouraged submitters to mark their own patches as "Superseded":
> 
>    "If you're really gung-ho, you can go to Patchwork [2] and mark
>     your superseded patches as "Superseded" so I don't have to do that
>     myself."
> 
>     https://lore.kernel.org/r/20171026223701.GA25649@bhelgaas-glaptop.roam.corp.google.com/
> 
> ... and I was assuming that also applies to marking one's own patches
> as "Accepted", but I might be jumping to the wrong conclusion.

Between Bjorn, Lorenzo, Mani and I, we are getting better as leveraging
Patchwork for a little bit of tracking and "project management", so to
speak.

But, any help with the housekeeping always appreciated. :)

Thank you!

	Krzysztof