From: Fengguang Wu <fengguang.wu@intel.com>
To: NeilBrown <neilb@suse.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: [md:for-linus 7/8] drivers/md/md.c:5297:6: sparse: symbol '__md_stop' was not declared. Should it be static?
Date: Tue, 20 Nov 2012 16:52:54 +0800 [thread overview]
Message-ID: <20121120085254.GA12104@localhost> (raw)
In-Reply-To: <20121120194614.3bb75ef0@notabene.brown>
On Tue, Nov 20, 2012 at 07:46:14PM +1100, NeilBrown wrote:
> On Tue, 20 Nov 2012 16:25:21 +0800 kbuild test robot <fengguang.wu@intel.com>
> wrote:
>
> > tree: git://neil.brown.name/md for-linus
> > head: 879d63a5d4cc36ff804a9cf0de2c092dd538fa45
> > commit: fceef26b94e8507f33e28741f755c010de052042 [7/8] md: make sure everything is freed when dm-raid stops an array.
> >
> >
> > sparse warnings:
> >
> > drivers/md/md.c:1553:34: sparse: cast to restricted __le64
> > drivers/md/md.c:1823:40: sparse: incorrect type in assignment (different base types)
> > drivers/md/md.c:1823:40: expected unsigned long long [unsigned] [long] [long long] [usertype] <noident>
> > drivers/md/md.c:1823:40: got restricted __le64 [usertype] <noident>
> > drivers/md/md.c:1898:26: sparse: incorrect type in assignment (different base types)
> > drivers/md/md.c:1898:26: expected restricted __le64 [usertype] super_offset
> > drivers/md/md.c:1898:26: got unsigned long long [unsigned] [usertype] sb_start
> > + drivers/md/md.c:5297:6: sparse: symbol '__md_stop' was not declared. Should it be static?
> >
> > Please consider folding the attached diff :-)
>
> Wow! What wonderful service.
>
> Attached diff has been folded in.
Thank you! :)
Regards,
Fengguang
prev parent reply other threads:[~2012-11-20 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 8:25 [md:for-linus 7/8] drivers/md/md.c:5297:6: sparse: symbol '__md_stop' was not declared. Should it be static? kbuild test robot
2012-11-20 8:46 ` NeilBrown
2012-11-20 8:52 ` Fengguang Wu [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=20121120085254.GA12104@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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