From: Ralf Baechle <ralf@linux-mips.org>
To: Andrew Sharp <tigerand@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 2/5] mips: PMC MSP71xx mips common
Date: Wed, 28 Feb 2007 19:42:51 +0000 [thread overview]
Message-ID: <20070228194251.GC16562@linux-mips.org> (raw)
In-Reply-To: <20070227184555.GA32425@onstor.com>
On Tue, Feb 27, 2007 at 10:46:01AM -0800, Andrew Sharp wrote:
> Experience. ~:^) You never know when a little extra room for expansion
> might come in handy. For example, let's say next year you release a
> quad-core SOC (hint-hint), and a line of eval boards. You would have
> room to put them in the file next to your other boards. But just a
> suggestion.
Since mips_machtype and mips_machgroup are mostly used to identify systems
within Linux changing would not be the most terrible thing on earth.
There is no requirement for these numbers to be contiguous either.
Ralf
next prev parent reply other threads:[~2007-02-28 19:42 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-27 17:09 [PATCH 2/5] mips: PMC MSP71xx mips common Marc St-Jean
2007-02-27 17:38 ` Thiemo Seufer
2007-02-28 19:32 ` Ralf Baechle
2007-02-27 18:46 ` Andrew Sharp
2007-02-28 19:42 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-03-16 23:53 Marc St-Jean
2007-03-17 0:46 ` Ralf Baechle
2007-03-07 18:01 Marc St-Jean
2007-03-16 1:58 ` Ralf Baechle
2007-03-01 20:41 Marc St-Jean
2007-02-28 22:35 Marc St-Jean
2007-02-28 21:35 Marc St-Jean
2007-02-28 21:43 ` Uhler, Mike
2007-02-28 21:43 ` Uhler, Mike
2007-02-28 22:18 ` Ralf Baechle
2007-02-28 0:04 Marc St-Jean
2007-02-27 21:27 Marc St-Jean
2007-02-28 19:52 ` Ralf Baechle
2007-02-27 17:59 Marc St-Jean
2007-02-27 20:03 ` Thiemo Seufer
2007-02-27 0:12 Marc St-Jean
2007-02-27 0:43 ` Andrew Sharp
2007-02-23 21:27 Marc St-Jean
2007-02-23 21:15 Marc St-Jean
2007-02-23 20:53 Marc St-Jean
2007-02-23 21:02 ` Sergei Shtylyov
2007-02-23 21:02 ` David Daney
2007-02-23 19:56 Marc St-Jean
2007-02-23 20:35 ` Sergei Shtylyov
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=20070228194251.GC16562@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=tigerand@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 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.