public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Jiri Kosina <jikos@jikos•cz>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
	Srinivas Pandruvada <srinivas.pandruvada@linux•intel.com>
Subject: linux-next: manual merge of the hid tree with Linus' tree
Date: Tue, 24 Feb 2015 11:00:48 +1100	[thread overview]
Message-ID: <20150224110048.209cacba@canb.auug.org.au> (raw)

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

Hi Jiri,

Today's linux-next merge of the hid tree got a conflict in
drivers/iio/common/hid-sensors/hid-sensor-trigger.c between commit
2b89635e9a9e ("iio: hid_sensor_hub: Common PM functions") from Linus'
tree and commit 6adc83fca74a ("HID: hid-sensor-hub: Enhance get feature
report API") from the hid tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc drivers/iio/common/hid-sensors/hid-sensor-trigger.c
index 2f1d535b94c4,910e82a7d06e..000000000000
--- a/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
+++ b/drivers/iio/common/hid-sensors/hid-sensor-trigger.c
@@@ -80,11 -77,8 +81,11 @@@ static int _hid_sensor_power_state(stru
  	}
  
  	sensor_hub_get_feature(st->hsdev, st->power_state.report_id,
- 					st->power_state.index,
- 					&state_val);
+ 			       st->power_state.index,
+ 			       sizeof(state_val), &state_val);
 +	if (state && poll_value)
 +		msleep_interruptible(poll_value * 2);
 +
  	return 0;
  }
  EXPORT_SYMBOL(hid_sensor_power_state);

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-02-24  0:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24  0:00 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-08-15  1:53 linux-next: manual merge of the hid tree with Linus' tree Stephen Rothwell
2022-04-21 23:33 Stephen Rothwell
2014-10-31  0:58 Stephen Rothwell
2014-03-17  2:32 Stephen Rothwell
2014-02-20  2:04 Stephen Rothwell
2014-02-20  2:03 Stephen Rothwell
2013-03-28  0:40 Stephen Rothwell
2012-09-10  1:33 Stephen Rothwell
2012-09-10  5:49 ` Marek Vasut
2012-06-27  1:05 Stephen Rothwell
2011-10-11  3:37 Stephen Rothwell
2011-10-11 10:52 ` Jiri Kosina
2010-11-09  1:33 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=20150224110048.209cacba@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=jikos@jikos$(echo .)cz \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=srinivas.pandruvada@linux$(echo .)intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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