[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d120d5000706140559h10461e50q2f30ff423468676e@mail.gmail.com>
Date: Thu, 14 Jun 2007 08:59:20 -0400
From: "Dmitry Torokhov" <dmitry.torokhov@...il.com>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: "Kay Sievers" <kay.sievers@...y.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"Alan Stern" <stern@...land.harvard.edu>,
"David Brownell" <david-b@...bell.net>, "Greg KH" <greg@...ah.com>,
LKML <linux-kernel@...r.kernel.org>,
"Pavel Machek" <pavel@....cz>
Subject: Re: [PATCH -mm 4/7] PM: Remove suspend and resume support from struct device_type
On 6/14/07, Rafael J. Wysocki <rjw@...k.pl> wrote:
> On Thursday, 14 June 2007 06:10, Dmitry Torokhov wrote:
> > On Wednesday 13 June 2007 18:20, Kay Sievers wrote:
> > > Dmitry, you added this recently, is this used in any code you plan to
> > > merge soon?
> > >
> >
> > Yes, I will need it to implement input device resume (mainly to restore LED
> > state and repeat rate for keyboards).
>
> Would that be a big problem to reintroduce it along with the user?
>
Yes because that part is in Greg's domain so I am trying to set
infrastructure up before I can commit my patches into my tree so that
Andrew can safely pull from me into -mm. Greg normally adds such stuff
during merge window so that means if we remove it now we'd need ~2
releases to get it and the user back in.
--
Dmitry
-
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