From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/pali/linux
Date: Tue, 16 Mar 2021 09:53:13 -0000 [thread overview]
Message-ID: <161588839325.32076.13859420858093273342@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: 8f72d5f605946218e44230bec36e8697c4ee86bf
new: 5ced34c8a567159f1c3c78f6a0dd452bf41067bb
log: revlist-8f72d5f60594-5ced34c8a567.txt
[-- Attachment #2: revlist-8f72d5f60594-5ced34c8a567.txt --]
[-- Type: text/plain, Size: 2678 bytes --]
8e75d09a75c8f3cab7f2403997084ec1659799d0 PCI: aardvark: Do not touch status bits of masked interrupts in interrupt handler
69f328ad3763c4fe5056fc105472c75ba62c6237 PCI: aardvark: Fix support for MSI interrupts
32179eb9f110d8ea5b634946ba217b832b3f4ee6 PCI: aardvark: Fix support for PME on emulated bridge
5d93fdaaac0dc2fea4c60bee3c5a54bd441707f7 PCI: aardvark: Fix support for PME requester on emulated bridge
429d89beea7fdd4fe6c80f72e730279593ac4bbc PCI: aardvark: Fix support for bus mastering and PCI_COMMAND on emulated bridge
d9e48c76767ca5fcef20983a2090477c4621f0cd PCI: aardvark: Disable bus mastering and mask all interrupts when unbinding driver
3c26b78ab8fca6f8161e16ace6610a7d6d4904dc PCI: aardvark: Free config space for emulated root bridge when unbinding driver to fix memory leak
34c1d9ed42f7e08bb7888fa888064c0fa0e04f3a PCI: aardvark: Reset PCIe card when unbinding driver
47b891c005f8412e439baa6f0e21b477edcedbdd PCI: aardvark: Disable PHY when unbinding driver
9818dcb43deef845a7850770c0df6b08ab5e4a80 PCI: pci-bridge-emul: Add description for class_revision field
7c4a639bb7e943f10956087b6b5efe8bc446022e PCI: pci-bridge-emul: Add definitions for missing capabilities registers
7030af8bc0892bd789956747df04e446ff636773 PCI: aardvark: Add support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2 registers on emulated bridge
0ea2559866f2fbb53e5769c83e12ff6d11d3ada5 PCI: aardvark: Fix LNKCAP2 and LNKCTL2 registers on emulated bridge
97cbce7931698f74d6858e4eea751abe847d5e65 PCI: aardvark: Add support for PCI_BRIDGE_CTL_BUS_RESET on emulated bridge
a5b8af615f46f9745e6167eb968955da8b07aca5 PCI: aardvark: Replace custom PCIE_CORE_ERR_CAPCTL_* macros by linux/pci_regs.h macros
28a9cf17b8488be582170f1bb1c6fbe3a42929b5 PCI: aardvark: Replace custom PCIE_CORE_INT_* macros by linux PCI_INTERRUPT_* values
a73f9cf07e383fe070a765c03d156c255816fa8a PCI: aardvark: Cleanup some register macros
4fb8e30c646345754c000edcddd6cc7a8a7351cd PCI: aardvark: Add comments for OB_WIN_ENABLE and ADDR_WIN_DISABLE
65c927f820ef4ae2d893a39b4729028cdb77c323 PCI: pci-bridge-emul: re-arrange register tests
ce7e0c54d83cda94f1ca099221e46609f890c6b7 PCI: pci-bridge-emul: add support for PCIe extended capabilities
ee12a063b43b885be6f17298c8475ef7ca1ae36a PCI: aardvark: Add support for Advanced Error Reporting registers on emulated bridge
c08dd139ebfdba1c2e9521e1bbd439581e559150 PCI: aardvark: Add support for error reporting interrupt on emulated bridge
541629371056c70eabe051ff28ad1fcb4b88c151 PCI: aardvark: Remove PCIE_CORE_CTRL0_REG macros not applicable for Root Complex
5ced34c8a567159f1c3c78f6a0dd452bf41067bb PCI: aardvark: Show warning when Hot Reset or Link Down event occurs
next reply other threads:[~2021-03-16 9:53 UTC|newest]
Thread overview: 92+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 9: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-12 17: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=161588839325.32076.13859420858093273342@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.