From: Pavel Machek <pavel@ucw.cz>
To: re.emese@gmail.com
Cc: linux-kernel@vger.kernel.org, len.brown@intel.com,
akpm@linux-foundation.org, torvalds@linux-foundation.org
Subject: Re: [PATCH 05/10] Constify struct platform_suspend_ops for 2.6.32-git-053fe57ac v2
Date: Mon, 14 Dec 2009 06:17:45 +0100 [thread overview]
Message-ID: <20091214051745.GG5114@elf.ucw.cz> (raw)
In-Reply-To: <2218084c294878ee335de04178d4c0b93167e248.1260663003.git.re.emese@gmail.com>
On Mon 2009-12-14 01:00:21, re.emese@gmail.com wrote:
> From: Emese Revfy <re.emese@gmail.com>
>
>
> Signed-off-by: Emese Revfy <re.emese@gmail.com>
It definitely needs an explanation, and it has none.
> index 5e781d8..3a2553d 100644
> --- a/include/linux/suspend.h
> +++ b/include/linux/suspend.h
> @@ -104,15 +104,15 @@ typedef int __bitwise suspend_state_t;
> * which require special recovery actions in that situation.
> */
> struct platform_suspend_ops {
> - int (*valid)(suspend_state_t state);
> - int (*begin)(suspend_state_t state);
> - int (*prepare)(void);
> - int (*prepare_late)(void);
> - int (*enter)(suspend_state_t state);
> - void (*wake)(void);
> - void (*finish)(void);
> - void (*end)(void);
> - void (*recover)(void);
> + int (* const valid)(suspend_state_t state);
> + int (* const begin)(suspend_state_t state);
> + int (* const prepare)(void);
> + int (* const prepare_late)(void);
> + int (* const enter)(suspend_state_t state);
> + void (* const wake)(void);
> + void (* const finish)(void);
> + void (* const end)(void);
> + void (* const recover)(void);
> };
>
I'm not sure what this is good for. Are you afraid that I'd do
*(char *)ops->end = 0x90 , or what?
> @@ -120,7 +120,7 @@ struct platform_suspend_ops {
> * suspend_set_ops - set platform dependent suspend operations
> * @ops: The new suspend operations to set.
> */
> -extern void suspend_set_ops(struct platform_suspend_ops *ops);
> +extern void suspend_set_ops(const struct platform_suspend_ops *ops);
> extern int suspend_valid_only_mem(suspend_state_t state);
>
These I can at least understand, and are probably ok.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-12-14 5:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 0:00 [PATCH 00/10] Constify struct platform_suspend_ops for 2.6.32-git-053fe57ac v2 re.emese
2009-12-14 0:00 ` [PATCH 01/10] " re.emese
2009-12-14 0:00 ` [PATCH 02/10] " re.emese
2009-12-14 0:00 ` [PATCH 03/10] " re.emese
2009-12-14 0:00 ` [PATCH 04/10] " re.emese
2009-12-14 0:00 ` [PATCH 1/3] Constify struct platform_hibernation_ops " re.emese
2009-12-14 0:00 ` [PATCH 1/1] Constify struct pci_raw_ops " re.emese
2009-12-14 0:00 ` [PATCH 05/10] Constify struct platform_suspend_ops " re.emese
2009-12-14 5:17 ` Pavel Machek [this message]
2009-12-14 22:47 ` Emese Revfy
2009-12-14 0:00 ` [PATCH 2/3] Constify struct platform_hibernation_ops " re.emese
2009-12-14 0:00 ` [PATCH 06/10] Constify struct platform_suspend_ops " re.emese
2009-12-14 0:00 ` [PATCH 3/3] Constify struct platform_hibernation_ops " re.emese
2009-12-14 0:00 ` [PATCH 07/10] Constify struct platform_suspend_ops " re.emese
2009-12-14 0:00 ` [PATCH 08/10] " re.emese
2009-12-14 0:00 ` [PATCH 09/10] " re.emese
2009-12-14 0:00 ` [PATCH 10/10] " re.emese
2009-12-14 5:15 ` [PATCH 00/10] " 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=20091214051745.GG5114@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@linux-foundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=re.emese@gmail.com \
--cc=torvalds@linux-foundation.org \
/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