All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Gitolite <devnull@kernel.org>
Subject: post-receive: pub/scm/linux/kernel/git/pali/linux
Date: Fri, 19 Feb 2021 18:21:01 -0000	[thread overview]
Message-ID: <161375886191.18993.7650995150221971893@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: 1d14b723174927c05220d5f9127de1b7d4e58d0c
    new: 16f256aa9d587d94ad3d717a4f67344247c05c85
    log: revlist-1d14b7231749-16f256aa9d58.txt

[-- Attachment #2: revlist-1d14b7231749-16f256aa9d58.txt --]
[-- Type: text/plain, Size: 2422 bytes --]

a40f904e94eb7642d9714be4f507410c2fe2d90e PCI: aardvark: Fix reading PCI_EXP_FLAGS_VERS on emulated bridge
3a8132c662e9c1d7e8dfacce8612cb792ae33994 PCI: aardvark: Fix reading PCI_EXP_LNKCAP_SLS on emulated bridge
95496d35397461382d7676c1779508be78c12190 PCI: aardvark: Implement workaround for the readback value of VEND_ID
27a3db356ee401613af26a6de69e9fab3f10a7d7 PCI: aardvark: Set link speed also into PCIe Link Control 2 register
f8064a2998b4981f290b1a666b0d0b6990d2763d PCI: aardvark: Fix support for MSI interrupts
bef7f516957cce1fd0954408f8a9d15d411ba5ee PCI: aardvark: Fix support for PME on emulated bridge
99428846f8f36ba8ffcb1d00f77753be6efa21ac PCI: aardvark: Fix support for PME requester on emulated bridge
498552624e280ad59dfb9e0c08cd0abaa0ec4ab4 PCI: aardvark: Fix support for bus mastering and PCI_COMMAND on emulated bridge
6e9d49c38786a7cf490cc5e20019fe4ca08620e6 PCI: aardvark: Replace custom PCIE_CORE_ERR_CAPCTL_* macros by linux/pci_regs.h macros
cc6ea55c117c54cc3d3133139a7f88ee21dd4781 PCI: aardvark: Replace custom PCIE_CORE_INT_* macros by linux PCI_INTERRUPT_* values
3232714bfc939bf99e7675027e9ed3aac936a866 PCI: aardvark: Cleanup some register macros
bb87a82819f770aa2867d59653918de96e30fa0d PCI: aardvark: Add comments for OB_WIN_ENABLE and ADDR_WIN_DISABLE
a0ef9f1e956feffb5ff55ef9a7c75001e0e0eb59 PCI: pci-bridge-emul: Add description for class_revision field
14f613b8b3bb67e08e29ea1e1f6405a9fb9aee7e PCI: pci-bridge-emul: Add definitions for missing capabilities registers
01ae7a80ae5e0ffe57af53a70095f9fc8c1db1fb PCI: aardvark: Add support for DEVCAP2, DEVCTL2, LNKCAP2 and LNKCTL2 registers on emulated bridge
01ec3b09d041a8baae8c23aadb511f13d4beda8a PCI: aardvark: Add support for PCI_BRIDGE_CTL_BUS_RESET on emulated bridge
b14d991c73c4781c4df83e4551237a8c071c86cb PCI: pci-bridge-emul: re-arrange register tests
408491090c5a49340ad9bd10bb6585eeb835e59b PCI: pci-bridge-emul: add support for PCIe extended capabilities
4a7601a24a8d3f70c5564d7763d147288b03393a PCI: aardvark: Add support for Advanced Error Reporting registers on emulated bridge
e6c234360704b195fe466bf72756d0995d701856 PCI: aardvark: Add support for error reporting interrupt on emulated bridge
652a15b3ca491d1f871ca116300cac52b74ffc4c PCI: aardvark: Show warning when Hot Reset or Link Down event occurs
16f256aa9d587d94ad3d717a4f67344247c05c85 PCI: aardvark: Move enabling of link training to advk_pcie_train_link()

             reply	other threads:[~2021-02-19 18:21 UTC|newest]

Thread overview: 92+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 18:21 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-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-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=161375886191.18993.7650995150221971893@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.