From: Paul Moore <paul@paul-moore.com>
To: Ricardo Robaina <rrobaina@redhat.com>,
audit@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: eparis@redhat.com, Ricardo Robaina <rrobaina@redhat.com>
Subject: Re: [PATCH] audit: fix whitespace alignment in include/uapi/linux/audit.h
Date: Mon, 02 Mar 2026 16:31:02 -0500 [thread overview]
Message-ID: <ec57713c0a9c8b1f13f74d1cbb0b18fd@paul-moore.com> (raw)
In-Reply-To: <20260226171546.2231505-1-rrobaina@redhat.com>
On Feb 26, 2026 Ricardo Robaina <rrobaina@redhat.com> wrote:
>
> Fixed minor indentation inconsistencies in the audit macros
> to align with standard kernel coding style using 8-character
> hard tabs.
>
> Signed-off-by: Ricardo Robaina <rrobaina@redhat.com>
> ---
> include/uapi/linux/audit.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/include/uapi/linux/audit.h b/include/uapi/linux/audit.h
> index 14a1c1fe013a..410dfb41b810 100644
> --- a/include/uapi/linux/audit.h
> +++ b/include/uapi/linux/audit.h
> @@ -350,7 +350,7 @@ enum {
> #define AUDIT_STATUS_ENABLED 0x0001
> #define AUDIT_STATUS_FAILURE 0x0002
> #define AUDIT_STATUS_PID 0x0004
> -#define AUDIT_STATUS_RATE_LIMIT 0x0008
> +#define AUDIT_STATUS_RATE_LIMIT 0x0008
I had to fix a space-before-tab issue in this line, but otherwise this
looked fine to me. It is worth mentioning that checkpatch.pl would
have caught the space-before-tab problem; please get in the habit of
running checkpatch.pl before posting patches.
Merged into audit/dev, thanks.
--
paul-moore.com
next prev parent reply other threads:[~2026-03-02 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 17:15 [PATCH] audit: fix whitespace alignment in include/uapi/linux/audit.h Ricardo Robaina
2026-03-02 21:31 ` Paul Moore [this message]
2026-03-03 11:41 ` Ricardo Robaina
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=ec57713c0a9c8b1f13f74d1cbb0b18fd@paul-moore.com \
--to=paul@paul-moore.com \
--cc=audit@vger.kernel.org \
--cc=eparis@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rrobaina@redhat.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