public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: James Simmons <jsimmons@infradead.org>
Cc: devel@driverdev.osuosl.org,
	Andreas Dilger <andreas.dilger@intel.com>,
	Oleg Drokin <oleg.drokin@intel.com>, wang di <di.wang@intel.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lustre Development List <lustre-devel@lists.lustre.org>
Subject: Re: [PATCH 01/37] staging: lustre: llite: add missing LMV_MAGIC_V1 case
Date: Tue, 27 Sep 2016 13:01:02 +0200	[thread overview]
Message-ID: <20160927110102.GA16196@kroah.com> (raw)
In-Reply-To: <1474901450-28730-1-git-send-email-jsimmons@infradead.org>

On Mon, Sep 26, 2016 at 10:50:50AM -0400, James Simmons wrote:
> From: wang di <di.wang@intel.com>
> 
> The port to upstream dropped handling the LMV_MAGIC_V1
> case for ll_dir_getstripe. This adds it back.
> 
> Signed-off-by: wang di <di.wang@intel.com>
> Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3531
> Reviewed-on: http://review.whamcloud.com/7228
> Reviewed-by: Andreas Dilger <andreas.dilger@intel.com>
> Reviewed-by: John L. Hammond <john.hammond@intel.com>
> Reviewed-by: Alex Zhuravlev <alexey.zhuravlev@intel.com>
> Reviewed-by: Oleg Drokin <oleg.drokin@intel.com>
> Signed-off-by: James Simmons <jsimmons@infradead.org>
> ---
>  drivers/staging/lustre/lustre/llite/dir.c           | 4 ++++
>  drivers/staging/lustre/lustre/ptlrpc/pack_generic.c | 1 +
>  2 files changed, 5 insertions(+)

I got this single patch, what about the other 36 patches you are saying
this is a series of?

thanks,

greg k-h

      reply	other threads:[~2016-09-27 11:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-26 14:50 [PATCH 01/37] staging: lustre: llite: add missing LMV_MAGIC_V1 case James Simmons
2016-09-27 11:01 ` 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=20160927110102.GA16196@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=di.wang@intel.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