From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
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
Date: Fri, 22 Mar 2024 12:05:57 +0200 (EET) [thread overview]
Message-ID: <424d43f0-bcbc-f904-03bf-9f4c0488d706@linux.intel.com> (raw)
In-Reply-To: <20240321212521.3834-1-ivor@iwanders.net>
[-- Attachment #1: Type: text/plain, Size: 1314 bytes --]
On Thu, 21 Mar 2024, Ivor Wanders wrote:
> > Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.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.
next prev parent reply other threads:[~2024-03-22 10:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 22:37 [PATCH v2 0/1] platform/surface: platform_profile: add fan profile Ivor Wanders
2024-03-14 22:37 ` [PATCH v2 1/1] platform/surface: platform_profile: add fan profile switching Ivor Wanders
2024-03-15 11:05 ` Ilpo Järvinen
2024-03-21 21:25 ` Ivor Wanders
2024-03-22 10:05 ` Ilpo Järvinen [this message]
2024-03-22 11:43 ` Ivor Wanders
2024-03-25 14:56 ` Hans de Goede
2024-03-26 11:43 ` Ivor Wanders
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=424d43f0-bcbc-f904-03bf-9f4c0488d706@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=hdegoede@redhat.com \
--cc=ivor@iwanders.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luzmaximilian@gmail.com \
--cc=platform-driver-x86@vger.kernel.org \
/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
all inboxes | Powered by JetHome®