From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Re: [PATCH 1/1] um: fix error return code in winch_tramp() #forregzbot
Date: Tue, 31 May 2022 10:17:34 +0200 [thread overview]
Message-ID: <a7fe8b09-e666-492f-e693-b616940cec6b@leemhuis.info> (raw)
In-Reply-To: <f4f17203-df77-bf51-d761-3db63075d5a6@leemhuis.info>
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
On 24.03.22 13:40, Thorsten Leemhuis wrote:
> [TLDR: I'm adding the regression report below to regzbot, the Linux
> kernel regression tracking bot; all text you find below is compiled from
> a few templates paragraphs you might have encountered already already
> from similar mails.]
>
> Hi, this is your Linux kernel regression tracker. Top-posting for once,
> to make this easily accessible to everyone.
>
> Thanks for the report.
>
> To be sure below issue doesn't fall through the cracks unnoticed, I'm
> adding it to regzbot, my Linux kernel regression tracking bot:
>
> #regzbot ^introduced ccf1236ecac4
> #regzbot title uml: UML fails to exit cleanly when it is called from
> within in a shell script
> #regzbot ignore-activity
#regzbot fixed-by: 57ae0b67b747
Ciao, Thorsten
next prev parent reply other threads:[~2022-05-31 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210508032239.2177-1-thunder.leizhen@huawei.com>
2022-03-23 19:41 ` [PATCH 1/1] um: fix error return code in winch_tramp() Nathan Chancellor
2022-03-24 12:40 ` Thorsten Leemhuis
2022-05-31 8:17 ` Thorsten Leemhuis [this message]
2022-04-10 8:41 ` Thorsten Leemhuis
2022-04-10 9:33 ` Richard Weinberger
2022-04-11 17:48 ` Nathan Chancellor
2022-04-11 18:45 ` Richard Weinberger
2022-05-20 6:08 ` Thorsten Leemhuis
2022-05-20 15:55 ` Nathan Chancellor
2022-05-20 17:18 ` Johannes Berg
2022-05-20 17:31 ` Nathan Chancellor
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=a7fe8b09-e666-492f-e693-b616940cec6b@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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).