From: Heiner Kallweit <hkallweit1@gmail.com>
To: Realtek linux nic maintainers <nic_swsd@realtek.com>,
David Miller <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [PATCH net-next 0/2] r8169: create function pointer arrays for PHY and chip hw init functions
Date: Sun, 14 Apr 2019 10:29:23 +0200 [thread overview]
Message-ID: <4cb6d89c-144b-6e9a-1a1e-1085452b96c2@gmail.com> (raw)
Using function pointer arrays makes the code easier to read and better
maintainable. AFAIK function pointer arrays cause some performance
drawback due to Spectre mitigation, but we're not in a hot path.
Heiner Kallweit (2):
r8169: create function pointer array for PHY init functions
r8169: create function pointer array for chip hw init functions
drivers/net/ethernet/realtek/r8169.c | 401 +++++++++------------------
1 file changed, 127 insertions(+), 274 deletions(-)
--
2.21.0
next reply other threads:[~2019-04-14 8:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-14 8:29 Heiner Kallweit [this message]
2019-04-14 8:30 ` [PATCH net-next 1/2] r8169: create function pointer array for PHY init functions Heiner Kallweit
2019-04-14 8:32 ` [PATCH net-next 2/2] r8169: create function pointer array for chip hw " Heiner Kallweit
2019-04-14 20:50 ` [PATCH net-next 0/2] r8169: create function pointer arrays for PHY and " 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=4cb6d89c-144b-6e9a-1a1e-1085452b96c2@gmail.com \
--to=hkallweit1@gmail.com \
--cc=davem@davemloft.net \
--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 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.