From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Dominik Brodowski <linux@dominikbrodowski.net>,
Mark Brown <broonie@kernel.org>,
lgirdwood@gmail.com, perex@perex.cz, tiwai@suse.com,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
pierre-louis.bossart@linux.intel.com,
kai.vehmanen@linux.intel.com, ranjani.sridharan@linux.intel.com,
linux-kernel@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Oops in hdac_hda_dev_probe (6.7-rc7)
Date: Wed, 3 Jan 2024 18:24:53 +0200 [thread overview]
Message-ID: <d61245f1-cd4a-4369-9d32-087b892cf4fa@linux.intel.com> (raw)
In-Reply-To: <87o7e2a3hr.wl-tiwai@suse.de>
On 03/01/2024 16:36, Takashi Iwai wrote:
>>> Mark, Takashi, can you pick the fix for 6.7 (it is in -next)? I think we
>>> might have time for it to land?
>>
>> Oh that landed to Mark's for-next branch, i.e. only for 6.8.
>> Mark, please cherry-pick and send a PR before 6.7 final.
>
> I ended up with cherry-picking by myself now.
>
> I'm going to send a PR to Linus for 6.7 final in tomorrow.
Thank you, I really appreciate it!
--
Péter
next prev parent reply other threads:[~2024-01-03 16:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-27 7:37 Oops in hdac_hda_dev_probe (6.7-rc7) Dominik Brodowski
2023-12-29 13:11 ` Takashi Iwai
2023-12-29 15:24 ` Dominik Brodowski
2023-12-29 17:11 ` Takashi Iwai
2023-12-30 7:27 ` Dominik Brodowski
2023-12-30 10:03 ` Takashi Iwai
2023-12-31 10:28 ` Takashi Iwai
2024-01-02 9:08 ` Péter Ujfalusi
2024-01-02 9:25 ` Takashi Iwai
2024-01-03 14:36 ` Takashi Iwai
2024-01-03 16:24 ` Péter Ujfalusi [this message]
2024-01-03 18:31 ` Mark Brown
2024-01-02 17:37 ` Dominik Brodowski
-- strict thread matches above, loose matches on Subject: below --
2024-01-02 22:56 Willian Wang
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=d61245f1-cd4a-4369-9d32-087b892cf4fa@linux.intel.com \
--to=peter.ujfalusi@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=kai.vehmanen@linux.intel.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=ranjani.sridharan@linux.intel.com \
--cc=regressions@lists.linux.dev \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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