Messages in this thread | | | Date | Thu, 23 Jan 2003 15:44:00 +0100 | From | Pavel Machek <> | Subject | Re: [PATCH] [TRIVIAL] kstrdup |
| |
Hi!
> > Ehm?! What's confusing on strdup? Or you want to also introduce > > kmemcpy, kmemcmp, ksprintf etc? > > No, as long as they don't allocate any memory. > > "kstrdup" makes it clear that the string is allocated by kmalloc() > and should be freed by kfree().
As we do not have any free(), there's no possibility for confusion.
As I said, if kstrdup took GFP_XXX argument, I'd agree, but as it hardcodes GFP_KERNEL... Pavel -- Casualities in World Trade Center: ~3k dead inside the building, cryptography in U.S.A. and free speech in Czech Republic. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |