From: Ralf Baechle <ralf@linux-mips.org>
To: David Daney <ddaney@caviumnetworks.com>
Cc: Robert Millan <rmh@gnu.org>,
Aurelien Jarno <aurelien@aurel32.net>,
linux-mips@linux-mips.org
Subject: Re: [PATCH] Enable AT_PLATFORM for Loongson 2F CPU
Date: Thu, 4 Nov 2010 19:29:43 +0000 [thread overview]
Message-ID: <20101104192943.GA28245@linux-mips.org> (raw)
In-Reply-To: <4CD30551.1000006@caviumnetworks.com>
On Thu, Nov 04, 2010 at 12:11:13PM -0700, David Daney wrote:
> >Well I appreciate consistency with GCC flag names, so I'd rather keep
> >the dash, but then again it's not my decision to make. In any case,
> >whoever commits this can adjust the name to his/her liking.
>
> I don't like to put words into Ralf's mouth, but it is easier to
> work with patches that have been tested and are ready to go, rather
> than having to re-write everything.
Indeed. I modify lots of patches that I can't test on my hardware
collection so any change I have to do also increases of me adding bugs.
Heck, I do most of my builds on fairly modest dual core machines so I
can't even afford test builds which is how occasionally the most stupid
errors end up getting committed.
Which is why I'm increasingly asking people to do trivial changes to
patches, not because I'm lazy.
> Some of the strings in use are "i686", "x86_64", "octeon",
> "octeon2", "PARISC", "PARISC32", tilegx-m32", "v4l", "v3l", "v4b",
> and "v3b", these last for for ARM and they don't match the GCC
> -mcpu= values.
>
> So I guess what ever you want.
It's probably reasonable if the names don't diverge too far from each
other. Then again with the number of cpu type synonyms accepted by gcc
that may just be wishful thinking.
Ralf
next prev parent reply other threads:[~2010-11-04 19:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 12:18 [PATCH] Enable AT_PLATFORM for Loongson 2F CPU Robert Millan
2010-11-04 16:44 ` David Daney
2010-11-04 17:33 ` Aurelien Jarno
2010-11-04 18:43 ` Robert Millan
2010-11-04 19:11 ` David Daney
2010-11-04 19:29 ` Ralf Baechle [this message]
2010-11-07 12:30 ` Robert Millan
2010-11-08 19:13 ` David Daney
2010-11-08 22:27 ` Robert Millan
2010-11-08 22:50 ` David Daney
2010-11-08 23:02 ` Robert Millan
2010-11-09 9:48 ` wu zhangjin
2010-11-09 12:24 ` Robert Millan
2010-11-09 15:40 ` Ralf Baechle
2010-11-11 14:47 ` Robert Millan
2010-11-15 23:50 ` Robert Millan
2010-11-15 23:59 ` David Daney
2010-11-22 12:44 ` Robert Millan
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=20101104192943.GA28245@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=aurelien@aurel32.net \
--cc=ddaney@caviumnetworks.com \
--cc=linux-mips@linux-mips.org \
--cc=rmh@gnu.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.