On Wednesday 09 August 2006 21:38, Pavel Machek wrote:
> Hi!
>
> > > Comments welcome.
> >
> > Thanks for the reminder. I'd forgotten half the reason why I didn't want
> > to make Suspend2 into incremental patches! You're a brave man!
>
> Why does this serve as a reminder? No, it is not easy to merge big
> patches to mainline. But it is actually a feature.
It serves as a reminder because it shows (just the description, I mean), how
inter-related all the changes that are needed are.
I don't get the "it is actually a feature" bit.
> > while (1) {
> > size=$RANDOM * 65536 + 1
> > dd if=/dev/random bs=1 count=$size | patch -p0-b
> > make && break
> >}
>
> Is this what you use to generate suspend2 patches? :-)))))
:) Actually, given Greg's OLS keynote, I was wondering if it was what he used
to generate them.
Regards,
Nigel
--
Nigel, Michelle and Alisdair Cunningham
5 Mitchell Street
Cobden 3266
Victoria, Australia
Attachment:
pgp6EYh8PmTWi.pgp
Description: PGP signature
- Follow-Ups:
- Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- From: Pavel Machek <[email protected]>
- Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- References:
- [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- From: "Rafael J. Wysocki" <[email protected]>
- Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- From: Nigel Cunningham <[email protected]>
- Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- From: Pavel Machek <[email protected]>
- [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- Prev by Date: Re: [RFC][PATCH -mm 2/5] swsusp: Use memory bitmaps during resume
- Next by Date: Re: [RFC][PATCH -mm 3/5] swsusp: Fix handling of highmem
- Previous by thread: Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- Next by thread: Re: [RFC][PATCH -mm 0/5] swsusp: Fix handling of highmem
- Index(es):
 |