From: Anand Gadiyar <gadiyar-l0cyMroinI0@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Anand Gadiyar <gadiyar-l0cyMroinI0@public.gmane.org>,
Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
Subject: [PATCH 2/2] i2c: i2c-omap: make dev_pm_ops a const struct
Date: Tue, 22 Feb 2011 12:21:27 +0530 [thread overview]
Message-ID: <1298357487-10966-2-git-send-email-gadiyar@ti.com> (raw)
In-Reply-To: <1298357487-10966-1-git-send-email-gadiyar-l0cyMroinI0@public.gmane.org>
dev_pm_ops is normally a const struct. Update the structure
in this driver accordingly.
Signed-off-by: Anand Gadiyar <gadiyar-l0cyMroinI0@public.gmane.org>
Cc: Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>
---
Checkpatch complained about this when I generated the previous patch.
So I thought I might as well fix it up.
drivers/i2c/busses/i2c-omap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-omap-usb/drivers/i2c/busses/i2c-omap.c
===================================================================
--- linux-omap-usb.orig/drivers/i2c/busses/i2c-omap.c
+++ linux-omap-usb/drivers/i2c/busses/i2c-omap.c
@@ -1156,7 +1156,7 @@ static int omap_i2c_resume(struct device
return 0;
}
-static struct dev_pm_ops omap_i2c_pm = {
+static const struct dev_pm_ops omap_i2c_pm = {
.suspend = omap_i2c_suspend,
.resume = omap_i2c_resume,
};
prev parent reply other threads:[~2011-02-22 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-22 6:51 [PATCH 1/2] i2c: i2c-omap: fix build break with CONFIG_SUSPEND=n Anand Gadiyar
[not found] ` <1298357487-10966-1-git-send-email-gadiyar-l0cyMroinI0@public.gmane.org>
2011-02-22 6:51 ` Anand Gadiyar [this message]
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=1298357487-10966-2-git-send-email-gadiyar@ti.com \
--to=gadiyar-l0cymroini0@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for NNTP newsgroup(s).