Re: [PATCH] usb: use memdup_user()

From: Oliver Neukum
Date: Wed May 06 2009 - 14:44:45 EST

Next message: Lifesaver: "DMI information from a kernel module?"
Previous message: Doug Thompson: "Re: [PATCH 09/21] amd64_edac: assign DRAM chip select base and mask in a family-specific way"
In reply to: Andrew Morton: "Re: [PATCH] usb: use memdup_user()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Am Mittwoch, 6. Mai 2009 20:31:17 schrieb Andrew Morton:
> > > There must be some particular action which flips the thread of control
> > > from one state to the other. eg, taking of a lock.
> >
> > Basically assigning an interface to the storage or ub driver.
>
> That's hardly enough information for anyone to understand what you
> mean :(

But isn't that always the same? If you take a lock that a method in the block
IO takes, you must use GFP_NOIO. What exactly do you want me to explain
better?

Regards
Oliver

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Next message: Lifesaver: "DMI information from a kernel module?"
Previous message: Doug Thompson: "Re: [PATCH 09/21] amd64_edac: assign DRAM chip select base and mask in a family-specific way"
In reply to: Andrew Morton: "Re: [PATCH] usb: use memdup_user()"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]