From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>,
hch@lst.de, linux-arch@vger.kernel.org
Subject: Re: + move-die-notifier-handling-to-common-code.patch added to -mm tree
Date: Fri, 23 Mar 2007 18:51:49 +0100 [thread overview]
Message-ID: <20070323175148.GA12158@lst.de> (raw)
In-Reply-To: <20070322100117.GC29627@flint.arm.linux.org.uk>
On Thu, Mar 22, 2007 at 10:01:17AM +0000, Russell King wrote:
> It seems that breaking ARM builds is all the rage; they've broken
> three times during this cycle due to peoples dumb untested patches,
> and with the restrictions Linus placed on my merging it's painful
> to keep resolving these issues one week or so after they happen.
I don't think Linus puts limits on your merging, you're just too
unfleible to send him the right patches. Secondary architectures
do get broken once in a while, and other maintainers can cope
with that just fine. That's of course not an excuse for this
breakage, as you might have notices I actually did steps to
prevent arm breakage and just got it wrong.
> Folk *need* to spend more time testing their work before submitting
> it upstream. Merely building the ARM defconfig would've found this
> error.
There is no arm defconfig. And the various board configs are totally
outdated aswell. I just tried to build five of them and all of them
haven;'t been updated for ages and need answering of a gazillion
questions during make oldconfig.
next prev parent reply other threads:[~2007-03-23 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 22:11 + move-die-notifier-handling-to-common-code.patch added to -mm tree akpm
2007-03-21 22:17 ` Russell King
2007-03-21 22:59 ` Andrew Morton
2007-03-22 10:01 ` Russell King
2007-03-23 17:51 ` Christoph Hellwig [this message]
2007-03-23 17:52 ` Christoph Hellwig
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=20070323175148.GA12158@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox