From: Greg KH <gregkh@suse.de>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Len Brown <lenb@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-acpi <linux-acpi@vger.kernel.org>
Subject: Re: acpi_cpu_freq_init warning...
Date: Mon, 5 May 2008 23:47:41 -0700 [thread overview]
Message-ID: <20080506064741.GA6062@suse.de> (raw)
In-Reply-To: <87k5i8hrmk.fsf@duaron.myhome.or.jp>
On Tue, May 06, 2008 at 03:29:55PM +0900, OGAWA Hirofumi wrote:
> > calling acpi_cpufreq_init+0x0/0x68()
> > sysdev: class cpu: driver (ffffffff80da0110) has already been
> > registered to a class, something is wrong, but will forge on!
> > ------------[ cut here ]------------
> > WARNING: at drivers/base/sys.c:183 sysdev_driver_register+0x82/0x150()
> > Modules linked in:
> > Pid: 1, comm: swapper Not tainted
> > 2.6.26-rc1-sched-devel.git-x86-latest.git-00485-g253148c-dirty #333
>
> I've seen this too. The following patch seems to work for me.
> --
> OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
>
>
> [PATCH] Fix bogus warning in sysdev_driver_register()
>
> if ((drv->entry.next != drv->entry.prev) ||
> (drv->entry.next != NULL)) {
>
> warns list_empty(&drv->entry).
should we just call list_empty() here to make sure it is correct?
thanks,
greg k-h
next prev parent reply other threads:[~2008-05-06 6:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-06 2:51 acpi_cpu_freq_init warning Yinghai Lu
2008-05-06 6:29 ` OGAWA Hirofumi
2008-05-06 6:47 ` Greg KH [this message]
2008-05-06 7:13 ` OGAWA Hirofumi
2008-05-06 14:47 ` Linus Torvalds
2008-05-06 19:02 ` OGAWA Hirofumi
2008-05-06 20:20 ` Greg KH
2008-05-06 20:27 ` Linus Torvalds
2008-05-06 21:38 ` Greg KH
2008-05-06 15:44 ` Thomas Renninger
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=20080506064741.GA6062@suse.de \
--to=gregkh@suse.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.org \
--cc=yhlu.kernel@gmail.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