From: "Miguel Ojeda" <maxextreme@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.17.13] display: Driver ks0108 and cfag12864b
Date: Tue, 12 Sep 2006 08:09:22 +0200 [thread overview]
Message-ID: <653402b90609112309p7be570a2ra9e1c22ad9c7a0d7@mail.gmail.com> (raw)
In-Reply-To: <20060912035131.GA27472@kroah.com>
On 9/12/06, Greg KH <greg@kroah.com> wrote:
>
> The patch is linewrapped :(
>
Please tell me if the next one is linewrapped too.
>
> Why would you need to touch udev? It will handle stuff loaded at any
> point in time automatically. You don't have to "update udev" at all.
>
My fault. My firsts tests were on a Vector Linux, and, I don't know
why (bad cfg I guess), but udev didn't create the nodes automatically.
Now, in Debian, it does. I have noticed that and the last patch
doesn't have such lines. Sorry.
>
> Do you really mean for your header file to be under the GPL for
> userspace programs?
>
Ups, it is just an example for a user-space program that wants to use
the cfag12864b. I will remove the License line anyway.
>
> Which version of the GPL?
>
The same as the kernel, I think. Is that right?
> [about useless printk's]
> Is this really needed?
>
It isn't anymore. In the patch it is also removed and all the printks
improved, as Alexey Dobriyan told me also to do.
> "Display" is very generic, people will think it is for video stuff too.
> LCD perhaps might be better?
>
I thought the same, but LCD is already used by the "PDA Frontal LCD
Panel". They got the "linux/lcd.h" and "drivers/lcd/*", as well as a
fixed major number.
So I thought "bigger" and, IMHO a new folder for this kind of
misc-secondary-display devices (LCD or not) will be fine.
I think (maybe I'm wrong but...), we can just put the drivers right
there. There are a lot of this kind of hardware, but it will take time
to code more drivers. So if the resulting drivers are so different or
the drivers/* get a major update, relocate them. If not, leave them
until we have enough samples to start classifying.
prev parent reply other threads:[~2006-09-12 6:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-11 23:27 Miguel Ojeda
2006-09-11 23:54 ` [PATCH 1/2] " Miguel Ojeda
2006-09-11 23:57 ` [PATCH 2/2] " Miguel Ojeda
2006-09-12 1:13 ` Alexey Dobriyan
2006-09-12 2:37 ` Miguel Ojeda
2006-09-12 3:51 ` [PATCH 2.6.17.13] " Greg KH
2006-09-12 5:50 ` [PATCH V2] " Miguel Ojeda
2006-09-12 6:09 ` Miguel Ojeda [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=653402b90609112309p7be570a2ra9e1c22ad9c7a0d7@mail.gmail.com \
--to=maxextreme@gmail.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--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
all inboxes | Powered by JetHome®