> As a last resort, I'll try to maintain this as separate patch to be > applied to the kernel, but that is something I'd really try to avoid, > because: the problem is this: The export is going away for a reason and not "just because". And that reason is that the implementation is going to be radically redone such that this isn't possible anymore. At all. No amount of patching can fix that ;) - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
- From: Török Edwin <[email protected]>
- Re: [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
- From: Török Edwin <[email protected]>
- Re: [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
- From: Christoph Hellwig <[email protected]>
- Re: [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
- From: Török Edwin <[email protected]>
- [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
- Prev by Date: Re: [PATCH] register sysfs device for lp devices
- Next by Date: [2.6 patch] kernel/time.c: remove unused pps_* variables
- Previous by thread: Re: [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
- Next by thread: Re: [PATCH 2.6.15.4 1/1][RFC] ipt_owner: inode match supporting both incoming and outgoing packets
- Index(es):
 |