From: Xeonacid <h.dwwwwww@gmail.com>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH] fix typo
Date: Wed, 2 Jun 2021 17:45:18 +0800 [thread overview]
Message-ID: <CAPWxxEULO0n+DKJFoUd_aBMUwqqK6SGgR9Rd0LW5Ue+hJ4vAiw@mail.gmail.com> (raw)
In-Reply-To: <CAPWxxEWJdZ6NuCHzULLBY7=ZWSnew7L9EctThaBZV9DTz7+A3A@mail.gmail.com>
Oh no... My mailer seems to cut it again... I checked before sending
but it did again... I will try to use another mailer.
Sorry for the inconvenience...
On Wed, Jun 2, 2021 at 5:43 PM Xeonacid <h.dwwwwww@gmail.com> wrote:
>
> "accomodate" should be "accommodate"
> ---
> malloc/malloc.c | 2 +-
> manual/summary.pl | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> 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,
> diff --git a/manual/summary.pl b/manual/summary.pl
> index 4319c56415..ab0801b045 100755
> --- a/manual/summary.pl
> +++ b/manual/summary.pl
> @@ -374,7 +374,7 @@ outside @*x lists ("Misplaced @standardsx").
> "Spurious @standardsx"
> refers to otherwise valid @standardsx macros that were not matched to
> an element in an @*x list. "Invalid syntax" means just that.
>
> -The syntax of @standards annotations is designed to accomodate
> +The syntax of @standards annotations is designed to accommodate
> multiple header and standards annotations, as necessary.
>
> Examples:
> --
> 2.31.1
next prev parent reply other threads:[~2021-06-02 9:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-02 9:43 Xeonacid
2021-06-02 9:45 ` Xeonacid [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-02 10:12 Xeonacid
2021-06-02 10:16 ` Paul Zimmermann
2021-06-02 9:56 Xeonacid
2021-06-02 10:01 ` Paul Zimmermann
2021-06-02 9:29 Xeonacid
2021-06-02 8:49 Xeonacid
2021-06-02 8:55 ` Paul Zimmermann
2021-06-02 9:02 ` Paul Zimmermann
2021-06-02 9:27 ` Xeonacid
2021-06-02 9:29 ` Xeonacid
2021-06-02 9:30 ` 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=CAPWxxEULO0n+DKJFoUd_aBMUwqqK6SGgR9Rd0LW5Ue+hJ4vAiw@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).