From: Andrew Morton <akpm@osdl.org>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: [PATCH 1/13] vt: printk: Fix framebuffer console triggering might_sleep assertion
Date: Mon, 31 Jul 2006 23:51:00 -0700 [thread overview]
Message-ID: <20060731235100.9f792539.akpm@osdl.org> (raw)
In-Reply-To: <44CE9108.1030606@gmail.com>
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.
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-08-01 6:51 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 [this message]
2006-08-01 23:10 ` Antonino A. Daplas
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=20060731235100.9f792539.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adaplas@gmail.com \
--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 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).