From: John Johansen <john.johansen@canonical.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org,
James Morris <jmorris@namei.org>,
"Serge E . Hallyn" <serge@hallyn.com>
Subject: Re: [PATCH v1] apparmor: Remove duplicate macro list_entry_is_head()
Date: Tue, 8 Dec 2020 16:18:58 -0800 [thread overview]
Message-ID: <6c72b22b-4dca-8a77-4b56-f2314307e6d6@canonical.com> (raw)
In-Reply-To: <20201208100639.88182-1-andriy.shevchenko@linux.intel.com>
On 12/8/20 2:06 AM, Andy Shevchenko wrote:
> Strangely I hadn't had noticed the existence of the list_entry_is_head() in
> apparmor code when added the same one in the list.h. Luckily it's fully
> identical and didn't break builds. In any case we don't need a duplicate
> anymore, thus remove it from apparmor code.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
oh nice,
I will pull into the apparmor tree
Acked-by: John Johansen <john.johansen@canonical.com>
> ---
> security/apparmor/apparmorfs.c | 3 ---
> 1 file changed, 3 deletions(-)
>
> diff --git a/security/apparmor/apparmorfs.c b/security/apparmor/apparmorfs.c
> index 5fd4a64e431f..f95c6bfa8b8e 100644
> --- a/security/apparmor/apparmorfs.c
> +++ b/security/apparmor/apparmorfs.c
> @@ -2046,9 +2046,6 @@ int __aafs_ns_mkdir(struct aa_ns *ns, struct dentry *parent, const char *name,
> return error;
> }
>
> -
> -#define list_entry_is_head(pos, head, member) (&pos->member == (head))
> -
> /**
> * __next_ns - find the next namespace to list
> * @root: root namespace to stop search at (NOT NULL)
>
prev parent reply other threads:[~2020-12-09 0:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-08 10:06 Andy Shevchenko
2020-12-09 0:18 ` John Johansen [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=6c72b22b-4dca-8a77-4b56-f2314307e6d6@canonical.com \
--to=john.johansen@canonical.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=serge@hallyn.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
all inboxes | Powered by JetHome®