mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: Build regressions/improvements in v2.6.37-rc2
Date: Thu, 18 Nov 2010 23:28:26 +1100	[thread overview]
Message-ID: <1290083306.22575.12.camel@concordia> (raw)
In-Reply-To: <AANLkTi=NTGOv+EF_y=__=+P1ud7vqjvoaELPNi6ZhqbE@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

On Wed, 2010-11-17 at 20:32 +0100, Geert Uytterhoeven wrote:
> On Wed, Nov 17, 2010 at 20:28, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> > Below is the list of build error/warning regressions/improvements in
> > v2.6.37-rc2[1] compared to v2.6.36[2].
> 
> > Thanks to the linux-next team for providing the build service.
> >
> > [1] http://kisskb.ellerman.id.au/kisskb/head/3363/ (97 out of 108 configs)
> > [2] http://kisskb.ellerman.id.au/kisskb/head/3461/ (75 out of 108 configs)
> 
> Would it be possible to make sure tagged versions are always built for
> all 108 configs?
> Currently the coverage depends on how soon Linus pushes a new commit.

Hmm. Not in a five minute hack no. I'll think about it though.

cheers


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-11-18 12:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-17 19:28 Geert Uytterhoeven
2010-11-17 19:32 ` Geert Uytterhoeven
2010-11-18 12:28   ` Michael Ellerman [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=1290083306.22575.12.camel@concordia \
    --to=michael@ellerman.id.au \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --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

all inboxes | Powered by JetHome®