| 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
| ||
|
Message-ID: <m3d3jp2tde.fsf@pullcord.laptop.org> Date: Wed, 11 May 2011 10:40:13 -0400 From: Chris Ball <cjb@...top.org> To: Per Forlin <per.forlin@...aro.org> Cc: linux-mmc@...r.kernel.org, linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org, linaro-dev@...ts.linaro.org Subject: Re: [PATCH v4] sdio: optimized SDIO IRQ handling for single irq Hi Per, On Wed, May 11 2011, Per Forlin wrote: > Optimize performance for single irq > > Changes since v2. > * Rebase on mmc-next, change of line numbers no code changes. > > Stefan Nilsson XK (1): > sdio: optimized SDIO IRQ handling for single irq > > drivers/mmc/core/sdio_irq.c | 33 ++++++++++++++++++++++++++++++++- > include/linux/mmc/card.h | 1 + > 2 files changed, 33 insertions(+), 1 deletions(-) Odd, still doesn't apply here: error: patch failed: drivers/mmc/core/sdio_irq.c:42 error: drivers/mmc/core/sdio_irq.c: patch does not apply patch -p1 says: Hunk #2 succeeded at 53 with fuzz 1. So this still isn't rebased onto mmc-next properly. There haven't been any changes to drivers/mmc/core/sdio_irq.c since 2008, though, so now I'm wondering where you got the fuzz from.. - Chris. -- Chris Ball <cjb@...top.org> <http://printf.net/> One Laptop Per Child -- 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