From: "Miguel Ojeda" <maxextreme@gmail.com>
To: "Joe Perches" <joe@perches.com>
Cc: torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] [120/2many] MAINTAINERS - CFAG12864BFB LCD FRAMEBUFFER DRIVER
Date: Fri, 17 Aug 2007 06:37:33 +0200 [thread overview]
Message-ID: <653402b90708162137r6079d431ud91216bb7b140610@mail.gmail.com> (raw)
In-Reply-To: <1187272507.5906.80.camel@localhost>
On 8/16/07, Joe Perches <joe@perches.com> wrote:
> On Thu, 2007-08-16 at 11:16 +0200, Miguel Ojeda wrote:
> > I think you could add also:
> > +F: Documentation/auxdisplay/cfag12864bfb
>
> This is what I have now:
>
> CFAG12864BFB LCD FRAMEBUFFER DRIVER
> P: Miguel Ojeda Sandonis
> M: maxextreme@gmail.com
> L: linux-kernel@vger.kernel.org
> W: http://auxdisplay.googlepages.com/
> S: Maintained
> F: Documentation/auxdisplay/cfag12864bfb
> F: drivers/auxdisplay/cfag12864bfb.c
> F: include/linux/cfag12864b.h
>
> Joe
>
>
Oh, I got confused by the different emails:
Documentation/auxdisplay/cfag12864bfb
does not exist. I meant
Documentation/auxdisplay/cfag12864b
Also, in this patch:
[PATCH] [119/2many] MAINTAINERS - CFAG12864B LCD DRIVER
You could add the same line:
Documentation/auxdisplay/cfag12864b
As it is related to the same stuff: cfag12864b is the driver that
makes the LCD work along with ks0108; and cfag12864bfb is a
framebuffer to work with the LCD from userspace. I named it
"cfag12864b" because that is the name of the LCD, so people will not
get confused with the "fb".
As Documentation/auxdisplay/cfag12864b describes both at the same
time, it is OK to add them in both entries.
Sorry for the mistake.
--
Miguel Ojeda
http://maxextreme.googlepages.com/index.htm
next prev parent reply other threads:[~2007-08-17 4:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 6:25 joe
2007-08-16 9:16 ` Miguel Ojeda
2007-08-16 13:55 ` Joe Perches
2007-08-17 4:27 ` Miguel Ojeda
2007-08-17 4:37 ` Miguel Ojeda [this message]
2007-08-17 4:55 ` Joe Perches
2007-08-17 5:21 ` Miguel Ojeda
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=653402b90708162137r6079d431ud91216bb7b140610@mail.gmail.com \
--to=maxextreme@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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®