From: Andrew Morton <akpm@linux-foundation.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: cooloney@kernel.org, torvalds@linux-foundation.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
magnus.damm@gmail.com, damm@igel.co.jp, lethal@linux-sh.org,
nico@cam.org, vapier.adi@gmail.com
Subject: Re: Blackfin STAMP537 compiling error in 2.6.25-rc8
Date: Mon, 7 Apr 2008 15:28:00 -0700 [thread overview]
Message-ID: <20080407152800.1a8e37fc.akpm@linux-foundation.org> (raw)
In-Reply-To: <47FA813D.6090505@garzik.org>
On Mon, 07 Apr 2008 16:17:01 -0400
Jeff Garzik <jeff@garzik.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.
next prev parent reply other threads:[~2008-04-07 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-07 7:57 Blackfin STAMP537 compiling error in 2.6.25-rc8 Bryan Wu
2008-04-07 8:13 ` Jeff Garzik
2008-04-07 8:15 ` Bryan Wu
2008-04-07 20:17 ` Jeff Garzik
2008-04-07 22:28 ` Andrew Morton [this message]
2008-04-08 2:08 ` Bryan Wu
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=20080407152800.1a8e37fc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cooloney@kernel.org \
--cc=damm@igel.co.jp \
--cc=davem@davemloft.net \
--cc=jeff@garzik.org \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=nico@cam.org \
--cc=torvalds@linux-foundation.org \
--cc=vapier.adi@gmail.com \
/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