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@bracecomputerlab.com>
Subject: [PATCH net 4/4] via-rhine: Version bumped to 1.5.2
Date: Mon, 28 Sep 2020 15:00:41 -0700	[thread overview]
Message-ID: <20200928220041.6654-5-kevinbrace@gmx.com> (raw)
In-Reply-To: <20200928220041.6654-1-kevinbrace@gmx.com>

From: Kevin Brace <kevinbrace@bracecomputerlab.com>

via-rhine Version 1.5.2 contains a fix for reset failure and hardware
disappearance after resume.  I am taking over code maintenance work
for via-rhine.

Signed-off-by: Kevin Brace <kevinbrace@bracecomputerlab.com>
---
 drivers/net/ethernet/via/via-rhine.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/ethernet/via/via-rhine.c b/drivers/net/ethernet/via/via-rhine.c
index f2ac55172b09..9e2af4bf2f0e 100644
--- a/drivers/net/ethernet/via/via-rhine.c
+++ b/drivers/net/ethernet/via/via-rhine.c
@@ -32,8 +32,8 @@
 #define pr_fmt(fmt) KBUILD_MODNAME ": " fmt

 #define DRV_NAME	"via-rhine"
-#define DRV_VERSION	"1.5.1"
-#define DRV_RELDATE	"2010-10-09"
+#define DRV_VERSION	"1.5.2"
+#define DRV_RELDATE	"2020-09-18"

 #include <linux/types.h>

--
2.17.1


  parent reply	other threads:[~2020-09-28 23:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-28 22:00 [PATCH net 0/4] via-rhine: Resume fix and other maintenance work Kevin Brace
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 ` Kevin Brace [this message]
2020-09-29  1:50   ` [PATCH net 4/4] via-rhine: Version bumped to 1.5.2 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-5-kevinbrace@gmx.com \
    --to=kevinbrace@gmx.com \
    --cc=kevinbrace@bracecomputerlab.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.