linux-kernel - Re: [PATCH 0/4] 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] [day] [month] [year] [list]

Message-ID: <CAHp75VdTVKnR8chYRPrLea_PbbHQy3tbHDwXpVn9=f6wfkoyNw@mail.gmail.com>
Date:	Tue, 21 May 2013 20:49:14 +0300
From:	Andy Shevchenko <andy.shevchenko@...il.com>
To:	David Cohen <david.a.cohen@...el.com>
Cc:	Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Mika Westerberg <mika.westerberg@...ux.intel.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] gpio-langwell: bugfix and amendments

On Tue, May 21, 2013 at 8:23 PM, David Cohen <david.a.cohen@...el.com> wrote:
> On 05/21/2013 03:33 AM, Andy Shevchenko wrote:
>>
>> There is locking bug fix and few amendments. Each commit message verbose
>> enoough I think.
>>
>> Andy Shevchenko (4):
>>    gpio-langwell: initialize lock before usage
>>    gpio-langwell: amend error messages
>>    gpio-langwell: do not use direct access to iomapped memory
>>    gpio-langwell: use managed functions pcim_* and devm_*
>
>
> I wonder if you should rebase those patches on top of this one:
> https://patchwork.kernel.org/patch/2527431/

I actually made my patchset on top of that one.
I think I have to fix patch 2/4 here to call that as real amendment.

--
With Best Regards,
Andy Shevchenko
--
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/