[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <MW5PR11MB58101FBF45EFEC362A8A1E18A3442@MW5PR11MB5810.namprd11.prod.outlook.com>
Date: Thu, 8 Feb 2024 13:26:15 +0000
From: "Korenblit, Miriam Rachel" <miriam.rachel.korenblit@...el.com>
To: Johannes Berg <johannes@...solutions.net>, Kalle Valo <kvalo@...nel.org>,
"Rafael J. Wysocki" <rjw@...ysocki.net>
CC: Linux PM <linux-pm@...r.kernel.org>, "linux-wireless@...r.kernel.org"
<linux-wireless@...r.kernel.org>, LKML <linux-kernel@...r.kernel.org>,
"Daniel Lezcano" <daniel.lezcano@...aro.org>, Stanislaw Gruszka
<stanislaw.gruszka@...ux.intel.com>
Subject: RE: [PATCH v1 0/3] iwlwifi: mvm: Thermal management fixes
> On Thu, 2024-02-08 at 08:13 +0200, Kalle Valo wrote:
> > >
> > > If possible, I'd like to route the $subject series through the
> > > thermal tree, it is requisite for the above one.
> >
> > iwlwifi is getting a lot of patches lately, though I don't know if any
> > of them touch the thermal stuff. But if this patchset goes to the
> > thermal I am a bit worried about conflicts.
>
> Should be OK, I checked now and apart from the trivial change in mvm.h this is
> contained in tt.c, which isn't touched (even in our internal feeder tree) after
> commit 0106cce5ad0c ("wifi: iwlwifi: mvm: drop NULL pointer check in
> iwl_mvm_tzone_set_trip_temp()").
>
> But I'll let Miri send an Acked-by to go through your tree, since she's the
> maintainer :-)
>
> Johannes
Hi,
This seems fine to go through your tree, as Johannes said, we don't expect any conflicts.
Thanks,
Miri
Powered by blists - more mailing lists