linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Lezcano <daniel.lezcano@linaro.org>,
	Zhang Rui <rui.zhang@intel.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Ido Schimmel <idosch@nvidia.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Vadim Pasternak <vadimp@nvidia.com>
Subject: linux-next: manual merge of the thermal tree with Linus' tree
Date: Mon, 15 Aug 2022 09:20:46 +1000	[thread overview]
Message-ID: <20220815092046.644a0afa@canb.auug.org.au> (raw)

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

Hi all,

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

  drivers/net/ethernet/mellanox/mlxsw/core_thermal.c

between commits:

  03978fb88b06 ("mlxsw: core_thermal: Use common define for thermal zone name length")
  ef0df4fa324a ("mlxsw: core_thermal: Extend internal structures to support multi thermal areas")

from Linus' tree and commit:

  9b5e2c897cd1 ("Revert "mlxsw: core: Add the hottest thermal zone detection"")

from the thermal 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.

-- 
Cheers,
Stephen Rothwell

diff --cc drivers/net/ethernet/mellanox/mlxsw/core_thermal.c
index 3548fe1df7c8,373a77c3da02..000000000000
--- a/drivers/net/ethernet/mellanox/mlxsw/core_thermal.c
+++ b/drivers/net/ethernet/mellanox/mlxsw/core_thermal.c
@@@ -21,7 -21,7 +21,6 @@@
  #define MLXSW_THERMAL_ASIC_TEMP_HOT	105000	/* 105C */
  #define MLXSW_THERMAL_HYSTERESIS_TEMP	5000	/* 5C */
  #define MLXSW_THERMAL_MODULE_TEMP_SHIFT	(MLXSW_THERMAL_HYSTERESIS_TEMP * 2)
- #define MLXSW_THERMAL_TEMP_SCORE_MAX	GENMASK(31, 0)
 -#define MLXSW_THERMAL_ZONE_MAX_NAME	16
  #define MLXSW_THERMAL_MAX_STATE	10
  #define MLXSW_THERMAL_MIN_STATE	2
  #define MLXSW_THERMAL_MAX_DUTY	255
@@@ -101,9 -91,10 +100,7 @@@ struct mlxsw_thermal 
  	struct thermal_cooling_device *cdevs[MLXSW_MFCR_PWMS_MAX];
  	u8 cooling_levels[MLXSW_THERMAL_MAX_STATE + 1];
  	struct mlxsw_thermal_trip trips[MLXSW_THERMAL_NUM_TRIPS];
- 	unsigned int tz_highest_score;
- 	struct thermal_zone_device *tz_highest_dev;
 -	struct mlxsw_thermal_module *tz_module_arr;
 -	u8 tz_module_num;
 -	struct mlxsw_thermal_module *tz_gearbox_arr;
 -	u8 tz_gearbox_num;
 +	struct mlxsw_thermal_area line_cards[];
  };
  
  static inline u8 mlxsw_state_to_duty(int state)

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

             reply	other threads:[~2022-08-14 23:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14 23:20 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-09-26 23:50 linux-next: manual merge of the thermal tree with Linus' tree Stephen Rothwell
2019-09-20 12:46 Mark Brown
2012-11-05  0:46 Stephen Rothwell
2012-11-05  1:17 ` Zhang Rui
2012-11-05  6:47 ` Zhang Rui

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=20220815092046.644a0afa@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=daniel.lezcano@linaro.org \
    --cc=davem@davemloft.net \
    --cc=idosch@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=vadimp@nvidia.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 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).