LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: "Christophe Leroy (CS GROUP)" <chleroy@kernel.org>,
	Ethan Nelson-Moore <enelsonmoore@gmail.com>,
	Michael Ellerman <mpe@ellerman.id.au>,
	Nicholas Piggin <npiggin@gmail.com>,
	"Ritesh Harjani (IBM)" <ritesh.list@gmail.com>,
	linuxppc-dev@lists.ozlabs.org
Cc: Madhavan Srinivasan <maddy@linux.ibm.com>
Subject: Re: [PATCH] powerpc: remove unused audit_32.h header
Date: Fri, 18 Sep 2026 14:21:28 +0530	[thread overview]
Message-ID: <cf92173d-b9f2-469c-8f1e-3978ef5469b3@linux.ibm.com> (raw)
In-Reply-To: <093ca6ba-5585-40ec-9337-8621c6741d33@kernel.org>



On 9/18/26 1:41 PM, Christophe Leroy (CS GROUP) wrote:
> Hi Shrikanth,
> 
> Le 18/09/2026 à 09:11, Shrikanth Hegde a écrit :
>>
>>
>> On 9/18/26 8:38 AM, Ethan Nelson-Moore wrote:
>>> The last use of arch/powerpc/kernel/audit_32.h was removed in
>>> commit f26ad12356a2 ("powerpc/audit: Convert powerpc to
>>> AUDIT_ARCH_COMPAT_GENERIC"), but it was left behind. Remove it.
>>>
>>
>> Does it need fixes tag, So that it can propagate correctly?
> 
> My understanding is that this patch is not a real bug fix so it doesn't qualify for -stable trees at the first place. Therefore it shouldn't contain a Fixes: tag.
> 
> See https://docs.kernel.org/process/stable-kernel-rules.html :
> 
> Rules on what kind of patches are accepted, and which ones are not, into the “-stable” tree:
> 
>      It or an equivalent fix must already exist in Linux mainline (upstream).
> 
>      It must be obviously correct and tested.
> 
>      It cannot be bigger than 100 lines, with context.
> 
>      It must follow the Documentation/process/submitting-patches.rst rules.
> 
>      It must either fix a real bug that bothers people or just add a device ID. To elaborate on the former:
> 
>          It fixes a problem like an oops, a hang, data corruption, a real security issue, a hardware quirk, a build error (but not for things marked CONFIG_BROKEN), or some “oh, that’s not good” issue.
> 
>          Serious issues as reported by a user of a distribution kernel may also be considered if they fix a notable performance or interactivity issue. As these fixes are not as obvious and have a higher risk of a subtle regression they should only be submitted by a distribution kernel maintainer and include an addendum linking to a bugzilla entry if it exists and additional information on the user-visible impact.
> 
>          No “This could be a problem...” type of things like a “theoretical race condition”, unless an explanation of how the bug can be exploited is also provided.
> 
>          No “trivial” fixes without benefit for users (spelling changes, whitespace cleanups, etc).
> 
> 

Alright. Makes sense.

>>
>> Reviewed-by: Shrikanth Hegde <sshegde@linux.ibm.com>
>>
>>> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>
>>> ---
>>>   arch/powerpc/kernel/audit_32.h | 7 -------
>>>   1 file changed, 7 deletions(-)
>>>   delete mode 100644 arch/powerpc/kernel/audit_32.h
>>>
>>> diff --git a/arch/powerpc/kernel/audit_32.h b/arch/powerpc/kernel/ audit_32.h
>>> deleted file mode 100644
>>> index c6c79c3041ab..000000000000
>>> --- a/arch/powerpc/kernel/audit_32.h
>>> +++ /dev/null
>>> @@ -1,7 +0,0 @@
>>> -// SPDX-License-Identifier: GPL-2.0
>>> -#ifndef __AUDIT_32_H__
>>> -#define __AUDIT_32_H__
>>> -
>>> -extern int ppc32_classify_syscall(unsigned);
>>> -
>>> -#endif
>>
> 



      reply	other threads:[~2026-09-18  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-18  3:08 [PATCH] powerpc: remove unused audit_32.h header Ethan Nelson-Moore
2026-09-18  6:20 ` Christophe Leroy (CS GROUP)
2026-09-18  7:11 ` Shrikanth Hegde
2026-09-18  8:11   ` Christophe Leroy (CS GROUP)
2026-09-18  8:51     ` Shrikanth Hegde [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=cf92173d-b9f2-469c-8f1e-3978ef5469b3@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=chleroy@kernel.org \
    --cc=enelsonmoore@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.com \
    --cc=ritesh.list@gmail.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