From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: <linux-cxl@vger.kernel.org>, <vishal.l.verma@intel.com>,
<dave.jiang@intel.com>, <ira.weiny@intel.com>,
<alison.schofield@intel.com>
Subject: Re: [PATCH] tools/testing/cxl: Use DEFINE_STATIC_SRCU()
Date: Mon, 15 May 2023 10:37:22 +0100 [thread overview]
Message-ID: <20230515103722.00004a06@Huawei.com> (raw)
In-Reply-To: <168392709546.1135523.10424917245934547117.stgit@dwillia2-xfh.jf.intel.com>
On Fri, 12 May 2023 14:31:35 -0700
Dan Williams <dan.j.williams@intel.com> wrote:
> Starting with commit:
>
> 95433f726301 ("srcu: Begin offloading srcu_struct fields to srcu_update")
>
> ...it is no longer possible to do:
>
> static DEFINE_SRCU(x)
>
> Switch to DEFINE_STATIC_SRCU(x) to fix:
>
> tools/testing/cxl/test/mock.c:22:1: error: duplicate ‘static’
> 22 | static DEFINE_SRCU(cxl_mock_srcu);
> | ^~~~~~
>
> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
I guess this got missed because of hiding kernel code in tools :)
(not that I want to restart that 'discussion / argument')
Jonathan
> ---
> tools/testing/cxl/test/mock.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/testing/cxl/test/mock.c b/tools/testing/cxl/test/mock.c
> index c4e53f22e421..de3933a776fd 100644
> --- a/tools/testing/cxl/test/mock.c
> +++ b/tools/testing/cxl/test/mock.c
> @@ -19,7 +19,7 @@ void register_cxl_mock_ops(struct cxl_mock_ops *ops)
> }
> EXPORT_SYMBOL_GPL(register_cxl_mock_ops);
>
> -static DEFINE_SRCU(cxl_mock_srcu);
> +DEFINE_STATIC_SRCU(cxl_mock_srcu);
>
> void unregister_cxl_mock_ops(struct cxl_mock_ops *ops)
> {
>
prev parent reply other threads:[~2023-05-15 9:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 21:31 [PATCH] tools/testing/cxl: Use DEFINE_STATIC_SRCU() Dan Williams
2023-05-12 21:51 ` Dave Jiang
2023-05-15 9:37 ` Jonathan Cameron [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=20230515103722.00004a06@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=vishal.l.verma@intel.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