From: David Miller <davem@davemloft.net>
To: sergej.benilov@googlemail.com
Cc: venza@brownhat.org, netdev@vger.kernel.org
Subject: Re: [PATCH] sis900: increment revision number
Date: Sun, 23 Jun 2019 08:36:52 -0700 (PDT) [thread overview]
Message-ID: <20190623.083652.1200010744616612417.davem@davemloft.net> (raw)
In-Reply-To: <20190623074707.6348-1-sergej.benilov@googlemail.com>
From: Sergej Benilov <sergej.benilov@googlemail.com>
Date: Sun, 23 Jun 2019 09:47:07 +0200
> Increment revision number to 1.08.11 (TX completion fix).
>
> Signed-off-by: Sergej Benilov <sergej.benilov@googlemail.com>
These are useless, really...
People are going to backport the TX completion fix all by itself
and not this change if I were to merge it.
I really want to heavily discourage these kinds of things, sorry.
Code is code, the fix is there or it isn't.
prev parent reply other threads:[~2019-06-23 15:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 7:47 [PATCH] sis900: increment revision number Sergej Benilov
2019-06-23 8:57 ` Daniele Venzano
2019-06-23 9:10 ` Joe Perches
2019-06-23 9:13 ` Daniele Venzano
2019-06-23 15:37 ` David Miller
2019-06-23 16:26 ` Joe Perches
2019-06-23 15:36 ` David Miller [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=20190623.083652.1200010744616612417.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sergej.benilov@googlemail.com \
--cc=venza@brownhat.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