The usual cause for this is when the directories in the patch file do not match the tree being patched. AFAIK, for the default -p0 to work correctly, the paths in the patch file relating to "OLD" or "Original" location must match exactly the paths in the source tree being patched. For the linux kernel, this means that the root of your tree must be called ./linux, and not something like ./linux-2.1.89.
Other than that I've never had a problem.
Hope this helps,
Steven N. Hirsch wrote in message ...
>I've seen the same advisory in the man pages about -p0 being the default.
>Don't believe it. I learned a long time back (well, 1994 anyway) to
>always use -p0 when applying patches to anything. Without this switch,
>files are often created in new trees or, occasionally, the current working
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org