public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mariusz Mazur <mmazur@kernel.pl>
To: linux-kernel@vger.kernel.org
Subject: [ANNOUNCE] linux-libc-headers 2.6.6.0
Date: Wed, 9 Jun 2004 16:37:55 +0200	[thread overview]
Message-ID: <200406091637.55771.mmazur@kernel.pl> (raw)

Available at http://ep09.pld-linux.org/~mmazur/linux-libc-headers/
Changes:
- updated to 2.6.6 kernel
- readded allmost all of the sound/* headers; some of those contain driver 
specific definitions that might be used in userland apps to control various 
hardware features 
- added scsi headers - more on that below 
- fixed macros in byteorder/swab.h - now hdparm on big endian machines really 
builds
- other fixes (eg. frottle should build)
- I've made linux/audit.h parse out of the box; if I understand correctly this 
is supposed to be a "kernel talks to userland" thing


First of all sorry for the long delay - this version should be here three 
weeks ago, but I've been kind of busy. This shouldn't happen anymore and new 
version should be released no more than a week after the kernel.
(yes, I know 2.6.7 will probably be here in a week or so :)

As for the addition of sanitized scsi headers - I've had some requests for it. 
Up until now I've encountered only one app that wanted something more than 
glibc had to offer and am not entirely sure if using these headers instead of 
glibc's won't break more things than it fixes. Test it if you like and do 
send a bugreport if you find that it breaks something.


-- 
In the year eighty five ten
God is gonna shake his mighty head
He'll either say,
"I'm pleased where man has been"
Or tear it down, and start again

                 reply	other threads:[~2004-06-09 14:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200406091637.55771.mmazur@kernel.pl \
    --to=mmazur@kernel.pl \
    --cc=linux-kernel@vger.kernel.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