linux-kernel - Re: [PATCH 03/03] mmc: Balance tmio-mmc cell enable()/disable() calls

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: <aec7e5c31001190625x2b0629f7xdef38dc6edc43586@mail.gmail.com>
Date:	Tue, 19 Jan 2010 23:25:18 +0900
From:	Magnus Damm <magnus.damm@...il.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
	ian@...menth.co.uk, lethal@...ux-sh.org, philipp.zabel@...il.com,
	pierre@...man.eu
Subject: Re: [PATCH 03/03] mmc: Balance tmio-mmc cell enable()/disable() calls

On Sat, Jan 16, 2010 at 9:06 AM, Andrew Morton
<akpm@...ux-foundation.org> wrote:
> On Fri, 27 Nov 2009 14:00:22 +0900
> Magnus Damm <magnus.damm@...il.com> wrote:
>
>> From: Magnus Damm <damm@...nsource.se>
>>
>> This patch adds cell->disable() calls to the tmio-mmc
>> probe() error handling and the remove() function.
>>
>
> This patch still doesn't apply due to linux-next changes which never
> got merged into 2.6.33-rcX.

Good news is that the linux-next issue seems solved now thanks to help
from Samuel Ortiz.

> If you think it should go into 2.6.33 then please redo a patch against
> mainline and we'll cheerily trash the problematic stuff in linux-next.

Nah, this patch is not urgent. It may also break other platforms, so I
prefer to resend it later.

Thanks,

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