From: Willy Tarreau <wtarreau@hera.kernel.org>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Marcelo Tosatti <mtosatti@redhat.com>
Subject: Linux 2.4.34-pre6
Date: Sun, 19 Nov 2006 20:21:51 +0000 [thread overview]
Message-ID: <20061119202151.GA25104@hera.kernel.org> (raw)
Here's Linux 2.4.34-pre6.
Location: ftp://ftp.kernel.org/pub/linux/kernel/v2.4/testing/
Mostly cleanupts this time, as well as fixes for a few "&& 0xff"
typos. As I receivedthe RAM for my Alpha, I could attempt a few
builds with gcc-4.1 and fix 4 obvious problems (lvalue casts).
However, there are other problems somewhere else as the system
seems to hang on a pipe within the init scripts. I merged the
build fixes anyway so that people with more time can try to
chase the bugs down if they want.
Next version will be -rc1 and if everything goes well, I expect
to release 2.4.34 by the end of the year.
Regards,
Willy
Summary of changes from v2.4.34-pre5 to v2.4.34-pre6
============================================
Jean Delvare (5):
[PATCH][I2C] update web site address and contacts
[PATCH][I2C] do not ignore error when returning from i2c_add_adapter()
[PATCH][I2C] i2c-matroxfb: Struct init conversion
[PATCH][I2C] Fix copy-n-paste error in i2c Config.in.
[PATCH][I2C] remove non-existing functions declarations.
NeilBrown (1):
knfsd: Fix race that can disable NFS server.
Willy Tarreau (12):
[PATCH-2.4] i2c-elv: fix erroneous '&&' operator
fix "&& 0xffff" typo in gdth.c
fix obvious "&& 0xFFFFFF" typo in cpqfcTSworker
fix "&& 0xff" typo in qeth_qdio_input_handler
fix two "&& 0x03" in usbnet
EXT3: avoid crashing by not dividing by zero.
EXT2: avoid crashing by not dividing by zero.
[GCC4] fix build error in arch/alpha/kernel/osf_sys.c
[GCC4] fix build error in arch/alpha/kernel/irq.c
[GCC4] fix build error in arch/alpha/lib/io.c
[GCC4] fix build error in arch/alpha/math-emu/math.c
Change VERSION to 2.4.34-pre6
reply other threads:[~2006-11-19 20:22 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=20061119202151.GA25104@hera.kernel.org \
--to=wtarreau@hera.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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.