public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Yu Luming <luming.yu@intel.com>
To: danny@mailmij.org
Cc: linux-acpi@vger.kernel.org, "Brown, Len" <lenb@hera.kernel.org>
Subject: Re: double proc entries
Date: Mon, 21 Aug 2006 16:49:12 +0800	[thread overview]
Message-ID: <200608211649.13421.luming.yu@intel.com> (raw)
In-Reply-To: <20060821044915.B18790@luna.ellen.dexterslabs.com>

On Monday 21 August 2006 10:49, danny@mailmij.org wrote:
> Hi,
>  Recently I noticed that unloading video.ko causes a warning from
> remove_proc_entry because the subdir is not empty. This is related to the
> fact that I have 2 VID entries in /proc/acpi/video, and this messes up
> things a bit. The cause of this is that the VID entry appears both on the
> PCI and on the AGP bus, sysfs handles this nicely:
>  ./firmware/acpi/namespace/ACPI/_SB/PCI0/AGP/VID
>...

Yes,  This is a problem.

>  More information can be found here:
>  http://qa.mandriva.com/show_bug.cgi?id=22249
>
>  proc/acpi/video/ does not know about AGP or PCI. Attached patch fixes the
> problem but is not so beautiful. Maybe it's better to make another subdir
> in video for the parent of the device, but I thought this would be more
> likely to break userland apps. Perhaps someone can do better.
>

The beautiful way is to completely delete /proc/acpi, and turn to sysfs. :-)
But we still have to live with /proc/acpi for some times.
So, I think your patch is right thing.

>+        strcpy(proc_dir_name, acpi_device_bid(device));
>+        strcat(proc_dir_name, "_");
>+        strcat(proc_dir_name, acpi_device_bid(device->parent));
 
but, when you are using acpi_device_bid(device->parent), you 
should have checked  device->parent is NOT NULL.

-- 
Thanks,
Luming

  reply	other threads:[~2006-08-21  8:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-21  2:49 double proc entries danny
2006-08-21  8:49 ` Yu Luming [this message]
2006-08-21  8:50   ` danny
2006-08-21 22:02     ` Len Brown
2006-08-24  1:46       ` danny
2006-09-06  7:27         ` danny

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=200608211649.13421.luming.yu@intel.com \
    --to=luming.yu@intel.com \
    --cc=danny@mailmij.org \
    --cc=lenb@hera.kernel.org \
    --cc=linux-acpi@vger.kernel.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