From: Roberto Nibali <ratz@drugphish.ch>
To: hugang <gang_hu@soul.com.cn>
Cc: adasi@kernel.pl, linux-kernel@vger.kernel.org
Subject: Re: [2.5.7] compilation problem
Date: Thu, 21 Mar 2002 01:30:46 +0100 [thread overview]
Message-ID: <3C9929B6.2040203@drugphish.ch> (raw)
In-Reply-To: <006301c1ceca$87937c70$0201a8c0@WITEK> <3C967FB2.1080706@drugphish.ch> <20020319154853.43fbe03b.gang_hu@soul.com.cn>
Hi,
> Today I download the latest patch, And I patch it into
> the 2.5.6 tree, But it do't have that problem.?
> I chech dev.c , that is right.
Funny, the patches (from 2.5.6 to 2.5.7 and from 2.5.7-pre2 to 2.5.7) I
downloaded from ftp.kernel.org do contain following patch:
laphish:/usr/src/patches # grep handle_diverter *
patch-2.5.7:-
handle_diverter(skb);
patch-2.5.7:+
ret = handle_diverter(skb);
patch-2.5.7-pre2:-
handle_diverter(skb);
patch-2.5.7-pre2:+
ret = handle_diverter(skb);
laphish:/usr/src/patches #
My patch reverts this but since you mention that for you it was correct
I wonder if we're really talking about the same patch so I just
downloaded them again and I can verify that the problem is really present:
ratz@laphish:~ > md5sum patch-2.5.7.*
f89d55b1e94fbd974d8b3f4625a86a2a patch-2.5.7.bz2
0f5dec319d693dfe6c528a76e10cd1d1 patch-2.5.7.gz
ratz@laphish:~ > bunzip2 patch-2.5.7.bz2
ratz@laphish:~ > grep handle_diverter patch-2.5.7
-
handle_diverter(skb);
+
ret = handle_diverter(skb);
ratz@laphish:~ > rm patch-2.5.7
ratz@laphish:~ > gunzip patch-2.5.7.gz
ratz@laphish:~ > grep handle_diverter patch-2.5.7
-
handle_diverter(skb);
+
ret = handle_diverter(skb);
ratz@laphish:~ > rm patch-2.5.7
ratz@laphish:~ >
Cheers,
Roberto Nibali, ratz
prev parent reply other threads:[~2002-03-21 0:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-18 22:16 [2.5.7] compilation problem Witek Kręcicki
2002-03-19 0:00 ` Roberto Nibali
2002-03-19 7:48 ` hugang
2002-03-21 0:30 ` Roberto Nibali [this message]
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=3C9929B6.2040203@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=adasi@kernel.pl \
--cc=gang_hu@soul.com.cn \
--cc=linux-kernel@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