From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: richard -rw- weinberger <richard.weinberger@gmail.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
benh@kernel.crashing.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, hughd@google.com,
akpm@linux-foundation.org, dave@linux.vnet.ibm.com,
kamezawa.hiroyu@jp.fujitsu.com
Subject: Re: [PATCH] mm: don't access vm_flags as 'int'
Date: Fri, 27 May 2011 08:08:26 +0200 [thread overview]
Message-ID: <20110527060826.GA9260@elte.hu> (raw)
In-Reply-To: <BANLkTin3vHzUu-p654jvkG4R1Td261b3Aw@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Thu, May 26, 2011 at 11:50 AM, richard -rw- weinberger
> <richard.weinberger@gmail.com> wrote:
> >
> > This breaks kernel builds with CONFIG_HUGETLBFS=n. :-(
>
> Grr. I did the "allyesconfig" build to find any problems, but that
> obviously also sets HUGETLBFS.
>
> But "allnoconfig" does find this.
Yeah, my experience is that [all[yes|no|mod]|def]config covers about
95% of the build bugs and the remaining 5% are rarely showstopper
problems (they generally don't show up in configs that people use).
Given how fast allnoconfig and defconfig builds i've got allnoconfig
and defconfig scripted to always execute together with allyesconfig.
So if you go the trouble to build allyesconfig manually, it costs
almost no time to tack on the allnoconfig and defconfig as well (and
stick this all into a script), while it increases the efficiency of
the build test remarkably.
Thanks,
Ingo
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2011-05-27 6:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 10:16 [PATCH] mm: don't access vm_flags as 'int' KOSAKI Motohiro
2011-05-26 17:53 ` Linus Torvalds
2011-05-26 18:44 ` Alexey Dobriyan
2011-05-26 18:49 ` Linus Torvalds
2011-05-26 18:50 ` richard -rw- weinberger
2011-05-26 19:01 ` Linus Torvalds
2011-05-27 6:08 ` Ingo Molnar [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=20110527060826.GA9260@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weinberger@gmail.com \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).