Linux 2.4.26-rc1

From: Marcelo Tosatti
Date: Sat Mar 27 2004 - 23:43:49 EST

Finally, -rc1.

The first -rc contains an ACPI update, networking fixes, amongst others.

Please test!

Summary of changes from v2.4.26-pre6 to v2.4.26-rc1

Chas Williams:
o [ATM]: [lec] lec_push() races with vcc->proto_data
o [ATM]: [nicstar] use kernel min/max (by Randy.Dunlap <rddunlap@xxxxxxxx>)

David S. Miller:
o [IGMP]: Do nothing in ip_mc_down() if ip_mc_up() was not called previously
o [SPARC64]: Update defconfig

Dmitry Torokhov:
o [NET_SCHED]: Fix class reporting in TBF qdisc
o [NET_SCHED]: Trailing whitespace cleanup in TBF scheduler

Jon Oberheide:
o [CRYPTO]: Remove confusing TODO comment in arc4.c

Julian Anastasov:
o [IPVS] Fix to update the skb->h.raw after skb reallocation in tunnel_xmit
o [IPVS] Fix connection rehashing with new cport

Len Brown:
o [ACPI] PCI interrupt link routing (Luming Yu) use _PRS to determine resource type for _SRS fixes HP Proliant servers
o [ACPI] proposed fix for non-identity-mapped SCI override
o [ACPI] ACPICA 20040326 from Bob Moore
o [ACPI] Linux specific updates from ACPICA 20040326 "acpi_wake_gpes_always_on" boot flag for old GPE behaviour

Marcel Holtmann:
o [Bluetooth] Add support for AVM BlueFRITZ! USB v2.0
o [Bluetooth] Remove non-blocking socket fix

Marcelo Tosatti:
o Trond: Avoid refile_inode() from putting locked inodes on the dirty list
o Changed EXTRAVERSION to -rc1

Martin Devera:
o [NET_SCHED]: HTB scheduler updates

Patrick McHardy:
o [NET_SCHED]: Fix broken indentation in HFSC scheduler
o [NET_SCHED]: Fix requeueing in HFSC scheduler
o [NET_SCHED]: Use queue limit of 1 when tx_queue_len is zero

Sridhar Samudrala:
o [SCTP] Don't do any ppid byte-order conversions as it is opaque to SCTP
o [SCTP] Avoid the use of hacking CONFIG_IPV6_SCTP__ option

Stephen Hemminger:
o [NET_SCHED]: Add packet delay scheduler

Wensong Zhang:
o [IPVS]: Fix to hold the lock before updating a service

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at