From: "tip-bot2 for Gautam Somani" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Gautam Somani <gautamsomani@gmail.com>,
Ingo Molnar <mingo@kernel.org>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: x86/mm] x86/mm/selftests: Fix typo in lam.c
Date: Fri, 06 Dec 2024 19:12:38 -0000 [thread overview]
Message-ID: <173351235881.412.10396233513650012252.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20241130184102.2182-1-gautamsomani@gmail.com>
The following commit has been merged into the x86/mm branch of tip:
Commit-ID: 9d93db0d1881c9e37e1528cd796e20ff13b7692c
Gitweb: https://git.kernel.org/tip/9d93db0d1881c9e37e1528cd796e20ff13b7692c
Author: Gautam Somani <gautamsomani@gmail.com>
AuthorDate: Sun, 01 Dec 2024 03:41:02 +09:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Fri, 06 Dec 2024 20:04:32 +01:00
x86/mm/selftests: Fix typo in lam.c
Change the spelling from metadate -> metadata
Signed-off-by: Gautam Somani <gautamsomani@gmail.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Link: https://lore.kernel.org/r/20241130184102.2182-1-gautamsomani@gmail.com
---
tools/testing/selftests/x86/lam.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/testing/selftests/x86/lam.c b/tools/testing/selftests/x86/lam.c
index 0ea4f68..4d4a765 100644
--- a/tools/testing/selftests/x86/lam.c
+++ b/tools/testing/selftests/x86/lam.c
@@ -237,7 +237,7 @@ static uint64_t set_metadata(uint64_t src, unsigned long lam)
* both pointers should point to the same address.
*
* @return:
- * 0: value on the pointer with metadate and value on original are same
+ * 0: value on the pointer with metadata and value on original are same
* 1: not same.
*/
static int handle_lam_test(void *src, unsigned int lam)
prev parent reply other threads:[~2024-12-06 19:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 18:41 [PATCH] selftests: x86: fix " Gautam Somani
2024-12-06 19:12 ` tip-bot2 for Gautam Somani [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=173351235881.412.10396233513650012252.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=gautamsomani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=x86@kernel.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®