From: Gene Heskett <gene.heskett@gmail.com>
To: walt <w41ter@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Noticeable slow-down in 2.6.35-rc3
Date: Mon, 14 Jun 2010 12:27:40 -0400 [thread overview]
Message-ID: <201006141227.40233.gene.heskett@gmail.com> (raw)
In-Reply-To: <hv58sc$b1b$1@dough.gmane.org>
On Monday 14 June 2010, walt wrote:
>On 06/13/2010 03:13 PM, Gene Heskett wrote:
>> Unfortunately, this patch will not apply to my src tree for 2.6.35-rc3,
>> even after I fixed the unwanted line wrap in the first active line.
>>
>> I get:
>>
>> [root@coyote linux-2.6.35-rc3]# patch -p1<../2.6.35-rc3-test.patch
>> patching file net/core/skbuff.c
>> Hunk #1 FAILED at 532.
>> 1 out of 1 hunk FAILED -- saving rejects to file net/core/skbuff.c.rej
>>
>> Did my grabbing it with swiftfox damage it even further?
>> ------------------------------------------------------------------
>> diff --git a/net/core/skbuff.c b/net/core/skbuff.c
>> index 9f07e74..bcf2fa3 100644
>> --- a/net/core/skbuff.c
>> +++ b/net/core/skbuff.c
>> @@ -532,6 +532,7 @@ static void __copy_skb_header(struct sk_buff *new,
>> const struct sk_buff *old) new->ip_summed = old->ip_summed;
It also seems that the whole string ">ip_" has been traded for the
leading c in the var names. So that patch was totally trashed by a broken
html converter by the time it actually got to my machine.
Where can I get a pristine copy?
I am also wondering if this has anything to do with my missing USB devices
when booted to 2.6.35-rc3. In my case the symptoms are as it it did not
recurse far enough up the various branches of my usb tree from hell to find
everything.
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
FROM THE DESK OF
Rapunzel
Dear Prince:
Use ladder tonight -- you're splitting my ends.
prev parent reply other threads:[~2010-06-14 16:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 20:15 Chris Clayton
2010-06-13 20:35 ` François Valenduc
2010-06-13 20:58 ` Chris Clayton
2010-06-13 21:11 ` Chris Clayton
2010-06-13 22:13 ` Gene Heskett
2010-06-14 12:55 ` walt
2010-06-14 15:31 ` Gene Heskett
2010-06-14 16:27 ` Gene Heskett [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=201006141227.40233.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=w41ter@gmail.com \
/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
all inboxes | Powered by JetHome®