From: Lukas Wunner <lukas@wunner.de>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Wilczy??ski <kw@linux.com>,
Nirmal Patel <nirmal.patel@linux.intel.com>,
Siddharth Vadapalli <s-vadapalli@ti.com>,
Rohit Agarwal <quic_rohiagar@quicinc.com>,
Shunsuke Mie <mie@igel.co.jp>,
Damien Le Moal <dlemoal@kernel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Subject: Re: [GIT PULL] PCI changes for v6.4
Date: Thu, 27 Apr 2023 05:28:16 +0200 [thread overview]
Message-ID: <20230427032816.GA18461@wunner.de> (raw)
In-Reply-To: <20230425200936.GA66754@bhelgaas>
Hi Bjorn,
On Tue, Apr 25, 2023 at 03:09:36PM -0500, Bjorn Helgaas wrote:
> The following changes since commit fe15c26ee26efa11741a7b632e9f23b01aca4cc6:
>
> Linux 6.3-rc1 (2023-03-05 14:52:03 -0800)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git tags/pci-v6.4-changes
>
> for you to fetch changes up to 09a8e5f01dfb30667a8f05e35c1cc073cb4fd134:
>
> Merge branch 'pci/controller/kconfig' (2023-04-20 16:19:37 -0500)
Just a heads-up that this pull request doesn't include the following
topic branches in pci.git:
controller/endpoint
controller/cadence
controller/vmd
... as well as the following commit on the controller/dt branch:
661a7e9aa551 ("dt-bindings: PCI: qcom: Add SDX65 SoC")
Perhaps you intend to submit them in a second pull request this
merge window, but I just wanted to make sure they're not forgotten.
The patches applied to those topic branches are marked "Accepted"
in patchwork, so if the topic branches are deleted when the 6.5
cycle begins, the patches would seem to have been merged even though
they're not.
Thanks,
Lukas
next prev parent reply other threads:[~2023-04-27 3:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-25 20:09 [GIT PULL] PCI changes for v6.4 Bjorn Helgaas
2023-04-27 3:28 ` Lukas Wunner [this message]
2023-04-27 3:53 ` Bjorn Helgaas
2023-05-08 7:29 ` Lorenzo Pieralisi
2023-04-27 19:20 ` pr-tracker-bot
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=20230427032816.GA18461@wunner.de \
--to=lukas@wunner.de \
--cc=dlemoal@kernel.org \
--cc=helgaas@kernel.org \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mie@igel.co.jp \
--cc=nirmal.patel@linux.intel.com \
--cc=quic_rohiagar@quicinc.com \
--cc=robh@kernel.org \
--cc=s-vadapalli@ti.com \
--cc=torvalds@linux-foundation.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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