From: Ralf Baechle <ralf@linux-mips.org>
To: Martin Michlmayr <tbm@cyrius.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [MIPS] Separate CPU entries in /proc/cpuinfo with a blank line
Date: Mon, 20 Mar 2006 13:28:20 +0000 [thread overview]
Message-ID: <20060320132820.GA11139@linux-mips.org> (raw)
In-Reply-To: <20060320025120.GA18414@deprecation.cyrius.com>
On Mon, Mar 20, 2006 at 02:51:20AM +0000, Martin Michlmayr wrote:
> Put in a blank line between CPU entries in /proc/cpuinfo, just like
> most other architectures (i386, ia64, x86_64) do.
Thanks, applied.
In the past I frequently used to reply to the mailing lists when applying
a patch. Since I resurrected the commits mailing lists I do no longer do
this. Just so people know.
Ralf
prev parent reply other threads:[~2006-03-20 13:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 2:51 [MIPS] Separate CPU entries in /proc/cpuinfo with a blank line Martin Michlmayr
2006-03-20 13:28 ` Ralf Baechle [this message]
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=20060320132820.GA11139@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=tbm@cyrius.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox