public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Denys Vlasenko <vda.linux@googlemail.com>
To: Jan Dittmer <jdi@l4x.org>
Cc: Jeff Garzik <jeff@garzik.org>, Jens Axboe <jens.axboe@oracle.com>,
	Ingo Molnar <mingo@elte.hu>,
	linux-kernel@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mark Lord <lkml@rtr.ca>
Subject: Re: libata crash
Date: Fri, 19 Oct 2007 11:12:39 +0100	[thread overview]
Message-ID: <200710191112.39515.vda.linux@googlemail.com> (raw)
In-Reply-To: <47185722.8020606@l4x.org>

On Friday 19 October 2007 08:05, Jan Dittmer wrote:
> Jeff Garzik wrote:
> > Building on x86-64, I'm betting?  :)
> > 
> > I fell victim to the same thing a few days ago, missing some compile 
> > breakage that only appeared with
> > 
> >     make ARCH=i386 allmodconfig && make ARCH=i386 -sj9
> > 
> > Though am I alone in dreaming of a kernel.org service that would permit 
> > all-arch build testing of a git URL?
> 
> I could add that to the service at http://l4x.org/k/ if there is
> sufficient (>1) interest.

Wow.

When you click on Ok/Fail, you get a build log. One part of it
(make oldconfig output) is not usable much, verbatim .config would be more useful.

But this is a minor nitpicking. Overall looks awesome.
--
vda

  reply	other threads:[~2007-10-19 10:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071018164745.GD10674@kernel.dk>
2007-10-18 19:28 ` libata crash Ingo Molnar
2007-10-18 19:32   ` Jens Axboe
2007-10-18 19:59     ` Ingo Molnar
2007-10-18 20:41       ` Jens Axboe
2007-10-18 20:52         ` Jeff Garzik
2007-10-19  7:05           ` Jan Dittmer
2007-10-19 10:12             ` Denys Vlasenko [this message]
2007-10-19  6:48         ` Ingo Molnar

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=200710191112.39515.vda.linux@googlemail.com \
    --to=vda.linux@googlemail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=davem@davemloft.net \
    --cc=jdi@l4x.org \
    --cc=jeff@garzik.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@rtr.ca \
    --cc=mingo@elte.hu \
    --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