All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Brace <kevinbrace@gmx.com>
To: netdev@vger.kernel.org
Cc: Kevin Brace <kevinbrace@gmx.com>
Subject: [PATCH net 0/4] via-rhine: Resume fix and other maintenance work
Date: Mon, 28 Sep 2020 15:00:37 -0700	[thread overview]
Message-ID: <20200928220041.6654-1-kevinbrace@gmx.com> (raw)

I use via-rhine based Ethernet regularly, and the Ethernet dying
after resume was really annoying me.  I decided to take the
matter into my own hands, and came up with a fix for the Ethernet
disappearing after resume.  I will also want to take over the code
maintenance work for via-rhine.  The patches apply to the latest
code, but they should be backported to older kernels as well.
--

Kevin Brace (4):
  via-rhine: Fix for the hardware having a reset failure after resume
  via-rhine: VTunknown1 device is really VT8251 South Bridge
  via-rhine: New device driver maintainer
  via-rhine: Version bumped to 1.5.2

 MAINTAINERS                          |  3 ++-
 drivers/net/ethernet/via/via-rhine.c | 10 ++++++----
 2 files changed, 8 insertions(+), 5 deletions(-)

--
2.17.1


             reply	other threads:[~2020-09-29  0:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 22:00 Kevin Brace [this message]
2020-09-28 22:00 ` [PATCH net 1/4] via-rhine: Fix for the hardware having a reset failure after resume Kevin Brace
2020-09-28 22:00 ` [PATCH net 2/4] via-rhine: VTunknown1 device is really VT8251 South Bridge Kevin Brace
2020-09-28 22:00 ` [PATCH net 3/4] via-rhine: New device driver maintainer Kevin Brace
2020-09-28 22:00 ` [PATCH net 4/4] via-rhine: Version bumped to 1.5.2 Kevin Brace
2020-09-29  1:50   ` David Miller
2020-09-29 21:10     ` Kevin Brace

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=20200928220041.6654-1-kevinbrace@gmx.com \
    --to=kevinbrace@gmx.com \
    --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 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.