From: Martin Loschwitz <madkiss@madkiss.org>
To: linux-kernel@vger.kernel.org
Subject: Linux 2.5.38-ml1
Date: Sun, 22 Sep 2002 19:30:56 +0200 [thread overview]
Message-ID: <20020922173056.GA874@minerva.local.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 668 bytes --]
After some months, another patch for the Linux kernel by me. Applies against
Linux-2.5.38.
Summary of changes from v2.5.38 to v2.5.38-ml1
==============================================
o [PATCH] make check.c compile in 2.5.38 with DevFS (me)
o ALSA 0.9rc3 (except some ppc stuff) (ALSA Team)
o cpufreq for 2.5.38 (Dominik Brodowski)
o [PATCH] LTT for 2.5.38 (Karim Yaghmour)
o Linux 2.5.38-ml1 (me)
Linux 2.5.38-ml1 is available at http://www.madkiss.org/kernel/2.5.38/
--
.''`. Name: Martin Loschwitz
: :' : E-Mail: madkiss@madkiss.org
`. `'` www: http://www.madkiss.org/
`- Use Debian GNU/Linux - http://www.debian.org
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2002-09-22 17:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-22 17:30 Martin Loschwitz [this message]
2002-09-22 17:45 ` Linux 2.5.38-ml1 Martin Loschwitz
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=20020922173056.GA874@minerva.local.lan \
--to=madkiss@madkiss.org \
--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