From: Ralf Baechle <ralf@linux-mips.org>
To: Johannes Dickgreber <tanzy@gmx.de>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 2/2] show_cpuinfo prints the name of the calling CPU, which i think is wrong.
Date: Mon, 13 Oct 2008 23:21:46 +0100 [thread overview]
Message-ID: <20081013222146.GD8145@linux-mips.org> (raw)
In-Reply-To: <1223919381-24521-1-git-send-email-tanzy@gmx.de>
On Mon, Oct 13, 2008 at 07:36:21PM +0200, Johannes Dickgreber wrote:
> Cc: linux-mips@linux-mips.org
> Subject: [PATCH 2/2] show_cpuinfo prints the name of the calling CPU, which i
> think is wrong.
Patch is correct and so I applied it. Not a big issue though. There is
only one system supported currently that supports a mix of different
processor types (IP27) and those are very similar so it doesn't cause
pain.
Ralf
next prev parent reply other threads:[~2008-10-13 22:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 17:36 [PATCH 2/2] show_cpuinfo prints the name of the calling CPU, which i think is wrong Johannes Dickgreber
2008-10-13 22:21 ` Ralf Baechle [this message]
2008-10-13 23:34 ` David Daney
2008-10-14 8:36 ` Ralf Baechle
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=20081013222146.GD8145@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=tanzy@gmx.de \
/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.