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] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 24 Dec 2012 08:26:22 -0600
From:	Omar Ramirez Luna <omar.ramirez@...itl.com>
To:	Chen Gang <gang.chen@...anux.com>
Cc:	Greg KH <gregkh@...uxfoundation.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [Suggestion] drivers/staging/tidspbridge: pr_err and pr_debug for
 uninitialized buffer (name buf not initialized).

Hi,

On Thu, Dec 13, 2012 at 7:30 PM, Chen Gang <gang.chen@...anux.com> wrote:
>   also another suggestions:
>     I built ti otmap with ti dsp bridge by arm cross-compiler under i386 platform.
>     the version tag is next-20121213
>     I met 2 compiling issues.
>
>       a: module dependency:
>         Multifunction device drivers --> Texas Instruments TWL/4030/TWL5030.... is required for TI OTMAP.
>         it need depend on CONFIG_REGMAP (maybe also inculde CONFIG_REGMAP*)
>         if CONFIG_REGMAP* not defined, building will be failed.

This is not related to tidspbridge, I sent a patch anyway as it looks
to be a valid build dependency bug.

>       b: version merging issue:
>         in drivers/staging/tidspbridge/core/_tiomap.h
>         need use "#include <mach-omap2/cm3xxx.h>" instead of "#include <mach-omap2/cm2xxx_3xxx.h>"
>         the macro OMAP3430_CM_AUTOIDLE_PLL has already move from cm2xxx_3xxx.h to cm3xxx.h.
>           (it seems arch/arm/mach-omap2/ is not a suitable place for including, but we have to)
>         if not change, compiling will be failed.

Done.

Cheers,

Omar
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ