From: Paul Mundt <lethal@linux-sh.org>
To: Magnus Damm <magnus.damm@gmail.com>
Cc: linux-sh@vger.kernel.org, linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH] sh: split coherent pages
Date: Wed, 17 Dec 2008 17:33:02 +0900 [thread overview]
Message-ID: <20081217083302.GA6483@linux-sh.org> (raw)
In-Reply-To: <20081217082949.30120.83664.sendpatchset@rx1.opensource.se> <20081217081845.28528.20104.sendpatchset@rx1.opensource.se>
On Wed, Dec 17, 2008 at 05:18:45PM +0900, Magnus Damm wrote:
> Split pages returned by dma_alloc_coherent() and make sure
> we free them one by one.
>
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
On Wed, Dec 17, 2008 at 05:29:49PM +0900, Magnus Damm wrote:
> Since the sh_mobile_lcdc hardware has the framebuffer(s) in system RAM,
> use FB_SYS instead of FB_CFB. Also hook in read and write helpers.
>
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
Both applied, thanks.
prev parent reply other threads:[~2008-12-17 8:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-17 8:29 [PATCH] sh_mobile_lcdc: use FB_SYS helpers instead of FB_CFB Magnus Damm
[not found] ` <20081217081845.28528.20104.sendpatchset@rx1.opensource.se>
2008-12-17 8:33 ` Paul Mundt [this message]
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=20081217083302.GA6483@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).