Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Bjorn Helgaas <helgaas@kernel.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: baruch@tkos.co.il, bhelgaas@google.com,
	linux-pci@vger.kernel.org, Alex Williamson <alex@shazbot.org>
Subject: Re: [PATCH] PCI: Change PCIe capability registers offset to hex
Date: Fri, 27 Feb 2026 06:42:10 -0600	[thread overview]
Message-ID: <20260227124210.GA3891195@bhelgaas> (raw)
In-Reply-To: <3ae392a0158e9d9ab09a1d42150429dd8ca42791.camel@infradead.org>

On Fri, Feb 27, 2026 at 09:12:39AM +0000, David Woodhouse wrote:
> > On Thu, Nov 18, 2021 at 04:13:00PM +0200, Baruch Siach wrote:
> > > Hex notation matches the spec documents, and is less error prone.
> > > 
> > > Suggested-by: Bjorn Helgaas <helgaas@kernel.org>
> > > Link: https://lore.kernel.org/r/20210825160516.GA3576414@bjorn-Precision-5520/
> > > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > 
> > Applied to pci/misc for v5.17, thanks!
> > 
> > I also converted some other capabilities that had offsets > 8.
> ...

> What you committed in fb82437fdd8cd also changes
> PCI_CAP_EXP_ENDPOINT_SIZEOF_V2:
> 
> -#define PCI_CAP_EXP_ENDPOINT_SIZEOF_V2	52	/* v2 endpoints with link end here */
> +#define PCI_CAP_EXP_ENDPOINT_SIZEOF_V2	0x32	/* end of v2 EPs w/ link */
> 
> That's not actually the same number. Was that intentional? If so it
> should have been done in a separate commit...

Ouch.  Unintentional and completely my mistake.  Did you trip over
something, or find it by inspection?  If there's any kind of defect
signature, I'd like to include it in the commit log.

I posted a fix:
https://lore.kernel.org/linux-pci/20260227123653.3891008-1-bhelgaas@google.com/T/#u

and put it on pci/for-linus.  I intend to ask Linus to pull it later
today.

Thank you very much for finding this.

Bjorn

  reply	other threads:[~2026-02-27 12:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-18 14:13 [PATCH] PCI: Change PCIe capability registers offset to hex Baruch Siach
2021-12-15 21:36 ` Bjorn Helgaas
2026-02-27  9:12   ` David Woodhouse
2026-02-27 12:42     ` Bjorn Helgaas [this message]
2026-02-27 13:38       ` David Woodhouse

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=20260227124210.GA3891195@bhelgaas \
    --to=helgaas@kernel.org \
    --cc=alex@shazbot.org \
    --cc=baruch@tkos.co.il \
    --cc=bhelgaas@google.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-pci@vger.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