From: Dan Kegel <dkegel@ixiacom.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [Bug 791] New: motorola sandpoint code does not compile
Date: Mon, 09 Jun 2003 13:31:33 -0700 [thread overview]
Message-ID: <3EE4EEA5.60106@ixiacom.com> (raw)
Tom Rini wrote:
> The Motorola Sandpoint code (along with many other MPC107 based
> platforms) is out of date in 2.5. Is there a way to close this bug and
> have it reflect that?
Sure -- just change the name of the bug to "2.5 tree out of date
with respect to MPC107 platforms" and add a comment saying
where the up to date code is that needs to be merged in.
Then leave it open to reflect the fact that the vger tree
is out of date for these platforms.
Isn't this an example of the eternal struggle between the vger tree and
the trees maintained by the ppc, arm, and SH teams? I don't
have any idea how far apart the trees are at the moment,
but I use x86, ppc, and SH at work, and would like to
use the same kernel tree for all three, so this is a bit
of a sore point for me.
- Dan
next prev reply other threads:[~2003-06-09 20:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 14:38 [Bug 791] New: motorola sandpoint code does not compile Martin J. Bligh
2003-06-09 15:20 ` Tom Rini
2003-06-09 20:31 ` Dan Kegel [this message]
2003-06-10 16:00 ` Tom Rini
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=3EE4EEA5.60106@ixiacom.com \
--to=dkegel@ixiacom.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox