[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080407152800.1a8e37fc.akpm@linux-foundation.org>
Date: Mon, 7 Apr 2008 15:28:00 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Jeff Garzik <jeff@...zik.org>
Cc: cooloney@...nel.org, torvalds@...ux-foundation.org,
davem@...emloft.net, linux-kernel@...r.kernel.org,
magnus.damm@...il.com, damm@...l.co.jp, lethal@...ux-sh.org,
nico@....org, vapier.adi@...il.com
Subject: Re: Blackfin STAMP537 compiling error in 2.6.25-rc8
On Mon, 07 Apr 2008 16:17:01 -0400
Jeff Garzik <jeff@...zik.org> wrote:
> Since it was an arch patch to a driver I cannot build, I made the
> [mistaken] assumption that your sending it to me was an indication that
> it should actually be merged :) Especially with a subject like "fix
> build breakage", for a platform I cannot easily build...
>
> Are there any process tweaks that could be made here? Maybe -mm stuff
> sent to maintainers could be tagged, noting dependencies on other -mm
> patches that are not yet upstream?
Well. It really helps if submitters tell us that a patch fixes another
pending patch, and which one that is. Usually Ihave to ask if I can't work
it out.
But if a) we weren't told that and b) I have no reason to think it's not a
mainline problem and c) the patch applies to mainline and d) the patch
affects an architecture which I'm not cross-compiling for, it's going to
sneak through.
Fortunately, a && b && c && d doesn't happen at all often.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists