From: Ido Schimmel <idosch@nvidia.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Networking <netdev@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Petr Machata <petrm@nvidia.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Subject: Re: linux-next: manual merge of the net-next tree with the pm tree
Date: Thu, 22 Aug 2024 11:17:33 +0300 [thread overview]
Message-ID: <Zsb0HXmnllt9SPWM@shredder.mtl.com> (raw)
In-Reply-To: <20240822110430.08a98b0d@canb.auug.org.au>
On Thu, Aug 22, 2024 at 11:04:30AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the net-next tree got a conflict in:
>
> drivers/net/ethernet/mellanox/mlxsw/core_thermal.c
>
> between commit:
>
> 019c393b17cb ("mlxsw: core_thermal: Use the .should_bind() thermal zone callback")
>
> from the pm tree and commit:
>
> fb76ea1d4b12 ("mlxsw: core_thermal: Make mlxsw_thermal_module_{init, fini} symmetric")
>
> from the net-next 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.
Thanks Stephen. Looks correct to me and also fits the one posted by
Rafael:
https://lore.kernel.org/netdev/CAJZ5v0hX+HyNB5Xqwr6Q44rgAThNLqp5PUQXN-uTC+cDqdjpqA@mail.gmail.com/
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc drivers/net/ethernet/mellanox/mlxsw/core_thermal.c
> index 0c50a0cc316d,303d2ce4dc1e..000000000000
> --- a/drivers/net/ethernet/mellanox/mlxsw/core_thermal.c
> +++ b/drivers/net/ethernet/mellanox/mlxsw/core_thermal.c
> @@@ -389,12 -450,8 +388,9 @@@ mlxsw_thermal_module_init(struct mlxsw_
> struct mlxsw_thermal_area *area, u8 module)
> {
> struct mlxsw_thermal_module *module_tz;
> + int i;
>
> module_tz = &area->tz_module_arr[module];
> - /* Skip if parent is already set (case of port split). */
> - if (module_tz->parent)
> - return;
> module_tz->module = module;
> module_tz->slot_index = area->slot_index;
> module_tz->parent = thermal;
> @@@ -404,8 -461,8 +400,10 @@@
> sizeof(thermal->trips));
> memcpy(module_tz->cooling_states, default_cooling_states,
> sizeof(thermal->cooling_states));
> + for (i = 0; i < MLXSW_THERMAL_NUM_TRIPS; i++)
> + module_tz->trips[i].priv = &module_tz->cooling_states[i];
> +
> + return mlxsw_thermal_module_tz_init(module_tz);
> }
>
> static void mlxsw_thermal_module_fini(struct mlxsw_thermal_module *module_tz)
next prev parent reply other threads:[~2024-08-22 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 1:04 linux-next: manual merge of the net-next tree with the pm tree Stephen Rothwell
2024-08-22 8:17 ` Ido Schimmel [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-05 0:26 Stephen Rothwell
2024-03-05 10:52 ` Rafael J. Wysocki
2024-03-05 13:23 ` Alex Elder
2023-04-03 1:44 Stephen Rothwell
2013-06-26 3:08 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=Zsb0HXmnllt9SPWM@shredder.mtl.com \
--to=idosch@nvidia.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=petrm@nvidia.com \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=sfr@canb.auug.org.au \
/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).