All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
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 14:33:01 +0200	[thread overview]
Message-ID: <aCXe_SMq6vsAIAin@wunner.de> (raw)
In-Reply-To: <98fa31e7-db86-35f0-a71c-a1ebf27f93f0@linux.intel.com>

On Thu, May 15, 2025 at 03:21:39PM +0300, Ilpo Järvinen wrote:
> 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.

Thanks,

Lukas

  reply	other threads:[~2025-05-15 12:33 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
2025-05-15 12:33           ` Lukas Wunner [this message]
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=aCXe_SMq6vsAIAin@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 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.