mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Denis Benato <benato.denis96@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Denis Benato" <denis.benato@linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
	platform-driver-x86@vger.kernel.org,
	Hans de Goede <hansg@kernel.org>,
	"Luke D . Jones" <luke@ljones.dev>,
	Mateusz Schyboll <dragonn@op.pl>
Subject: Re: [PATCH] platform/x86: asus-armoury: add support for GU605CR
Date: Mon, 29 Dec 2025 15:56:45 +0100	[thread overview]
Message-ID: <79bb267b-d24b-40a8-ae82-fa4d813cb234@gmail.com> (raw)
In-Reply-To: <491d2182-930c-46fd-20f6-5d6e7f5ffeb7@linux.intel.com>


On 12/29/25 14:09, Ilpo Järvinen wrote:
> On Thu, 25 Dec 2025, Denis Benato wrote:
>
>> Add TDP data for laptop model GU605CR.
>>
>> Signed-off-by: Denis Benato <denis.benato@linux.dev>
> Hi Denis,
>
> I've applied these 4 to the review-ilpo-fixes branch, but next time please 
> please make them a series instead of sending 4 very similar ID addition 
> changes to the same file independently.
>
> A series is easier for me to apply as a whole than 4 patches individually. 
> Also, series won't cause some messy misapplication as easily as individual 
> patches that can be applied in order different from what was used by the 
> submitter to create them (it seems there were no context conflicts with 
> these but I had to check that == extra work for me).
>
Hi,

Thank you, I'll keep this in mind.

      reply	other threads:[~2025-12-29 14:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-25  2:38 Denis Benato
2025-12-29 13:09 ` Ilpo Järvinen
2025-12-29 14:56   ` Denis Benato [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=79bb267b-d24b-40a8-ae82-fa4d813cb234@gmail.com \
    --to=benato.denis96@gmail.com \
    --cc=denis.benato@linux.dev \
    --cc=dragonn@op.pl \
    --cc=hansg@kernel.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    --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®