From: Paul Mundt <lethal@linux-sh.org>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: Andrew Morton <akpm@osdl.org>,
Linux Fbdev development list
<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH 9/16] kyrofb: Driver cleanups
Date: Wed, 30 Nov 2005 12:42:43 +0200 [thread overview]
Message-ID: <20051130104243.GA16158@linux-sh.org> (raw)
In-Reply-To: <438B2257.60100@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 388 bytes --]
On Mon, Nov 28, 2005 at 11:29:27PM +0800, Antonino A. Daplas wrote:
> - remove unneeded casts
> - use framebuffer_alloc/framebuffer_release to allocate/free memory
> - the pseudo_palette is always u32 regardless of bpp if using generic
> drawing functions
>
> Signed-off-by: Antonino Daplas <adaplas@pol.net>
Looks good, thanks.
Acked-by: Paul Mundt <lethal@linux-sh.org>
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-11-30 10:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-28 15:29 [PATCH 9/16] kyrofb: Driver cleanups Antonino A. Daplas
2005-11-30 10:42 ` 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=20051130104243.GA16158@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).