linux-kernel - Re: [PATCH v3 0/5] gpio-langwell: bugfix and amendments

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: <519CF23D.3050906@intel.com>
Date:	Wed, 22 May 2013 09:28:45 -0700
From:	David Cohen <david.a.cohen@...el.com>
To:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
CC:	Linus Walleij <linus.walleij@...aro.org>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 0/5] gpio-langwell: bugfix and amendments

On 05/22/2013 03:20 AM, Andy Shevchenko wrote:
> There is locking bug fix and few amendments. Each commit message verbose
> enoough I think.
>
> Since v2:
>   - apply ACKs
>   - addressed Mika's comment for patch 3/4
>   - append patch 5/5
>
> Since v1:
>   - patch 2/4 ("amend error messages") moved to 4/4
>   - minor fix in patch 3/4 ("use managed ...")
>   - fix patch 4/4 ("amend error messages") to be real amendment
>
> Andy Shevchenko (5):
>    gpio-langwell: initialize lock before usage
>    gpio-langwell: do not use direct access to iomapped memory
>    gpio-langwell: use managed functions pcim_* and devm_*
>    gpio-langwell: amend error messages
>    gpio-langwell: drop away explicit casting
>
>   drivers/gpio/gpio-langwell.c | 117 ++++++++++++++-----------------------------
>   1 file changed, 38 insertions(+), 79 deletions(-)
>
For the whole set:
Acked-by: David Cohen <david.a.cohen@...el.com>
--
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/