From: Al Viro <viro@ZenIV.linux.org.uk>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Sam Ravnborg <sam@ravnborg.org>, linux-kernel@vger.kernel.org
Subject: Re: new asm-offsets.h patch problems
Date: Mon, 12 Sep 2005 17:50:56 +0100 [thread overview]
Message-ID: <20050912165056.GM25261@ZenIV.linux.org.uk> (raw)
In-Reply-To: <B8E391BBE9FE384DAA4C5C003888BE6F045A9188@scsmsx401.amr.corp.intel.com>
On Mon, Sep 12, 2005 at 09:00:06AM -0700, Luck, Tony wrote:
> So I still don't understand what is really happening here.
>
> I left my build script running overnight ... working on a
> kernel at the 357d596bd... commit (where Linus merged in
> my tree last night). This one has your "archprepare" patch
> already included.
>
> Sometimes a build for a config succeeds, and sometimes it
> fails. (tiger_defconfig for the last six builds has had a
> GOOD, BAD, BAD, BAD, GOOD, GOOD sequence, while bigsur_defconfig
> went GOOD, BAD, BAD, BAD, BAD, BAD). This non-determinism
> doesn't fit in well with your explanation of missing defines
> for PAGE_SIZE etc.
There's more, apparently - I'm seeing
make # successful full build
make C=2 # triggering full rebuild, not just sparse run
next prev parent reply other threads:[~2005-09-12 16:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 16:00 new asm-offsets.h patch problems Luck, Tony
2005-09-12 16:50 ` Al Viro [this message]
2005-09-12 19:01 ` Sam Ravnborg
2005-09-12 18:59 ` Sam Ravnborg
2005-09-13 0:08 ` Peter Chubb
-- strict thread matches above, loose matches on Subject: below --
2005-09-13 0:14 Luck, Tony
2005-09-12 21:02 Luck, Tony
2005-09-12 23:17 ` Tony Luck
2005-09-11 21:48 Luck, Tony
2005-09-11 22:07 ` Sam Ravnborg
2005-09-11 20:39 Luck, Tony
2005-09-11 21:36 ` Sam Ravnborg
2005-09-11 14:54 Luck, Tony
2005-09-11 6:07 Luck, Tony
2005-09-11 7:45 ` Sam Ravnborg
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=20050912165056.GM25261@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=tony.luck@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 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.