linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Mariusz Kozlowski <m.kozlowski@tuxland.pl>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	kernel-testers@vger.kernel.org, linux-next@vger.kernel.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 27
Date: Sun, 29 Jun 2008 21:57:22 +0200	[thread overview]
Message-ID: <200806292157.22860.rjw@sisk.pl> (raw)
In-Reply-To: <200806292129.57465.m.kozlowski@tuxland.pl>

On Sunday, 29 of June 2008, Mariusz Kozlowski wrote:
> Hello,
> 
> It's too good. It survived hours of testing on 4 different arches. I stressed
> them with latest ltp, autotest, my own testing scripts and anything else
> I could think of. Good job :) The game is on.

Lucky you.

There are no less than three different patches in it that break sigle box for
me. :-(

Thanks,
Rafael

  reply	other threads:[~2008-06-29 19:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27  8:24 linux-next: Tree for June 27 Stephen Rothwell
2008-06-27 18:24 ` [BUILD-FAILURE] linux-next: Tree for June 27 - randconfig build fails with !CONFIG_XFS_POSIX_ACL Kamalesh Babulal
2008-06-28  1:05   ` Stephen Rothwell
2008-06-28 17:34     ` Kamalesh Babulal
2008-06-27 18:58 ` linux-next: Tree for June 27 - build fails at tc6393xb_attach_irq() with randconfig build Kamalesh Babulal
2008-06-30 13:44   ` Dmitry Baryshkov
     [not found] ` <20080627182406.a54b00c1.sfr-3FnU+UHB4dNDw9hX6IcOSA@public.gmane.org>
2008-06-29 19:29   ` linux-next: Tree for June 27 Mariusz Kozlowski
2008-06-29 19:57     ` Rafael J. Wysocki [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-06-27  6:16 Stephen Rothwell

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=200806292157.22860.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=m.kozlowski@tuxland.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).