From: Tejun Heo <htejun@gmail.com>
To: Pierre Ossman <drzeus@drzeus.cx>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Kernel Testers List <kernel-testers@vger.kernel.org>,
scsi <linux-scsi@vger.kernel.org>,
Jens Axboe <jens.axboe@oracle.com>,
linux-ide <linux-ide@vger.kernel.org>,
Jeff Garzik <jeff@garzik.org>, Takashi Iwai <tiwai@suse.de>,
tino.keitel@gmx.de
Subject: Re: linux-next: Tree for July 16 (crash on quad core AMD)
Date: Mon, 21 Jul 2008 09:38:36 +0900 [thread overview]
Message-ID: <4883DA8C.5030306@gmail.com> (raw)
In-Reply-To: <20080721004033.1fc66aa3@mjolnir.drzeus.cx>
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
next prev parent reply other threads:[~2008-07-21 0:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-16 13:50 linux-next: Tree for July 16 Stephen Rothwell
2008-07-16 18:15 ` Takashi Iwai
2008-07-17 7:17 ` Tino Keitel
2008-07-16 22:53 ` linux-next: Tree for July 16 (crash on quad core AMD) Rafael J. Wysocki
2008-07-16 23:01 ` James Bottomley
2008-07-16 23:09 ` Rafael J. Wysocki
2008-07-18 12:38 ` Tejun Heo
2008-07-18 22:47 ` Pierre Ossman
2008-07-19 0:59 ` Tejun Heo
2008-07-19 1:30 ` Pierre Ossman
2008-07-19 2:12 ` Tejun Heo
2008-07-19 12:07 ` Pierre Ossman
2008-07-19 14:03 ` Tejun Heo
2008-07-20 22:40 ` Pierre Ossman
2008-07-21 0:38 ` Tejun Heo [this message]
2008-07-21 11:32 ` Pierre Ossman
2008-07-21 15:35 ` Tejun Heo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4883DA8C.5030306@gmail.com \
--to=htejun@gmail.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=akpm@linux-foundation.org \
--cc=drzeus@drzeus.cx \
--cc=jeff@garzik.org \
--cc=jens.axboe@oracle.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=rjw@sisk.pl \
--cc=sfr@canb.auug.org.au \
--cc=tino.keitel@gmx.de \
--cc=tiwai@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox