From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/pali/linux
Date: Thu, 11 Mar 2021 16:58:27 -0000 [thread overview]
Message-ID: <161548190795.6897.11071692643281730282@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: 15bbdf44b13a0a539b09948627b8541cb532fec2
new: 91c3883a26ab350d0b170217e86f4ac082570eef
log: revlist-15bbdf44b13a-91c3883a26ab.txt
[-- Attachment #2: revlist-15bbdf44b13a-91c3883a26ab.txt --]
[-- Type: text/plain, Size: 2688 bytes --]
191b930660865e6c59cacd14bd64d92da0d83bd9 PCI: aardvark: Fix support for MSI interrupts
989bb0d636e0e3a377ac9f227fda683155267f66 PCI: aardvark: Fix support for PME on emulated bridge
b0891870b6ad5e6e0a248f83718d7f9e0aa14051 PCI: aardvark: Fix support for PME requester on emulated bridge
e0477fa2ab203f53fac82f4a956b7d43c78e8e94 PCI: aardvark: Fix support for bus mastering and PCI_COMMAND on emulated bridge
d09749a89a07f4b97e8c58ab4957d7e6c3b6136f PCI: aardvark: Disable bus mastering and mask all interrupts when unbinding driver
f46e8acac8bac9f99efe14ad51ba6b685f311a4a PCI: aardvark: Free config space for emulated root bridge when unbinding driver to fix memory leak
31edf6c3b2c5839679ec6bcc98889b1e4217a84d PCI: aardvark: Reset PCIe card when unbinding driver
47a480a1267b7ff14ea199d52c6bda8a401f4333 PCI: aardvark: Disable PHY when unbinding driver
0e5ad00a11433508b5b51145d1fab84003be5194 PCI: pci-bridge-emul: Add description for class_revision field
efc74dd686818bc2f67b31e795dfbf2d80b441d5 PCI: pci-bridge-emul: Add definitions for missing capabilities registers
f96f0cf4a3ca7c4d3fdeca58ce54170e10abeeca PCI: aardvark: Add support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2 registers on emulated bridge
fa7a3155238654f8dd4610130cafa56362f38834 PCI: aardvark: Fix LNKCAP2 and LNKCTL2 registers on emulated bridge
9244644291bd56d4d0d2530563548399ca7a9151 PCI: aardvark: Add support for PCI_BRIDGE_CTL_BUS_RESET on emulated bridge
5eeb768db66a2bb3485d9e67fd53089171eea73b PCI: aardvark: Replace custom PCIE_CORE_ERR_CAPCTL_* macros by linux/pci_regs.h macros
55074cba2f6323755dfcc7e0a65ea3b990e96ad0 PCI: aardvark: Replace custom PCIE_CORE_INT_* macros by linux PCI_INTERRUPT_* values
00750cd9e910633d0827a6f9e667c8fa0f0deb60 PCI: aardvark: Cleanup some register macros
80575c7793dc83834202fbef2b28d1ab25d73de7 PCI: aardvark: Add comments for OB_WIN_ENABLE and ADDR_WIN_DISABLE
77111cdf7fd21b10baaf8684c5c6bd448dcd0be3 PCI: pci-bridge-emul: re-arrange register tests
43fafc69dc2f86ed70eaf0e76fa0519ba7e3df3a PCI: pci-bridge-emul: add support for PCIe extended capabilities
903dde7357ab875d56fcdc61ca070ad7541acd4c PCI: aardvark: Add support for Advanced Error Reporting registers on emulated bridge
ca2e7a8972bb1f47da1d514ea3c9d6b1572d5fc1 PCI: aardvark: Add support for error reporting interrupt on emulated bridge
8be8de65c80d1b384899c2e349b1af82cf5a89e0 PCI: aardvark: Remove PCIE_CORE_CTRL0_REG macros not applicable for Root Complex
0331df8159ce075571a679eacdccb0121182d493 PCI: aardvark: Show warning when Hot Reset or Link Down event occurs
91c3883a26ab350d0b170217e86f4ac082570eef PCI: aardvark: Use Link Down event and PCI_EXP_LNKCTL_RL for checking if card is accessible
next reply other threads:[~2021-03-11 16:58 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 16:58 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 17:53 Gitolite
2021-03-12 11:56 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=161548190795.6897.11071692643281730282@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.