From: John Belmonte <john-wanGne27zNesTnJN9+BGXg@public.gmane.org>
To: "Brown, Len" <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: preparing toshiba_acpi driver release
Date: Mon, 26 Jan 2004 11:32:57 -0500 [thread overview]
Message-ID: <40154139.40009@neggie.net> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Len,
I'm preparing a new release of the toshiba_acpi driver. Below is the
tentative changelog. I haven't been following the check-in policy of
the kernel or acpi subsystem lately, so I'm wondering if I can give this
to you as a single patch or do you need it in several parts.
~ * Fix remote chance of invalid buffer access in write_video.
~ * Support alternate HCI method path (recent "Phoenix BIOS" Toshiba's).
~ * Report more proc-write errors.
~ * On proc-reads, report errors via printk instead of proc output.
~ * Add level to all printk's.
~ * Add missing __init and __exit function attributes.
Regards,
- -John Belmonte
- --
http:// if ile.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFAFUE35Nfg6kxAQQoRAjQaAKCsdt8QoBH6w2TbtyPSzfpEy1ywMACguflq
cc6Z79zaEhCmj4C9USs5TBE=
=oq55
-----END PGP SIGNATURE-----
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next reply other threads:[~2004-01-26 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-26 16:32 John Belmonte [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-26 17:44 preparing toshiba_acpi driver release Brown, Len
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=40154139.40009@neggie.net \
--to=john-wangne27znestnjn9+bgxg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 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.