[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20170426.104416.270999555163740292.davem@davemloft.net>
Date: Wed, 26 Apr 2017 10:44:16 -0400 (EDT)
From: David Miller <davem@...emloft.net>
To: simon.horman@...ronome.com
Cc: jhs@...atatu.com, jakub.kicinski@...ronome.com,
netdev@...r.kernel.org, johannes@...solutions.net,
dsa@...ulusnetworks.com, daniel@...earbox.net,
alexei.starovoitov@...il.com, bblanco@...il.com,
john.fastabend@...il.com, kubakici@...pl, oss-drivers@...ronome.com
Subject: Re: [oss-drivers] Re: [RFC 3/4] nfp: make use of extended ack
message reporting
From: Simon Horman <simon.horman@...ronome.com>
Date: Wed, 26 Apr 2017 13:13:16 +0200
> On Tue, Apr 25, 2017 at 10:20:22AM -0400, David Miller wrote:
>> From: Jamal Hadi Salim <jhs@...atatu.com>
>> Date: Tue, 25 Apr 2017 08:42:32 -0400
>>
>> > So are we going to standardize these strings?
>>
>> No.
>>
>> > i.e what if some user has written a bash script that depends on this
>> > string and it gets changed later.
>>
>> They can't do that.
>>
>> It's free form extra information an application may or not provide
>> to the user when the kernel emits it.
>
> I don't feel strongly about this and perhaps it can be revisited at some
> point but perhaps it would be worth documenting that he strings do not
> form part of the UAPI as my expectation would have been that they do f.e. to
> facilitate internationalisation.
These two things are entirely separate.
We can maintain uptodate translations of the strings, yet document that
they can change at any time and are thus not UAPI.
Powered by blists - more mailing lists