Re: [PATCH 0/3] fix alloc_coherent allocation issues(tip/x86/iommu)

[Ingo Molnar]

* FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx> wrote:

> On Fri,  5 Sep 2008 17:58:46 +0900
> FUJITA Tomonori <fujita.tomonori@xxxxxxxxxxxxx> wrote:
> 
> > This patchset restores some of the current alloc_coherent behaviors
> > that Joerg's x86 patchset (in tip/x86/iommu) changes.
> > 
> > The first patch uses __GFP_DMA for NULL device argument (fallback_dev)
> > with pci-nommu. It's a hack for ISA (and some old code) so we need
> > DMA_ZONE.
> > 
> > The second patch uses __GFP_NORETRY in the case of GFP_DMA.
> > 
> > The third patch is a minor cleanup.

I've applied them to tip/x86/iommu:

 52fceb1: x86: gart alloc_coherent doesn't need to check NULL device argument
 150ba17: x86: use __GFP_NORETRY in the case of GFP_DMA with pci-nommu
 3b3d509: x86: fix nommu_alloc_coherent allocation with NULL device argument

and merged them into tip/master. Thanks!

> Oops, I messed up the subjects. They should have been:
> 
> [PATCH 1/3] x86: fix nommu_alloc_coherent allocation with NULL device argument
> [PATCH 2/3] x86: use __GFP_NORETRY in the case of GFP_DMA with pci-nommu
> [PATCH 3/3] x86: gart alloc_coherent doesn't need to check NULL device argument

that's OK - i dont rely on the numbering when picking up patches and 
they get discarded by git-am for the commit log anyway.

The only real use for numbering is when there's some really large set of 
patches (dozens of them) where i'd like to make sure no mail got dropped 
or reordered before i do some more difficult merge or conflict 
resolution run.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/