All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Khalid Ali <khaliidcaliy@gmail.com>,
	peterz@infradead.org, luto@kernel.org
Cc: linux-kernel@vger.kernel.org, Khalid Ali <khaliidcaliy@gmail.com>
Subject: Re: [PATCH] kernel/entry: Remove unneeded header "common.h"
Date: Fri, 13 Jun 2025 18:12:55 +0200	[thread overview]
Message-ID: <875xgziprs.ffs@tglx> (raw)
In-Reply-To: <20250611072400.4376-1-khaliidcaliy@gmail.com>

On Wed, Jun 11 2025 at 07:23, Khalid Ali wrote:
> syscall_user_dispatch() is part syscall user dispatch and it has a
> header already, so this patch moves that function to
> include/linux/syscall_user_dispatch.h which fits well. In that case we don't need 
> common.h anymore. All functions related to syscall
> user dispatch are on that header i mentioned, so this one shouldn't be
> special. We need to access the function from that header.

This word salad does not qualify as a change log. Please read

  https://www.kernel.org/doc/html/latest/process/maintainer-tip.html#changelog

including the documentation it links to.

The reason why common.h exists is that syscall_user_dispatch() is a
internal function, which is on purpose not exposed globally. There is no
reason to expose it globally, so it stays where it is.

Thanks,

        tglx

  reply	other threads:[~2025-06-13 16:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11  7:23 [PATCH] kernel/entry: Remove unneeded header "common.h" Khalid Ali
2025-06-13 16:12 ` Thomas Gleixner [this message]
2025-06-14 19:47   ` Khalid Ali
2025-06-16  7:01     ` Thomas Gleixner

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=875xgziprs.ffs@tglx \
    --to=tglx@linutronix.de \
    --cc=khaliidcaliy@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=peterz@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.