From: Andrew Morton <akpm@osdl.org>
To: "Luke Yang" <luke.adi@gmail.com>
Cc: rgetz@blackfin.uclinux.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2]Blackfin archtecture patche for 2.6.16
Date: Tue, 21 Mar 2006 23:49:35 -0800 [thread overview]
Message-ID: <20060321234935.1d006a13.akpm@osdl.org> (raw)
In-Reply-To: <489ecd0c0603212342w4124dddfy1bb50c02984c0e8f@mail.gmail.com>
"Luke Yang" <luke.adi@gmail.com> wrote:
>
> > More things might come out once people start paying more attention, but if
> > that's the extent of things, I'd be OK with a merge when you're ready.
> Does this merge has to be within 1 week after the release, so we
> have to wait for 2.6.17? Or this can be done on mm-tree?
The whole patch affects just one line in one Kconfig file outside
arch/bluefin, so I don't see a reason why this needs to be tied into the
two-week-window thing. I figure that if we can get it into -mm within a
few weeks we'll be OK for 2.6.17.
But that depends upon review comments. My ten-minute-peek was not
sufficient. But given this discussion and its probably appearance in -mm,
I'd expect a few more people will get in there and help.
We'll see how it goes.
next prev parent reply other threads:[~2006-03-22 7:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-22 6:12 [PATCH 1/2]Blackfin archtecture patche for 2.6.16 Robin Getz
2006-03-22 6:36 ` Andrew Morton
2006-03-22 7:42 ` Luke Yang
2006-03-22 7:49 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-20 10:00 Luke Yang
2006-03-21 7:30 ` Luke Yang
2006-03-21 11:14 ` Andrew Morton
2006-03-21 23:45 ` Bernd Schmidt
2006-03-22 0:32 ` Andrew Morton
2006-03-22 3:45 ` Luke Yang
[not found] ` <20060321194848.4d041ab5.akpm@osdl.org>
2006-03-22 4:47 ` Luke Yang
2006-03-22 23:43 ` Ingo Oeser
2006-03-23 7:20 ` Luke Yang
2006-03-23 10:21 ` Philippe Gerum
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=20060321234935.1d006a13.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luke.adi@gmail.com \
--cc=rgetz@blackfin.uclinux.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.