From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: "Pihet-XID, Jean" <j-pihet@ti.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build failure after merge of the final tree (pm tree related)
Date: Fri, 19 Aug 2011 13:33:45 -0700 [thread overview]
Message-ID: <20110819133345.36349fc9.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110819233950.e526ac71ca862f45538b8721@canb.auug.org.au>
On Fri, 19 Aug 2011 23:39:50 +1000 Stephen Rothwell wrote:
> Hi,
>
> On Fri, 19 Aug 2011 10:14:11 +0200 "Pihet-XID, Jean" <j-pihet@ti.com> wrote:
> >
> > Well, it is not as easy as it seems. As the patch set describes, I am
> > build testing for x86 and OMAP. At the moment due to config
> > dependencies it is _impossible_ to disable PM in the OMAP config.
> >
> > Also I cannot build test every platform out there.
> > Do you have a procedure for build testing?
>
> I do not expect developers (or even maintainers) to build for every
> architecture/platform - that is partly what linux-next is for (see
> http://kisskb.ellerman.id.au/linux-next ). It is good to see you at
> least thought about the !PM case. Can't it be turned off in x86?
Sure it can. For mainline -rc and 3.x releases, I am trying to build
an almost-allmodconfig kernel (x86_64 only) with one major option
disabled. The $major option that is disabled is one of each of the
following:
BLOCK HOTPLUG INET INPUT MAGIC_SYSRQ NET PCI PM PROC_FS SMP SYSCTL SYSFS
There used to be several build errors for HOTPLUG or MAGIC_SYSRQ disabled,
but those aren't finding problems lately like they used to. I could probably
drop them.
> I am a bit sensitive about these sort of build errors as I see it happen
> way to often that a developer make a typo in the !CONFIG_XXX stubs.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-08-19 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 3:03 linux-next: build failure after merge of the final tree (pm tree related) Stephen Rothwell
2011-08-19 8:14 ` Pihet-XID, Jean
2011-08-19 13:39 ` Stephen Rothwell
2011-08-19 20:33 ` Randy Dunlap [this message]
2011-08-19 21:58 ` Rafael J. Wysocki
2011-08-20 7:50 ` Pihet-XID, Jean
2011-11-14 3:24 Stephen Rothwell
2011-11-14 23:12 ` Rafael J. Wysocki
2011-11-24 6:19 ` Stephen Rothwell
2011-11-24 6:32 ` Tejun Heo
2011-11-24 10:15 ` Rafael J. Wysocki
2011-12-22 5:28 Stephen Rothwell
2011-12-23 0:32 ` Rafael J. Wysocki
2012-10-24 3:44 Stephen Rothwell
2012-10-24 3:58 ` Song, Youquan
2012-10-24 21:40 ` Rafael J. Wysocki
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=20110819133345.36349fc9.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=j-pihet@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
/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).