linux-kernel - Re: [PATCH 00/05] tmio_mmc: Minor fixes and cnf/irq changes

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]

Date:	Tue, 31 Mar 2009 11:51:11 +0900
From:	Magnus Damm <magnus.damm@...il.com>
To:	Ian Molton <ian@...menth.co.uk>
Cc:	Pierre Ossman <drzeus@...eus.cx>, linux-kernel@...r.kernel.org,
	drzeus-wbsd@...eus.cx, akpm@...ux-foundation.org
Subject: Re: [PATCH 00/05] tmio_mmc: Minor fixes and cnf/irq changes

On Wed, Mar 25, 2009 at 5:56 PM, Magnus Damm <magnus.damm@...il.com> wrote:
> On Tue, Mar 24, 2009 at 11:07 AM, Ian Molton <ian@...menth.co.uk> wrote:
>> Ideally, the MMC code would use the clock API for some of this, but I seem
>> to remember there were issues with this (cant recall what right now and its
>> 2:05 AM).
>
> No worries. For me the clock framework would be the best fit too. Not
> sure about the exact details right now, but I _do_ know that we right
> now we have nothing, so being able to use tmio_mmc as is (with posted
> patches) is a great step forward. Working out the clock framework
> details after that should be no biggie. Step by step.
>
> Or if you want me to rewrite things that's fine as well. Just let me
> know what to do. =)

Ping? Please let me know how you want me to rework the patches. Unless
they are ok as-is. Any feedback on how to rewrite them would be
greatly appreciated.

These patches should leave register accesses unchanged for the common
case. The only change is to allow using the driver with only a single
io memory area. I split out this change in two separate patches to
make review easy.

I realize that we're running late for 2.6.30-rc1, but since these
patches are isolated driver changes a later merge may be possible, I'm
not sure.

Anyway, regardless of merge timing it would be great to move forward somehow.

Thank you.

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