From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/pali/linux
Date: Fri, 12 Mar 2021 17:53:52 -0000 [thread overview]
Message-ID: <161557163237.29792.16224731049677990469@gitolite.kernel.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 272 bytes --]
---
service: git-receive-pack
repo: pub/scm/linux/kernel/git/pali/linux
user: pali
changes:
- ref: refs/heads/pci-aardvark
old: f46c491a718f163f0a2709b7f87844c58e895c51
new: 8f72d5f605946218e44230bec36e8697c4ee86bf
log: revlist-f46c491a718f-8f72d5f60594.txt
[-- Attachment #2: revlist-f46c491a718f-8f72d5f60594.txt --]
[-- Type: text/plain, Size: 2853 bytes --]
40bfbb9e53be72158c5847449e1f2f5ca7403142 PCI: aardvark: Fix checking for PIO Non-posted Request
bec5e4c85434cf23ef7d51262e1939af4b36c2fe PCI: aardvark: Fix checking for PIO status
7be7cb63d7d1895daf1616c506c794d1c4aaa8aa PCI: aardvark: Increase polling delay to 1.5s while waiting for PIO response
a52c60c0e14ea4755b81545f9a26fec52ce6efa4 PCI: aardvark: Fix support for MSI interrupts
c491cebd3fbc8d341b686e39f9c107e6a03b9ae7 PCI: aardvark: Fix support for PME on emulated bridge
2307d709d80f7dd860455c2f4e01f83497b284aa PCI: aardvark: Fix support for PME requester on emulated bridge
36e592104cd12bb0cfc92e824e19d11e2a1337a1 PCI: aardvark: Fix support for bus mastering and PCI_COMMAND on emulated bridge
1653770ee3ffa3d9e1aabbab88a38d49951ab3c2 PCI: aardvark: Disable bus mastering and mask all interrupts when unbinding driver
4cd4f7ea1d818d18ee2478699b93cbcfa672e5a8 PCI: aardvark: Free config space for emulated root bridge when unbinding driver to fix memory leak
d41ad3e01beccda0edebe33ad3b6385b7fcab9cd PCI: aardvark: Reset PCIe card when unbinding driver
84eea872031bb5cea64e3925f2f490a6c0834941 PCI: aardvark: Disable PHY when unbinding driver
929d089d8beb95edbec4c453dfd29f210b2dd48b PCI: pci-bridge-emul: Add description for class_revision field
757412a099e86ce87bc4b1edc08bc8e9bbf712a1 PCI: pci-bridge-emul: Add definitions for missing capabilities registers
863ecb6921faf74738fb7620fbd26bdbef4bc1dd PCI: aardvark: Add support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2 registers on emulated bridge
235dec1be8e6acb12ff12778bcffdec93b2bec5b PCI: aardvark: Fix LNKCAP2 and LNKCTL2 registers on emulated bridge
7208ed7479b1fb1acdcc301931afe482bf8bd870 PCI: aardvark: Add support for PCI_BRIDGE_CTL_BUS_RESET on emulated bridge
5d9a8b5cd6cf1cd5a457429d46199d4867d962fc PCI: aardvark: Replace custom PCIE_CORE_ERR_CAPCTL_* macros by linux/pci_regs.h macros
b2e9935d11309021fe84a5e8c2137339f98cd415 PCI: aardvark: Replace custom PCIE_CORE_INT_* macros by linux PCI_INTERRUPT_* values
4aed8a29c156f4848a0affc3f475929b83971419 PCI: aardvark: Cleanup some register macros
30805e11ec69e43c30015933f8df9237af298b59 PCI: aardvark: Add comments for OB_WIN_ENABLE and ADDR_WIN_DISABLE
11c6c23b3a3d7050d3b69c0d0d63a99ce59318c4 PCI: pci-bridge-emul: re-arrange register tests
cdc2ffd737a4f954a2927667d90c1754e06e77c3 PCI: pci-bridge-emul: add support for PCIe extended capabilities
7c5699a814cce7a121e8a9b90e086f24e2ac3dea PCI: aardvark: Add support for Advanced Error Reporting registers on emulated bridge
38cbc571aab784ddde66aa2f28676406b2fe9944 PCI: aardvark: Add support for error reporting interrupt on emulated bridge
21b76559bd7c8c24ce392363aa0757aafca95ddb PCI: aardvark: Remove PCIE_CORE_CTRL0_REG macros not applicable for Root Complex
8f72d5f605946218e44230bec36e8697c4ee86bf PCI: aardvark: Show warning when Hot Reset or Link Down event occurs
next reply other threads:[~2021-03-12 17:53 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-12 17:53 Gitolite [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-05-06 10:19 post-receive: pub/scm/linux/kernel/git/pali/linux Gitolite
2021-05-06 9:43 Gitolite
2021-05-06 9:01 Gitolite
2021-05-06 8:59 Gitolite
2021-04-30 23:21 Gitolite
2021-04-27 15:38 Gitolite
2021-04-27 13:59 Gitolite
2021-04-25 11:05 Gitolite
2021-04-21 23:44 Gitolite
2021-04-20 15:13 Gitolite
2021-04-20 14:55 Gitolite
2021-04-20 12:34 Gitolite
2021-04-20 10:01 Gitolite
2021-04-19 8:23 Gitolite
2021-04-17 13:40 Gitolite
2021-04-16 19:12 Gitolite
2021-04-16 19:09 Gitolite
2021-04-16 19:08 Gitolite
2021-04-07 12:01 Gitolite
2021-04-06 13:24 Gitolite
2021-04-01 21:22 Gitolite
2021-03-26 13:42 Gitolite
2021-03-18 16:26 Gitolite
2021-03-16 9:53 Gitolite
2021-03-12 11:56 Gitolite
2021-03-11 16:58 Gitolite
2021-03-10 17:48 Gitolite
2021-03-08 8:36 Gitolite
2021-03-03 17:13 Gitolite
2021-03-03 16:14 Gitolite
2021-02-26 16:02 Gitolite
2021-02-23 11:28 Gitolite
2021-02-22 16:50 Gitolite
2021-02-22 13:55 Gitolite
2021-02-22 13:55 Gitolite
2021-02-22 13:54 Gitolite
2021-02-22 13:53 Gitolite
2021-02-19 18:21 Gitolite
2021-02-17 23:51 Gitolite
2021-02-17 20:37 Gitolite
2021-02-15 19:52 Gitolite
2021-02-15 19:50 Gitolite
2021-01-26 11:20 Gitolite
2021-01-14 10:02 Gitolite
2021-01-11 11:40 Gitolite
2021-01-06 18:01 Gitolite
2021-01-04 12:45 Gitolite
2020-12-30 15:44 Gitolite
2020-12-30 15:40 Gitolite
2020-12-30 15:40 Gitolite
2020-12-30 15:40 Gitolite
2020-12-30 15:39 Gitolite
2020-12-30 15:39 Gitolite
2020-12-30 15:39 Gitolite
2020-12-30 15:38 Gitolite
2020-12-30 15:37 Gitolite
2020-11-03 13:15 Gitolite
2020-11-03 13:11 Gitolite
2020-10-20 17:03 Gitolite
2020-06-25 23:27 Gitolite
2020-06-02 12:03 Gitolite
2020-06-02 12:03 Gitolite
2020-06-01 10:27 Gitolite
2020-05-28 13:54 Gitolite
2020-05-28 12:57 Gitolite
2020-05-27 11:09 Gitolite
2020-05-26 15:41 Gitolite
2020-05-26 15:29 Gitolite
2020-05-26 8:08 Gitolite
2020-05-22 12:08 Gitolite
2020-05-22 8:06 Gitolite
2020-05-22 8:03 Gitolite
2020-05-22 8:02 Gitolite
2020-05-21 9:01 Gitolite
2020-05-15 7:52 Gitolite
2020-05-14 11:03 Gitolite
2020-05-14 11:01 Gitolite
2020-04-29 15:21 Gitolite
2020-04-24 14:56 Gitolite
2020-04-24 14:44 Gitolite
2020-04-24 11:29 Gitolite
2020-04-23 17:38 Gitolite
2020-04-22 16:13 Gitolite
2020-04-22 15:09 Gitolite
2020-04-15 15:38 Gitolite
2020-04-14 12:50 Gitolite
2020-04-14 9:29 Gitolite
2020-04-09 11:48 Gitolite
2020-04-09 11:44 Gitolite
2020-03-17 22:11 Gitolite
2020-03-17 21:51 Gitolite
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=161557163237.29792.16224731049677990469@gitolite.kernel.org \
--to=devnull@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 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.