From: Thorsten Leemhuis <regressions@leemhuis.info>
To: regressions@lists.linux.dev
Cc: linux-riscv@lists.infradead.org, stable@vger.kernel.org
Subject: Re: Regression: Fwd: Re: [PATCH] riscv: mmap with PROT_WRITE but no PROT_READ is invalid #forregzbot
Date: Fri, 4 Nov 2022 13:02:42 +0100 [thread overview]
Message-ID: <464d46df-cad0-720a-9193-6e569d9c1d91@leemhuis.info> (raw)
In-Reply-To: <d6c9e249-08bd-4439-7dcc-371b32e7b851@canonical.com>
[Note: this mail is primarily send for documentation purposes and/or for
regzbot, my Linux kernel regression tracking bot. That's why I removed
most or all folks from the list of recipients, but left any that looked
like a mailing lists. These mails usually contain '#forregzbot' in the
subject, to make them easy to spot and filter out.]
On 11.10.22 18:52, Dimitri John Ledkov wrote:
> #regzbot ^introduced 2139619bcad7ac44cc8f6f749089120594056613
#regzbot fixed-by: 9e2e6042a7ec
prev parent reply other threads:[~2022-11-04 12:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 16:52 Regression: Fwd: Re: [PATCH] riscv: mmap with PROT_WRITE but no PROT_READ is invalid Dimitri John Ledkov
2022-10-11 16:58 ` Conor Dooley
2022-10-11 17:18 ` Dimitri John Ledkov
2022-11-04 12:02 ` Thorsten Leemhuis [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=464d46df-cad0-720a-9193-6e569d9c1d91@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=linux-riscv@lists.infradead.org \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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).