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]
Message-ID: <AANLkTikL3FyfN-PqA9f3fIFwqPJtbra5i1T-ETvJXDUa@mail.gmail.com>
Date:	Wed, 14 Jul 2010 12:27:01 +0300
From:	Felipe Contreras <felipe.contreras@...il.com>
To:	Nishanth Menon <nm@...com>
Cc:	Greg Kroah-Hartman <gregkh@...e.de>,
	Omar Ramirez Luna <omar.ramirez@...com>,
	Ohad Ben-Cohen <ohad@...ery.com>,
	Ameya Palande <ameya.palande@...ia.com>,
	Fernando Guzman Lugo <fernando.lugo@...com>,
	Andy Shevchenko <andy.shevchenko@...il.com>,
	lkml <linux-kernel@...r.kernel.org>,
	linux-omap <linux-omap@...r.kernel.org>
Subject: Re: [PATCH 00/11] staging: tidspbridge: header cleanup series

On Tue, Jul 13, 2010 at 1:55 AM, Nishanth Menon <nm@...com> wrote:
> Series targetted to remove std.h, GlobalTypes.h and dbdefs.h. These
> introduce custom types and macros which dont make sense for linux kernel
>
> Nishanth Menon (11):
>  staging: tidspbridge: remove custom TRUE FALSE
>  staging: tidspbridge: no need for custom NULL
>  staging: tidspbridge: remove std.h
>  staging: tidspbridge: remove custom typedef reg_uword32
>  staging: tidspbridge: remove RET_OK RET_FAIL
>  staging: tidspbridge: remove GlobalTypes.h
>  staging: tidspbridge: replace CONST with c standard const
>  staging: tidspbridge: remove IN modifier
>  staging: tidspbridge: remove OPTIONAL
>  staging: tidspbridge: remove OUT define
>  staging: tidspbridge: remove dbdefs.h

FWIW: Reviewed-by: Felipe Contreras <felipe.contreras@...il.com>

-- 
Felipe Contreras
--
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