From: Xeonacid <h.dwwwwww@gmail.com>
To: libc-alpha@sourceware.org
Subject: [COMMITTED 1/1] malloc: fix typo "accomodate" should be "accommodate"
Date: Tue, 1 Jun 2021 14:57:37 +0800 [thread overview]
Message-ID: <CAPWxxEVPhdnOUxyPaKR=EfbO0Y2=0D+oL4k5u5HK=io=xjt+TQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1125 bytes --]
Hi,
I'm a newbie to glibc contribution. I've followed the Contribution
checklist but I'm not sure if I've done the right thing.
I've not completed the FSF Copyright Assignment. I've read that
"Copyright assignment for commulative changes by any one author of
less than 15 lines do not require copyright assignment.".
-- >8 --
---
malloc/malloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/malloc/malloc.c b/malloc/malloc.c
index e2d7b1b583..0e2e1747e0 100644
--- a/malloc/malloc.c
+++ b/malloc/malloc.c
@@ -1477,7 +1477,7 @@ checked_request2size (size_t req, size_t *sz)
__nonnull (1)
chunksize (p) - CHUNK_HDR_SZ : \
chunksize (p) - CHUNK_HDR_SZ + (chunk_is_mmapped (p) ? 0 : SIZE_SZ))
-/* If memory tagging is enabled the layout changes to accomodate the granule
+/* If memory tagging is enabled the layout changes to accommodate the granule
size, this is wasteful for small allocations so not done by default.
Both the chunk header and user data has to be granule aligned. */
_Static_assert (__MTAG_GRANULE_SIZE <= CHUNK_HDR_SZ,
--
2.31.1
[-- Attachment #2: 0001-malloc-fix-typo-accomodate-should-be-accommodate.patch --]
[-- Type: text/x-patch, Size: 1410 bytes --]
From 84ec52fad96826c874405d1d3c22176a22791cc5 Mon Sep 17 00:00:00 2001
From: Xeonacid <xeonacid@hit.edu.cn>
Date: Tue, 1 Jun 2021 14:18:47 +0800
Subject: [COMMITTED 1/1] malloc: fix typo "accomodate" should be "accommodate"
To: libc-alpha@sourceware.org
Cc: carlos@systemhalted.org
Hi,
I'm a newbie to glibc contribution. I've followed the Contribution checklist but I'm not sure if I've done the right thing.
I've not completed the FSF Copyright Assignment. I've read that "Copyright assignment for commulative changes by any one author of less than 15 lines do not require copyright assignment.".
-- >8 --
---
malloc/malloc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/malloc/malloc.c b/malloc/malloc.c
index e2d7b1b583..0e2e1747e0 100644
--- a/malloc/malloc.c
+++ b/malloc/malloc.c
@@ -1477,7 +1477,7 @@ checked_request2size (size_t req, size_t *sz) __nonnull (1)
chunksize (p) - CHUNK_HDR_SZ : \
chunksize (p) - CHUNK_HDR_SZ + (chunk_is_mmapped (p) ? 0 : SIZE_SZ))
-/* If memory tagging is enabled the layout changes to accomodate the granule
+/* If memory tagging is enabled the layout changes to accommodate the granule
size, this is wasteful for small allocations so not done by default.
Both the chunk header and user data has to be granule aligned. */
_Static_assert (__MTAG_GRANULE_SIZE <= CHUNK_HDR_SZ,
--
2.31.1
next reply other threads:[~2021-06-01 6:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-01 6:57 Xeonacid [this message]
2021-06-01 7:23 ` Paul Zimmermann
2021-06-01 7:42 ` Xeonacid
2021-06-01 8:09 ` Paul Zimmermann
2021-06-02 8:00 ` Paul Zimmermann
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='CAPWxxEVPhdnOUxyPaKR=EfbO0Y2=0D+oL4k5u5HK=io=xjt+TQ@mail.gmail.com' \
--to=h.dwwwwww@gmail.com \
--cc=libc-alpha@sourceware.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).