From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/3] Kconfig add config ERR_PTR_OFFSET
Date: Fri, 8 Nov 2019 10:32:36 -0500 [thread overview]
Message-ID: <20191108153236.GC19317@bill-the-cat> (raw)
In-Reply-To: <20191022192948.11080-2-simon.k.r.goldschmidt@gmail.com>
On Tue, Oct 22, 2019 at 09:29:46PM +0200, Simon Goldschmidt wrote:
> Some U-Boot pointers have redundant information, so we can use a scheme
> where we can return either an error code or a pointer with the same
> return value. The default implementation just casts the pointer to a
> number, however, this may fail on platforms where the end of the address
> range is used for valid pointers (e.g. 0xffffff00 is a valid heap pointer
> in socfpga SPL). For such platforms, this value provides an upper range
> of those error pointer values - up to 'MAX_ERRNO' bytes below this value
> must be unused/invalid addresses.
>
> Signed-off-by: Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com>
Applied to u-boot/master, thanks!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20191108/b2253ddc/attachment.sig>
next prev parent reply other threads:[~2019-11-08 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-22 19:29 [U-Boot] [PATCH 0/3] make ERR_PTR/PTR_ERR architecture specific Simon Goldschmidt
2019-10-22 19:29 ` [U-Boot] [PATCH 1/3] Kconfig add config ERR_PTR_OFFSET Simon Goldschmidt
2019-11-08 15:32 ` Tom Rini [this message]
2019-10-22 19:29 ` [U-Boot] [PATCH 2/3] linux err: make ERR_PTR/PTR_ERR architecture specific Simon Goldschmidt
2019-11-08 15:32 ` Tom Rini
2019-10-22 19:29 ` [U-Boot] [PATCH 3/3] arm: socfpga: gen5: fix ERR_PTR_OFFSET Simon Goldschmidt
2019-11-08 15:32 ` Tom Rini
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=20191108153236.GC19317@bill-the-cat \
--to=trini@konsulko.com \
--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