From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: build logs for -mm
Date: Fri, 01 Apr 2005 09:01:30 -0800 [thread overview]
Message-ID: <424D7E6A.3020608@osdl.org> (raw)
In-Reply-To: <E1DHJLZ-00039U-00@dorka.pomaz.szeredi.hu>
Miklos Szeredi wrote:
>>>do I believe correctly that you do automatic builds of -mm for lots of
>>>architectures? If yes, is there some place where the output is
>>>available? This would be useful for fixing warnings.
>>
>>The OSDL PLM tool also does automated builds of all -linus
>>and -mm releases. 2.6.12-rc1-mm4 results are here:
>>
>>http://www.osdl.org/plm-cgi/plm?module=patch_info&patch_id=4352
>
>
> Thanks. I see that for most architectures this only builds a
> defconfig kernel, which is not useful for projects not included in
> defconfig.
>
> Would it be too much load for the server to handle a full config for
> all archs?
I'm asking about that (I don't do the PLM builds).
--
~Randy
prev parent reply other threads:[~2005-04-01 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-31 21:35 build logs for -mm Miklos Szeredi
2005-03-31 21:48 ` Randy.Dunlap
2005-04-01 10:25 ` Miklos Szeredi
2005-04-01 17:01 ` Randy.Dunlap [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=424D7E6A.3020608@osdl.org \
--to=rddunlap@osdl.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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