It should not be a problem, it just means that the first "hunk" of
patched code for ksyms.c applied 14 lines down from where it expected.
This is normal if you're not applying the patch against the exact same
code from which it was generated.
-Eric
On Mon, 2001-11-26 at 15:42, Steven Farrier wrote:
> I am attempting to use the 2.4.14-2 preempt patch and the xfs 1.0.2 patch on
> my kernel.
>
> When I apply the xfs patch then the preempt patch this show up while applying
> preempt
>
> ----
> patching file kernel/fork.c
> patching file kernel/ksyms.c
> Hunk #1 succeeded at 448 (offset 14 lines).
> patching file kernel/sched.c
> patching file lib/dec_and_lock.c
> ----
>
> When I apply the preempt patch then the xfs patch this shows up while
> applying xfs
>
> ----
> patching file mm/page_alloc.c
> patching file mm/slab.c
> Hunk #1 succeeded at 1568 (offset 2 lines).
> patching file mm/vmalloc.c
> patching file mm/vmscan.c
> ----
>
> What is this Hunk #1 line mean?
>
> Do it mean the patch failed to apply?
>
> Steven
--
Eric Sandeen XFS for Linux http://oss.sgi.com/projects/xfs
sandeen@xxxxxxx SGI, Inc.
|