lkml.org 
[lkml]   [2017]   [Jun]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [lustre-devel] [PATCH] staging: lustre: headers: potential UAPI headers
On Thu, Jun 15, 2017 at 04:48:20PM +0100, James Simmons wrote:
> So this is coming from trying to understand the "merge them together"
> part. Some people reading this it implies all the headers would be
> eventually merged into one big header and placed into include/uapi/linux.

Sounds like a good plan, why wouldn't you want something nice and simple
like that? :)

> We are getting to the point where some sites are migrating from the out
> of tree branch to this client. This also means they will be moving
> external open source userland applications shortly. If we expose UAPI
> headers that are completely different that it breaks their tools users
> will dump this client and go back to the out source tree. We really like
> to avoid that.

Note, as the code is still in staging, files will get renamed and moved
around, you know that, nothing we can do here at the moment.

I have yet to see any patches yet, so I don't know why people are
complaining...

thanks,

greg k-h

\
 
 \ /
  Last update: 2017-06-15 18:57    [W:0.074 / U:0.072 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site