Kexec Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Luis Chamberlain <mcgrof@kernel.org>
Cc: hch@infradead.org, djwong@kernel.org, sandeen@sandeen.net,
	song@kernel.org, rafael@kernel.org, gregkh@linuxfoundation.org,
	viro@zeniv.linux.org.uk, jack@suse.cz, jikos@kernel.org,
	bvanassche@acm.org, ebiederm@xmission.com, mchehab@kernel.org,
	keescook@chromium.org, p.raghav@samsung.com,
	da.gomez@samsung.com, linux-fsdevel@vger.kernel.org,
	kernel@tuxforce.de, kexec@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/3] filesystems: start removal of the kthread freezer
Date: Fri, 12 May 2023 09:31:00 +0200	[thread overview]
Message-ID: <20230512073100.GC32559@twin.jikos.cz> (raw)
In-Reply-To: <20230508011927.4036707-1-mcgrof@kernel.org>

On Sun, May 07, 2023 at 06:19:24PM -0700, Luis Chamberlain wrote:
> Here's 3 filesystems converted over to remove the kthread freezer.
> 
> Luis Chamberlain (3):
>   ext4: replace kthread freezing with auto fs freezing
>   btrfs: replace kthread freezing with auto fs freezing
>   xfs: replace kthread freezing with auto fs freezing

All patches add FS_AUTOFREEZE but I don't see it defined anywhere, it's
not in linux-next either. Also please drop the SMPL code from the
changelog, it's not necessary for such targeted change (unlike for a
tree-wide one).

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

      parent reply	other threads:[~2023-05-12  7:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-08  1:19 [PATCH 0/3] filesystems: start removal of the kthread freezer Luis Chamberlain
2023-05-08  1:19 ` [PATCH 1/3] ext4: replace kthread freezing with auto fs freezing Luis Chamberlain
2023-05-25 16:07   ` Jan Kara
2023-05-08  1:19 ` [PATCH 2/3] btrfs: " Luis Chamberlain
2023-05-08  1:19 ` [PATCH 3/3] xfs: " Luis Chamberlain
2023-05-12  7:31 ` David Sterba [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=20230512073100.GC32559@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=bvanassche@acm.org \
    --cc=da.gomez@samsung.com \
    --cc=djwong@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=jikos@kernel.org \
    --cc=keescook@chromium.org \
    --cc=kernel@tuxforce.de \
    --cc=kexec@lists.infradead.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=mchehab@kernel.org \
    --cc=p.raghav@samsung.com \
    --cc=rafael@kernel.org \
    --cc=sandeen@sandeen.net \
    --cc=song@kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    /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