From: Kevin Brace <kevinbrace@gmx.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, kevinbrace@bracecomputerlab.com
Subject: Re: [PATCH net 4/4] via-rhine: Version bumped to 1.5.2
Date: Tue, 29 Sep 2020 23:10:04 +0200 [thread overview]
Message-ID: <trinity-c9fa5381-07f5-4aad-94e9-dcff576dae01-1601413804865@3c-app-mailcom-bs07> (raw)
In-Reply-To: <20200928.185020.239065830030111620.davem@davemloft.net>
Hi David,
I sent the v2 patches to netdev mailing list.
I hope they meet your standards.
Regards,
Kevin Brace
Brace Computer Laboratory blog
https://bracecomputerlab.com
> Sent: Monday, September 28, 2020 at 6:50 PM
> From: "David Miller" <davem@davemloft.net>
> To: kevinbrace@gmx.com
> Cc: netdev@vger.kernel.org, kevinbrace@bracecomputerlab.com
> Subject: Re: [PATCH net 4/4] via-rhine: Version bumped to 1.5.2
>
> From: Kevin Brace Date: Mon, 28 Sep 2020 15:00:41 -0700 > @@ -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" Driver versions like this are deprecated and we are removing them from every driver. Please remove, rather than update, such values. Thank you.
prev parent reply other threads:[~2020-09-29 21:10 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 ` [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 [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=trinity-c9fa5381-07f5-4aad-94e9-dcff576dae01-1601413804865@3c-app-mailcom-bs07 \
--to=kevinbrace@gmx.com \
--cc=davem@davemloft.net \
--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.