All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Scardovi <scardracs@disroot.org>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: corentin.chary@gmail.com, denis.benato@linux.dev,
	Hans de Goede <hansg@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	luke@ljones.dev, platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH v2] platform/x86: asus-armoury: add support for G614PR
Date: Mon, 29 Jun 2026 13:27:56 +0200	[thread overview]
Message-ID: <w5lQn2_tRS-_d31lk_IeWw@disroot.org> (raw)
In-Reply-To: <e7d71740-8e69-0433-aa49-d5023bd59a98@linux.intel.com>

Hi Ilpo,

In data lunedì 29 giugno 2026 13:04:51 Ora legale dell’Europa centrale, Ilpo Järvinen ha scritto:
> On Sat, 27 Jun 2026, Marco Scardovi wrote:
> 
> > you around? I'd need this to be fixed to set the correct values.
> 
> I'm not sure what the context here is, whether you're just asking for the 
> patch to be applied (which is entirely unnecessary, as long as the patch 
> appears in the patchwork's queue, I've not lost it), or if you're saying 
> there's a problem in v2 patch?
>
There was a problem with the v1 patch, where I wrote 4 values wrongly,
so I posted the v2 with the correct values.
> 
> Usually, the merge window is quiet time anyway when it comes to applying 
> patches so don't expect much to happen for them until clearly after rc1 
> (= not right after rc1 has been published, because the piled up patch 
> queue will take some time to drain and there are other things to do around 
> that timeframe as well).
> 
I see, sorry for bothering. I'm new to the kernel patching workflow and
still learning how it works.



  reply	other threads:[~2026-06-29 19:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 15:21 [PATCH] platform/x86: asus-armoury: add support for G614PR Marco Scardovi
2026-06-10 17:54 ` Denis Benato
2026-06-11 15:02 ` Ilpo Järvinen
2026-06-11 15:53   ` Marco Scardovi
2026-06-14  8:44   ` [PATCH v2 0/1] " Marco Scardovi
2026-06-14  8:44     ` [PATCH v2] " Marco Scardovi
2026-06-14 12:33       ` Denis Benato
2026-06-15 15:07         ` Marco Scardovi
2026-06-27  6:18           ` Marco Scardovi
2026-06-29 11:04             ` Ilpo Järvinen
2026-06-29 11:27               ` Marco Scardovi [this message]
2026-06-30 14:18                 ` Ilpo Järvinen

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=w5lQn2_tRS-_d31lk_IeWw@disroot.org \
    --to=scardracs@disroot.org \
    --cc=corentin.chary@gmail.com \
    --cc=denis.benato@linux.dev \
    --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 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.