From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Greg KH <greg@kroah.com>,
Valdis.Kletnieks@vt.edu, Anton Blanchard <anton@samba.org>,
linux-kernel@vger.kernel.org
Subject: Re: mmotm 2010-09-22 - build error in drivers/staging/zram
Date: Thu, 23 Sep 2010 16:04:23 +1000 [thread overview]
Message-ID: <20100923160423.06c5bf34.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100922212653.6f55104c.akpm@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
Hi Andrew,
On Wed, 22 Sep 2010 21:26:53 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> ooh, intentional dumbness!
:-)
> What was the reasoning?
It was done when the staging stuff was added to linux-next - otherwise my
builds (and many others) would fail most of the time (it may be better
now, but at the beginning, there was a lot of mess in staging).
The reasoning is that build failures in staging should in no way hold up
the rest of our development.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2010-09-23 6:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 23:12 mmotm 2010-09-22-16-11 uploaded akpm
2010-09-23 3:26 ` mmotm 2010-09-22 - build error in drivers/staging/zram Valdis.Kletnieks
2010-09-23 3:43 ` Andrew Morton
2010-09-23 4:21 ` Greg KH
2010-09-23 4:26 ` Andrew Morton
2010-09-23 6:04 ` Stephen Rothwell [this message]
2010-09-23 17:29 ` Randy Dunlap
2010-09-23 17:51 ` mmotm 2010-09-22-16-11 uploaded (staging/spectra) Randy Dunlap
2010-09-27 9:34 ` i915 flickering [was: mmotm 2010-09-22-16-11 uploaded] Jiri Slaby
2010-09-27 15:25 ` Jiri Slaby
2010-09-27 9:36 ` i915: glxgears causes GPU hang " Jiri Slaby
2010-09-27 9:51 ` Chris Wilson
2010-09-29 8:33 ` Jiri Slaby
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=20100923160423.06c5bf34.sfr@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=anton@samba.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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 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.