All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Arve Hj?nnev?g <arve@android.com>
Cc: Brian Swetland <swetland@google.com>,
	kernel list <linux-kernel@vger.kernel.org>
Subject: Re: HTC: touchscreen driver
Date: Mon, 20 Jul 2009 12:47:26 +0200	[thread overview]
Message-ID: <20090720104726.GE19341@elf.ucw.cz> (raw)
In-Reply-To: <d6200be20907192043w3f1aa2abvd0125163e6f5519c@mail.gmail.com>

Hi!

You probably want (something like) this to mostly fix !EARLY_SUSPEND
compilation.

Signed-off-by: Pavel Machek <pavel@ucw.cz>

index a45634b..e916cea 100644
--- a/drivers/staging/dream/synaptics_i2c_rmi.c
+++ b/drivers/staging/dream/synaptics_i2c_rmi.c
@@ -45,7 +44,9 @@ struct synaptics_ts_data {
 	int snap_up[2];
 	uint32_t flags;
 	int (*power)(int on);
+#ifdef CONFIG_HAS_EARLYSUSPEND
 	struct early_suspend early_suspend;
+#endif
 };
 
 #ifdef CONFIG_HAS_EARLYSUSPEND
@@ -515,7 +516,9 @@ err_check_functionality_failed:
 static int synaptics_ts_remove(struct i2c_client *client)
 {
 	struct synaptics_ts_data *ts = i2c_get_clientdata(client);
+#ifdef CONFIG_HAS_EARLYSUSPEND
 	unregister_early_suspend(&ts->early_suspend);
+#endif
 	if (ts->use_irq)
 		free_irq(client->irq, ts);
 	else


-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2009-07-20 10:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090710084323.GA6522@elf.ucw.cz>
     [not found] ` <a55d774e0907100155m25366994pe9ec5d0f5f868818@mail.gmail.com>
     [not found]   ` <20090710103243.GB7789@elf.ucw.cz>
     [not found]     ` <a55d774e0907100431j3fdc4671i6b185019594367fa@mail.gmail.com>
     [not found]       ` <20090713202302.GC2569@elf.ucw.cz>
2009-07-13 20:57         ` HTC: touchscreen driver Pavel Machek
2009-07-13 22:07           ` Pavel Machek
2009-07-14  1:29             ` Arve Hjønnevåg
2009-07-14  1:44               ` Joe Perches
2009-07-14  9:46                 ` Pavel Machek
2009-07-15 19:05                 ` Frank Rowand
2009-07-14  9:23               ` Pavel Machek
2009-07-14  9:46               ` Pavel Machek
2009-07-14 22:07                 ` Arve Hjønnevåg
2009-07-14 22:16                   ` Pavel Machek
2009-07-14 22:45                     ` Arve Hjønnevåg
2009-07-15  6:21                       ` Trilok Soni
2009-07-15  6:48                         ` Arve Hjønnevåg
2009-07-19 21:23                       ` Pavel Machek
2009-07-20  3:43                         ` Arve Hjønnevåg
2009-07-20 10:47                           ` Pavel Machek [this message]
2009-07-21 10:11                           ` Pavel Machek
2009-07-22  1:12                             ` Arve Hjønnevåg
2009-07-23 21:25                               ` Pavel Machek
2009-07-24  0:11                                 ` Arve Hjønnevåg
2009-07-27 23:14                                   ` Pavel Machek
2009-07-27 23:38                                     ` Arve Hjønnevåg
2009-07-14 10:02               ` Pavel Machek
2009-07-14  1:48             ` Daniel Walker
2009-07-14  6:47               ` Trilok Soni
2009-07-14  0:17           ` Brian Swetland
2009-07-14  9:47             ` 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=20090720104726.GE19341@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=arve@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=swetland@google.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.