From: Bjorn Helgaas <helgaas@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux PCI <linux-pci@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
Subject: Re: [GIT PULL] PCI changes for v5.12
Date: Wed, 24 Feb 2021 15:40:36 -0600 [thread overview]
Message-ID: <20210224214036.GA1586541@bjorn-Precision-5520> (raw)
In-Reply-To: <CAHk-=wiUjFdHYxQzTPJX+J38iSz-hS8Sn9sNx=+B=uMX+Q3wwQ@mail.gmail.com>
On Wed, Feb 24, 2021 at 11:21:44AM -0800, Linus Torvalds wrote:
> On Wed, Feb 24, 2021 at 11:03 AM Bjorn Helgaas <helgaas@kernel.org> wrote:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git tags/pci-v5.12-changes
>
> I pulled this, but I'm now unpulling it again.
>
> Why are many of those commits only two hours old, and most of the rest
> is from yesterday?
>
> Has any of this been in linux-next?
Sorry about the mess. This has been in linux-next. Most of the
recent commit dates are from typos I fixed in commit logs and
documentation patches. A few are because I also sorted a few patches
onto different topic branches.
Here's a little history of the pci/next branch from linux-next and
from my pull request:
next-20210222: pci/next 84c8d3d0b60e
next-20210223: pci/next 4cb431e82c25
$ git diff 84c8d3d0b60e 4cb431e82c25
- fix documentation and comment typos, whitespace issues
- add fc235fcb0f7c ("PCI: acpiphp: Remove unused acpiphp_callback typedef")
- add f8ee579d53ac ("PCI: pci-bridge-emul: Fix array overruns, improve safety")
- add f6bda644fa3a ("PCI: Fix pci_register_io_range() memory leak")
- add d2bb2f9e1af6 ("PCI/ASPM: Move LTR, ASPM L1SS save/restore into PCIe save/restore")
- add e34a4f0b7001 ("PCI/ASPM: Move LTR save/restore state functions earlier")
next-20210224: pci/next 6039bd61b69f
$ git diff 4cb431e82c25 6039bd61b69f
- drop d2bb2f9e1af6 ("PCI/ASPM: Move LTR, ASPM L1SS save/restore into PCIe save/restore")
- drop e34a4f0b7001 ("PCI/ASPM: Move LTR save/restore state functions earlier")
- dropped these cosmetic changes
pci-v5.12-changes: 2bd36c391515
$ git diff 6039bd61b69f 2bd36c391515
<empty>
- no content changes; changed commit logs and moved patches
between topic branches
pci-v5.12-changes: e18fb64b7986 (updated)
$ git diff 2bd36c391515 e18fb64b7986
<empty>
- no content changes; added Signed-off-by for patches moved to
topic branch
I'll send you a new pull request because I forgot to add my sign-off
on a couple patches I had moved to a topic branch.
Sorry again.
Bjorn
prev parent reply other threads:[~2021-02-24 21:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-24 19:03 [GIT PULL] PCI changes for v5.12 Bjorn Helgaas
2021-02-24 19:21 ` Linus Torvalds
2021-02-24 21:40 ` Bjorn Helgaas [this message]
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=20210224214036.GA1586541@bjorn-Precision-5520 \
--to=helgaas@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox