From: Alexander Kuleshov <kuleshovmail@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Alexander Kuleshov <kuleshovmail@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H . Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] x86/entry64: remove unused audit related macros
Date: Sun, 23 Oct 2016 19:47:56 +0600 [thread overview]
Message-ID: <20161023134756.GB1360@localhost> (raw)
In-Reply-To: <20161023133310.hq24zte6n3qqe4f4@pd.tnic>
On 10-23-16, Borislav Petkov wrote:
> Now, I went and made it a bit more readable and put the commit IDs and
> their names on separate lines, like we do in tip:
>
> "These macros were added in commit
>
> 86a1c34a929f ("x86_64 syscall audit fast-path").
>
> They were used for sycalls auditing, but this functionality was moved to
> the arch/x86/entry/common.c:syscall_trace_enter() in
>
> 1f484aa69046 ("x86/entry: Move C entry and exit code to arch/x86/entry/common.c")
>
> syscall_trace_enter() now uses the same defines from <linux/audit.h>,
> so these defines are no longer used anywhere in entry_64.S and we may
> remove them."
>
Agree, this looks more readable. I will take into account this formatting.
> Also, we abbreviate git commits to 12 chars. What you could do is add
> this to your .gitconfig:
>
> [alias]
> one = show -s --pretty='format:%h (\"%s\")'
>
> and then simply do
>
> $ git one 1f484aa69
>
> and it'll format it properly for ya.
>
> Anyway, just a couple of things to pay attention to in the future.
Yes, thanks for this.
> With this, you can add
>
> Reviewed-by: Borislav Petkov <bp@suse.de>
>
> to your v3.
Thank you.
prev parent reply other threads:[~2016-10-23 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-23 13:14 [PATCH v2] x86/entry64: remove unused audit related macros Alexander Kuleshov
2016-10-23 13:33 ` Borislav Petkov
2016-10-23 13:47 ` Alexander Kuleshov [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=20161023134756.GB1360@localhost \
--to=kuleshovmail@gmail.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=tglx@linutronix.de \
/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