From: Dirk Behme <dirk.behme@googlemail.com>
To: linux-omap-open-source@linux.omap.com, randy.dunlap@oracle.com
Subject: OMAP FB drivers muck up the FB menu?
Date: Sun, 21 Oct 2007 08:02:00 +0200 [thread overview]
Message-ID: <471AEB58.5010608@googlemail.com> (raw)
In
http://www.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.23-git15.log
I just found this:
-- cut --
commit 0058f479e52d0c0718c843cb34223bc1bfce36e1
Author: Randy Dunlap <randy.dunlap@oracle.com>
Date: Tue Oct 16 01:29:35 2007 -0700
video gfx: fix menu ordering
Move video graphics driver configs to fix menus:
...
The OMAP FB drivers still muck up the FB menu a bit, so I put
OMAP drivers at the end of the FB menu.
...
-- cut --
Anybody with an idea what is meant there?
In same changelog there is from Randy as well:
-- cut --
commit e82ce352335b643755a7fa4130b11d6d7adcf10c
Author: Randy Dunlap <randy.dunlap@oracle.com>
Date: Tue Oct 16 23:29:44 2007 -0700
maintainers: linux-omap list is subscribers only
You are not allowed to post to this mailing list, and your
message has been
automatically rejected. If you think that your messages are
being rejected
in error, contact the mailing list owner at
linux-omap-open-source-owner@linux.omap.com.
Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Tony Lindgren <tony@atomide.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
-- cut --
Randy: Did you like to contact linux-omap list regarding OMAP FB issue
and got a reject?
Regards
Dirk
next reply other threads:[~2007-10-21 6:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-21 6:02 Dirk Behme [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-22 18:40 OMAP FB drivers muck up the FB menu? Dirk Behme
2007-10-31 12:59 ` Tony Lindgren
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=471AEB58.5010608@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=randy.dunlap@oracle.com \
/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