From: "Jaya Kumar" <jayakumar.lkml@gmail.com>
To: Sebastian Siewior <frame+buffer@ml.breakpoint.cc>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fbdev-devel@lists.sourceforge.net, tglx@linutronix.de,
Antonino Daplas <adaplas@gmail.com>
Subject: Re: [PATCH] [FB] Add the carmine FB driver.
Date: Sun, 20 Apr 2008 08:03:18 -0400 [thread overview]
Message-ID: <45a44e480804200503m7e2d158j10a87dc510e195f5@mail.gmail.com> (raw)
In-Reply-To: <20080418172824.GB22342@Chamillionaire.breakpoint.cc>
On Fri, Apr 18, 2008 at 1:28 PM, Sebastian Siewior
<frame+buffer@ml.breakpoint.cc> wrote:
> +#ifndef MODULE
> +static int __init carminefb_setup(void)
> +{
> + char *options;
> +
> + if (fb_get_options("carmine", &options))
> + return -ENXIO;
Hi Sebastian,
Interesting work. btw, I think there was some discussion of
deprecating the fb_get_options and associated manual parsing code in
favor of using module.option = value. Since this is a new driver, is
there an advantage in keeping the legacy option support?
> +
> + if (!strncmp(this_opt, "mode:", 5))
> + carminefb_mode = simple_strtoul(this_opt + 5, NULL, 0);
checkpatch suggests using strict_strtoul.
Thanks,
jaya
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
next prev parent reply other threads:[~2008-04-20 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-18 17:28 [PATCH] [FB] Add the carmine FB driver Sebastian Siewior
2008-04-19 11:06 ` Hans J. Koch
2008-04-20 8:28 ` Sebastian Siewior
2008-04-20 12:03 ` Jaya Kumar [this message]
2008-04-20 19:27 ` Sebastian Siewior
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=45a44e480804200503m7e2d158j10a87dc510e195f5@mail.gmail.com \
--to=jayakumar.lkml@gmail.com \
--cc=adaplas@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=frame+buffer@ml.breakpoint.cc \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=tglx@linutronix.de \
/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).