Prev: linux-next: manual merge of the drbd tree with Linus' tree
Next: [RFC] lp_events: an lternitive to suspend blocker user mode and kernel API
From: Jesse Barnes on 18 Jun 2010 13:20
On Fri, 11 Jun 2010 15:42:12 +0800
Frank Pan <frankpzh(a)gmail.com> wrote:

> > Per the discussion in this thread it sounds like this really has
> > nothing to do with sysfs and more to do with being a convenient API for
> > drivers.
> Yes.
>
> > Is that correct? If so, and assuming there's not some other way of
> > getting this info from a driver, I'm ok with it, but it should be
> > submitted as part of a patchset including driver code that uses it.
> Yes, I may submit them all after the driver hack is complete. I put the
> issue here to get response of some thing like, is this change possible?
> or is there a better way to do it?
>
> Thanks for reply.

I think once we see the driver usage it'll be easier to say.

Chris is the one you'll need to convince though.

--
Jesse Barnes, Intel Open Source Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
First  |  Prev  | 
Pages: 1 2 3 4
Prev: linux-next: manual merge of the drbd tree with Linus' tree
Next: [RFC] lp_events: an lternitive to suspend blocker user mode and kernel API