From: Michal Privoznik <mprivozn@redhat.com>
To: David Miller <davem@davemloft.net>
Cc: jiri@resnulli.us, gregkh@linuxfoundation.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH] net-sysfs: Report link speed only when possible
Date: Mon, 16 Jun 2014 09:32:35 +0200 [thread overview]
Message-ID: <539E9D93.9040405@redhat.com> (raw)
In-Reply-To: <20140613.130350.1729507484821351177.davem@davemloft.net>
On 13.06.2014 22:03, David Miller wrote:
> From: Michal Privoznik <mprivozn@redhat.com>
> Date: Fri, 13 Jun 2014 11:19:51 +0200
>
>> So if I were developing brand new application I could say: I'm
>> dropping all this workaround code and have it clean and require say
>> 3.16 kernel at least.
>
> Then your application wouldn't be usable on %99 of systems for a long
> long time.
>
How come? The application is going to be usable for as long as
library/kernel APIs won't change. Or until the time a new regression is
introduced and fix is rejected. Speaking of which - long long time
applications *are* broken now. This patch is combining the good from
both worlds: old applications are fixed, new applications doesn't have
to learn anything new.
> I don't think this is the right tradeoff at all.
>
Neither is keeping things broken.
Michal
next prev parent reply other threads:[~2014-06-16 7:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 8:40 [PATCH] net-sysfs: Report link speed only when possible Michal Privoznik
2014-06-06 8:57 ` Jiri Pirko
2014-06-06 19:54 ` David Miller
2014-06-13 9:19 ` Michal Privoznik
2014-06-13 20:03 ` David Miller
2014-06-16 7:32 ` Michal Privoznik [this message]
2014-06-16 8:11 ` David Miller
2014-06-16 8:30 ` Michal Privoznik
2014-06-16 8:44 ` David Miller
2014-06-16 8:59 ` Michal Privoznik
2014-06-16 9:01 ` Jiri Pirko
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=539E9D93.9040405@redhat.com \
--to=mprivozn@redhat.com \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=jiri@resnulli.us \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).