Re: acpi_cpu_freq_init warning...

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Linus Torvalds
Date: Tuesday, May 6, 2008 - 1:27 pm

On Tue, 6 May 2008, Greg KH wrote:


Umm. And what do you think the test for drv->entry.next is there for?

Ie the assumption is that it's at least zeroed out, if it's not 
initialized. 

Now, admittedly it could be *total* crud, but if so, I'd seriously suggest 
just fixing the callers, rather than passing totally uninitialized 
structures with random crap in it around.

			Linus
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
acpi_cpu_freq_init warning..., Yinghai Lu, (Mon May 5, 7:51 pm)
Re: acpi_cpu_freq_init warning..., OGAWA Hirofumi, (Mon May 5, 11:29 pm)
Re: acpi_cpu_freq_init warning..., Greg KH, (Mon May 5, 11:47 pm)
Re: acpi_cpu_freq_init warning..., OGAWA Hirofumi, (Tue May 6, 12:13 am)
Re: acpi_cpu_freq_init warning..., Linus Torvalds, (Tue May 6, 7:47 am)
Re: acpi_cpu_freq_init warning..., Thomas Renninger, (Tue May 6, 8:44 am)
Re: acpi_cpu_freq_init warning..., OGAWA Hirofumi, (Tue May 6, 12:02 pm)
Re: acpi_cpu_freq_init warning..., Greg KH, (Tue May 6, 1:20 pm)
Re: acpi_cpu_freq_init warning..., Linus Torvalds, (Tue May 6, 1:27 pm)
Re: acpi_cpu_freq_init warning..., Greg KH, (Tue May 6, 2:38 pm)