[lkml]   [2019]   [Mar]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Subjectlinux-next: manual merge of the drivers-x86 tree with the watchdog tree
Hi all,

Today's linux-next merge of the drivers-x86 tree got a conflict in:


between commit:

9f03161a1bd8 ("platform_data/mlxreg: additions for Mellanox watchdog driver.")

from the watchdog tree and commit:

9b28aa1d0eae ("platform_data/mlxreg: Document fixes for core platform data")

from the drivers-x86 tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

Stephen Rothwell

diff --cc include/linux/platform_data/mlxreg.h
index 31f7c25a44da,1b2f86f96743..000000000000
--- a/include/linux/platform_data/mlxreg.h
+++ b/include/linux/platform_data/mlxreg.h
@@@ -120,12 -109,9 +122,12 @@@ struct mlxreg_core_item
* struct mlxreg_core_platform_data - platform data:
- * @led_data: led private data;
+ * @data: instance private data;
* @regmap: register map of parent device;
- * @counter: number of led instances;
+ * @counter: number of instances;
+ * @features: supported features of device;
+ * @version: implementation version;
+ * @identity: device identity name;
struct mlxreg_core_platform_data {
struct mlxreg_core_data *data;
[unhandled content-type:application/pgp-signature]
 \ /
  Last update: 2019-03-04 04:38    [W:0.060 / U:0.292 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site