(2014/11/26 2:15), Seth Jennings wrote: > Note to Steve: > Masami's IPMODIFY patch is heading for -next via your tree. Once it arrives, > I'll rebase and make the change to set IPMODIFY. Do not pull this for -next > yet. This version (v4) is for review and gathering acks.
BTW, as we discussed IPMODIFY is an exclusive flag. So if we allocate ftrace_ops for each function in each patch, it could be conflict each other. Maybe we need to have another ops hashtable to find such conflict and new handler to handle it. Thank you, -- Masami HIRAMATSU Software Platform Research Dept. Linux Technology Research Center Hitachi, Ltd., Yokohama Research Laboratory E-mail: masami.hiramatsu...@hitachi.com -- 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/
