From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>,
"Wolfram Sang" <wsa+renesas@sang-engineering.com>
Cc: <tiwai@suse.com>, <mika.westerberg@linux.intel.com>,
<linux-sound@vger.kernel.org>, <linux-spi@vger.kernel.org>,
<linux-i2c@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<patches@opensource.cirrus.com>
Subject: Re: [PATCH v2 0/3] ALSA: Add support for new HP G12 laptops
Date: Tue, 6 Aug 2024 12:06:25 +0100 [thread overview]
Message-ID: <554660e1-01ea-4bb4-877f-fd8deb527ce7@opensource.cirrus.com> (raw)
In-Reply-To: <8734njl7my.wl-tiwai@suse.de>
On 5/8/24 09:02, Takashi Iwai wrote:
> On Fri, 02 Aug 2024 17:22:12 +0200,
> Richard Fitzgerald wrote:
>>
>> Add support for HP G12 laptops that use CS35L54 or CS35L56 amplifiers
>> with Realtek HDA codecs. Some of these use the same SSID for models with
>> CS35L54 and models with CS35L56 so the ACPI entries are examined to
>> determine which amp is present.
>>
>> To avoid having to #ifdef around this code we've fixed the definitions
>> of SPI and I2C functions that were not correctly supplying dummy functions
>> when the real functions are not in the build.
>>
>> Changes since V1:
>> Added I2C and SPI patches to provide dummy functions.
>>
>> Richard Fitzgerald (2):
>> spi: Add empty versions of ACPI functions
>> i2c: Fix conditional for substituting empty ACPI functions
>>
>> Simon Trimmer (1):
>> ALSA: hda/realtek: Add support for new HP G12 laptops
>
> Hm, the 3rd patch requires both patch 1 and 2, and now those seem to
> have been applied to two different trees, which makes hard to apply
> the 3rd one.
>
> Mark, Wolfram, will you guys submit PR for 6.11-rc3 including the
> patch 1 and 2? If so, I can apply the patch 3 later on top of
> 6.11-rc3.
>
> Or, I'd need to pull from both of you and apply the patch 3.
>
>
> thanks,
>
> Takashi
We've just noticed that the SPI patches have gone into for-6.12.
We really hoped that we could get the main patch (G12 support) into
6.11 (yes, I know, I didn't actually say that we were targeting 6.11 -
sorry).
next prev parent reply other threads:[~2024-08-06 11:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-02 15:22 [PATCH v2 0/3] ALSA: Add support for new HP G12 laptops Richard Fitzgerald
2024-08-02 15:22 ` [PATCH v2 1/3] spi: Add empty versions of ACPI functions Richard Fitzgerald
2024-08-02 15:22 ` [PATCH v2 2/3] i2c: Fix conditional for substituting empty " Richard Fitzgerald
2024-08-04 14:34 ` Wolfram Sang
2024-08-02 15:22 ` [PATCH v2 3/3] ALSA: hda/realtek: Add support for new HP G12 laptops Richard Fitzgerald
2024-08-02 21:49 ` (subset) [PATCH v2 0/3] ALSA: " Mark Brown
2024-08-05 8:02 ` Takashi Iwai
2024-08-06 11:06 ` Richard Fitzgerald [this message]
2024-08-06 11:19 ` Takashi Iwai
2024-08-06 11:29 ` Wolfram Sang
2024-08-06 11:41 ` Takashi Iwai
2024-08-12 6:53 ` Wolfram Sang
2024-08-12 7:04 ` Takashi Iwai
2024-08-05 19:40 ` Mark Brown
2024-08-12 7:19 ` Takashi Iwai
2024-08-12 7:20 ` Takashi Iwai
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=554660e1-01ea-4bb4-877f-fd8deb527ce7@opensource.cirrus.com \
--to=rf@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
--cc=patches@opensource.cirrus.com \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
--cc=wsa+renesas@sang-engineering.com \
/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