From: Waldek <sp2ong@wp.pl>
To: linux-hams <linux-hams@vger.kernel.org>
Subject: Re: patch INP3 for kernel 3.6
Date: Thu, 26 Sep 2013 10:02:06 +0200 [thread overview]
Message-ID: <5243e9fee1a652.62390282@wp.pl> (raw)
Hi Matt,
I have try use this patch in 3.6.11 kernel:
patching file include/linux/netrom.h
Hunk #1 succeeded at 18 (offset 2 lines).
patching file include/net/netrom.h
Hunk #1 FAILED at 9.
Hunk #2 succeeded at 38 (offset 1 line).
Hunk #3 succeeded at 67 (offset 1 line).
Hunk #4 succeeded at 106 (offset 1 line).
Hunk #5 succeeded at 127 (offset 1 line).
Hunk #6 succeeded at 231 (offset 1 line).
Hunk #7 succeeded at 296 (offset 1 line).
1 out of 7 hunks FAILED -- saving rejects to file include/net/netrom.h.rej
patching file net/ax25/Kconfig
patching file net/netrom/af_netrom.c
Hunk #2 succeeded at 1252 with fuzz 2 (offset -3 lines).
Hunk #3 succeeded at 1441 (offset -18 lines).
Hunk #4 succeeded at 1476 (offset -18 lines).
Hunk #5 succeeded at 1508 (offset -18 lines).
patching file net/netrom/inp3.c
patching file net/netrom/Makefile
patching file net/netrom/nr_route.c
Hunk #2 succeeded at 41 (offset 1 line).
Hunk #3 succeeded at 69 (offset 1 line).
Hunk #4 succeeded at 94 (offset 1 line).
Hunk #5 succeeded at 132 (offset 1 line).
Hunk #6 succeeded at 163 (offset 1 line).
Hunk #7 succeeded at 185 (offset 1 line).
Hunk #8 succeeded at 230 (offset 1 line).
Hunk #9 succeeded at 279 with fuzz 2 (offset 1 line).
Hunk #10 succeeded at 342 (offset 4 lines).
Hunk #11 succeeded at 370 (offset 4 lines).
Hunk #12 succeeded at 415 (offset 4 lines).
Hunk #13 succeeded at 456 (offset 4 lines).
Hunk #14 succeeded at 504 (offset 4 lines).
Hunk #15 succeeded at 549 (offset 4 lines).
Hunk #16 succeeded at 560 (offset 4 lines).
Hunk #17 succeeded at 579 (offset 4 lines).
Hunk #18 succeeded at 617 (offset 5 lines).
Hunk #19 succeeded at 690 (offset 5 lines).
Hunk #20 succeeded at 897 (offset 9 lines).
Hunk #21 succeeded at 912 (offset 9 lines).
Hunk #22 succeeded at 944 (offset 9 lines).
Hunk #23 succeeded at 954 (offset 9 lines).
Hunk #24 succeeded at 973 (offset 9 lines).
Hunk #25 succeeded at 1004 (offset 9 lines).
and display rejected netrom.h:
include/net$ more netrom.h.rej
*** include/net/netrom.h2012-09-23 05:24:40.000000000 +1000
--- include/net/netrom.h2012-12-14 17:00:59.000000000 +1100
***************
*** 9,14 ****
#include <linux/netrom.h>
#include <linux/list.h>
#include <net/sock.h>
#defineNR_NETWORK_LEN15
--- 9,15 ----
#include <linux/netrom.h>
#include <linux/list.h>
+ #include <linux/types.h>
#include <net/sock.h>
#defineNR_NETWORK_LEN15
next reply other threads:[~2013-09-26 8:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 8:02 Waldek [this message]
2013-09-26 8:10 ` patch INP3 for kernel 3.6 Matt Maguire
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5243e9fee1a652.62390282@wp.pl \
--to=sp2ong@wp.pl \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox