[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AANLkTi=oM6bzga1HffOxZ6_T7yjSNi5RTCZtTFd4r=7j@mail.gmail.com>
Date: Wed, 13 Oct 2010 11:06:51 +0200
From: Vitaly Wool <vitalywool@...il.com>
To: Ohad Ben-Cohen <ohad@...ery.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 10:55 AM, Ohad Ben-Cohen <ohad@...ery.com> wrote:
> Hi Vitaly,
>
> On Wed, Oct 13, 2010 at 9:54 AM, Vitaly Wool <vitalywool@...il.com> wrote:
>> what about moving this logic to sdio bus_ops as this seems to be
>> completely specific to sdio right now?
>
> I actually prefer not to have any SDIO-specific logic of that kind at
> all, and instead, to use the logic we already have in mmc_pm_notify
> for all types of MMC buses.
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?
Thanks,
Vitaly
--
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