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: <4A324C0C.8070302@atmel.com>
Date:	Fri, 12 Jun 2009 14:37:32 +0200
From:	Nicolas Ferre <nicolas.ferre@...el.com>
To:	Rob Emanuele <poorarm@...reis.com>
CC:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>,
	Joey Oravec <joravec@...wtech.com>,
	linux-arm-kernel@...ts.arm.linux.org.uk,
	linux-kernel@...r.kernel.org, drzeus-mmc@...eus.cx
Subject: Re: [PATCH][Fix] New Unified AVR32/AT91 MCI Driver that supports
 both 	MCI slots used at the same time

Rob Emanuele :
>>  - The patch seems to do a bit too much all at once. The bug fix which
>>    has already been fixed is one example, another is the clock cap
>>    option -- we used to have a module parameter for the same purpose,
>>    but Pierre (the MMC maintainer, who should probably be added to the
>>    loop) had problems with it. If this feature was in a separate
>>    patch, it could be rejected without blowing away the rest of the
>>    driver.
> 
> Which kernel branch should I generate the patch against to have the
> most recent set of changes?

I think that you can use current (today) linus' git tree with this
additional patch from Haavard in avr32 tree
"Add support for inverted detect pin":
http://git.kernel.org/?p=linux/kernel/git/hskinnemoen/avr32-2.6.git;a=commit;h=1c1452be2e9ae282a7316c3b23987811bd7acda6

Kind regards,
-- 
Nicolas Ferre

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