From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Jeff Chua <jeff.chua.linux@gmail.com>,
lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Bagas Sanjaya <bagasdotme@gmail.com>,
Jaegeuk Kim <jaegeuk@kernel.org>, Chao Yu <chao@kernel.org>,
F2FS Development <linux-f2fs-devel@lists.sourceforge.net>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Fwd: f2fs write error Linux v6.2
Date: Fri, 17 Feb 2023 13:48:09 +0100 [thread overview]
Message-ID: <86281fdf-2cea-0fec-d17d-4d6ac3a58176@leemhuis.info> (raw)
In-Reply-To: <f500d64b-c26d-ee34-092a-421c64c69f9e@leemhuis.info>
[TLDR: This mail in primarily relevant for Linux regression tracking. A
change or fix related to the regression discussed in this thread was
posted or applied, but it did not use a Link: tag to point to the
report, as Linus and the documentation call for. Things happen, no
worries -- but now the regression tracking bot needs to be told manually
about the fix. See link in footer if these mails annoy you.]
On 30.12.22 06:56, Thorsten Leemhuis wrote:
> On 30.12.22 05:04, Jeff Chua wrote:
>> On 12/24/22 19:43, Bagas Sanjaya wrote:
>>> On Sat, Dec 24, 2022 at 01:48:55PM +0800, Jeff Chua wrote:
>>>> Got the following error in latest linux-6.2-git with just vim (:w
>>>> file1). No problem with linux-6.1.1
>>
>> What happened to the f2fs developers? No response from anyone yet.
>
> Well, that indeed is unfortunate and ideally shouldn't happen, but the
> simple reality is: that can happen this time of the year due to this
> thing called "festive season".
> [...]
#regzbot fix: b3d83066cbebc76dbac8a5fca931f64b4c6fff34
#regzbot ignore-activity
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
That page also explains what to do if mails like this annoy you.
prev parent reply other threads:[~2023-02-17 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAAJw_Ztzyh-GNTJYpXbA0CeJv2Rz=fLZKE6_Q=7JMmM+s9yHXQ@mail.gmail.com>
2022-12-24 5:48 ` f2fs write error Linux v6.2 Jeff Chua
2022-12-24 12:43 ` Bagas Sanjaya
2022-12-24 14:00 ` Bagas Sanjaya
2022-12-30 4:04 ` Fwd: " Jeff Chua
2022-12-30 5:56 ` Thorsten Leemhuis
2022-12-30 6:39 ` Eric Biggers
2022-12-30 7:15 ` Yangtao Li
2022-12-31 12:01 ` Jeff Chua
2022-12-31 2:51 ` Chao Yu
2022-12-31 11:57 ` Jeff Chua
2022-12-31 12:41 ` Jeff Chua
2023-02-17 12:48 ` Linux regression tracking (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=86281fdf-2cea-0fec-d17d-4d6ac3a58176@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bagasdotme@gmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=torvalds@linux-foundation.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).