From: Greg KH <gregkh@linuxfoundation.org>
To: Jeff Woods <jwoods@fnordco.com>
Cc: Takashi Iwai <tiwai@suse.de>,
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
Date: Mon, 9 Aug 2021 08:50:59 +0200 [thread overview]
Message-ID: <YRDQU7hrctUAdRci@kroah.com> (raw)
In-Reply-To: <17b272bac81.10ac3bd0570099.4091761174182420511@fnordco.com>
On Sun, Aug 08, 2021 at 12:09:38PM -0700, Jeff Woods wrote:
>
> 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?
Yes, that would be great to do.
thanks,
greg k-h
next prev parent reply other threads:[~2021-08-09 6:51 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 [this message]
2021-08-09 6:55 ` 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=YRDQU7hrctUAdRci@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=jwoods@fnordco.com \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).