From: Dave Hansen <haveblue@us.ibm.com>
To: Jordan Crouse <jordan.crouse@amd.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
info-linux@ldcmail.amd.com
Subject: Re: [PATCH 1/5] AMD Geode GX/LX support V2
Date: Wed, 05 Oct 2005 09:59:08 -0700 [thread overview]
Message-ID: <1128531548.26009.37.camel@localhost> (raw)
In-Reply-To: <20051005165405.GB25189@cosmic.amd.com>
On Wed, 2005-10-05 at 10:54 -0600, Jordan Crouse wrote:
> +/* This function handles National Semiconductor branded processors */
> +
> +static void __init init_nsc(struct cpuinfo_x86 *c)
> +{
> + int r;
> +
> + /* There may be GX1 processors in the wild that are branded
> + * NSC and not Cyrix.
> + *
> + * This function only handles the GX processor, and kicks
> every
> + * thing else to the Cyrix init function above - that should
> + * cover any processors that might have been branded
> differently
> + * after NSC aquired Cyrix.
> + *
> + * If this breaks your GX1 horribly, please e-mail
> + * info-linux@ldcmail.amd.com to tell us.
> + */
> +
> + /* Handle the GX (Formally known as the GX2) */
> +
> + if ((c->x86 == 5) && (c->x86_model == 5)) {
> + r = get_model_name(c);
> + display_cacheinfo(c);
> + }
> + else
> + init_cyrix(c);
> +}
CodingStyle. Please keep the bracket and the else on the same line:
if {
foo();
} else
bar();
-- Dave
next prev parent reply other threads:[~2005-10-05 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-05 16:46 [PATCH 0/5] AMD Geode GX/LX support V2 Jordan Crouse
2005-10-05 16:54 ` [PATCH 1/5] " Jordan Crouse
2005-10-05 16:59 ` Dave Hansen [this message]
2005-10-05 18:29 ` Lennart Sorensen
2005-10-05 19:27 ` Jordan Crouse
2005-10-05 19:15 ` Lennart Sorensen
[not found] ` <LYRIS-4271-66233-2005.10.05-13.16.03--john.zulauf#amd.com@whitestar.amd.com>
2005-10-05 23:01 ` John Zulauf
2005-10-05 16:56 ` [PATCH 2/5] " Jordan Crouse
2005-10-05 16:57 ` [PATCH 3/5] " Jordan Crouse
2005-10-05 17:01 ` [PATCH 4/5] " Jordan Crouse
2005-10-05 17:02 ` [PATCH 5/5] " Jordan Crouse
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=1128531548.26009.37.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=info-linux@ldcmail.amd.com \
--cc=jordan.crouse@amd.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 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.