public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Joe Perches <joe@perches.com>
Cc: James Simmons <jsimmons@infradead.org>,
	devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Oleg Drokin <oleg.drokin@intel.com>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH 0/7] staging: lustre: last missing patches for lustre 2.6
Date: Mon, 22 Aug 2016 16:38:01 -0400	[thread overview]
Message-ID: <20160822203801.GB5166@kroah.com> (raw)
In-Reply-To: <1471888542.3746.70.camel@perches.com>

On Mon, Aug 22, 2016 at 10:55:42AM -0700, Joe Perches wrote:
> On Mon, 2016-08-22 at 18:41 +0100, James Simmons wrote:
> > On Fri, 2016-08-19 at 20:44 +0100, James Simmons wrote:
> 
> Hi again James.
> 
> > > I don't _need_ anything, but I think it'd be simpler to
> > > have just 2 directories, one for lustre kernel stuff
> > > and another for lustre uapi stuff.
> > > 
> > > That applies for LNet and libcfs #includes as well.
> > > 
> > > To me, ideally, there'd only be 2 #include directories
> > > so that the only used #include styles could become:
> > > 
> > > #include 
> > > and
> > > #include 
> > > 
> > > and that would work regardless of lustre's layout
> > > in staging or elsewhere.
> > I didn't expect this to be requested at this time. I thought this would be 
> > addressed just before we left staging.
> 
> Sooner is better to me, but that's up to you all.

No, please, let's wait, there's still lots of "real" work to be done in
the lustre code before messing with the .h files like this.

James, please just continue the great work you are doing so far, all is
fine :)

thanks,

greg k-h

      reply	other threads:[~2016-08-22 20:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 18:07 [PATCH 0/7] staging: lustre: last missing patches for lustre 2.6 James Simmons
2016-08-19 18:07 ` [PATCH 1/7] staging: lustre: lmv: implement lmv version of read_page James Simmons
2016-08-19 18:07 ` [PATCH 2/7] staging: lustre: llite: move dir cache to MDC layer James Simmons
2016-08-19 18:07 ` [PATCH 3/7] staging: lustre: obd: remove unused lmv_readpages()/mdc_readpage() James Simmons
2016-08-19 18:07 ` [PATCH 4/7] staging: lustre: mdt: add OBD_CONNECT_DIR_STRIPE flag James Simmons
2016-08-19 18:07 ` [PATCH 5/7] staging: lustre: obd: remove dead code James Simmons
2016-08-19 18:07 ` [PATCH 6/7] staging: lustre: obd: decruft md_enqueue() and md_intent_lock() James Simmons
2016-08-19 18:07 ` [PATCH 7/7] staging: lustre: update version to 2.5.99 James Simmons
2016-08-19 18:39 ` [PATCH 0/7] staging: lustre: last missing patches for lustre 2.6 Joe Perches
2016-08-19 19:44   ` James Simmons
2016-08-19 20:01     ` Joe Perches
2016-08-22 17:41       ` James Simmons
2016-08-22 17:55         ` Joe Perches
2016-08-22 20:38           ` Greg Kroah-Hartman [this message]

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=20160822203801.GB5166@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=joe@perches.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox