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
| ||
|
Date: Mon, 4 Feb 2013 11:47:37 +0300 From: Dan Carpenter <dan.carpenter@...cle.com> To: Roger Tseng <rogerable@...ltek.com> Cc: cjb@...top.org, sameo@...ux.intel.com, gregkh@...uxfoundation.org, linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org, wei_wang@...lsil.com.cn, devel@...uxdriverproject.org Subject: Re: [PATCH 1/3] MMC: rtsx: remove driving adjustment On Mon, Feb 04, 2013 at 03:45:57PM +0800, Roger Tseng wrote: > Several new models of readers use different way to select driving > capability(a necessary adjustment along with voltage change). Removing this > from device-independent rtsx_pci_sdmmc module. It will be implemented in > device-depend calls encapsulated by rtsx_pci_switch_output_voltage(). > I'm not sure I understand. Does this patch break things and then "[PATCH 2/3] mfd: rtsx: implement driving adjustment to device-dependent callbacks" fixes things again? In other words, will all the old devices run if we only apply patch 1/3 and not 2/3? That's not the right idea. Just merge the two patches into one patch. regards, dan carpenter -- 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