From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Problems with PM_FREEZE Date: Wed, 28 Sep 2005 23:19:09 +0200 Message-ID: <20050928211909.GF2506@elf.ucw.cz> References: <20050928205147.GB2506@elf.ucw.cz> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============25714829083974422==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Alan Stern Cc: Nigel Cunningham , linux-pm@lists.osdl.org List-Id: linux-pm@vger.kernel.org --===============25714829083974422== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On St 28-09-05 17:13:44, Alan Stern wrote: > On Wed, 28 Sep 2005, Pavel Machek wrote: > > > > The problem that no pm_message_t is passed to resume routines. > > > > > > Another solution would be to create a globally-available subroutine, > > > something like: > > > > > > int resuming_from_disk(void) > > > > No. We do not have freezing_devices() nor suspending_devices(), and we > > should not have this one. > > Well, it would be a lot easier than changing all the resume routines. > > Do you have some reason for not allowing this? Yes, it is ugly and inconsistent. Pavel -- if you have sharp zaurus hardware you don't need... you know my address --===============25714829083974422== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============25714829083974422==--