From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: linux-next: Tree for July 16 (crash on quad core AMD) Date: Mon, 21 Jul 2008 09:38:36 +0900 Message-ID: <4883DA8C.5030306@gmail.com> References: <20080716235011.ac9643aa.sfr@canb.auug.org.au> <200807170053.36661.rjw@sisk.pl> <1216249292.3358.66.camel@localhost.localdomain> <200807170109.30655.rjw@sisk.pl> <48808EE0.2060603@gmail.com> <20080719004736.626ef169@mjolnir.drzeus.cx> <48813C5F.70007@gmail.com> <20080719033050.552f9b49@mjolnir.drzeus.cx> <48814D81.8060001@gmail.com> <20080719140717.7b296eae@mjolnir.drzeus.cx> <4881F437.7000503@gmail.com> <20080721004033.1fc66aa3@mjolnir.drzeus.cx> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:received:message-id:date:from :user-agent:mime-version:to:cc:subject:references:in-reply-to :x-enigmail-version:content-type:content-transfer-encoding; bh=Q1xALcW3OdtScfyIyuDwvdhDMG6WtVdJAxzuW+J6gOw=; b=C1Q427BbUs4CUKV/HJtOsk1cbbQU4maIlKvBQhsf+75hBvedCFsyTyRpBftiMTT2cl B7jzhLBce2wUyV4hZq1qpB/AXQIwEKqEZ3EtWNhZzctTsZhcw+dA/tFa47vnOWhXyDDN mu6S2CK34VAJ/r6awzRz+BBYHWzfeQlIjjVnk= In-Reply-To: <20080721004033.1fc66aa3-OhHrUh4vRMSnewYJFaQfwJ5kstrrjoWp@public.gmane.org> Sender: kernel-testers-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Pierre Ossman Cc: "Rafael J. Wysocki" , James Bottomley , Stephen Rothwell , linux-next-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, LKML , Andrew Morton , Kernel Testers List , scsi , Jens Axboe , linux-ide , Jeff Garzik , Takashi Iwai , tino.keitel-Mmb7MZpHnFY@public.gmane.org Hello, Pierre. Pierre Ossman wrote: > I've converted my code to use your implementation instead, and it seems > to be working perfectly. Cool. > How comfortable to you feel about your patch? :) I think it should be okay (well, of course :-) and tested a few corner cases by modifying the copy function. > This fixes a big problem in the sdhci driver where falling back on PIO > (because of hw DMA bugs) would create lots of potential issues as the > driver couldn't access highmem pages. I'd like to get this fix in for > 2.6.27, which means that your patch also needs to go in now. I think it needs an ACK from Jens. Jens? -- tejun