From: Michal Simek <monstr@monstr.eu>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] input: key_matrix: fix header inclusion
Date: Tue, 07 Aug 2012 07:04:29 +0200 [thread overview]
Message-ID: <5020A1DD.5030903@monstr.eu> (raw)
In-Reply-To: <CAPnjgZ2OGeBc7daAVm6=EXprvrgL0WSeKLnUVOGoCGGBVt4DKw@mail.gmail.com>
On 08/06/2012 07:56 PM, Simon Glass wrote:
> On Thu, Aug 2, 2012 at 1:49 PM, Stephan Linz <linz@li-pro.net> wrote:
>> On Microblaze with device tree support enabled we run into
>> the error below.
>>
>> I'm not sure, but I think that all source code should include
>> at least the common.h and just this fix the problem on
>> Microblaz architecture.
>>
>> The error is:
>>
>> In file included from key_matrix.c:29:
>> include/malloc.h:364: error: conflicting types for 'memset'
>> include/linux/string.h:71: error: previous declaration of 'memset' was here
>> include/malloc.h:365: error: conflicting types for 'memcpy'
>> include/linux/string.h:74: error: previous declaration of 'memcpy' was here
>>
>> Signed-off-by: Stephan Linz <linz@li-pro.net>
>> CC: Bernie Thompson <bhthompson@chromium.org>
>> CC: Simon Glass <sjg@chromium.org>
>> CC: Tom Warren <twarren@nvidia.com>
>> CC: Michal Simek <monstr@monstr.eu>
>
> Acked-by: Simon Glass <sjg@chromium.org>
Acked-by: Michal Simek <monstr@monstr.eu>
Thanks,
Michal
--
Michal Simek, Ing. (M.Eng)
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/
Microblaze U-BOOT custodian
next prev parent reply other threads:[~2012-08-07 5:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 20:49 [U-Boot] [PATCH] input: key_matrix: fix header inclusion Stephan Linz
2012-08-06 17:56 ` Simon Glass
2012-08-07 5:04 ` Michal Simek [this message]
2012-09-02 15:44 ` Wolfgang Denk
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=5020A1DD.5030903@monstr.eu \
--to=monstr@monstr.eu \
--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