From: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: devel@driverdev.osuosl.org, linux-fbdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] staging: sm7xxfb: start using module parameters
Date: Tue, 24 Mar 2015 10:40:35 +0000 [thread overview]
Message-ID: <20150324102835.GA7986@sudip-PC> (raw)
In-Reply-To: <20150324094826.GB6378@kroah.com>
On Tue, Mar 24, 2015 at 10:48:26AM +0100, Greg Kroah-Hartman wrote:
> On Tue, Mar 24, 2015 at 10:20:08AM +0530, Sudip Mukherjee wrote:
> > + "\t\t0x31B = 1280x1024-24\n"
> > + "\t\tUsual example:\n"
> > + "\t\tinsmod ./sm7xxfb.ko mode_option=\"0x301\"\n");
> > +
>
> That's funny :)
>
> And how do you handle multiple devices in the system?
frankly speaking, never got the idea about multiple devices.
>
> :(
>
> Seriously, never use module parameters for device parameters, they are
> two different things. The framebuffer core has options for handling
> modes, why not use them?
>
> And yes, lots of framebuffer drivers do have crazy module parameters,
> but that doesn't mean you have to perpetuate the insanity, please do
> things properly here.
i am learning from other framebuffer drivers. i guess i should only
see at skeletonfb.c and not the others.
please drop this 1/2 patch, do i need to resend the 2/2 which adds
the MODULE_DEVICE_TABLE ?
regards
sudip
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2015-03-24 10:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-24 4:50 [PATCH 1/2] staging: sm7xxfb: start using module parameters Sudip Mukherjee
2015-03-24 4:50 ` [PATCH 2/2] staging: sm7xxfb: add MODULE_DEVICE_TABLE Sudip Mukherjee
2015-03-24 9:48 ` [PATCH 1/2] staging: sm7xxfb: start using module parameters Greg Kroah-Hartman
2015-03-24 10:40 ` Sudip Mukherjee [this message]
2015-03-24 10:40 ` Greg Kroah-Hartman
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=20150324102835.GA7986@sudip-PC \
--to=sudipm.mukherjee@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).