linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joerg Roedel <joerg.roedel@amd.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	mingo@elte.hu
Subject: Re: linux-next: Tree for September 2
Date: Wed, 3 Sep 2008 09:06:10 +0200	[thread overview]
Message-ID: <20080903070610.GA17919@amd.com> (raw)
In-Reply-To: <20080903093011.a5cc6887.kamezawa.hiroyu@jp.fujitsu.com>

On Wed, Sep 03, 2008 at 09:30:11AM +0900, KAMEZAWA Hiroyuki wrote:
> On Tue, 2 Sep 2008 19:02:07 +1000
> Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> 
> > Hi all,
> > 
> > Changes since next-20080901:
> > 
> > The x86 tree gained a conflict against the dwmw2 tree for which I
> > reverted a commit from the dwmw2 tree.
> > 
> > The sound tree lost its conflict.
> > 
> > The block tree gained a conflict against the device-mapper tree but lost
> > its build fix patch.
> > 
> > The ttydev tree lost a conflict but gained a build fix patch.
> > 
> > I have also applied the following patches for known problems:
> > 
> > 	ftrace: protect the definition of ftrace_release
> > 	revert BUILD_BUG_ON change
> > 	Revert "debug: add notifier chain debugging"
> > 	debug: add notifier chain debugging (different version)
> > 	sparc: qlogicpti fallout from sbus removal
> > 	powerpc: make sure all kernel test is before _etext
> > 
> From patch (not tested yet), it seems dma_alloc_coherent() on x86_64
> is still broken as I reported to August 29's linux-next.
> It easily goes down to swiotlb routine, which uses __GFP_DMA, and show
> "page allocation failure" at boot. Old code used __GFP_DMA32 as much as
> possible, I think.

Hmm, SWIOTLB unconditionally allocates from the DMA zone. Thats bad but
should be easy to change. I prepare a patch.

> Just a notification.

Thanks for pointing that out.

Joerg

-- 
           |           AMD Saxony Limited Liability Company & Co. KG
 Operating |         Wilschdorfer Landstr. 101, 01109 Dresden, Germany
 System    |                  Register Court Dresden: HRA 4896
 Research  |              General Partner authorized to represent:
 Center    |             AMD Saxony LLC (Wilmington, Delaware, US)
           | General Manager of AMD Saxony LLC: Dr. Hans-R. Deppe, Thomas McCoy

  reply	other threads:[~2008-09-03  7:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-02  9:02 linux-next: Tree for September 2 Stephen Rothwell
2008-09-03  0:30 ` KAMEZAWA Hiroyuki
2008-09-03  7:06   ` Joerg Roedel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-02  9:46 Stephen Rothwell
2010-09-02  6:13 Stephen Rothwell

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=20080903070610.GA17919@amd.com \
    --to=joerg.roedel@amd.com \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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;
as well as URLs for NNTP newsgroup(s).