From: David Miller <davem@davemloft.net>
To: sfr@canb.auug.org.au
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: Linux 3.4-rc1
Date: Sun, 01 Apr 2012 15:19:37 -0400 (EDT) [thread overview]
Message-ID: <20120401.151937.436689731888432426.davem@davemloft.net> (raw)
In-Reply-To: <20120401220340.57df6c1fe19ffd7070bc552f@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Sun, 1 Apr 2012 22:03:40 +1000
> Well, we may have avoided some of that pain (or at least moved the pain
> out of your tree while you were merging everything else) by putting the
> system.h disintegration into linux-next for at least a day or two ...
I was really surprised this didn't soak in linux-next for a little
while first. All of those sparc build regressions, I can guarantee,
would have been sorted out completely before being merged to Linus.
next prev parent reply other threads:[~2012-04-01 19:21 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-31 23:58 Linux 3.4-rc1 Linus Torvalds
2012-04-01 0:09 ` Christoph Hellwig
2012-04-01 1:46 ` Shea Levy
2012-04-01 3:11 ` Linus Torvalds
2012-04-01 1:48 ` Shea Levy
2012-04-01 2:07 ` Shea Levy
2012-04-01 8:34 ` Ingo Molnar
2012-04-01 12:03 ` Stephen Rothwell
2012-04-01 19:19 ` David Miller [this message]
2012-04-01 13:14 ` linux-next stats (Was: Linux 3.4-rc1) Stephen Rothwell
2012-04-01 15:34 ` Linux 3.4-rc1 Rob Clark
2012-04-02 3:40 ` Kyungmin Park
2012-04-02 8:41 ` Daniel Vetter
2012-04-04 12:24 ` Subash Patel
2012-04-04 12:33 ` Anca Emanuel
2012-04-05 7:41 ` Marek Szyprowski
2012-04-02 12:31 ` Alex Deucher
2012-04-02 9:15 ` Artem Bityutskiy
2012-04-02 9:20 ` Shubhrajyoti Datta
2012-04-02 15:48 ` Linus Walleij
2012-04-02 20:30 ` Carlos Chinea
2012-04-03 2:57 ` Kyungmin Park
2012-04-03 3:57 ` Linus Torvalds
2012-04-03 6:29 ` Hiroshi Doyu
2012-04-03 9:07 ` Arnd Bergmann
2012-04-03 14:58 ` Jerome Glisse
2012-04-03 15:35 ` Arnd Bergmann
2012-04-03 19:26 ` Krishna Reddy
2012-04-04 12:10 ` Anca Emanuel
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=20120401.151937.436689731888432426.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--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;
as well as URLs for NNTP newsgroup(s).