NTFS3 file system kernel mode driver
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Linux kernel regressions list <regressions@lists.linux.dev>
Cc: ntfs3@lists.linux.dev
Subject: Re: [regressions] ntfs3: empty file on update without forced cache drop
Date: Sun, 11 Feb 2024 08:28:18 +0100	[thread overview]
Message-ID: <64261685-1f82-4ba5-98f5-6d76178db53a@leemhuis.info> (raw)
In-Reply-To: <138ed123-0f84-4d7a-8a17-67fe2418cf29@leemhuis.info>

On 27.11.23 07:18, Thorsten Leemhuis wrote:
> 
> Konstantin, I noticed a regression report in bugzilla.kernel.org.
> Apparently it's cause by a change of yours.
> 
> As many (most?) kernel developers don't keep an eye on bugzilla, I
> decided to forward it by mail. Note, you have to use bugzilla to reach
> the reporter, as I sadly[1] can not CCed them in mails like this.
> 
> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=218180 :

#regzbot fix: d68968440b1a75dee0
#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.

      parent reply	other threads:[~2024-02-11  7:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27  6:18 [regressions] ntfs3: empty file on update without forced cache drop Thorsten Leemhuis
2023-12-05 12:49 ` Linux regression tracking (Thorsten Leemhuis)
2024-01-21  9:14   ` Thorsten Leemhuis
2024-01-26 12:57     ` Konstantin Komarov
2024-01-15 11:15 ` Giovanni Santini
2024-02-11  7:28 ` 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=64261685-1f82-4ba5-98f5-6d76178db53a@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=ntfs3@lists.linux.dev \
    --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 read-only IMAP folder(s) and NNTP newsgroup(s).