From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Rodolfo Giometti <giometti@linux.it>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/13] vt: printk: Fix framebuffer console triggering might_sleep assertion
Date: Wed, 02 Aug 2006 07:10:31 +0800 [thread overview]
Message-ID: <44CFDF67.4030206@gmail.com> (raw)
In-Reply-To: <20060731235100.9f792539.akpm@osdl.org>
Andrew Morton wrote:
> hm, which (if any) of these would be considered 2.6.18 material?
>
> *vt-printk-fix-framebuffer-console-triggering-might_sleep.patch
> *au1100fb-info-varrotate-fix.patch
> au1100fb-add-option-to-enable-disable-the-cursor.patch
> *au1100fb-fix-startup-sequence.patch
> intelfb-documentation-update.patch
> rivafb-use-constants-instead-of-magic-values.patch
> vfb-document-option-to-enable-the-driver.patch
> fbdev-add-generic-ddc-read-functionality.patch
> nvidiafb-use-generic-ddc-reading.patch
> rivafb-use-generic-ddc-reading.patch
> i810fb-use-generic-ddc-reading.patch
> savagefb-use-generic-ddc-reading.patch
> radeonfb-use-generic-ddc-reading.patch
>
> I've asterisked my guesses.
>
The first and third guesses, I believe, are 2.6.18 material. Not sure on
the second...
Tony
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
prev parent reply other threads:[~2006-08-01 23:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-31 23:23 [PATCH 1/13] vt: printk: Fix framebuffer console triggering might_sleep assertion Antonino A. Daplas
2006-08-01 6:51 ` Andrew Morton
2006-08-01 23:10 ` Antonino A. Daplas [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=44CFDF67.4030206@gmail.com \
--to=adaplas@gmail.com \
--cc=akpm@osdl.org \
--cc=giometti@linux.it \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.