linux-kernel - Re: [PATCH --mmotm v5 0/3] Make fault injection available for MMC IO

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: <CAJ0pr18Mpv7mFHC3NnfqEqtTFd_qgNhH9rZgCENgH0zKmBfFsQ@mail.gmail.com>
Date:	Tue, 9 Aug 2011 11:02:53 +0200
From:	Per Forlin <per.forlin@...aro.org>
To:	Akinobu Mita <akinobu.mita@...il.com>
Cc:	akpm@...ux-foundation.org,
	Linus Walleij <linus.ml.walleij@...il.com>,
	linux-kernel@...r.kernel.org, Randy Dunlap <rdunlap@...otime.net>,
	Chris Ball <cjb@...top.org>, linux-doc@...r.kernel.org,
	linux-mmc@...r.kernel.org, linaro-dev@...ts.linaro.org,
	linux-mm@...ck.org
Subject: Re: [PATCH --mmotm v5 0/3] Make fault injection available for MMC IO

On 9 August 2011 02:51, Akinobu Mita <akinobu.mita@...il.com> wrote:
> All three patches look good.
> Acked-by: Akinobu Mita <akinobu.mita@...il.com>
>
> 2011/8/9 Per Forlin <per.forlin@...aro.org>:
>> This patchset is sent to the mm-tree because it depends on Akinobu's patch
>> "fault-injection: add ability to export fault_attr in..."
>
> That patch has already been merged in mainline.
>
Please drop this patchset.
Patch #1 "fault-injection: export fault injection functions" is merged
too. There is no need to merge this through mm-tree anymore. All
fault-injection patches needed by MMC fault injection code are merged.
I'll repost the patchset to mmc-next when mmc-next has moved to 3.1
code base.

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