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 in driver
> code, a new inline routine is created.
>
> Signed-off-by: Larry Finger <larry.fin...@lwfinger.net>
> ---
>
> Index: wireless-testing-save/include/linux/device.h
> ===================================================================
> --- wireless-testing-save.orig/include/linux/device.h
> +++ wireless-testing-save/include/linux/device.h
> @@ -27,6 +27,7 @@
> #include <linux/ratelimit.h>
> #include <linux/uidgid.h>
> #include <asm/device.h>
> +#include <linux/slab.h>
>
> struct device;
> struct device_private;
> @@ -789,6 +790,11 @@ static inline const char *dev_name(const
> return kobject_name(&dev->kobj);
> }
>
> +static inline void dev_free_name(struct device *dev)
> +{
> + kfree(dev->kobj.name);
> +}
Please show how you would use this function, I can't add functions that
no one calls.
And given that this type of thing hasn't been needed before, I'm
thinking that it still isn't needed :)
thanks,
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
