linux-kernel - Re: [PATCH v3 1/7] gpio: davinci: coding style correction

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: <5217A1A7.6080305@ti.com>
Date:	Fri, 23 Aug 2013 23:23:43 +0530
From:	Sekhar Nori <nsekhar@...com>
To:	"Lad, Prabhakar" <prabhakar.csengg@...il.com>
CC:	DLOS <davinci-linux-open-source@...ux.davincidsp.com>,
	LKML <linux-kernel@...r.kernel.org>,
	LAK <linux-arm-kernel@...ts.infradead.org>,
	Linus Walleij <linus.walleij@...aro.org>,
	Grant Likely <grant.likely@...aro.org>,
	Kevin Hilman <khilman@...aro.org>
Subject: Re: [PATCH v3 1/7] gpio: davinci: coding style correction

Prabhakar,

On 8/18/2013 10:48 AM, Lad, Prabhakar wrote:
> From: Philip Avinash <avinashphilip@...com>
> 
> Make some minor coding style fixes. Use proper multi-line
> commenting style, arrange include files alphabetically and
> use a macro for register offset.
> 
> Signed-off-by: Philip Avinash <avinashphilip@...com>
> [nsekhar@...com: dropped changes which were considered
> churn - line break fixes and variable name changes]
> Acked-by: Linus Walleij <linus.walleij@...aro.org>
> Signed-off-by: Sekhar Nori <nsekhar@...com>
> Signed-off-by: Lad, Prabhakar <prabhakar.csengg@...il.com>

Queuing this for v3.12 through DaVinci tree (since there are dependent
mach-davinci patches). That said, its late for v3.12 and I cannot say if
ARM SoC team will take it.

Thanks,
Sekhar
--
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/