Hi Greg. On Tue, 2008-06-10 at 20:29 -0700, Greg KH wrote:The patch I distribute now does have a few parts to it that could be separated into distinct patches (cryptoapi LZF support, fuse freezer support), but the bulk of it is TuxOnIce itself, which just adds new files and inserts the hooks necessary to share the lowlevel code with [u]swsusp. I think, therefore, it would akin to adding a new driver or filesystem. I don't think I do want to have my own series of patches, because TuxOnIce doesn't remove or rework swsusp or uswsusp, but sits along side them. I'm not trying to mutate swsusp into TuxOnIce, because that would require a complete rework of swsusp from the ground up (TuxOnIce does everything but the atomic copy/restore and associated prep/cleanup differently). Regards, Nigel --
| Greg KH | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | -mm merge plans for 2.6.23 |
| Pavel Roskin | ndiswrapper and GPL-only symbols redux |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
| Paweł Staszewski | Re: rib_trie / Fix inflate_threshold_root. Now=15 size=11 bits |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Stephen Hemminger | Re: HTB accuracy for high speed |
git: | |
| Sander | 'struct task_struct' has no member named 'mems_allowed' (was: Re: 2.6.20-rc4-mm1) |
