From: "Justin Mattock" <justinmattock@gmail.com>
To: "Linus Torvalds" <torvalds@linux-foundation.org>
Cc: "Alexey Dobriyan" <adobriyan@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: ACPI vs proc_create_data() mismerge (was Re: proc_dir_entry 'info' already registered)
Date: Thu, 1 May 2008 00:24:13 +0000 [thread overview]
Message-ID: <dd18b0c30804301724h2be338bfydba320b719190972@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0804301706590.5947@woody.linux-foundation.org>
On Thu, May 1, 2008 at 12:07 AM, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
>
>
> On Thu, 1 May 2008, Alexey Dobriyan wrote:
> >
>
> > acpi_device_dir() is NULL until all files are createst, so everyting is
> > created in straight in /proc/ and creation code warns.
>
> Ok, I tested this on a laptop, it works for me. Committed. Thanks again,
>
> Linus
>
Hello; I ran into a problem, for some reason with adding:
acpi_device_dir(device) = device_dir;
I received:
acpi_video_device_aqdd_fs: implicit declaration of function acpi_device
lvalue required as left operand of assignment = after these errors, as a test
I went in and put /*acpi_device_dir(device); */ around that line then
recompiled, compiling went o.k., then rebooting
I'm not seeing any messages like before.
regards;
--
Justin P. Mattock
prev parent reply other threads:[~2008-05-01 0:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-30 22:38 proc_dir_entry 'info' already registered Justin Mattock
2008-05-01 0:10 ` ACPI vs proc_create_data() mismerge (was Re: proc_dir_entry 'info' already registered) Alexey Dobriyan
2008-04-30 23:24 ` Linus Torvalds
2008-05-01 0:07 ` Linus Torvalds
2008-05-01 0:24 ` Justin Mattock [this message]
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=dd18b0c30804301724h2be338bfydba320b719190972@mail.gmail.com \
--to=justinmattock@gmail.com \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®