From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from smtp-out2.suse.de (smtp-out2.suse.de [195.135.220.29])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by smtp.subspace.kernel.org (Postfix) with ESMTPS id 750F1177
	for <regressions@lists.linux.dev>; Mon,  9 Aug 2021 06:55:54 +0000 (UTC)
Received: from relay2.suse.de (relay2.suse.de [149.44.160.134])
	by smtp-out2.suse.de (Postfix) with ESMTP id 5D9651FD93;
	Mon,  9 Aug 2021 06:55:47 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.de; s=susede2_rsa;
	t=1628492147; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc:
	 mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=XMuz+JjYXbYKp1pTdPAhRf7DC0gyx+Na7dCqAleUp/k=;
	b=hM9k0NNuJcqMZJOm2ANU/lSf9KKXxC97JckATWfoBJ9Zjz0SWrNRe2R6i3Ah0n/XoowU2q
	at2PDh1IBPvVCExiSbjeoirMxVFaP6xzQcKh4+9oyOPcybFvhiQ3tkXWh8/KlMK8Hh5gNM
	s8lWLuFijZF8k19qpxJKb0iVSj/bZzE=
DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=suse.de;
	s=susede2_ed25519; t=1628492147;
	h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc:
	 mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=XMuz+JjYXbYKp1pTdPAhRf7DC0gyx+Na7dCqAleUp/k=;
	b=goYOBBbhixZ8wl7xpucOzOPL7rVtJ/k00+tfdgTbXt05BY6TudvGSj0RoKvP9F0q+dAw6K
	9wc8HqKa/RMlZ9Bw==
Received: from alsa1.suse.de (alsa1.suse.de [10.160.4.42])
	by relay2.suse.de (Postfix) with ESMTP id 55070A3B89;
	Mon,  9 Aug 2021 06:55:47 +0000 (UTC)
Date: Mon, 09 Aug 2021 08:55:47 +0200
Message-ID: <s5h4kbzp0ng.wl-tiwai@suse.de>
From: Takashi Iwai <tiwai@suse.de>
To: Jeff Woods <jwoods@fnordco.com>
Cc: "Greg KH" <gregkh@linuxfoundation.org>,
	"alsa-devel" <alsa-devel@alsa-project.org>,
	"stable" <stable@vger.kernel.org>,
	"regressions" <regressions@lists.linux.dev>
Subject: Re: Kernel 5.13.6 breaks mmap with snd-hdsp module
In-Reply-To: <17b272bac81.10ac3bd0570099.4091761174182420511@fnordco.com>
References: <17b1f9647ee.1179b6a05461889.5940365952430364689@fnordco.com>
	<YQ5Bb+mPgPivLqvX@kroah.com>
	<s5htuk1ppvb.wl-tiwai@suse.de>
	<17b22d08355.f21da1f938057.6900412371441404465@fnordco.com>
	<s5him0gpghv.wl-tiwai@suse.de>
	<17b272bac81.10ac3bd0570099.4091761174182420511@fnordco.com>
User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI/1.14.6 (Maruoka)
 FLIM/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL/10.8 Emacs/25.3
 (x86_64-suse-linux-gnu) MULE/6.0 (HANACHIRUSATO)
Precedence: bulk
X-Mailing-List: regressions@lists.linux.dev
List-Id: <regressions.lists.linux.dev>
List-Subscribe: <mailto:regressions+subscribe@lists.linux.dev>
List-Unsubscribe: <mailto:regressions+unsubscribe@lists.linux.dev>
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset=US-ASCII

On Sun, 08 Aug 2021 21:09:38 +0200,
Jeff Woods wrote:
> 
> I applied the patch to 5.13.9, and it did indeed solve the problem.
> 
> Thank you very much!

Great, now I pushed the fix to for-linus branch, to be included in
5.14-rc6.

> For future reference, if I am reporting an issue with stable and I know the
> commit that caused it, should I contact the committer directly *and* cc the
> stable and regressions list?

Involving those relevant parties at the first place is always good.
IMO, it doesn't matter who is in Cc and who is in To.  The point is to
reduce the unnecessary hop and latency, so that developers can react
quickly.


Thanks!

Takashi