From: Andrew Morton <akpm@osdl.org>
To: Andreas Steinmetz <ast@domdv.de>
Cc: pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: [swsusp] encrypt suspend data for easy wiping
Date: Mon, 25 Jul 2005 20:10:36 -0700 [thread overview]
Message-ID: <20050725201036.2205cac3.akpm@osdl.org> (raw)
In-Reply-To: <42DA7B12.7030307@domdv.de>
Andreas Steinmetz <ast@domdv.de> wrote:
>
> the attached patches are acked by Pavel and signed off by me
OK, well I queued this up, without a changelog. Because you didn't send
one. Please do so. As it adds a new feature, quite a bit of info is
relevant.
It should include a description of what the patch tries to do, and how it
does it. It should include a description of any known shortcomings. If
any user configuration is needed then that should be placed somewhere under
Documentation/
Take a look at how other people document their feature additions and you'll
get the idea.
Please don't send multiple patches per email. In this case I did the
handwork and put both diffs into the same patch.
Personally, I don't like this:
+config SWSUSP_ENCRYPT
+ bool "Encrypt suspend image"
+ depends on SOFTWARE_SUSPEND && CRYPTO=y && (CRYPTO_AES=y || CRYPTO_AES_586=y || CRYPTO_AES_X86_64=y)
This requires the user to hunt around in config until all the right options
are enabled to permit SWSUSP_ENCRYPT to appear in config. That can be
quite frustrating and is very poor UI.
For a top-level feature such as this it is much better to always offer the
feature to the user and to then use `select' to turn on all the
infrastructure bits which the user will need. Make the computer do the
work rather than the user.
Yes, it might be a bit tricky in this case because you have a dependency on
one of the AES encryption types, but it would be good if you can come up
with something which doesn't force the user into a game of hide-and-seek.
next prev parent reply other threads:[~2005-07-26 3:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 21:35 Pavel Machek
2005-07-06 9:02 ` Andrew Morton
2005-07-06 9:11 ` Pavel Machek
2005-07-06 12:49 ` Grzegorz Kulewski
2005-07-07 19:14 ` Pavel Machek
2005-07-07 19:30 ` Grzegorz Kulewski
2005-07-17 15:36 ` Andreas Steinmetz
2005-07-26 3:10 ` Andrew Morton [this message]
2005-07-26 22:04 ` Matt Mackall
2005-07-26 22:14 ` Pavel Machek
2005-07-26 22:58 ` Matt Mackall
2005-07-26 23:12 ` Pavel Machek
2005-07-26 23:53 ` Matt Mackall
2005-07-27 7:38 ` Pavel Machek
2005-07-27 14:22 ` Andreas Steinmetz
2005-07-26 22:26 ` 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=20050725201036.2205cac3.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=ast@domdv.de \
--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
all inboxes | Powered by JetHome®