From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Florian Westphal <fw@strlen.de>,
netfilter-devel@vger.kernel.org, coreteam@netfilter.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nft_counter: remove wrong __percpu of nft_counter_resest()'s arg
Date: Mon, 28 Jan 2019 11:20:22 +0100 [thread overview]
Message-ID: <20190128102022.mrnh2j6orgnrdfyp@salvia> (raw)
In-Reply-To: <20190119215024.90174-1-luc.vanoostenryck@gmail.com>
On Sat, Jan 19, 2019 at 10:50:24PM +0100, Luc Van Oostenryck wrote:
> nft_counter_rest() has its first argument declared as
> struct nft_counter_percpu_priv __percpu *priv
> but this structure is not percpu (it only countains
> a member 'counter' which is, correctly, a pointer to a
> percpu struct nft_counter).
>
> So, remove the '__percpu' from the argument's declaration.
Applied, thanks.
prev parent reply other threads:[~2019-01-28 10:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 21:50 [PATCH] nft_counter: remove wrong __percpu of nft_counter_resest()'s arg Luc Van Oostenryck
2019-01-28 10:20 ` Pablo Neira Ayuso [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=20190128102022.mrnh2j6orgnrdfyp@salvia \
--to=pablo@netfilter.org \
--cc=coreteam@netfilter.org \
--cc=fw@strlen.de \
--cc=kadlec@blackhole.kfki.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.vanoostenryck@gmail.com \
--cc=netfilter-devel@vger.kernel.org \
/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).