From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: "Antipov, Dmitriy" <Dmitriy.Antipov@softline.com>
Cc: "dmantipov@yandex.ru" <dmantipov@yandex.ru>,
"hdegoede@redhat.com" <hdegoede@redhat.com>,
"lvc-project@linuxtesting.org" <lvc-project@linuxtesting.org>,
"platform-driver-x86@vger.kernel.org"
<platform-driver-x86@vger.kernel.org>,
"jlee@suse.com" <jlee@suse.com>
Subject: Re: [lvc-project] [PATCH] platform/x86: acer-wmi: fix fan mode setup in WMID_gaming_set_fan_mode()
Date: Thu, 19 Dec 2024 14:08:31 +0200 (EET) [thread overview]
Message-ID: <e86854aa-f2d4-4bde-9fe7-a6da91c41a76@linux.intel.com> (raw)
In-Reply-To: <f10a93f710667be330620dd550c164f0dbbd6799.camel@softline.com>
[-- Attachment #1: Type: text/plain, Size: 818 bytes --]
On Thu, 19 Dec 2024, Antipov, Dmitriy wrote:
> On Tue, 2024-12-17 at 16:47 +0200, Ilpo Järvinen wrote:
>
> > When you use an "automated" tools to find "problems", you have to read
>
> Such a sentence would have much more effect if correctly rephrased.
> For example: "Since I'm paying you, you have to [whatever]" etc.
No, that's not an optional thing when it comes to problems from automated
tools. We've a special policy when it comes to contributions that
originate from running analysis tools such as SVACE. For details, please
see:
Documentation/process/researcher-guidelines.rst
In particular, please check the list after "Answer". It list among
other things "How could the problem be reached on a running system?". To
answer that, you need to understand the related code.
--
i.
prev parent reply other threads:[~2024-12-19 12:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-16 13:24 [PATCH] platform/x86: acer-wmi: fix fan mode setup in WMID_gaming_set_fan_mode() Dmitry Antipov
2024-12-17 0:50 ` Armin Wolf
2024-12-17 14:47 ` Ilpo Järvinen
2024-12-19 11:25 ` [lvc-project] " Antipov, Dmitriy
2024-12-19 12:08 ` Ilpo Järvinen [this message]
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=e86854aa-f2d4-4bde-9fe7-a6da91c41a76@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=Dmitriy.Antipov@softline.com \
--cc=dmantipov@yandex.ru \
--cc=hdegoede@redhat.com \
--cc=jlee@suse.com \
--cc=lvc-project@linuxtesting.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.