From: Takashi Iwai <tiwai@suse.de>
To: Lucy Thrun <lucy.thrun@digital-rabbithole.de>
Cc: tiwai@suse.de, perex@perex.cz, linux-sound@vger.kernel.org,
lkp@intel.com
Subject: Re: [PATCH v2 0/2] Regarding recent patches
Date: Tue, 10 Jun 2025 20:24:36 +0200 [thread overview]
Message-ID: <877c1jxxnf.wl-tiwai@suse.de> (raw)
In-Reply-To: <20250610175012.918-1-lucy.thrun@digital-rabbithole.de>
On Tue, 10 Jun 2025 19:50:10 +0200,
Lucy Thrun wrote:
>
> Hello Takashi,
>
> Thank you for the response to my last patches.
> I've created them in response to the kernel test warnings.
> I apologise for the left out description, while I have experience with git,
> I'm new to using it via email submission and must have not realised after getting home from work.
> I hope the following patches are suiting your requirements better.
>
> Regards,
> A Linux enthusiast trying to get their soundcard to work without having to deal with dkms after every distro hop,
> Lucy Thrun
>
> Lucy Thrun (2):
> ALSA: hda/ca0132: Fix using plain integer as NULL pointer in
> add_tuning_control
> ALSA: hda/ca0132: Fix buffer overflow in add_tuning_control
Applied both patches now. Thanks!
Takashi
prev parent reply other threads:[~2025-06-10 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-10 17:50 [PATCH v2 0/2] Regarding recent patches Lucy Thrun
2025-06-10 17:50 ` [PATCH v2 1/2] ALSA: hda/ca0132: Fix using plain integer as NULL pointer in add_tuning_control Lucy Thrun
2025-06-10 17:50 ` [PATCH v2 2/2] ALSA: hda/ca0132: Fix buffer overflow " Lucy Thrun
2025-06-10 18:24 ` [PATCH v2 0/2] Regarding recent patches Geraldo Nascimento
2025-06-10 18:24 ` Takashi Iwai [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=877c1jxxnf.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=linux-sound@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lucy.thrun@digital-rabbithole.de \
--cc=perex@perex.cz \
/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