All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: "Drokin, Oleg" <oleg.drokin@intel.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"Dilger, Andreas" <andreas.dilger@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: [lustre-devel] [PATCH] staging: lustre: headers: potential UAPI headers
Date: Thu, 15 Jun 2017 18:56:33 +0200	[thread overview]
Message-ID: <20170615165633.GA4478@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1706140149160.20798@casper.infradead.org>

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

WARNING: multiple messages have this Message-ID (diff)
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: "Drokin, Oleg" <oleg.drokin@intel.com>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
	"Dilger, Andreas" <andreas.dilger@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [lustre-devel] [PATCH] staging: lustre: headers: potential UAPI headers
Date: Thu, 15 Jun 2017 18:56:33 +0200	[thread overview]
Message-ID: <20170615165633.GA4478@kroah.com> (raw)
In-Reply-To: <alpine.LFD.2.20.1706140149160.20798@casper.infradead.org>

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

  reply	other threads:[~2017-06-15 16:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 17:06 [lustre-devel] [PATCH] staging: lustre: headers: potential UAPI headers James Simmons
2016-12-19 17:06 ` James Simmons
2017-01-03 14:12 ` [lustre-devel] " Greg Kroah-Hartman
2017-01-03 14:12   ` Greg Kroah-Hartman
2017-01-16 21:28   ` [lustre-devel] " James Simmons
2017-01-16 21:28     ` James Simmons
2017-01-17  7:41     ` [lustre-devel] " Greg Kroah-Hartman
2017-01-17  7:41       ` Greg Kroah-Hartman
2017-01-20 23:33       ` [lustre-devel] " James Simmons
2017-01-20 23:33         ` James Simmons
2017-01-21  9:24         ` [lustre-devel] " Greg Kroah-Hartman
2017-01-21  9:24           ` Greg Kroah-Hartman
2017-01-30  0:09           ` [lustre-devel] " James Simmons
2017-01-30  0:09             ` James Simmons
2017-06-12 20:20           ` [lustre-devel] " Dilger, Andreas
2017-06-12 20:20             ` Dilger, Andreas
2017-06-12 20:25             ` [lustre-devel] " Dan Carpenter
2017-06-12 20:25               ` Dan Carpenter
2017-06-13  4:25             ` [lustre-devel] " Greg Kroah-Hartman
2017-06-13  4:25               ` Greg Kroah-Hartman
2017-06-15 15:48               ` [lustre-devel] " James Simmons
2017-06-15 15:48                 ` James Simmons
2017-06-15 16:56                 ` Greg Kroah-Hartman [this message]
2017-06-15 16:56                   ` Greg Kroah-Hartman

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=20170615165633.GA4478@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=jsimmons@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lustre-devel@lists.lustre.org \
    --cc=oleg.drokin@intel.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.