mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Len Brown <lenb@kernel.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alan Jenkins <alan-jenkins@tuffmail.co.uk>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: linux-next: manual merge of the acpi tree with Linus' tree
Date: Wed, 16 Dec 2009 13:00:49 +1100	[thread overview]
Message-ID: <20091216130049.60a1774c.sfr@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1889 bytes --]

Hi Len,

Today's linux-next merge of the acpi tree got a conflict in
drivers/platform/x86/eeepc-laptop.c between commit
471452104b8520337ae2fb48c4e61cd4896e025d ("const: constify remaining
dev_pm_ops") from Linus' tree and commit
52bbe3c7b413d656833686f9f08e5dcab3786eeb ("eeepc-laptop: code movement")
from the acpi tree.

The latter just moved the code that the former was updating.  I fixed it
up (see below) and can carry the fix for a while.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc drivers/platform/x86/eeepc-laptop.c
index e647a85,d07a4c0..0000000
--- a/drivers/platform/x86/eeepc-laptop.c
+++ b/drivers/platform/x86/eeepc-laptop.c
@@@ -866,16 -862,37 +862,37 @@@ static int eeepc_hotk_restore(struct de
  	return 0;
  }
  
 -static struct dev_pm_ops eeepc_pm_ops = {
++static const struct dev_pm_ops eeepc_pm_ops = {
+ 	.thaw = eeepc_hotk_thaw,
+ 	.restore = eeepc_hotk_restore,
+ };
+ 
+ static struct platform_driver platform_driver = {
+ 	.driver = {
+ 		.name = EEEPC_LAPTOP_FILE,
+ 		.owner = THIS_MODULE,
+ 		.pm = &eeepc_pm_ops,
+ 	}
+ };
+ 
  /*
-  * Hwmon
+  * Hwmon device
   */
+ 
+ #define EEEPC_EC_SC00      0x61
+ #define EEEPC_EC_FAN_PWM   (EEEPC_EC_SC00 + 2) /* Fan PWM duty cycle (%) */
+ #define EEEPC_EC_FAN_HRPM  (EEEPC_EC_SC00 + 5) /* High byte, fan speed (RPM) */
+ #define EEEPC_EC_FAN_LRPM  (EEEPC_EC_SC00 + 6) /* Low byte, fan speed (RPM) */
+ 
+ #define EEEPC_EC_SFB0      0xD0
+ #define EEEPC_EC_FAN_CTRL  (EEEPC_EC_SFB0 + 3) /* Byte containing SF25  */
+ 
  static int eeepc_get_fan_pwm(void)
  {
- 	int value = 0;
+ 	u8 value = 0;
  
- 	read_acpi_int(NULL, EEEPC_EC_FAN_PWM, &value);
- 	value = value * 255 / 100;
- 	return (value);
+ 	ec_read(EEEPC_EC_FAN_PWM, &value);
+ 	return value * 255 / 100;
  }
  
  static void eeepc_set_fan_pwm(int value)

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

             reply	other threads:[~2009-12-16  2:01 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-16  2:00 Stephen Rothwell [this message]
2009-12-23 22:11 Stephen Rothwell
2009-12-23 22:39 ` Stephen Rothwell
2009-12-24  0:02   ` Stephen Rothwell
2009-12-24  5:02   ` Len Brown
2009-12-24 12:26     ` Stephen Rothwell
2009-12-24 20:05       ` Len Brown
2009-12-25  0:19         ` Stephen Rothwell
2010-01-18  2:56 Stephen Rothwell
2010-01-20  6:12 ` Len Brown
2010-01-20  6:29   ` Stephen Rothwell
2010-05-12  1:21 Stephen Rothwell
2012-03-30  0:46 Stephen Rothwell
2012-10-04  1:40 Stephen Rothwell
2012-10-07 23:49 Stephen Rothwell

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=20091216130049.60a1774c.sfr@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=alan-jenkins@tuffmail.co.uk \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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

all inboxes | Powered by JetHome®