[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49E0F98C.1090202@linux.intel.com>
Date: Sat, 11 Apr 2009 13:11:56 -0700
From: Arjan van de Ven <arjan@...ux.intel.com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
CC: Len Brown <lenb@...nel.org>, "Rafael J. Wysocki" <rjw@...k.pl>,
Takashi Iwai <tiwai@...e.de>,
pm list <linux-pm@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
linux-acpi@...r.kernel.org, Heinz Diehl <htd@...cy-poultry.org>,
Arkadiusz Miskiewicz <a.miskiewicz@...il.com>,
Vegard Nossum <vegard.nossum@...il.com>
Subject: Re: [linux-pm] [2.6.30-rc1-git2 regressions] Hibernation broken and
(minor but annoying) audio problem
Linus Torvalds wrote:
>
> On Sat, 11 Apr 2009, Arjan van de Ven wrote:
>> Now that I've been able to scan most of my mail; it looks like the one-liner
>> should just go in.
>
> Ok, I committed my one-liner, and then also reverted the ACPI battery
> workaround of removing __init, since the one-liner should fix that too.
>
> Cc'ing the people involved with that commit, just so that they know to
> test to make sure the alternate fix really did fix it for them (I'm pretty
> sure it does, but still a good idea to verify or at least let people know
> that a previous fix got reverted)
longer term I would like to work on two things
1) Fix the __init thing by just only freeing when appropriate, but not having to wait for it
2) Find a way for userland to trigger a sync
- for all storage probing
- for just async work
- "global sync", which includes all driver init
We can then have insmod/modprobe use this always, unless a flag is set
(so say, udev, can load a slew of modules, and then sync only on the last one)
and then after a year or two we can maybe remove the sync from the module loader ;(
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists