From: Stefan Seyfried <seife@suse.de>
To: Erik Rigtorp <erik@rigtorp.com>
Cc: linux-kernel@vger.kernel.org, Pavel Machek <pavel@ucw.cz>
Subject: Re: [PATCH] make swsusp produce nicer screen output
Date: Sun, 29 Aug 2004 16:59:25 +0200 [thread overview]
Message-ID: <4131EF4D.5080400@suse.de> (raw)
In-Reply-To: <20040829135403.GA8182@linux.nu>
Erik Rigtorp wrote:
> On Tue, Aug 24, 2004 at 11:49:30PM +0200, Pavel Machek wrote:
>>It really should not crash. 100 pages is 4MB. Thats little low but
>>seems possible.
>
> Well it's probably best to handle this case, to be on the safe side.
yes, better safe than sorry. And it's not exactly a hot code path.
> Here's a new version of the patch.
i like it, FWIW :-)
Regards,
Stefan
next prev parent reply other threads:[~2004-08-29 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 15:23 [PATCH] make swsusp produce nicer screen output Erik Rigtorp
2004-08-21 23:42 ` Stefan Seyfried
2004-08-23 17:42 ` Pavel Machek
2004-08-23 20:08 ` Erik Rigtorp
2004-08-24 21:49 ` Pavel Machek
2004-08-27 10:55 ` Stefan Seyfried
2004-08-28 22:58 ` Pavel Machek
2004-08-29 13:54 ` Erik Rigtorp
2004-08-29 14:59 ` Stefan Seyfried [this message]
2004-08-29 15:20 ` Pavel Machek
2004-08-29 16:36 ` Pavel Machek
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=4131EF4D.5080400@suse.de \
--to=seife@suse.de \
--cc=erik@rigtorp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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