From: pr-tracker-bot@kernel.org
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>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Guchun Chen" <guchun.chen@amd.com>,
"Pali Rohár" <pali@kernel.org>, "Jan Palus" <jpalus@fastmail.com>,
"Marcel Menzel" <mail@mcl.gg>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] PCI fixes for v5.17
Date: Thu, 24 Feb 2022 21:40:34 +0000 [thread overview]
Message-ID: <164573883471.15008.15419625252124832547.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20220224195611.GA289605@bhelgaas>
The pull request you sent on Thu, 24 Feb 2022 13:56:11 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.17-fixes-5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d8152cfe2f21d6930c680311b03b169899c8d2a0
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
WARNING: multiple messages have this Message-ID (diff)
From: pr-tracker-bot@kernel.org
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>,
"Alex Deucher" <alexander.deucher@amd.com>,
"Christian König" <christian.koenig@amd.com>,
"Guchun Chen" <guchun.chen@amd.com>,
"Pali Rohár" <pali@kernel.org>, "Jan Palus" <jpalus@fastmail.com>,
"Marcel Menzel" <mail@mcl.gg>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] PCI fixes for v5.17
Date: Thu, 24 Feb 2022 21:40:34 +0000 [thread overview]
Message-ID: <164573883471.15008.15419625252124832547.pr-tracker-bot@kernel.org> (raw)
In-Reply-To: <20220224195611.GA289605@bhelgaas>
The pull request you sent on Thu, 24 Feb 2022 13:56:11 -0600:
> git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.17-fixes-5
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/d8152cfe2f21d6930c680311b03b169899c8d2a0
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/prtracker.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-02-24 21:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-24 19:56 [GIT PULL] PCI fixes for v5.17 Bjorn Helgaas
2022-02-24 19:56 ` Bjorn Helgaas
2022-02-24 21:40 ` pr-tracker-bot [this message]
2022-02-24 21:40 ` pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2022-02-11 20:40 Bjorn Helgaas
2022-02-11 21:36 ` pr-tracker-bot
2022-02-04 21:30 Bjorn Helgaas
2022-02-04 23:29 ` pr-tracker-bot
2022-01-29 16:15 Bjorn Helgaas
2022-01-29 17:07 ` pr-tracker-bot
2022-01-20 20:48 Bjorn Helgaas
2022-01-21 7:38 ` 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=164573883471.15008.15419625252124832547.pr-tracker-bot@kernel.org \
--to=pr-tracker-bot@kernel.org \
--cc=alexander.deucher@amd.com \
--cc=christian.koenig@amd.com \
--cc=guchun.chen@amd.com \
--cc=helgaas@kernel.org \
--cc=jpalus@fastmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=mail@mcl.gg \
--cc=pali@kernel.org \
--cc=torvalds@linux-foundation.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.