From: David Miller <davem@davemloft.net>
To: hkallweit1@gmail.com
Cc: nic_swsd@realtek.com, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/5] r8169: some functional improvements
Date: Fri, 23 Nov 2018 17:32:43 -0800 (PST) [thread overview]
Message-ID: <20181123.173243.1747240846778402562.davem@davemloft.net> (raw)
In-Reply-To: <79f821cf-2ad4-98f0-558d-eda3148cec38@gmail.com>
From: Heiner Kallweit <hkallweit1@gmail.com>
Date: Thu, 22 Nov 2018 21:54:36 +0100
> This series includes a few functional improvements.
Series applied.
prev parent reply other threads:[~2018-11-24 12:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 20:54 [PATCH net-next 0/5] r8169: some functional improvements Heiner Kallweit
2018-11-22 20:56 ` [PATCH net-next 1/5] r8169: remove ancient GCC bug workaround in a second place Heiner Kallweit
2018-11-22 20:58 ` [PATCH net-next 2/5] r8169: remove default chip versions Heiner Kallweit
2018-11-22 21:00 ` [PATCH net-next 3/5] r8169: simplify detecting chip versions with same XID Heiner Kallweit
2018-11-22 21:02 ` [PATCH net-next 4/5] r8169: use napi_consume_skb where possible Heiner Kallweit
2018-11-22 21:03 ` [PATCH net-next 5/5] r8169: replace macro TX_FRAGS_READY_FOR with a function Heiner Kallweit
2018-11-24 1:32 ` David Miller [this message]
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=20181123.173243.1747240846778402562.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--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).