From: Greg KH <greg@kroah.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Dave Peterson <dsp@llnl.gov>,
"Randy.Dunlap" <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, torvalds@osdl.org, alan@redhat.com
Subject: Re: [PATCH] EDAC: core EDAC support code
Date: Tue, 7 Mar 2006 11:05:49 -0800 [thread overview]
Message-ID: <20060307190549.GA18944@kroah.com> (raw)
In-Reply-To: <1141758219.3048.10.camel@laptopd505.fenrus.org>
On Tue, Mar 07, 2006 at 08:03:38PM +0100, Arjan van de Ven wrote:
>
> > I was initially a bit confused because I thought the comment
> > specifically pertained to the piece of code shown above. I need to
> > take a closer look at the EDAC sysfs code - I'm not as familiar with
> > some of its details as I should be. Thanks for pointing out the
> > issue.
>
> afaics it is a list of pci devices. these should just be symlinks to the
> sysfs resource of these pci devices instead, not a flat table file.
Ugh, all this talk is making me wonder what in the world this code is
doing. Time to go look at it...
And people complain that all interfaces in userspace should be instantly
marked "stable" because we all know exactly what we are doing :)
greg k-h
next prev parent reply other threads:[~2006-03-07 19:06 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200601190414.k0J4EZCV021775@hera.kernel.org>
2006-03-05 10:18 ` [PATCH] EDAC: core EDAC support code Arjan van de Ven
2006-03-05 10:30 ` Arjan van de Ven
2006-03-06 18:14 ` Dave Peterson
2006-03-06 18:22 ` Randy.Dunlap
2006-03-07 17:03 ` Dave Peterson
2006-03-07 17:20 ` Greg KH
2006-03-08 0:29 ` Dave Peterson
2006-03-07 19:03 ` Arjan van de Ven
2006-03-07 19:05 ` Greg KH [this message]
2006-03-09 23:51 ` Dave Peterson
2006-03-10 0:02 ` Greg KH
2006-03-10 1:46 ` Dave Peterson
2006-03-10 7:36 ` Arjan van de Ven
2006-03-10 11:06 ` Tim Small
2006-03-10 11:40 ` Arjan van de Ven
2006-03-10 17:46 ` Dave Peterson
2006-03-10 17:58 ` Arjan van de Ven
2006-03-10 19:07 ` Dave Peterson
2006-03-10 19:33 ` Arjan van de Ven
2006-03-10 21:13 ` Dave Peterson
2006-03-10 21:23 ` Arjan van de Ven
2006-03-11 1:57 ` Dave Peterson
2006-03-11 7:18 ` Arjan van de Ven
2006-03-13 19:31 ` Dave Peterson
2006-03-06 19:52 ` Greg KH
2006-03-05 15:55 ` Greg KH
2006-03-05 16:24 ` Arjan van de Ven
2006-03-06 18:52 ` Dave Peterson
2006-03-06 19:53 ` Greg KH
2006-03-06 21:01 ` Dave Peterson
2006-03-06 21:07 ` Arjan van de Ven
2006-03-09 3:19 ` Dave Peterson
2006-03-09 3:44 ` Al Viro
2006-03-09 5:51 ` Greg KH
2006-03-06 21:32 ` Al Viro
2006-03-06 21:53 ` Greg KH
2006-03-06 22:24 ` Al Viro
2006-03-06 22:55 ` Greg KH
2006-03-07 10:41 ` Andrew Morton
2006-03-07 11:08 ` Al Viro
2006-03-08 2:46 ` Rusty Russell
2006-03-07 1:45 ` Dmitry Torokhov
2006-03-07 1:57 ` Greg KH
2006-03-07 2:10 ` Dmitry Torokhov
2006-03-07 16:47 ` Dave Peterson
2006-03-07 17:04 ` Greg KH
2006-03-07 17:06 ` Dave Peterson
2006-03-08 1:03 ` Dmitry Torokhov
2006-03-08 1:33 ` Greg KH
2006-03-10 0:44 Doug Thompson
-- strict thread matches above, loose matches on Subject: below --
2006-03-10 16:56 Doug Thompson
2006-03-10 17:11 ` Arjan van de Ven
2006-03-10 17:28 Doug Thompson
2006-03-10 20:37 Doug Thompson
2006-03-11 17:04 Doug Thompson
2006-03-13 19:35 ` Dave Peterson
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=20060307190549.GA18944@kroah.com \
--to=greg@kroah.com \
--cc=alan@redhat.com \
--cc=arjan@infradead.org \
--cc=dsp@llnl.gov \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox