On Mon, Oct 07, 2013 at 03:39:55PM -0500, Larry Finger wrote:
> On 10/07/2013 03:10 PM, Greg KH wrote:
> > On Mon, Oct 07, 2013 at 12:43:41PM -0500, Larry Finger wrote:
> >> At present, if one wants to free the memory allocation used for
> >> a dev->kobj name, it is necessary to go quite deeply int
On 10/07/2013 03:10 PM, Greg KH wrote:
On Mon, Oct 07, 2013 at 12:43:41PM -0500, Larry Finger wrote:
At present, if one wants to free the memory allocation used for
a dev->kobj name, it is necessary to go quite deeply into the structure.
Why would you ever want to do this?
To avoid this much
On Mon, Oct 07, 2013 at 12:43:41PM -0500, Larry Finger wrote:
> At present, if one wants to free the memory allocation used for
> a dev->kobj name, it is necessary to go quite deeply into the structure.
Why would you ever want to do this?
> To avoid this much dependence on the structure details i
At present, if one wants to free the memory allocation used for
a dev->kobj name, it is necessary to go quite deeply into the structure.
To avoid this much dependence on the structure details in driver
code, a new inline routine is created.
Signed-off-by: Larry Finger
---
Index: wireless-testing
4 matches
Mail list logo
