From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [PATCH v2 1/1] sandbox: redefine getc()
Date: Wed, 30 Sep 2020 13:49:29 +0200 [thread overview]
Message-ID: <222783.1601466569@gemini.denx.de> (raw)
In-Reply-To: <20200929185004.GO14816@bill-the-cat>
Dear Tom,
In message <20200929185004.GO14816@bill-the-cat> you wrote:
>
> Wolfgang, I was wondering could we not, given the few callers of 'getc'
> carefully change our internal usage / name to 'getchar', which is more
> POSIX-like and have our EXPORT_FUNC line be:
> EXPORT_FUNC(getc, int, getchar, void)
I guess we could, indeed.
> and that might be the clean solution here?
Probably.
I haven't tested this, though.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If I have seen further it is by standing on the shoulders of giants.
- Isaac Newton, Letter to Robert Hooke, 5 February 1676
prev parent reply other threads:[~2020-09-30 11:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 18:43 [PATCH v2 1/1] sandbox: redefine getc() Heinrich Schuchardt
2020-09-29 18:50 ` Tom Rini
2020-09-30 11:49 ` Wolfgang Denk [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=222783.1601466569@gemini.denx.de \
--to=wd@denx.de \
--cc=u-boot@lists.denx.de \
/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