Prev: perf: Split out arch specific code & improve PowerPC perf probe support
Next: Sound goes too fast due to commit 7b3a177b0
From: Greg KH on 14 Apr 2010 01:20
On Tue, Apr 13, 2010 at 07:33:34PM -0600, Alex Chiang wrote:
> * Eric Paris <eparis(a)redhat.com>:
> >
> > I get one for 1.0, 1.1, 1.2, 2.0, 3.0, 4.0, 5.0. Below I only show the
> > example for 1.0. Attached should be the full dmesg and config. Please
> > let me know about any ideas, tests, questions, or things I can do to
> > help debug the spew....
>
> These come from a patch I wrote, but unfortunately, I don't have
> the time or hardware to properly debug them. :(

It should be simple, for any dynamically allocated sysfs attribute, just
call sysfs_attribute_initialize() before registering it with the sysfs
core, and you will get rid of these messages.

If you have a pointer to your patch, I'll be glad to generate an add-on
patch to resolve this issue.

thanks,

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: perf: Split out arch specific code & improve PowerPC perf probe support
Next: Sound goes too fast due to commit 7b3a177b0