mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: audit@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] audit/audit-pr-20240312
Date: Tue, 12 Mar 2024 17:07:33 -0400	[thread overview]
Message-ID: <a51f65333f170f8079c72d98c16137d9@paul-moore.com> (raw)

Hi Linus,

Two small audit patches for the Linux v6.9 merge window:

- Use the KMEM_CACHE() macro instead of kmem_cache_create()

The guidance appears to be to use the KMEM_CACHE() macro when possible
and there is no reason why we can't use the macro, so let's use it.

- Remove an unnecessary assignment in audit_dupe_lsm_field()

A return value variable was assigned a value in its declaration, but
the declaration value is overwritten before the return value variable
is ever referenced; drop the assignment at declaration time.

Please merge when you have the chance,
-Paul

--
The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/audit.git
    tags/audit-pr-20240312

for you to fetch changes up to aa13b709084a0287ef250a9fbde5993e4dfc3078:

  audit: use KMEM_CACHE() instead of kmem_cache_create()
    (2024-01-25 10:12:22 -0500)

----------------------------------------------------------------
audit/stable-6.9 PR 20240312

----------------------------------------------------------------
Kunwu Chan (1):
      audit: use KMEM_CACHE() instead of kmem_cache_create()

Li zeming (1):
      audit: remove unnecessary assignment in audit_dupe_lsm_field()

 kernel/audit.c       | 4 +---
 kernel/auditfilter.c | 2 +-
 2 files changed, 2 insertions(+), 4 deletions(-)

--
paul-moore.com

             reply	other threads:[~2024-03-12 21:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 21:07 Paul Moore [this message]
2024-03-12 22:24 ` pr-tracker-bot

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=a51f65333f170f8079c72d98c16137d9@paul-moore.com \
    --to=paul@paul-moore.com \
    --cc=audit@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®