linux-kernel - Re: [PATCH v2 1/1] platform/surface: platform

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <424d43f0-bcbc-f904-03bf-9f4c0488d706@linux.intel.com>
Date: Fri, 22 Mar 2024 12:05:57 +0200 (EET)
From: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
To: Ivor Wanders <ivor@...nders.net>
cc: Hans de Goede <hdegoede@...hat.com>, LKML <linux-kernel@...r.kernel.org>, 
    luzmaximilian@...il.com, platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH v2 1/1] platform/surface: platform_profile: add fan
 profile switching

On Thu, 21 Mar 2024, Ivor Wanders wrote:

> > Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@...ux.intel.com>
> 
> 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 
release and the next -rc1). Usually, nothing happens during it for new 
patches that are not fixes (there might be exceptions with some 
subsystems but that's a good general rule and even with fixes severity 
matters a lot if they are considered until -rc1 is out).

Maintainer will consider your patch after the merge window (in this case, 
it will be Hans' turn for 3.10 cycle to handle for-next while I handle 
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 
against the latest version, there is no need to resubmit just because of 
tags people give to your patch.

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

-- 
 i.