From: Fengguang Wu <fengguang.wu@intel.com>
To: Stefan Behrens <sbehrens@giantdisaster.de>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: fs/btrfs/dev-replace.c:486:17: sparse: incompatible types in comparison expression (different address spaces)
Date: Thu, 8 Nov 2012 19:55:35 +0800 [thread overview]
Message-ID: <20121108115535.GB7277@localhost> (raw)
In-Reply-To: <509B98B9.1020509@giantdisaster.de>
> Hi Fengguang,
Hi Stefan!
> Assuming that your script performs a periodic git fetch and git reset,
> and then starts compile runs on different architectures, the only
> explanation that I have is that something went wrong with the git
> operation in your script. It looks like some C source files have been
> updated, but the header files are old. Some kind of inconsistency that
> either a git reset --hard should fix, or rm -rf . and git clone to start
> from the beginning.
>
> Could you check it please?
That's definitely good suggestion! I've added the check before each make
to make sure the tree is in a clean state:
git_check_reset()
{
[[ $(git --no-pager diff) ]] && {
notice "unexpected modified work tree"
dump_stack
git --no-pager diff
git reset --hard
}
}
> And could you please point me to some documentation, how this (very
> useful !) service from Intel is working?
Sure (and thanks!). Here is a nice article:
KS2012: Kernel build/boot testing
https://lwn.net/Articles/514278/
Thanks,
Fengguang
next prev parent reply other threads:[~2012-11-08 11:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <509b5327.UwD7JiNVjH75WdPI%yuanhan.liu@linux.intel.com>
2012-11-08 7:35 ` fs/btrfs/dev-replace.c:486:17: sparse: incompatible types in comparison expression (different address spaces) Fengguang Wu
2012-11-08 11:34 ` Stefan Behrens
2012-11-08 11:55 ` Fengguang Wu [this message]
2012-11-09 15:12 ` Stefan Behrens
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=20121108115535.GB7277@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=sbehrens@giantdisaster.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 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.