From: David Sterba <dsterba@suse.cz>
To: Wang Yugui <wangyugui@e16-tech.com>
Cc: linux-btrfs@vger.kernel.org,
Johannes Thumshirn <johannes.thumshirn@wdc.com>
Subject: Re: [PATCH v2] btrfs: slience the sparse warn of rcu_string
Date: Fri, 2 Sep 2022 15:55:35 +0200 [thread overview]
Message-ID: <20220902135534.GZ13489@twin.jikos.cz> (raw)
In-Reply-To: <20220824051208.19924-1-wangyugui@e16-tech.com>
On Wed, Aug 24, 2022 at 01:12:08PM +0800, Wang Yugui wrote:
> slience the sparse warn of rcu_string reported by 'make C=1'
>
> warning example:
> fs/btrfs/volumes.c:2300:41: warning: incorrect type in argument 3 (different address spaces)
> fs/btrfs/volumes.c:2300:41: expected char const *device_path
> fs/btrfs/volumes.c:2300:41: got char [noderef] __rcu *
>
> Reviewed-by: Johannes Thumshirn <johannes.thumshirn@wdc.com>
> Signed-off-by: Wang Yugui <wangyugui@e16-tech.com>
With an updated changelog added to misc-next, thanks.
next prev parent reply other threads:[~2022-09-02 14:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 5:12 [PATCH v2] btrfs: slience the sparse warn of rcu_string Wang Yugui
2022-08-24 7:25 ` Anand Jain
2022-09-02 13:55 ` David Sterba [this message]
2022-09-05 3:57 ` Wang Yugui
2022-09-05 15:34 ` David Sterba
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=20220902135534.GZ13489@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=johannes.thumshirn@wdc.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=wangyugui@e16-tech.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