From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: "Gross, Mark" <mark.gross@intel.com>
Cc: minyard@acm.org, alan@lxorguk.ukuu.org.uk,
bluesmoke-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, steven.carbonari@intel.com,
soo.keong.ong@intel.com, zhenyu.z.wang@intel.com
Subject: Re: Problems with EDAC coexisting with BIOS
Date: Tue, 25 Apr 2006 19:34:05 -0700 [thread overview]
Message-ID: <20060425193405.0ee50691.rdunlap@xenotime.net> (raw)
In-Reply-To: <5389061B65D50446B1783B97DFDB392DA97BD0@orsmsx411.amr.corp.intel.com>
On Tue, 25 Apr 2006 16:25:59 -0700 Gross, Mark wrote:
>
> How about printing nothing like it used too?
>
> See attached.
>
> Signed-off-by: Mark Gross
Hi Mark,
This small patch will need some cleaning up:
1. Signed-off-by: Mark Gross <mark.gross@intel.com>
2. Try not to use attachments. If you must, then make the attachment
type be text instead of octet-stream.
3. No need to init to 0:
+static int force_function_unhide = 0;
4. Typos:
+ /* check to see if device 0 function 1 is enbaled if it isn't we
enabled; it it isn't, we
+ * assume the BIOS has reserved it for a reason and is expecting
+ * exclusive access, we take care to not violate that assumption and
not to violate
+ * fail the probe. */
5. indentation, typos, and at least one trailing space:
+ if (!force_function_unhide && !(stat8 & (1 << 5))) {
+ printk(KERN_INFO "contact your bios vendor to see if the "
Contact your BIOS
+ "E752x error registers can be safely un-hidden\n");
^indent one more tab
---
~Randy
next prev parent reply other threads:[~2006-04-26 2:31 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 23:25 Gross, Mark
2006-04-26 2:19 ` Corey Minyard
2006-04-26 2:34 ` Randy.Dunlap [this message]
2006-04-26 18:26 ` mark gross
2006-04-26 18:38 ` Randy.Dunlap
2006-04-26 19:39 ` mark gross
2006-04-26 20:17 ` Randy.Dunlap
-- strict thread matches above, loose matches on Subject: below --
2006-05-04 16:44 David Peterson
2006-05-03 23:06 David Peterson
2006-05-03 22:22 Doug Thompson
2006-05-03 21:39 Doug Thompson
2006-05-03 20:49 Gross, Mark
2006-04-26 3:24 Gross, Mark
2006-04-26 3:19 Gross, Mark
2006-04-25 21:24 Gross, Mark
2006-04-25 22:39 ` Corey Minyard
2006-04-25 20:22 Gross, Mark
2006-04-25 18:19 Gross, Mark
2006-04-25 19:55 ` Corey Minyard
2006-04-24 18:14 Gross, Mark
2006-04-24 15:57 Gross, Mark
2006-04-24 17:08 ` Eric W. Biederman
2006-04-24 17:49 ` Alan Cox
2006-04-24 14:32 Ong, Soo Keong
2006-04-24 14:15 Ong, Soo Keong
2006-04-24 14:29 ` Alan Cox
2006-05-03 20:25 ` Tim Small
2006-05-03 20:37 ` thockin
2006-05-04 9:45 ` Tim Small
2006-05-03 21:44 ` Alan Cox
2006-05-04 9:02 ` Tim Small
2006-04-24 13:59 Ong, Soo Keong
2006-04-24 14:13 ` Alan Cox
2006-04-23 1:44 Gross, Mark
2006-04-21 22:36 Doug Thompson
2006-04-21 22:20 Gross, Mark
2006-04-22 18:31 ` Tim Small
2006-04-21 21:42 Doug Thompson
2006-04-21 21:32 Gross, Mark
2006-04-21 20:57 Doug Thompson
2006-04-21 16:01 Gross, Mark
2006-04-21 21:13 ` Ingo Oeser
2006-04-24 13:19 ` Alan Cox
2006-04-24 17:38 ` Doug Thompson
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=20060425193405.0ee50691.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bluesmoke-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.gross@intel.com \
--cc=minyard@acm.org \
--cc=soo.keong.ong@intel.com \
--cc=steven.carbonari@intel.com \
--cc=zhenyu.z.wang@intel.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
all inboxes | Powered by JetHome®