[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150311.131457.1314699780103858026.davem@davemloft.net>
Date: Wed, 11 Mar 2015 13:14:57 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: amirv@...lanox.com
Cc: gregkh@...uxfoundation.org, netdev@...r.kernel.org,
hadarh@...lanox.com, yevgenyp@...lanox.com, ogerlitz@...lanox.com,
talal@...lanox.com, shannon.nelson@...el.com, dledford@...hat.com,
greearb@...delatech.com, gregory.v.rose@...el.com,
jeffrey.t.kirsher@...el.com, jesse.brandeburg@...el.com,
john.ronciak@...el.com
Subject: Re: [PATCH net-next V1 0/3] net/mlx4_core: Allow setting init-time
device specific parameters
From: Amir Vadai <amirv@...lanox.com>
Date: Wed, 11 Mar 2015 11:08:50 +0200
> Also, customers are paying for a very sophisticated piece of
> hardware, and we would like to enable power user to tweak it in some
> situtations. Of course the default mode should be used in 99% of the
> use cases.
How much money someone pays for your hardware has nothing to do with
the standards by which we design userspace interfaces to configure
these devices.
These textual interfaces are arbitrary, and you are choosing it only
because you cannot come up with a more reasonable scheme,
I'm not applying these changes.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists