From: Niklas Cassel <cassel@kernel.org>
To: Bjorn Helgaas <helgaas@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,
"Koichiro Den" <den@valinux.co.jp>
Subject: Re: [PATCH] PCI: endpoint: pci-epf-test: select configfs
Date: Thu, 19 Feb 2026 20:14:29 +0100 [thread overview]
Message-ID: <aZdhFdzVqDLthmiP@fedora> (raw)
In-Reply-To: <20260219161348.GA3483770@bhelgaas>
On Thu, Feb 19, 2026 at 10:13:48AM -0600, Bjorn Helgaas wrote:
> On Thu, Feb 19, 2026 at 02:04:20PM +0100, Niklas Cassel wrote:
> > Since there now is a for-linus branch, is there any chance that we could
> > include:
> > https://lore.kernel.org/linux-pci/20260202145407.503348-3-den@valinux.co.jp/
> >
> > In the for-linus branch?
>
> The URL you mentioned is for "[PATCH v2 2/2] PCI: dwc: ep: Always
> clear IB maps on BAR update", but here you mention "the above
> *series*". Do we need both commits of that series?
Yes, sorry that I linked to 2/2 instead of the cover-letter (0/2):
https://lore.kernel.org/linux-pci/20260202145407.503348-1-den@valinux.co.jp/
If possible, I think it would be nice if we could queue both patches in
the series for-linus:
[PATCH v2 0/2] PCI: dwc: ep: Fix BAR update handling with in-place epf_bar reuse
Even if the first patch mainly avoid pointless execution of code, it also
helped us realize that patch 2/2 was needed in the first place.
Kind regards,
Niklas
next prev parent reply other threads:[~2026-02-19 19:14 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 [this message]
2026-02-19 16:00 ` Bjorn Helgaas
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=aZdhFdzVqDLthmiP@fedora \
--to=cassel@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=arnd@arndb.de \
--cc=arnd@kernel.org \
--cc=bhelgaas@google.com \
--cc=den@valinux.co.jp \
--cc=dlemoal@kernel.org \
--cc=helgaas@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