mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hemanth Selam <hemanth.selam@gmail.com>
To: Kees Cook <kees@kernel.org>,
	Andy Lutomirski <luto@amacapital.net>,
	Will Drewry <wad@chromium.org>
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH 2/3] seccomp: fix typo "overriden" in comment
Date: Fri,  4 Sep 2026 17:50:51 +0530	[thread overview]
Message-ID: <20260904122054.28531-3-hemanth.selam@gmail.com> (raw)
In-Reply-To: <20260904122054.28531-1-hemanth.selam@gmail.com>

Correct "overriden" to "overridden", reported by scripts/checkpatch.pl
using the misspelling list in scripts/spelling.txt.  Only touches comments,
no code changes.

Assisted-by: Cursor:claude-opus-5
Signed-off-by: Hemanth Selam <hemanth.selam@gmail.com>
---
 include/uapi/linux/seccomp.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/include/uapi/linux/seccomp.h b/include/uapi/linux/seccomp.h
index dbfc9b37fcae..6d9158152360 100644
--- a/include/uapi/linux/seccomp.h
+++ b/include/uapi/linux/seccomp.h
@@ -104,7 +104,7 @@ struct seccomp_notif {
  * SECCOMP_IOCTL_NOTIF_SEND from earlier filters, essentially allowing all
  * such filtered syscalls to be executed by sending the response
  * SECCOMP_USER_NOTIF_FLAG_CONTINUE. Note that SECCOMP_RET_TRACE can equally
- * be overriden by SECCOMP_USER_NOTIF_FLAG_CONTINUE.
+ * be overridden by SECCOMP_USER_NOTIF_FLAG_CONTINUE.
  */
 #define SECCOMP_USER_NOTIF_FLAG_CONTINUE (1UL << 0)
 
-- 
2.48.1


  parent reply	other threads:[~2026-09-04 12:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-04 12:20 [PATCH 0/3] elf: fix typos in comments Hemanth Selam
2026-09-04 12:20 ` [PATCH 1/3] elf: fix typo "accomodate" in comment Hemanth Selam
2026-09-04 12:20 ` Hemanth Selam [this message]
2026-09-04 12:20 ` [PATCH 3/3] kernel: fix typo "overriden" " Hemanth Selam
2026-09-04 14:52   ` Lorenzo Stoakes (ARM)

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=20260904122054.28531-3-hemanth.selam@gmail.com \
    --to=hemanth.selam@gmail.com \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=wad@chromium.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®