From: Max Uvarov <muvarov@gmail.com>
To: netdev@vger.kernel.org
Cc: linux-omap@vger.kernel.org, grygorii.strashko@ti.com,
Max Uvarov <muvarov@gmail.com>
Subject: [PATCHv3 0/2] davinci_mdio: remove busy loop on wait user access
Date: Fri, 11 Aug 2017 13:57:39 +0300 [thread overview]
Message-ID: <1502449061-30373-1-git-send-email-muvarov@gmail.com> (raw)
v3: no code change, just added cover letter
First patch fixes cpu load on polling busy mdio line.
Second patch just prints which mdio frequency was configured.
Max Uvarov (2):
drivers: net: davinci_mdio: remove busy loop on wait user access
drivers: net: davinci_mdio: print bus frequency
drivers/net/ethernet/ti/davinci_mdio.c | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
--
2.5.0
next reply other threads:[~2017-08-11 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 10:57 Max Uvarov [this message]
2017-08-11 10:57 ` [PATCHv3 1/2] drivers: net: davinci_mdio: remove busy loop on wait user access Max Uvarov
2017-08-11 10:57 ` [PATCHv3 2/2] drivers: net: davinci_mdio: print bus frequency Max Uvarov
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=1502449061-30373-1-git-send-email-muvarov@gmail.com \
--to=muvarov@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox