From: Heiner Kallweit <hkallweit1@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>,
David Miller <davem@davemloft.net>,
Bjorn Helgaas <helgaas@kernel.org>,
Realtek linux nic maintainers <nic_swsd@realtek.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/2] PCI: add two more values for PCIe Max_Read_Request_Size and initially use them in r8169 network driver
Date: Mon, 16 Apr 2018 21:35:42 +0200 [thread overview]
Message-ID: <00f1255f-acf0-4760-c20f-0b78bda44645@gmail.com> (raw)
In r8169 network driver I stumbled across a magic number translating
to PCI MRRS size 4K. The PCI core is still missing constants for
values 2K and 4K (as defined in PCI standard).
So let's add these two constants and use the 4K constant in r8169.
Second patch depends on the first one, therefore both patches
preferrably should go through either PCI or netdev tree.
Heiner Kallweit (2):
PCI: add two more values for PCIe Max_Read_Request_Size
r8169: replace magic numbers with PCI MRRS constant
drivers/net/ethernet/realtek/r8169.c | 39 ++++++++++++++--------------
include/uapi/linux/pci_regs.h | 2 ++
2 files changed, 21 insertions(+), 20 deletions(-)
--
2.17.0
next reply other threads:[~2018-04-16 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 19:35 Heiner Kallweit [this message]
2018-04-16 19:37 ` [PATCH net-next 1/2] PCI: Add two more values for PCIe Max_Read_Request_Size Heiner Kallweit
2018-04-16 21:42 ` Bjorn Helgaas
2018-04-16 22:06 ` David Miller
2018-04-16 19:38 ` [PATCH net-next 2/2] r8169: replace magic numbers with PCI MRRS constant Heiner Kallweit
2018-04-16 22:55 ` [PATCH net-next 0/2] PCI: add two more values for PCIe Max_Read_Request_Size and initially use them in r8169 network driver David Miller
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=00f1255f-acf0-4760-c20f-0b78bda44645@gmail.com \
--to=hkallweit1@gmail.com \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
/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;
as well as URLs for NNTP newsgroup(s).