X86 platform drivers
 help / color / mirror / Atom feed
From: Mario Limonciello <superm1@gmail.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Mario Limonciello" <mario.limonciello@amd.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
	"open list:X86 PLATFORM DRIVERS"
	<platform-driver-x86@vger.kernel.org>,
	Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH] platform/x86/amd: Extend Framework 13 quirk to more BIOSes
Date: Tue, 16 Apr 2024 07:37:03 -0500	[thread overview]
Message-ID: <f2ae6813-0e88-4d64-8dd5-465c02061cb6@gmail.com> (raw)
In-Reply-To: <ace9e5fe-0565-b24d-5394-ba4bd9f4305c@linux.intel.com>



On 4/16/24 07:24, Ilpo Järvinen wrote:
> On Wed, 10 Apr 2024, Mario Limonciello wrote:
> 
>> BIOS 03.05 still hasn't fixed the spurious IRQ1 issue.  As it's still
>> being worked on there is still a possiblitiy that it won't need to
>> apply to future BIOS releases.
> 
> Hi Mario,
> 
> Could you explain/confirm what the second sentence is supposed to mean?
> Mainly I mean "it won't need to apply to future", did you perhaps mean it
> might need to be applied still to some future versions too besides this
> one because the fix is still being worked on, or what?
> 
> There's also "possiblitiy" typo, in case you end up rewriting the message
> and send v2.
> 

You probably missed my follow up message in the thread, I tried to 
explain in more detail (and also caught the same typo; sorry!)

https://lore.kernel.org/platform-driver-x86/ace9e5fe-0565-b24d-5394-ba4bd9f4305c@linux.intel.com/T/#mcf25cbfbd9dc5f4aace5b58c56a7f91671b2f0cc

  reply	other threads:[~2024-04-16 12:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-10 14:10 [PATCH] platform/x86/amd: Extend Framework 13 quirk to more BIOSes Mario Limonciello
2024-04-10 16:34 ` Mario Limonciello
2024-04-15 13:54 ` Hans de Goede
2024-04-16 12:24 ` Ilpo Järvinen
2024-04-16 12:37   ` Mario Limonciello [this message]
2024-04-16 12:42     ` Ilpo Järvinen
2024-04-16 12:44 ` 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=f2ae6813-0e88-4d64-8dd5-465c02061cb6@gmail.com \
    --to=superm1@gmail.com \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=mario.limonciello@amd.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