Oliver Neukum writes: > They can't. Device specific protocols are known to the drivers only. > The fact remains, remove the freezer and you need to go through > all drivers. The freezer does not actually mean that you don't have to get the drivers right, because kernel threads can issue I/O requests. Paul. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Oliver Neukum <oliver@neukum.org>
- Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- References:
- [PATCH] Remove process freezer from suspend to RAM pathway
- From: Matthew Garrett <mjg59@srcf.ucam.org>
- Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Oliver Neukum <oliver@neukum.org>
- Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Paul Mackerras <paulus@samba.org>
- Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- From: Oliver Neukum <oliver@neukum.org>
- [PATCH] Remove process freezer from suspend to RAM pathway
- Prev by Date: Re: [linux-pm] [PATCH] Remove process freezer from suspend to RAM pathway
- Next by Date: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Previous by thread: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Next by thread: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
- Index(es):
![]() |