From: "Ming-Ching Tiew" <mingching.tiew@redtone.com>
To: netfilter@lists.netfilter.org
Subject: Re: ipt_random
Date: Wed, 20 Jul 2005 15:08:43 +0800 [thread overview]
Message-ID: <058a01c58cf9$dd3d88f0$1280a8c0@newlife> (raw)
In-Reply-To: Pine.LNX.4.61.0507200711010.9066@yvahk01.tjqt.qr
From: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
>
> 07:11 linux01:../random/linux > l net/ipv4/netfilter/
> total 24
> drwxr-xr-x 2 jengelh users 4096 2005-07-19 23:55 .
> drwxr-xr-x 3 jengelh users 4096 2005-07-19 23:55 ..
> -rw-r--r-- 1 jengelh users 172 2003-12-18 19:28 Config.in.ladd
> -rw-r--r-- 1 jengelh users 2236 2003-12-18 19:28 ipt_random.c
> -rw-r--r-- 1 jengelh users 326 2004-05-06 15:27 Kconfig.ladd
> -rw-r--r-- 1 jengelh users 93 2003-12-18 19:28 Makefile.ladd
> 07:11 linux01:../random/linux > pwd
> /home/jengelh/patch-o-matic-ng-20050719/patchlets/random/linux
>
> Given that there is Kconfig, this patch _is_ also for 2.6.
>
Too bad that's not how the patch-o-matic scripts are written. It will not
patch the kernel source, if it did not follow certain directory structure.
That's how the patch-o-matic 'runme --batch' behaves, if what I have
tried is correct.
next prev parent reply other threads:[~2005-07-20 7:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-19 9:25 ipt_random Ming-Ching Tiew
2005-07-19 10:17 ` ipt_random Jan Engelhardt
2005-07-20 1:17 ` ipt_random Ming-Ching Tiew
2005-07-20 6:25 ` ipt_random Jan Engelhardt
2005-07-20 7:08 ` Ming-Ching Tiew [this message]
2005-07-20 7:54 ` ipt_random Jan Engelhardt
2005-07-20 8:15 ` ipt_random Ming-Ching Tiew
2005-07-20 8:32 ` ipt_random Jozsef Kadlecsik
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='058a01c58cf9$dd3d88f0$1280a8c0@newlife' \
--to=mingching.tiew@redtone.com \
--cc=netfilter@lists.netfilter.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