From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] board_init.c: Always use memset()
Date: Thu, 19 Jan 2017 09:25:14 -0500 [thread overview]
Message-ID: <20170119142514.GG25981@bill-the-cat> (raw)
In-Reply-To: <CAPnjgZ3E1hecaWqyr3Qgf-DEaRJe2fKp17K9EboCee5ZvHshsg@mail.gmail.com>
On Thu, Jan 19, 2017 at 06:57:51AM -0700, Simon Glass wrote:
> On 12 January 2017 at 11:16, Tom Rini <trini@konsulko.com> wrote:
> > We can make the code read more easily here by simply using memset()
> > always as when we don't have an optimized version of the function we
> > will still have a version of this function around anyhow.
> >
> > Cc: Simon Glass <sjg@chromium.org>
> > Signed-off-by: Tom Rini <trini@konsulko.com>
> > ---
> > common/init/board_init.c | 18 ------------------
> > 1 file changed, 18 deletions(-)
>
> I recall this didn't work before, but I'm pleased it now does.
Do you recall where, if it was a runtime rather than build time failure?
There was a case or two of build-time failure I had to address.
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20170119/34fb0d4b/attachment.sig>
next prev parent reply other threads:[~2017-01-19 14:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 18:16 [U-Boot] [PATCH 1/2] ARM: Default to using optimized memset and memcpy routines Tom Rini
2017-01-12 18:16 ` [U-Boot] [PATCH 2/2] board_init.c: Always use memset() Tom Rini
2017-01-19 13:57 ` Simon Glass
2017-01-19 14:25 ` Tom Rini [this message]
2017-01-21 3:50 ` Simon Glass
2017-01-21 3:37 ` [U-Boot] [U-Boot,2/2] " Tom Rini
2017-01-13 6:16 ` [U-Boot] [PATCH 1/2] ARM: Default to using optimized memset and memcpy routines Stefan Roese
2017-01-19 13:58 ` Simon Glass
2017-01-21 3:37 ` [U-Boot] [U-Boot, " 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=20170119142514.GG25981@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.