From: Andy Whitcroft <apw@shadowen.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 6
Date: Thu, 6 Mar 2008 09:07:43 +0000 [thread overview]
Message-ID: <20080306090734.GJ17931@shadowen.org> (raw)
In-Reply-To: <20080306162606.970aefe1.sfr@canb.auug.org.au>
On Thu, Mar 06, 2008 at 04:26:06PM +1100, Stephen Rothwell wrote:
> There were a few merge conflicts (trivial) and one build break. I have
> notified the appropriate people.
I presume that when you report a build break here that this was something
you fixed and we should not see in the tree you released. By which I mean,
if any of our builds fail that is not expected and worth reporting.
-apw
next prev parent reply other threads:[~2008-03-06 9:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 5:26 linux-next: Tree for March 6 Stephen Rothwell
2008-03-06 9:07 ` Andy Whitcroft [this message]
2008-03-06 11:50 ` Stephen Rothwell
2008-03-07 2:10 ` Stephen Rothwell
2008-03-06 9:18 ` [BUILD_FAILURE] linux-next: Tree for March 6 drivers/usb broken Kamalesh Babulal
2008-03-06 12:10 ` Stephen Rothwell
2008-03-06 13:35 ` [BUILD_FAILURE] linux-next: Tree for March 6 build failure Kamalesh Babulal
2008-03-06 19:12 ` David Miller
2008-03-07 7:44 ` Kamalesh Babulal
2008-03-07 19:12 ` David Miller
2008-03-09 8:39 ` linux-next: Tree for March 6: acpi_os_wait_semaphore tries to register non-static key Laurent Riffard
2008-03-09 8:39 ` Laurent Riffard
-- strict thread matches above, loose matches on Subject: below --
2009-03-06 8:13 linux-next: Tree for March 6 Stephen Rothwell
2009-03-06 19:24 ` Andrew Morton
2009-03-10 5:47 ` 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=20080306090734.GJ17931@shadowen.org \
--to=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.