From: Christian Brauner <brauner@kernel.org>
To: Kemeng Shi <shikemeng@huaweicloud.com>
Cc: Christian Brauner <brauner@kernel.org>,
tj@kernel.org, xiujianfeng@huawei.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, viro@zeniv.linux.org.uk, jack@suse.cz,
akpm@linux-foundation.org
Subject: Re: [PATCH] writeback: move wb_wakeup_delayed defination to fs-writeback.c
Date: Mon, 22 Jan 2024 11:57:22 +0100 [thread overview]
Message-ID: <20240122-netzzugang-melodie-64d58a032679@brauner> (raw)
In-Reply-To: <20240118203339.764093-1-shikemeng@huaweicloud.com>
On Fri, 19 Jan 2024 04:33:39 +0800, Kemeng Shi wrote:
> The wb_wakeup_delayed is only used in fs-writeback.c. Move it to
> fs-writeback.c after defination of wb_wakeup and make it static.
>
>
Applied to the vfs.misc branch of the vfs/vfs.git tree.
Patches in the vfs.misc branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.misc
[1/1] writeback: move wb_wakeup_delayed defination to fs-writeback.c
https://git.kernel.org/vfs/vfs/c/983d926149ea
prev parent reply other threads:[~2024-01-22 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-18 20:33 [PATCH] writeback: move wb_wakeup_delayed defination to fs-writeback.c Kemeng Shi
2024-01-18 14:36 ` Christian Brauner
2024-01-19 15:26 ` Jan Kara
2024-01-22 10:57 ` Christian Brauner [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=20240122-netzzugang-melodie-64d58a032679@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=shikemeng@huaweicloud.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xiujianfeng@huawei.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.