From: Greg KH <gregkh@suse.de>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [BUG] linux-next: Tree for August 21 - WARNING: at fs/sysfs/dir.c:465 sysfs_add_one()
Date: Thu, 21 Aug 2008 12:23:15 -0700 [thread overview]
Message-ID: <20080821192315.GA17600@suse.de> (raw)
In-Reply-To: <48ADC08C.6030406@linux.vnet.ibm.com>
On Fri, Aug 22, 2008 at 12:52:52AM +0530, Kamalesh Babulal wrote:
> Hi,
>
> while booting up the next-20080821 kernel on x86 machine, warning shows up for sysfs_add_one
> of acpi getting called twice
See lkml, patches to resolve this have been posted.
thanks,
greg k-h
prev parent reply other threads:[~2008-08-21 19:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 9:12 linux-next: Tree for August 21 Stephen Rothwell
2008-08-21 19:22 ` [BUG] linux-next: Tree for August 21 - WARNING: at fs/sysfs/dir.c:465 sysfs_add_one() Kamalesh Babulal
2008-08-21 19:23 ` Greg KH [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=20080821192315.GA17600@suse.de \
--to=gregkh@suse.de \
--cc=apw@shadowen.org \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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