From: Takashi Iwai <firstname.lastname@example.org>
To: Jeff Woods <email@example.com>
Cc: "Greg KH" <firstname.lastname@example.org>,
Subject: Re: Kernel 5.13.6 breaks mmap with snd-hdsp module
Date: Mon, 09 Aug 2021 08:55:47 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
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
> 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
prev parent reply other threads:[~2021-08-09 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 7:49 Kernel 5.13.6 breaks mmap with snd-hdsp module Jeff Woods
2021-08-07 8:16 ` Greg KH
2021-08-07 9:26 ` Takashi Iwai
2021-08-07 22:51 ` Jeff Woods
2021-08-08 7:01 ` Takashi Iwai
2021-08-08 19:09 ` Jeff Woods
2021-08-09 6:50 ` Greg KH
2021-08-09 6:55 ` Takashi Iwai [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).