All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Xiong Zhou <jencce.kernel@gmail.com>
Cc: Peng Tao <bergwolf@gmail.com>,
	Andreas Dilger <andreas.dilger@intel.com>,
	Paul Bolle <pebolle@tiscali.nl>, Jiri Kosina <trivial@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>
Subject: Re: [PATCH v2] staging/lustre: lloop depends on BLOCK
Date: Wed, 31 Jul 2013 17:41:49 -0700	[thread overview]
Message-ID: <20130801004149.GA30696@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1307311028001.25194@M2420>

On Wed, Jul 31, 2013 at 10:30:41AM +0800, Xiong Zhou wrote:
> From: Xiong Zhou <jencce.kernel@gmail.com>
> 
> First version of this patch makes LUSTRE_FS depends on BLOCK.  Second
> version makes only lloop depends on BLOCK with a config option for this
> dependence, and remove unnecessary jdb header files which depends on
> BLOCK.
> 
> This version removes the wrapper ll_unregister_blkdev which depends on
> BLOCK in header and just call unregister_blkdev in lloop.c based on Peng
> Tao's comment.

This isn't all needed in the patch changelog info, just say what it
does.

Also, it doesn't apply for some reason, care to refresh this against my
latest tree and resend?

thanks,

greg k-h

  reply	other threads:[~2013-08-01  7:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30  0:29 [PATCH v2] staging/lustre: lloop depends on BLOCK Xiong Zhou
2013-07-30  7:44 ` Peng Tao
2013-07-31  2:30   ` Xiong Zhou
2013-08-01  0:41     ` Greg Kroah-Hartman [this message]
2013-08-02  2:20       ` Xiong Zhou
2013-08-02  3:11         ` Greg Kroah-Hartman
2013-08-01  8:45 ` Christoph Hellwig
2013-08-01 19:57   ` Dilger, Andreas
2013-08-02 10:49     ` Christoph Hellwig
2013-08-07  7:45       ` Dilger, Andreas
2013-08-08 12:17         ` Christoph Hellwig

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=20130801004149.GA30696@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=andreas.dilger@intel.com \
    --cc=bergwolf@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=jencce.kernel@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=trivial@kernel.org \
    /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.