Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: Niklas Cassel <cassel@kernel.org>
Cc: "Damien Le Moal" <dlemoal@kernel.org>,
	"Arnd Bergmann" <arnd@arndb.de>,
	"Arnd Bergmann" <arnd@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Frank Li" <Frank.Li@nxp.com>,
	"Kishon Vijay Abraham I" <kishon@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: endpoint: pci-epf-test: select configfs
Date: Thu, 19 Feb 2026 10:00:00 -0600	[thread overview]
Message-ID: <20260219160000.GA3477038@bhelgaas> (raw)
In-Reply-To: <aZbRkXM2vIgAwvzz@ryzen>

On Thu, Feb 19, 2026 at 10:02:16AM +0100, Niklas Cassel wrote:
> Bjorn, btw, is it perhaps possible for you to remove the tag:
> pci/for-linus
> 
> tag pci/for-linus
> ...

> Since most people why do a git log pci/for-linus wants to see what
> you have queued for linus, and since the ancient tag seems bogus
> anyway, perhaps you could just remove the tag from the PCI tree?

Thanks for reminding me about this.  I've tried in the past but was
unsuccessful.  I tried again and I *think* got it removed.  I'm
including the details in case I ever need to do this again :)

Current pci/for-linus branch in case I delete it by mistake:

  $ git show --oneline for-linus | cat
  a7b3343bbb57 PCI: endpoint: pci-epf-test: Select configfs

Local pci/for-linus tag:

  $ git tag -l pci/for-linus | cat
  pci/for-linus
  $ cat .git/refs/tags/pci/for-linus
  b4aef5ce82f1d27e0f14d1f8488dc2db9c22dd38

Delete local tag:

  $ git tag -d pci/for-linus
  Deleted tag 'pci/for-linus' (was b4aef5ce82f1)
  $ cat .git/refs/tags/pci/for-linus
  cat: .git/refs/tags/pci/for-linus: No such file or directory (os error 2)

Delete remote tag:

  $ git push --delete pci pci/for-linus
  remote: Recorded in the transparency log
  remote:  manifest: updated /pub/scm/linux/kernel/git/pci/pci.git
  To ra.kernel.org:/pub/scm/linux/kernel/git/pci/pci.git
   - [deleted]                   pci/for-linus

Verify:

  $ git fetch --prune --prune-tags
  $ git tag -l pci/for-linus | cat
  <none>
  $ git fetch pci
  $ git tag -l pci/for-linus | cat
  <none>

  parent reply	other threads:[~2026-02-19 16:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-11  7:07 [PATCH] PCI: endpoint: pci-epf-test: select configfs Arnd Bergmann
2026-02-11  8:43 ` Damien Le Moal
2026-02-11  9:05 ` Niklas Cassel
2026-02-11  9:37   ` Arnd Bergmann
2026-02-12 23:39     ` Damien Le Moal
2026-02-13  9:35       ` Niklas Cassel
2026-02-18 18:00         ` Bjorn Helgaas
2026-02-19  9:02           ` Niklas Cassel
2026-02-19 13:04             ` Niklas Cassel
2026-02-19 16:13               ` Bjorn Helgaas
2026-02-19 19:14                 ` Niklas Cassel
2026-02-19 16:00             ` Bjorn Helgaas [this message]
2026-02-18 18:00 ` Bjorn Helgaas

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=20260219160000.GA3477038@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=arnd@arndb.de \
    --cc=arnd@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=cassel@kernel.org \
    --cc=dlemoal@kernel.org \
    --cc=kishon@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mani@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