From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: YueHaibing <yuehaibing@huawei.com>,
clm@fb.com, josef@toxicpanda.com, dsterba@suse.com,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -next] btrfs: Make btrfs_sysfs_add_fs_devices static
Date: Thu, 17 Sep 2020 14:53:54 +0200 [thread overview]
Message-ID: <20200917125354.GT1791@twin.jikos.cz> (raw)
In-Reply-To: <9d4c2521-338a-8bce-46a7-b48818ddad66@oracle.com>
On Thu, Sep 17, 2020 at 09:47:24AM +0800, Anand Jain wrote:
>
>
>
> On 16/9/20 10:26 pm, YueHaibing wrote:
> > Fix sparse warning:
> >
> > fs/btrfs/sysfs.c:1386:5: warning:
> > symbol 'btrfs_sysfs_add_fs_devices' was not declared. Should it be static?
>
>
> misc-next branch has it declared static. It was fixed later.
Yeah it's fixed, the k.org for-next got a bit behind the snapshot
branches, I'll do an update today.
prev parent reply other threads:[~2020-09-17 12:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 14:26 [PATCH -next] btrfs: Make btrfs_sysfs_add_fs_devices static YueHaibing
2020-09-17 1:47 ` Anand Jain
2020-09-17 12:53 ` 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=20200917125354.GT1791@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yuehaibing@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 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).