From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>,
Christoph Hellwig <hch@infradead.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-mm@kvack.org, Suzuki K Poulose <suzuki.poulose@arm.com>,
Guenter Roeck <linux@roeck-us.net>,
Alexandru Elisei <alexandru.elisei@arm.com>
Subject: Re: [PATCH] init: Initialize noop_backing_dev_info early
Date: Wed, 15 Jun 2022 23:08:22 -0700 [thread overview]
Message-ID: <YqrI1kS/BxEQ+39V@infradead.org> (raw)
In-Reply-To: <20220615214815.6901-1-jack@suse.cz>
On Wed, Jun 15, 2022 at 11:48:15PM +0200, Jan Kara wrote:
> +extern int bdi_init(struct backing_dev_info *bdi);
No need for the extern.
Otherwise looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
And this remind me that I really want to kill noop_backing_dev_info
and just use a NULL bdi for this case eventually..
next prev parent reply other threads:[~2022-06-16 6:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 21:48 Jan Kara
2022-06-16 6:08 ` Christoph Hellwig [this message]
2022-06-16 9:00 ` Jan Kara
2022-06-16 8:10 ` Suzuki K Poulose
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=YqrI1kS/BxEQ+39V@infradead.org \
--to=hch@infradead.org \
--cc=alexandru.elisei@arm.com \
--cc=gregkh@linuxfoundation.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@roeck-us.net \
--cc=suzuki.poulose@arm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox