From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, dzu@denx.de, wd@denx.de,
Ilya Yanok <yanok@emcraft.com>
Subject: Re: [PATCH] powerpc: rework dma-noncoherent to use generic vmap/vunmap functions
Date: Sun, 11 Jan 2009 19:47:31 -0500 [thread overview]
Message-ID: <20090112004731.GA21457@zod.rchland.ibm.com> (raw)
In-Reply-To: <fa686aa40901101631h2adee7e2j2e36624e368dc1f5@mail.gmail.com>
On Sat, Jan 10, 2009 at 05:31:19PM -0700, Grant Likely wrote:
>On Fri, Jan 9, 2009 at 5:58 AM, Ilya Yanok <yanok@emcraft.com> wrote:
>> This patch rewrites consistent dma allocations support to use vmalloc
>> layer to allocate virtual memory space from vmalloc pool and get rid
>> of CONFIG_CONSISTENT_{START,SIZE}.
>
>Impressive patch. I'll pull it into my tree and see how it works on
>4xx and 5200.
Doing my job for me now? ;)
>BTW, you can drop all the defconfig updates in this patch. The old
>config values will just disappear when 'make *_defconfig' is run.
>Putting them in the patch makes it far more likely that it won't apply
>at a later date.
Yes, totally agreed. I update the 4xx defconfigs every release, so
they will get changed when I do that.
As Ben said, this is probably too late for .29, but definitely seems
like the right way to go.
josh
next prev parent reply other threads:[~2009-01-12 0:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 12:58 [PATCH] powerpc: rework dma-noncoherent to use generic vmap/vunmap functions Ilya Yanok
2009-01-10 23:30 ` Benjamin Herrenschmidt
2009-01-11 0:31 ` Grant Likely
2009-01-12 0:47 ` Josh Boyer [this message]
2009-02-04 4:43 ` Benjamin Herrenschmidt
2009-02-12 17:40 ` Ilya Yanok
2009-02-12 20:41 ` Benjamin Herrenschmidt
2009-02-12 21:03 ` Ilya Yanok
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=20090112004731.GA21457@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc=dzu@denx.de \
--cc=grant.likely@secretlab.ca \
--cc=linuxppc-dev@ozlabs.org \
--cc=wd@denx.de \
--cc=yanok@emcraft.com \
/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).