mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Hanna Linder <hannal@us.ibm.com>
Cc: Patrick Mochel <mochel@osdl.org>,
	linux-kernel@vger.kernel.org, andmike@us.ibm.com
Subject: Re: [RFC] Device class rework [0/5]
Date: Wed, 23 Apr 2003 09:23:11 -0700	[thread overview]
Message-ID: <20030423162311.GB11175@kroah.com> (raw)
In-Reply-To: <41570000.1051114688@w-hlinder>

On Wed, Apr 23, 2003 at 09:18:08AM -0700, Hanna Linder wrote:
> --On Tuesday, April 22, 2003 06:54:54 PM -0700 Greg KH <greg@kroah.com> wrote:
> 
> >> I did a quick sanity test of these patches on a 2-way PIII.
> >> It built and booted fine for me. I don't have any devices that 
> >> span multiple classes but the patch hasnt changed any of my 
> >> existing /sys/class output.
> > 
> > Hm, are you sure you applied them and are using that kernel?  :)
> > 
> 
> Yes. I did apply the patches... Just not to the kernel I booted ;(
> 
> Here is the correct tree I see on my 2xPIII:
> 
> 
> /sys/class
> |-- cpu
> |   |-- cpu0
> |   |   `-- device -> ../../../devices/sys/cpu0
> |   `-- cpu1
> |       `-- device -> ../../../devices/sys/cpu1

Looks good.  That "foo" file in the example I posted was from an older
kernel version on one of my boxes.  This is the correct information.

Thanks for testing,

greg k-h

  reply	other threads:[~2003-04-23 16:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:55 Greg KH
2003-04-22 20:57 ` [RFC] Device class rework [1/5] Greg KH
2003-04-22 20:57   ` [RFC] Device class rework [2/5] Greg KH
2003-04-22 20:58     ` [RFC] Device class rework [3/5] Greg KH
2003-04-22 20:59       ` [RFC] Device class rework [4/5] Greg KH
2003-04-22 20:59         ` [RFC] Device class rework [5/5] Greg KH
2003-04-23  0:59 ` [RFC] Device class rework [0/5] Hanna Linder
2003-04-23  1:54   ` Greg KH
2003-04-23 16:18     ` Hanna Linder
2003-04-23 16:23       ` Greg KH [this message]
2003-04-23  7:54 Shaheed R. Haque
2003-04-23 16:00 ` Greg KH

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=20030423162311.GB11175@kroah.com \
    --to=greg@kroah.com \
    --cc=andmike@us.ibm.com \
    --cc=hannal@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@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

all inboxes | Powered by JetHome®