public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Luke Jones <luke@ljones.dev>
Cc: platform-driver-x86@vger.kernel.org,
	Hans de Goede <hdegoede@redhat.com>,
	 LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/1] platform/x86: asus-wmi: add support for Vivobook GPU MUX
Date: Wed, 20 Mar 2024 14:02:27 +0200 (EET)	[thread overview]
Message-ID: <c7e375df-e709-a348-a240-0d6d8bde1840@linux.intel.com> (raw)
In-Reply-To: <fbd2dc65-33d9-447e-9edb-78df370778be@app.fastmail.com>

[-- Attachment #1: Type: text/plain, Size: 1215 bytes --]

On Wed, 20 Mar 2024, Luke Jones wrote:

> On Wed, 20 Mar 2024, at 1:26 AM, Ilpo Järvinen wrote:
> > On Sun, 10 Mar 2024, Luke D. Jones wrote:
> > 
> > > Adjust existing MUX support to select whichever MUX support is available
> > > so that ASUS Vivobook MUX can also be used if detected.
> > 
> > This description is a bit on the short side. It wouldn't have hurt to 
> > first state that Vivobooks come with a GPU MUX WMI that has a different 
> > WMI device ID. I can infer that after reading the diff but the description 
> > should not require reading the patch.
> 
> Would you prefer I changed the commit message?

I kind of tried to give some leeway for you and not sound like I'm 
enforcing you to do it but yes, I do prefer good commit messages myself
(I know that after reading this patch the reasons will be pretty obvious 
to anyone so it's not a grave problem). So half it was said future 
patches in mind, half you can do it if you want also for this patch.

But since you'll need to resend this anyway because of the 
independent/series issue I mentioned in my reply to one of the other 
patches, just cover this minor thing as well, it's one sentence after
all.

-- 
 i.

  reply	other threads:[~2024-03-20 12:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-10  5:53 [PATCH v2 0/1] asus-wmi: add support for Vivobook GPU MUX Luke D. Jones
2024-03-10  5:53 ` [PATCH v2 1/1] platform/x86: " Luke D. Jones
2024-03-19 12:26   ` Ilpo Järvinen
2024-03-20  1:04     ` Luke Jones
2024-03-20 12:02       ` Ilpo Järvinen [this message]
2024-03-20 20:07         ` Luke Jones

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=c7e375df-e709-a348-a240-0d6d8bde1840@linux.intel.com \
    --to=ilpo.jarvinen@linux.intel.com \
    --cc=hdegoede@redhat.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