[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170615165633.GA4478@kroah.com>
Date: Thu, 15 Jun 2017 18:56:33 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: James Simmons <jsimmons@...radead.org>
Cc: "Drokin, Oleg" <oleg.drokin@...el.com>,
"devel@...verdev.osuosl.org" <devel@...verdev.osuosl.org>,
"Dilger, Andreas" <andreas.dilger@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Lustre Development List <lustre-devel@...ts.lustre.org>
Subject: Re: [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
Powered by blists - more mailing lists