Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-14 Thread David Miller
From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> Date: Mon, 14 Jan 2008 10:33:34 +0200 (EET) > Thanks anyway for the tips & all, I think we have it now working > and I can return to inlines and rexmit_skb_hint things & other TCP > stuff rather than this hinderance. I've some interesting results > from ne

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-14 Thread Ilpo Järvinen
On Sun, 13 Jan 2008, David Miller wrote: > From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> > Date: Mon, 14 Jan 2008 09:43:08 +0200 (EET) > > > I'd prefer sending them as iso-8859-1 compliant (and I guess you are able > > to test your fix-to-utf-8 machinery with it as well :-)), as it would also > > m

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-13 Thread David Miller
From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> Date: Mon, 14 Jan 2008 09:43:08 +0200 (EET) > So which test case you prefer? :-) Is iso-8859-1 from+content ok? Or > should I keep trying to live with mixed utf-8 which I didn't got even > fully working last time because git-send-email is probably either

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-13 Thread Ilpo Järvinen
On Sat, 12 Jan 2008, David Miller wrote: > From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> > Date: Sat, 12 Jan 2008 14:59:50 +0200 (EET) > > > ...Maybe I just fall-back to changing my last name, it's the only > > full-proof solution... ;-) > > Don't do this! Otherwise I won't have a frequent test ca

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-12 Thread David Miller
From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> Date: Sat, 12 Jan 2008 14:59:50 +0200 (EET) > ...Maybe I just fall-back to changing my last name, it's the only > full-proof solution... ;-) Don't do this! Otherwise I won't have a frequent test case to make sure my patch applying scripts are working pr

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-12 Thread David Miller
From: Herbert Xu <[EMAIL PROTECTED]> Date: Sat, 12 Jan 2008 23:17:40 +1100 > Your emails are now using UTF-8 encoding but it's still declaring > ISO-8859-1 as the charset. So you probably want to fix that up or > your name may show up as Jävinen on the reader's screen. Yes, for people using the

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-12 Thread Herbert Xu
On Sat, Jan 12, 2008 at 02:59:50PM +0200, Ilpo Järvinen wrote: > > Here's one example... > > From: "=?utf-8?q?Ilpo_J=C3=A4rvinen?=" <[EMAIL PROTECTED]> > ... > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: 8bit > > Something still needed besides these to declare email utf-8

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-12 Thread Ilpo Järvinen
On Sat, 12 Jan 2008, Herbert Xu wrote: > On Sat, Jan 12, 2008 at 09:40:17AM +, Ilpo Järvinen wrote: > > Your emails are now using UTF-8 encoding but it's still declaring > ISO-8859-1 as the charset. Thanks for trying to help but my situation is such that I think it got also you confused (t

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-12 Thread Herbert Xu
Hi Ilpo: On Sat, Jan 12, 2008 at 09:40:17AM +, Ilpo Järvinen wrote: Your emails are now using UTF-8 encoding but it's still declaring ISO-8859-1 as the charset. So you probably want to fix that up or your name may show up as Jävinen on the reader's screen. Thanks, -- Visit Openswan at htt

Re: [RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-12 Thread David Miller
From: "Ilpo_Järvinen" <[EMAIL PROTECTED]> Date: Sat, 12 Jan 2008 11:34:29 +0200 > net/core/pktgen.c: > pktgen_stop_device | -50 > pktgen_run | -105 > pktgen_if_show | -37 > pktgen_thread_worker | -702 > 4 functions changed, 894 bytes removed, diff: -894 > > net/core/p

[RFC PATCH 8/8] [PKTGEN]: uninline getCurUs

2008-01-12 Thread Ilpo Järvinen
net/core/pktgen.c: pktgen_stop_device | -50 pktgen_run | -105 pktgen_if_show | -37 pktgen_thread_worker | -702 4 functions changed, 894 bytes removed, diff: -894 net/core/pktgen.c: getCurUs | +36 1 function changed, 36 bytes added, diff: +36 net/core/pktgen.o: 5