Received-SPF: pass (google.com: domain of linux-kernel+bounces-111269-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
From: =?UTF-8?q?Ilpo=20J=C3=A4rvinen?= <ilpo.jarvinen@linux.intel.com>
Date: Fri, 22 Mar 2024 12:05:57 +0200 (EET)
To: Ivor Wanders <ivor@iwanders.net>
cc: Hans de Goede <hdegoede@redhat.com>, LKML <linux-kernel@vger.kernel.org>, 
    luzmaximilian@gmail.com, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2 1/1] platform/surface: platform_profile: add fan
 profile switching
In-Reply-To: <20240321212521.3834-1-ivor@iwanders.net>
Message-ID: <424d43f0-bcbc-f904-03bf-9f4c0488d706@linux.intel.com>
References: <71c9e24b-c64b-581c-87f0-fb0c58066ceb@linux.intel.com> <20240321212521.3834-1-ivor@iwanders.net>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/mixed; BOUNDARY="8323328-787903796-1711101549=:1315"
Content-ID: <cb297c0a-ff37-eb02-7a38-466af40263f9@linux.intel.com>

  This message is in MIME format.  The first part should be readable text,
  while the remaining parts are likely unreadable without MIME-aware tools.

--8323328-787903796-1711101549=:1315
Content-Type: text/plain; CHARSET=ISO-8859-15
Content-Transfer-Encoding: QUOTED-PRINTABLE
Content-ID: <05229851-2721-282d-8862-61abe999deb4@linux.intel.com>

On Thu, 21 Mar 2024, Ivor Wanders wrote:

> > Reviewed-by: Ilpo J=E4rvinen <ilpo.jarvinen@linux.intel.com>
>=20
> What is the process to get this merged if no further review is coming in?
> Maximilian Luz approved v1 already. I just confirmed this patch still
> applies cleanly on the latest upstream master.

Hi Ivor,

We're currently in the two weeks merge window (the time between kernel=20
release and the next -rc1). Usually, nothing happens during it for new=20
patches that are not fixes (there might be exceptions with some=20
subsystems but that's a good general rule and even with fixes severity=20
matters a lot if they are considered until -rc1 is out).
=20
Maintainer will consider your patch after the merge window (in this case,=
=20
it will be Hans' turn for 3.10 cycle to handle for-next while I handle=20
fixes branch).

> Do I need to send v3 with
> this reviewed-by tag added to the commit or can this version be merged?

Our tools take care of the tags such as Reviewed-by when they're made=20
against the latest version, there is no need to resubmit just because of=20
tags people give to your patch.

(That being said, whenever submitting a new version for other reasons,=20
remember to add the tags to the new version because tools only capture=20
them for the latest version.)

--=20
 i.
--8323328-787903796-1711101549=:1315--