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: <AANLkTimqo5exLf46ONKvMs5=aPwXgLrBGPAexVZJHje0@mail.gmail.com>
Date:	Wed, 13 Oct 2010 11:46:36 +0200
From:	Ohad Ben-Cohen <ohad@...ery.com>
To:	Vitaly Wool <vitalywool@...il.com>
Cc:	linux-mmc@...r.kernel.org, Greg Kroah-Hartman <gregkh@...e.de>,
	Maxim Levitsky <maximlevitsky@...il.com>,
	libertas-dev@...ts.infradead.org, Nicolas Pitre <nico@...xnic.net>,
	Sven Neumann <s.neumann@...mfeld.com>,
	linux-kernel@...r.kernel.org, "Rafael J. Wysocki" <rjw@...k.pl>,
	Daniel Mack <daniel@...aq.de>,
	Colin Cross <ccross@...roid.com>, Chris Ball <cjb@...top.org>,
	stable@...nel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH] sdio: fix suspend/resume regression

On Wed, Oct 13, 2010 at 11:06 AM, Vitaly Wool <vitalywool@...il.com> wrote:
> I don't really see the point. Instead of having SDIO-specific handling
> in the SDIO specific code, we're trying to address SDIO specific
> corner cases elsewhere. What's the rationale?

MMC core already has a card-removal mechanism which is bus independent
(in mmc_pm_notify).

Why would you prefer to duplicate this code for SDIO ?

Thanks,
Ohad.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ