From: Jeff Johnston <jjohnstn@redhat.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: newlib@sourceware.org
Subject: Re: Fix iq2000 libgloss for c99/gcc-14
Date: Thu, 21 Dec 2023 14:07:28 -0500 [thread overview]
Message-ID: <CAOox84vhv0pu4DrtwLP_V7+NxEsn2Xad3ccm9K+g8CbDyMbgZg@mail.gmail.com> (raw)
In-Reply-To: <72ac9bcd-c525-4d7a-956b-df2441b46087@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 263 bytes --]
Please go ahead.
-- Jeff J.
On Thu, Dec 21, 2023 at 2:13 AM Jeff Law <jeffreyalaw@gmail.com> wrote:
>
> Similar to the others in this space. Make implicit ints explicit ints.
> Add prototype for _write in sbrk.c.
>
> OK for the trunk?
>
> jeff
prev parent reply other threads:[~2023-12-21 19:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-21 7:13 Jeff Law
2023-12-21 19:07 ` Jeff Johnston [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=CAOox84vhv0pu4DrtwLP_V7+NxEsn2Xad3ccm9K+g8CbDyMbgZg@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=newlib@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).