From: "Vladimir 'phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: [PATCH] types: Fix typo
Date: Tue, 31 Oct 2023 20:22:04 +0100 [thread overview]
Message-ID: <CAEaD8JN_xeKJ=1-c+jO6x-qy+V9HJ=FeBymo3ORH28QrixpUgg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 73 bytes --]
Just a small grammar mistake.
--
Regards
Vladimir 'phcoder' Serbinenko
[-- Attachment #2: 0001-types-Fix-typo.patch --]
[-- Type: text/x-patch, Size: 1167 bytes --]
From e597e474b4ac0423d42902708d536670dba44a1c Mon Sep 17 00:00:00 2001
From: Vladimir Serbinenko <phcoder@gmail.com>
Date: Sun, 13 Aug 2023 09:19:02 +0200
Subject: [PATCH] types: Fix typo
Just a small grammar mistake.
Signed-off-by: Vladimir Serbinenko <phcoder@gmail.com>
---
include/grub/types.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/grub/types.h b/include/grub/types.h
index 0d96006fe..45536a661 100644
--- a/include/grub/types.h
+++ b/include/grub/types.h
@@ -349,7 +349,7 @@ static inline void grub_set_unaligned64 (void *ptr, grub_uint64_t val)
/*
* The grub_absolute_pointer() macro borrows the idea from Linux kernel of using
* RELOC_HIDE() macro to stop GCC from checking the result of pointer arithmetic
- * and also it's conversion to be inside the symbol's boundary [1]. The check
+ * and also its conversion to be inside the symbol's boundary [1]. The check
* is sometimes false positive, especially it is controversial to emit the array
* bounds [-Warray-bounds] warning on all hardwired literal pointers since GCC
* 11/12 [2]. Unless a good solution can be settled, for the time being we
--
2.39.2
[-- Attachment #3: Type: text/plain, Size: 141 bytes --]
_______________________________________________
Grub-devel mailing list
Grub-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/grub-devel
next reply other threads:[~2023-10-31 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-31 19:22 Vladimir 'phcoder' Serbinenko [this message]
2023-11-06 17:06 ` [PATCH] types: Fix typo Daniel Kiper
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='CAEaD8JN_xeKJ=1-c+jO6x-qy+V9HJ=FeBymo3ORH28QrixpUgg@mail.gmail.com' \
--to=phcoder@gmail.com \
--cc=grub-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).