[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1205151424450.1796-100000@iolanthe.rowland.org>
Date: Tue, 15 May 2012 14:30:00 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Lin Ming <ming.m.lin@...el.com>
cc: Alan Cox <alan@...rguk.ukuu.org.uk>, Jens Axboe <axboe@...nel.dk>,
Kernel development list <linux-kernel@...r.kernel.org>,
Linux-pm mailing list <linux-pm@...r.kernel.org>,
SCSI development list <linux-scsi@...r.kernel.org>
Subject: Re: [RFC PATCH 1/3] block: add a flag to identify PM request
On Tue, 15 May 2012, Lin Ming wrote:
> > > IDE code still uses both types and they are used for system
> > > suspend/resume. See generic_ide_suspend and generic_ide_resume.
> >
> > drivers/ide is obsolete code though so we shouldn't be forcing its needs
> > on the future
>
> Do you mean we don't care about breaking ide code?
As far as I can tell, Alan means that you shouldn't hesitate to change
the IDE code in order to make things easier for more up-to-date
systems. But don't _break_ the IDE driver!
> struct request {
> ....
> unsigned int cmd_flags;
> enum rq_cmd_type_bits cmd_type;
>
> Another reason I didn't reuse REQ_TYPE_PM_SUSPEND/REQ_TYPE_PM_RESUME is
> because all scsi requests set the cmd_type to REQ_TYPE_BLOCK_PC.
>
> So I think we should add a new cmd_flags(REQ_PM) to tell if it's a
> runtime pm request.
Yes, that does make more sense, even though it seems silly to have both
a flag and a type code for the same thing. Maybe the IDE driver could
be changed to use the new flag.
Alan Stern
--
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