linux-kernel - Re: [PATCH] drivers/tty/nozomi.c: Use 'nozomi_setup_memory' instead of 'setup

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <53F3363E.3030601@suse.cz>
Date:	Tue, 19 Aug 2014 13:34:22 +0200
From:	Jiri Slaby <jslaby@...e.cz>
To:	Chen Gang <gang.chen.5i5j@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	Michal Simek <monstr@...str.eu>
Subject: Re: [PATCH] drivers/tty/nozomi.c: Use 'nozomi_setup_memory' instead
 of 'setup_memory'

On 08/08/2014, 05:56 PM, Chen Gang wrote:
> Several architectures (e.g. microblaze, um, and score) have already have
> extern 'setup_memory', so need use 'nozomi_setup_memory' instead of, or
> will cause compiling issue.
> 
> The related error (with allmodconfig for microblaze):
> 
>   CC [M]  drivers/tty/nozomi.o
> drivers/tty/nozomi.c:526:13: error: conflicting types for 'setup_memory'
>  static void setup_memory(struct nozomi *dc)
>              ^
> In file included from include/linux/mm.h:51:0,
>                  from ./arch/microblaze/include/asm/io.h:17,
>                  from include/linux/io.h:22,
>                  from include/linux/pci.h:31,
>                  from drivers/tty/nozomi.c:46:
> ./arch/microblaze/include/asm/pgtable.h:569:6: note: previous declaration of 'setup_memory' was here
>  void setup_memory(void);
>       ^
> 
> Signed-off-by: Chen Gang <gang.chen.5i5j@...il.com>

Oh, sure. Thanks.

Acked-by: Jiri Slaby <jslaby@...e.cz>


-- 
js
suse labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/