From: Greg KH <greg@kroah.com>
To: tvrtko.ursulin@sophos.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] ndevfs - a "nano" devfs
Date: Fri, 24 Jun 2005 08:23:11 -0700 [thread overview]
Message-ID: <20050624152311.GB29955@kroah.com> (raw)
In-Reply-To: <OF831AC472.851744FE-ON8025702A.004A57EC-8025702A.004B5AE9@sophos.com>
On Fri, Jun 24, 2005 at 02:43:04PM +0100, tvrtko.ursulin@sophos.com wrote:
> On 24/06/2005 09:18:08 linux-kernel-owner wrote:
>
> >Now I just know I'm going to regret this somehow...
>
> You got that right! ;)
>
> >Comments? Questions? Criticisms?
>
> It's cool and small. I like it, and I agree with Michael policy vs. policy
> analisys.
Thanks.
> I applied it to 2.6.12 (of course some manual intervention was needed) and
> are you curious about what happened next? Below are the relevant logs and
> outputs. As you can see, some of them are not working as expected.
Yeah, 2.6.12-git5 was what it was against, sorry I didn't mention that.
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI: Probing PCI hardware (bus 00)
> ndevfs: creating file '0000:00' with major 0 and minor 0
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
> ndevfs: creating file '0000:01' with major 0 and minor 0
> Boot video device is 0000:01:00.0
> ndevfs: creating file '0000:02' with major 0 and minor 0
Hm, that is odd. That shouldn't happen.
Wait, I think it was due to where you put the class hooks, try it
against Linus's latest tree, it will work better there (in fact, I don't
know if it would work properly in 2.6.12 due to the class driver core
changes.)
Could you try that and let me know if it still has issues?
thanks,
greg k-h
next parent reply other threads:[~2005-06-24 15:23 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF831AC472.851744FE-ON8025702A.004A57EC-8025702A.004B5AE9@sophos.com>
2005-06-24 15:23 ` Greg KH [this message]
2005-06-27 15:21 Adam J. Richter
2005-06-27 23:27 ` J.A. Magallon
-- strict thread matches above, loose matches on Subject: below --
2005-06-24 15:32 tvrtko.ursulin
2005-06-24 16:27 ` Greg KH
2005-06-24 8:18 Greg KH
2005-06-24 12:23 ` Michael Tokarev
2005-06-24 15:16 ` Greg KH
2005-06-24 15:40 ` Michael Tokarev
2005-06-24 16:26 ` Greg KH
2005-06-24 14:32 ` Bill Gatliff
2005-06-24 15:17 ` Steven Rostedt
2005-06-24 15:20 ` Greg KH
2005-06-24 17:10 ` Michael Tokarev
2005-06-24 17:10 ` Bill Gatliff
2005-06-28 7:40 ` Greg KH
2005-06-24 19:05 ` Mike Bell
2005-06-24 21:55 ` J.A. Magallon
2005-06-24 19:22 ` Alexey Dobriyan
2005-06-25 0:57 ` Kyle Moffett
2005-06-25 7:37 ` Denis Vlasenko
2005-06-28 7:41 ` Greg KH
2005-06-28 19:56 ` Tom Rini
2005-06-28 21:08 ` Olaf Hering
2005-06-28 21:25 ` Tom Rini
2005-06-28 22:08 ` Michael Tokarev
2005-06-28 22:23 ` Tom Rini
2005-06-25 22:15 ` Matt Mackall
2005-06-25 23:43 ` Greg KH
2005-06-26 8:23 ` Russell King
2005-06-28 3:36 ` Greg KH
2005-06-27 7:19 ` Mike Bell
2005-06-27 22:35 ` Dmitry Torokhov
2005-06-27 23:26 ` Mike Bell
2005-06-28 7:40 ` Greg KH
2005-06-28 9:08 ` Mike Bell
2005-06-28 9:21 ` Arjan van de Ven
2005-06-28 9:40 ` Mike Bell
2005-06-28 21:49 ` Jim Crilly
2005-06-28 22:23 ` Mike Bell
2005-06-28 23:43 ` Jim Crilly
2005-06-29 0:12 ` Mike Bell
2005-06-29 0:39 ` David Lang
2005-06-29 0:53 ` Mike Bell
2005-06-28 12:00 ` Oliver Neukum
2005-06-28 20:08 ` Greg KH
2005-06-29 6:41 ` Oliver Neukum
2005-06-29 16:06 ` Greg KH
2005-06-29 16:22 ` Oliver Neukum
[not found] ` <200506270819.20108.arnd@arndb.de>
2005-06-28 3:46 ` 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=20050624152311.GB29955@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@sophos.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
Powered by JetHome