From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Xiong Zhou <jencce.kernel@gmail.com>
Cc: "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
Paul Bolle <pebolle@tiscali.nl>, Jiri Kosina <trivial@kernel.org>,
Peng Tao <bergwolf@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andreas Dilger <andreas.dilger@intel.com>
Subject: Re: [PATCH v2] staging/lustre: lloop depends on BLOCK
Date: Fri, 2 Aug 2013 11:11:11 +0800 [thread overview]
Message-ID: <20130802031111.GA2329@kroah.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1308021019220.8333@M2420>
On Fri, Aug 02, 2013 at 10:20:28AM +0800, Xiong Zhou wrote:
>
>
> On Wed, 31 Jul 2013, Greg Kroah-Hartman wrote:
>
> > 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
> >
>
> OK, this patch is based on the staging-next branch of your staging tree.
>
>
> From: Xiong Zhou <jencce.kernel@gmail.com>
>
> Add a config option for llite/lloop in lustre driver, making it
> depends on BLOCK to fix this better:
> drivers/staging/lustre/lustre/fid/../include/linux/lustre_compat25.h:117:2:
> error: implicit declaration of function ‘unregister_blkdev’
>
> Also, remove the wrapper ll_unregister_blkdev which depends on BLOCK in
> the header and just call unregister_blkdev in lloop.c based on Peng Tao's
> comment. Drop the redundant dependency on STAGING for LUSTRE_FS, remove
> some unnecessary jdb header files which depends on BLOCK btw.
>
> Signed-off-by: Xiong Zhou <jencce.kernel@gmail.com>
> Reviewed-by: Peng Tao <tao.peng@emc.com>
Please resend this so I don't have to edit the body of the email, and
the Subject: line as well.
Also, you have a bunch of trailing whitespace in your changelog
comments, are you sure you want/need that?
thanks,
greg k-h
next prev parent reply other threads:[~2013-08-02 3:09 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
2013-08-02 2:20 ` Xiong Zhou
2013-08-02 3:11 ` Greg Kroah-Hartman [this message]
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=20130802031111.GA2329@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.