The naming wars continue...
Subsystems (4)
Ok,
Linux-2.6.10-rc1 is out there for your pleasure.
I thought long and hard about the name of this release (*), since one of the main complaints about 2.6.9 was the apparently release naming scheme.
Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
So to not overtax my poor brain, I'll just call them all -rc releases, and hope that developers see them as a sign that there's been stuff merged, and we should start calming down and seeing to the merged patches being stable soon enough..
So without any further ado, here's 2.6.10-rc1 in testing. A fair number of patches that were waiting for 2.6.9 to be out are in here, ranging all over the map: merges from -mm, network (and net driver) updates, SATA stuff, bluetooth, SCSI, device models, janitorial, you name it.
Oh, and the _real_ name did actually change. It's not Zonked Quokka any more, that's so yesterday. Today we're Woozy Numbat! Get your order in!
Linus
(*) In other words, I had a beer and watched TV. Mmm... Donuts.
----
Summary of changes from v2.6.9 to v2.6.10-rc1
============================================
Aaron Grothe:
o [CRYPTO]: Put khazad back into tcrypt table
Adam Radford:
o 3ware 5/6/7/8000 driver v1.26.02.000
o 3ware 5/6/7/8000 driver update
Adrian Bunk:
o qla2xxx gcc-3.5 fixes
o #include <asm/bitops.h> -> #include <linux/bitops.h>
o fix block/cciss.c with PROC_FS=n
o make CONFIG_PM_DEBUG depend on CONFIG_PM
o Another ISA PnP modem (USR0009)
Al Borchers:
o USB: corrected digi_acceleport 2.6.9-rc1 fix for hang on disconnect
o USB: circular buffer for pl2303
o USB: close waits for drain in pl2303
Alan Stern:
o USB: Make usbcore use usb_kill_urb()
o USB: Suspend/resume/wakeup support for UHCI root hub ports
o USB: Remove inappropriate unusual_devs.h entry
o USB: Nag message for usb_kill_urb
o USB: Centralize logical disconnects in the hub driver
o USB: Internal port numbers start at 0
o USB: Add OTG support to g_file_storage
o USB: New submission procedure for unusual_devs.h
o USB: Unusual_devs entry for Panasonic cameras
o Add BLIST_INQUIRY_36 to all USB blacklist entries
o USB: Improve UHCI suspend/resume
o USB: Fix off-by-one error in the hub driver
o USB: Updated USB device locking
o USB: Add locking support for USB device resets
o USB: Descriptor listing bugfix for g_file_storage
o USB: Allow device resets for hubs
o USB: Support system suspend in File-Storage Gadget
o USB: Suspend update for dummy_hcd
o USB: Activate new hubs and resumed hubs the same way
o USB: Use list_for_each_entry etc. in UHCI driver
o USB: Fix data toggle handling in the UHCI driver
o Let LLD specify INQUIRY length
o USB Storage: new unusual_devs entry
Albert Cahalan:
o distinct tgid/tid CPU usage
Alex Kanavin:
o USB: export inteface and configuration strings to sysfs
o USB: USB CDC OBEX driver
Alexander Viro:
o [netdrvr eth1394] use netdev_priv
o [netdrvr usb] use netdev_priv
o [netdrvr] netdev_priv for ewrk3, xircom_tulip_cb, wavelan_cs
o [netdrvr] netdev_priv for sundance, typhoon, yellowfin
o [netdrvr] use netdev_priv in dl2k, hamachi
o [netdrvr starfire] fix unregister_netdev call site
o [netdrvr starfire] use netdev_priv
o (1/27) eth1394 ethtool conversion
o (2/27) cris ethtool conversion
o (3/27) ixgb ethtool conversion
o (4/27) 3c509 ethtool conversion
o (5/27) smc91c92_cs ethtool conversion
o (6/27) tulip ethtool conversion
o (7/27) xircom ethtool conversion
o (8/27) wavelan ethtool conversion
o (9/27) wl3501_cs ethtool conversion
o (10/27) yellowfin ethtool conversion
o (11/27) typhoon ethtool conversion
o (12/27) sundance ethtool conversion
o (13/27) starfire ethtool conversion
o (14/27) ns83820 ethtool conversion
o (15/27) natsemi ethtool conversion
o (16/27) veth ethtool conversion
o (17/27) hamachi ethtool conversion
o (18/27) forcedeth ethtool conversion
o (19/27) ewrk3 ethtool conversion
o (20/27) eepro100 ethtool conversion
o (21/27) dl2k ethtool conversion
o (22/27) amd8111e ethtool conversion
o (23/27) gadget ethtool conversion
o (24/27) rtl8150 ethtool conversion
o (25/27) pegasus ethtool conversion
o (26/27) kaweth ethtool conversion
o (27/27) catc ethtool conversion
o amd8111e iomem annotations
o typhoon.c missing include
o 64bit fix in cycx_x25.c
o cyclom iomem annotations
o hd6457x iomem annotations
o dscc4 iomem annotations
o bunch of trivial iomem annotations in drivers/net
o rrunner iomem annotations
o via-velocity iomem annotations
o tulip iomem annotations, switch to io{read,write}
o winbond840 iomem annotations, switch to io{read,write}
o forcedeth iomem annotations
o yellowfin iomem annotations, switch to io{read,write}
o hp100 iomem annotations
o lanstreamer fix
o moxa iomem annotations
o sparc32 kconfig fixes
o if_ppp.h __user annotation
o sx.c iomem annotations and fixes
o skystar2 iomem annotations
o kyro iomem annotations
o teles{0,pci} iomem annotations
o isurf iomem annotations
o ipr iomem annotations
o ips iomem annotations
o megaraid iomem annotations
o nsp32 iomem annotations
o aac7xxx iomem annotations
o ioremap cleanups in aic7xxx
o qla1820 iomem annotations
o missing includes of asm/irq.h
o depca removal of bogus virt_to_bus() uses
o aacraid iomem annotations
o fusion iomem annotations
o alpha writeq fixes
o amd64 io.h annotations
o amd64 uaccess.h annotations
o alpha io_remap_page_range() compile fix
o ppc io.h annotations
o sparc64 missing volatile in io.h prototypes
o added typechecking ot sparc64 ioremap()
o qlogicisp iomem annotations
o aic7xxx_old iomem annotations (for real, this time)
o aty iomem annotations
o initio.c NULL noise removal
Andi Kleen:
o scsi: add proper pci id table to aic7xxx
o x86-64/i386: add mce tainting
o [TCP]: Remove bogus CONFIG_SYSCTL ifdef
o x86_64: drop old APIC workaround
o x86_64: intialize hpet char driver
o x86_64: use TSC on SMP EM64T machines
o x86_64: add notsc option
o x86_64: add an option to configure oops stack dump
o x86_64: fix IOAPIC on Nvidia boards
o x86_64 Kconfig: Split CONFIG_NUMA_EMU and CONFIG_K8_NUMA
Andrea Arcangeli:
o parport_pc superio chip fixes
Andreas Gruenbacher:
o Replace hard-coded MODVERDIR in modpost
o xattr: re-introduce validity check before xattr cache insert
Andreas Henriksson:
o fbdev: Remove i810fb explicit agp initialization hack
Andreas Herrmann:
o s390: zfcp host adapter
Andrei Konovalov:
o ppc32: Xilinx ML300 board support (very basic)
Andrew Morton:
o tmscsim.c build fix
o kobject_uevent warning fix
o ksysfs warning fix
o pegasus.c fixes
o PCI: fix up usb quirk __init marks
o PCI: CONFIG_PCI=n build fix
o PCI: pci_dev_put() build fix
o psi240i build fix
o sched: arch_destroy_sched_domains warning fix
o sched: print preempt count
o reiserfs: rename struct key
o jbd wakeup fix
o unreachable code in ext3_direct_IO()
o typhoon build fix
o module_parm_array fixups
o select-cpio_list-or-source-directory-for-initramfs-image fix
o vmalloc_to_page() preempt cleanup
o typhoon build fix
o v4l: missing bits
o i2o: missing bits from merge
o [NETFILTER]: Avoid warning on CONNTRACK_STAT_INC in death_by_timeout()
o [NET]: neigh_stat preempt fix
o [CRYPTO]: Deinline large function in blowfish.c
o Fix build for CONFIG_SECURITY=n
Andrew Vasquez:
o [1/8] qla2xxx: PCI posting fixes
o [2/8] qla2xxx: Dynamic resize of request-q
o qla2xxx: DMA pool/api usage
o [4/8] qla2xxx: Small fixes
o [5/8] qla2xxx: Rework ISR registration
o qla2xxx: 23xx/63xx firmware updates
o [8/8] qla2xxx: Update version
o Fix qla2xxx mismerge
o SCSI QLA not working on latest *-mm SN2 (qla_dbg fixes)
Andy Whitcroft:
o vm_dirty_ratio initialisation fix
Anton Altaparmakov:
o NTFS: Implement extent mft record deallocation
o NTFS: Splitt runlist related functions off from attrib.[hc] to runlist.[hc]
o NTFS: Add vol->mft_data_pos and initialize it at mount time
o NTFS: Rename init_runlist() to ntfs_init_runlist(), ntfs_vcn_to_lcn() to ntfs_rl_vcn_to_lcn(), decompress_mapping_pairs() to ntfs_mapping_pairs_decompress() and adapt all callers.
o NTFS: Forgot to lock the mft bitmap when clearing the bit in ntfs_extent_mft_record_free().
o NTFS: Add fs/ntfs/runlist.[hc]::ntfs_get_nr_significant_bytes(), ntfs_get_size_for_mapping_pairs(), ntfs_write_significant_bytes(), and ntfs_mapping_pairs_build(), adapted from libntfs.
o NTFS: Rename ntfs_merge_runlists() to ntfs_runlists_merge()
o NTFS: - Add fs/ntfs/lcnalloc.h::ntfs_cluster_free_from_rl() which is a static inline wrapper for ntfs_cluster_free_from_rl_nolock() which takes the cluster bitmap lock for the duration of the call.
o NTFS: Add fs/ntfs/attrib.[hc]::ntfs_attr_record_resize()
o NTFS: Implement the equivalent of memset() for an ntfs attribute in fs/ntfs/attrib.[hc]::ntfs_attr_set() and switch fs/ntfs/logfile.c::ntfs_empty_logfile() to using it.
o NTFS: Remove unnecessary casts from LCN_* constants
o NTFS: Implement fs/ntfs/runlist.c::ntfs_rl_truncate_nolock()
o NTFS: Add MFT_RECORD_OLD as a copy of MFT_RECORD in fs/ntfs/layout.h and change MFT_RECORD to contain the NTFS 3.1+ specific fields.
o NTFS: Add some debugging checks to fs/ntfs/inode.c::ntfs_truncate() and fix a typo in fs/ntfs/layout.h.
o NTFS: Add a helper function fs/ntfs/aops.c::mark_ntfs_record_dirty() which marks all buffers belonging to an ntfs record dirty, followed by marking the page the ntfs record is in dirty and also marking the vfs inode containing the ntfs record dirty (I_DIRTY_PAGES).
o NTFS: Switch fs/ntfs/index.h::ntfs_index_entry_mark_dirty() to using the new helper fs/ntfs/aops.c::mark_ntfs_record_dirty() and remove the no longer needed fs/ntfs/index.[hc]::__ntfs_index_entry_mark_dirty().
o NTFS: - Move ntfs_{un,}map_page() from ntfs.h to aops.h and fix resulting include errors.
o NTFS: Remove unused {__,}format_mft_record() from fs/ntfs/mft.c
o NTFS: - Modify fs/ntfs/mft.c::__mark_mft_record_dirty() to use the helper mark_ntfs_record_dirty() which also changes the behaviour in that we now set the buffers belonging to the mft record dirty as well as the page itself.
o NTFS: Update fs/ntfs/inode.c::ntfs_write_inode() to also use the helper mark_ntfs_record_dirty() and thus to set the buffers belonging to the mft record dirty as well as the page itself.
o NTFS: Fix warnings on x86-64. (Randy Dunlap with slight modification from me)
o NTFS: Add fs/ntfs/mft.c::try_map_mft_record() which fails with -EALREADY if the mft record is already locked and otherwise behaves the same way as fs/ntfs/mft.c::map_mft_record().
o NTFS: Modify fs/ntfs/mft.c::write_mft_record_nolock() so that it only writes the mft record if the buffers belonging to it are dirty.
o NTFS: Attempting to write outside initialized size is _not_ a bug so remove the bug check from fs/ntfs/aops.c::ntfs_write_mst_block(). It is in fact required to write outside initialized size when preparing to extend the initialized size.
o NTFS: Map the page instead of using page_address() before writing to it in fs/ntfs/aops.c::ntfs_mft_writepage().
o NTFS: Provide exclusion between opening an inode / mapping an mft record and accessing the mft record in fs/ntfs/mft.c::ntfs_mft_writepage() by setting the page not uptodate throughout ntfs_mft_writepage().
o NTFS: Big cleanup of mft record writing code
o NTFS: - Fix two race conditions in
fs/ntfs/inode.c::ntfs_put_inode()
o NTFS: Modify fs/ntfs/aops.c::mark_ntfs_record_dirty() to no longer take the ntfs inode as a parameter as this is confusing and misleading and the ntfs inode is available via NTFS_I(page->mapping->host).
o NTFS: Modify fs/ntfs/mft.c::write_mft_record_nolock() and fs/ntfs/aops.c::ntfs_write_mst_block() to only check the dirty state
o NTFS: Move the static inline ntfs_init_big_inode() from fs/ntfs/inode.c to inode.h and make fs/ntfs/inode.c::__ntfs_init_inode() non-static and add a declaration for it to inode.h. Fix some compilation issues that resulted due to #includes and header file interdependencies.
o NTFS: Simplify setup of i_mode in fs/ntfs/inode.c::ntfs_read_locked_inode()
o NTFS: Add helpers fs/ntfs/layout.h::MK_MREF() and MK_LE_MREF()
o NTFS: Modify fs/ntfs/mft.c::map_extent_mft_record() to only verify the mft record sequence number if it is specified (i.e. not zero).
o NTFS: Add fs/ntfs/mft.[hc]::ntfs_mft_record_alloc() and various helper functions used by it.
o NTFS: 2.1.21 release
o NTFS: Update Documentation/filesystems/ntfs.txt with instructions on how to use the Device-Mapper driver with NTFS ftdisk/LDM raid. This removes the linear raid problem with the Software RAID / MD driver when one
Antonino Daplas:
o fbdev: remove unnecessary banshee_wait_idle from tdfxfb
o fbdev: fix logo drawing failure for vga16fb
o fbcon: Fix setup boot options of fbcon
o fbdev: Pass struct device to class_simple_device_add
o fbdev: Add Tile Blitting support
o fbdev: fix scrolling corruption
o fbdev: Add iomem annotations to fbmem.c
o fbdev: Add iomem annotations to i810fb
o fbdev: Add iomem annotations to vga16fb.c
o fbcon unimap fix
o fbdev: fix framebuffer memory calculation for vesafb
o fbdev: split vesafb option vram into vtotal and vremap
o fbdev: trivial fb_get_options fix for cyber2000fb and bw2fb
Arjan van de Ven:
o aic79xx hostraid support
o mark scsi_add_host __must_check
Armin Schindler:
o Remove obsolete file Documentation/isdn/README.eicon
Arnd Bergmann:
o add missing linux/syscalls.h includes
o s390: z/VM watchdog timer
Arun Sharma:
o [IA64] Add missing prototypes to kill warnings in sys_ia32.c
Badari Pulavarty:
o sched: fix SCHED_SMT & numa=fake=2 lockup
Bartlomiej Zolnierkiewicz:
o libata: PCI IDE legacy mode fix
o [libata] do not memset() SCSI request buf in a get-reference style function
o [libata piix] Fix PATA UDMA masks
o REQUEST_SENSE support for ATAPI
o [libata] arbitrary size ATAPI PIO support
o arbitrary size ATAPI PIO support bugfixes
o make ATAPI PIO work
o [ide] add sg_init_one() helper and teach ide about it
o [ide] add ide_hwif_t->dma_setup()
o [ide] add ide_hwif_t->dma_exec_cmd()
o [ide] convert ide_hwif_t->ide_dma_begin() to ->dma_start()
o [ide] pmac: use more ide_hwif_t fields
o [ide] always allocate hwif->sg_table
o [ide] sg PIO for taskfile requests
o [ide] sg PIO for fs requests
o [ide] ide-disk: unify PIO write/multiwrite code
o [ide] unify PIO code
o [ide] remove broken pdc4030 driver
o [block] remove bio walking
o [ide] kill CONFIG_IDE_TASKFILE_IO
Ben Dooks:
o Add S3C2410 (Samsung ARM9 Mobile SoC) watchdog driver
o [WATCHDOG] s3c2410_wdt.c-wdog-fix-memrelease.patch
o [WATCHDOG] s3c2410_wdt.c-wdog-fix3.patch
o [ARM PATCH] 2131/1: Add _iomem to the IO string functions
o [ARM PATCH] 2144/1: S3C2410 - s3c2440 fixes and clock updates
o [ARM PATCH] 2145/1: S3C2410 - GPIO ID register update
o [ARM PATCH] 2132/1: Fix timer NULL pointer de-reference on suspend
o I2C: S3C2410 I2C Bus driver
Benjamin Herrenschmidt:
o ppc32/64: FPU/vector register restore after signal
o ppc64: Fix iSeries build (ouch !)
o radeonfb: Fix monitor probe logic
o rework radeonfb blanking
o ppc64: Fix boot on some non-LPAR pSeries
o ppc64: Fix typo in zImage boot wrapper
o ppc64: Update G5 thermal control driver
o ppc: Disable IRQ probe on ppc
o ppc: Fix build of irq.c with CONFIG_TAU_INT
Bjorn Helgaas:
o HCD PCI probe: print actual, not ioremapped, address
o QLogic ISP2x00: remove needless busyloop
o add-pci_fixup_enable-pass.patch
Borislav Petkov:
o USB: fix up usblp usb_unlink_urb() warning
o USB: remove calls to usb_unlink_urb in class/audio.c
o USB: remove calls to usb_unlink_urb in class/bluetty.c
o USB: remove calls to usb_unlink_urb in class/cdc-acm.c
o USB: remove calls to usb_unlink_urb in class/usb-midi.c
o USB: remove calls to usb_unlink_urb() in image/hpusbscsi.c
o USB: remove call to usb_unlink_urb() in media/usbvideo.c
o USB: remove calls to usb_unlink_urb in media/stv680.c
o USB: remove calls to usb_unlink_urb in media/se401.c
o USB: remove call to usb_unlink_urb in media/ov511.c
o USB: remove calls to usb_unlink_urb in media/konicawc.c
o USB: remove calls to usb_unlink_urb in input/xpad.c
o USB: usb_unlink_urb removal from input/ati_remote.c
o USB: remove calls to usb_unlink_urb in input/wacom.c
o USB: remove calls to usb_unlink_urb in input/usbmouse.c
o USB: remove calls to usb_unlink_urb in core/message.c
o USB: remove usb_unlink_urb() calls in input/kbtab.c
o USB: usb_unlink_urb removal from input/hid-core.c
o USB: remove calls to usb_unlink_urb in input/mtouchusb.c
o USB: usb_unlink_urb removal from input/aiptek.c
o USB: remove calls to usb_unlink_urb in input/usbkbd.c
o USB: remove calls to usb_unlink_urb() in input/pid.c
o USB: remove calls to usb_unlink_urb in image/mdc800.c (v2)
o USB: remove calls to usb_unlink_urb in input/powermate.c
o USB: remove calls to usb_unlink_urb() in input/touchkitusb.c
o USB: remove calls to usb_unlink_urb in net/catc.c
o USB: remove calls to usb_unlink_urb in misc/legousbtower.c
o USB: remove _some_ calls to usb_unlink_urb in misc/auerswald.c
o USB: remove calls to usb_unlink_urb in net/usbnet.c
o USB: remove calls to usb_unlink_urb() in net/pegasus.c
o USB: remove calls to usb_unlink_urb() in net/kaweth.c
Carlos Eduardo Medaglia Dyonisio:
o Fix types.h
Catalin Boie:
o USB Serial: Correct a use of out of range variable
o USB: cdc-acm-usb-use-uninit-mem-bug.patch
Chas Williams:
o [ATM]: use RCV_SHUTDOWN to exit skb_recv_datagram()
o [ATM]: point to multipoint signalling (from [email protected])
o [ATM]: [ambassador] eliminate pci_find_device()
o [ATM]: [firestream] remove dead code (from Francois Romieu
<[email protected]>) o [ATM]: [zatm] eliminate pci_find_device (from Francois Romieu <[email protected]>)
Chris Mason:
o reiserfs: small filesystem fix
Chris Wedgwood:
o UML IO sched support
Chris Wright:
o [PKT_SCHED]: Trivial spelling fix in net/sched/Kconfig
o [PKT_SCHED]: Make tcp_proto_lookup_ops() static
o lsm: rename security_scaffolding_startup to security_init
o lsm: reduce noise during security_register
o lsm: Lindent security/security.c
o make __sigqueue_alloc() a general helper
Christoph Hellwig:
o update NCR5380 comments
o update dmx3191d to modern pci/scsi probing
o first steps at BusLogic cleanup
o refactor tmscsim inititalization code
o update notcq blacklist
o don't include "scsi.h" in scsi_module.c
o avoid obsolete APIs in ide-scsi
o avoid obsolete APIs in eata
o allow non-modular mptctl
o fix aic79xx module_init return value when no hardware
o start removing queue from tmscsim
o fix Scsi_Host leak in BusLogic
o kill useless spinlock wrappers in BusLogic
o remove abort,reset methods from host templates
o some ncr53c8xx decrufting
o move scsi_add_host back to where it belongs in aacraid
o don't mark aacraid as experimental
o switch fusion to use <linux/list.h> everywhere
o don't mark the initio 9100 driver broken
o remove internal queueing from inia100
o fix inia100 dma mapping warnings
o fusion dead code removal
o tmscsim: back out bogus eeprom reading changes
o merge a100u2w source files
o qla1280: ISP1020/1040 support
o initio: remove obsolete APIs, cleanup
o a100u2w: cleanups
o merge initio source files
o tmscsim: remove superflous global host list
o get rid of obsolete APIs in u14-34f
o PCI: mark proc_bus_pci_dir static
o tmscsim: remove remaining INQUIRY sniffing
o get rid of obsolete APIs in BusLogic
o get rid of obsolete APIs in nsp32
o fdomain: reduce usage of global variables
o merge scsiiom.c into tmscsim.c
o sparse __iomem annotations for qla2xxx
o don't export blkdev_open and def_blk_ops
o remove dead code from fs/mbcache.c
o remove posix_acl_masq_nfs_mode
o don't export shmem_file_setup
o remove pm_find, unexport pm_send
o remove dead code and exports from signal.c
o unexport proc_sys_root
o unexport is_subdir and shrink_dcache_anon
o unexport devfs_mk_symlink
o unexport do_execve/do_select
o unexport exit_mm
o unexport files_lock and put_filp
o unexport f_delown
o unexport lookup_create
o remove wake_up_all_sync
o remove set_fs_root/set_fs_pwd
o remove MOD_INC_USE_COUNT/MOD_DEC_USE_COUNT
o mark inter_module_* deprecated
o don't include <linux/sysctl.h> in <linux/security.h>
o remove dead exports from fs/fat/
o don't include <linux/irq.h> from drivers
Christoph Lameter:
o Posix compliant cpu clocks
o Posix compliant cpu clocks V6: mmtimer provides CLOCK_SGI_CYCLE
Colin Leroy:
o Warning fix in drivers/macintosh/macio-adb.c
Con Kolivas:
o netconsole support for b44
o b44poll - whitespace
Craig Hughes:
o USB: host side fixes for pxa2xx/ethernet/rndis gadgets, like gumstix
Daniele Venzano:
o [netdrvr sis900] whitespace and codingstyle updates
Dave Hansen:
o remove weird pmd cast
Dave Jones:
o [CPUFREQ] speedstep-smi: only allow it to run on mobile Intel Pentium III
o [CPUFREQ] Work around AMD64 2nd identical PST errata
o Remove redundant freeing code from aic7770
o plug leaks in aic79xx
o Remove possible reuse of stale pointer in aic7xxx
o plug leaks in aic7xxx_osm
o [CPUFREQ] Fix numerous typos in drivers/cpufreq/Kconfig
o [CPUFREQ] i386 Kconfig fixes
o [CPUFREQ] x86_64 Kconfig fixes
o [CPUFREQ] arm Kconfig fixes
o [CPUFREQ] core Kconfig fix
o [CPUFREQ] speedstep-centrino should only decode MSR on certain CPUs
o [CPUFREQ] remove double calls to module_get/put in userspace governor
o [CPUFREQ][1/4] cpufreq "cpu group" awareness: add policy->cpus
o [CPUFREQ][2/4] cpufreq "cpu group" awareness: save sysdev for all CPUs
o [CPUFREQ][3/4] cpufreq "cpu group" awareness: do symlinks for other CPUs instead of registering kobjects
o [CPUFREQ][4/4] cpufreq "cpu group" awareness: remove FIXME in speedstep-ich
o [AGPGART] Fix incorrect VIA PT880 entry
Dave Kleikamp:
o generic acl support for ->permission
David Brownell:
o USB: OHCI init cleanups
o USB: EHCI SMP fix
o export usb_set_device_state(), use in ohci
o USB: gadget_is_n9604
o USB: ohci updates
o USB: khubd looks at ports after probe
o USB: omap_udc supports 5910/1510 chips
o USB: ohci init refactor
o USB: net2280 updates
o USB Gadget: Ethernet/RNDIS gadget, minor updates
o USB: OHCI support for PXA27x
o USB Gadget: debug files now Kconfigured
o USB: OHCI autodetects "need" for init reset quirk
o PCI: update Documentation/power/pci.txt
David Dillow:
o PCI cleanups and convert to ethtool_ops
David Howells:
o Add some key management specific error codes
o keys: new error codes for Alpha, MIPS, PA-RISC, Sparc & Sparc64
o implement in-kernel keys & keyring management
David S. Miller:
o [PKT_SCHED]: Fix sch_atm build
o [SPARC64]: Re-export force_sig to modules
o [SPARC]: Add entries for recently added system calls
o [AF_UNIX]: Remove spurious len test in unix_mkname
o [NET]: More pktgen.c warnings not caught by Randys patch
o [NET]: Need to disable preempt in softirq check of netif_rx_ni
o [CRYPTO]: Fix typo in Kconfig
o [NET]: TSO requires SG, enforce this at device registry
o [SPARC64]: Make iomap.o obj-y instead of lib-y for module exports
o [IEEE1394]: ohci1394.c/pcylynx.c need asm/irq.h
o [SPARC64]: Update defconfig
o [NET]: Uninline netif_rx_ni()
o [TG3]: Update driver version and reldate
o [TCP]: Add total num retransmits accounting
o [NET]: In netif_rx_ni, put netif_rx call inside preempt-disable
David T. Hollis:
o USB: Add Surecom USB Ethernet device ids to usbnet
David Woodhouse:
o USB: Generic USB ATM/DSL core and completed SpeedTouch driver
o USB: Reformat usb-atm code and rework SpeedTouch firmware loading
o USB: Fix assertion logic in USB ATM core
o USB: SpeedTouch / ATM update
o USB SpeedTouch / ATM: Make it work on 64-bit hosts
o JFFS2: work around uninitialised use of usercompr field by old code
o MTD cmdlinepart: Allow partition definitions to be set from elsewhere
o MTD map driver update: Alchemy DB1xxx boards
o MTD map driver update: ppc44x 'ebony' board
o MTD map access: Fix calculation of the number of longs in a bus access
o New MTD map drivers
o MTD: NOR flash chip driver updates
o MTD translation layer helper: set PF_NOFREEZE to allow sleep
o MTD userspace ABI: fix userspace compilation w.r.t. __user
o JFFS2 updates
Dean Gaudet:
o transmeta efficeon support and cpuid update
Dely Sy:
o PCI Hotplug: change bus speed patch
o PCI Hotplug: Bug fixes for shpchp driver
o PCI Hotplug: quirk fix missed out in last patch
Dimitry Andric:
o [WATCHDOG] s3c2410_wdt.c-wdog-fix4.patch
Dinakar Guniguntala:
o ps shows wrong ppid
o stat shows wrong ppid
Dipankar Sarma:
o Fix dcache lookup
o Remove d_bucket
o Document RCU based dcache lookup
Dmitry Torokhov:
o ieee1394: SBP-2 - rename some constants to fix clash with new SCSI core defines
Dominik Brodowski:
o [PCMCIA] 01-unused_bulkmem_code.diff
o [PCMCIA] 02-move_bulkmem.diff
o [PCMCIA] 03-remove_ftl_memory.diff
o [PCMCIA] 04-obsolete_kconfig.diff
o [PCMCICA] 05-obsolete_parts_of_cs.diff
o [PCMCIA] 06-Kconfig_PCMCIA.diff
o [PCMCIA] 01-lookup_bus.diff
o [PCMCIA] 02-adjust_resource_info.diff
o [PCMCIA] 03-replace_cis.diff
o [PCMCIA] 04-get_firstnext_tuple.diff
o [PCMCIA] 05-get_tuple_data.diff
o [PCMCIA] 06-parse_tuple.diff
o [PCMCIA] 07-read_tuple.diff
o [PCMCIA] 08-validate_cis.diff
o [PCMCIA] 09-pcmcia_compat.diff
o [PCMCIA] 10-get_window.diff
o [PCMCIA] 11-configuration_info.diff
o [PCMCIA] 12-reset_card.diff
o [PCMCIA] 13-get_status.diff
o [PCMCIA] 14-access_configuration.diff
o [PCMCIA] 15-get_firstnext_region.diff
Douglas Gilbert:
o scsi_debug version 1.74
o sg jiffy library calls [was: sg kill local jiffies
o scsi: normalize fixed and descriptor sense data
o scsi_mid_low_api.txt update
Duncan Sands:
o usb speedtch: no side-effects in BUG_ON
o usb speedtch: convert to using usb_kill_urb
o usb: extract sensible strings from buggy string descriptors
o USB SpeedTouch cleanup
o firmware_class: avoid double free
Ed Schouten:
o nfsd: Insecure port warning shows decimal IPv4 address
Egbert Eich:
o VGA console font problems on 2.6 kernel
Eric Rossman:
o s390: crypto device driver
Eric Valette:
o USB: rtl8150.c ethernet driver : usb_unlink_urb ->usb_kill_urb
Erik Rigtorp:
o swsusp: progress in percent
Evgeniy Polyakov:
o w1: Added slave->ttl - time to live for the registered slave
o W1: let W1 select NET
o w1_therm: more precise temperature calculation
o w1: schedule_timeout() issues
o scx200: pci_find_device() removal
Florian Schirmer:
o [netdrvr b44] ignore carrier lost errors
o [netdrvr b44] clean up SiliconBackplane definitions/functions
Frank Hirtz:
o Display committed memory limit and available in meminfo
Frank Pavlic:
o s390: qeth layer 2 support
François Romieu:
o sata_nv: enable hotplug event on successfull init only
o sata_nv: wrong failure path and leak
o sata_nv: housekeeping for goto labels
Geert Uytterhoeven:
o FrameMaster II build fix
o m68k: MM off-by-one
o Atari ACSI dependencies
o m68k: minmax-removal arch/m68k/kernel/bios32.c
o M68k: don't emit empty stack program header in vmlinux
o Amifb: update pseudocolor bitfield lenghts
o Amiga frame buffer: kill obsolete DMI Resolver code
o m68k: NULL vs. 0 cleanups
o Amifb: use new amifb:off logic to enhance audio experience
Gerald Schaefer:
o s390: add support to read z/VM monitor records
Gerd Knorr:
o I2C: i2c bus power management support
o v4l: tuner update
o v4l: avoid using struct file ptrs in video-buf
o v4l: adapt saa7146 to video-buf changes
o v4l: bttv driver update
o v4l: cx88 driver update
o DVB/V4L dependency fix
o v4l: msp3400 cleanup
Gordon Jin:
o x86_64: correct copy_user_generic return value when exception happens
Greg Kroah-Hartman:
o kobject: adjust hotplug_seqnum increment to keep userspace and kernel agreeing
o ksysfs: don't build ksysfs if CONFIG_SYSFS is not enabled
o kobject: fix build error if CONFIG_HOTPLUG is not enabled
o USB: remove usbdevfs filesystem name, usbfs is the proper one to use
o kobject: hotplug_seqnum is not 64 bits on all platforms, so fix it
o ksyms: don't implement /sys/kernel/hotplug_seqnum if CONFIG_HOTPLUG is not enabled
o USB: make usb_unlink_urb() message only show up if CONFIG_DEBUG_KERNEL is enabled
o USB: fix usb_unlink_urb() usage in pl2303 driver
o USB: fix usb_unlink_urb() usage in usb-serial core
o USB: fix usb_unlink_urb() usage in belkin_sa driver
o USB: fix usb_unlink_urb() usage in cyberjack driver
o USB: fix usb_unlink_urb() usage in whiteheat driver
o USB: fix usb_unlink_urb() usage in io_edgeport driver
o USB: fix usb_unlink_urb() usage in ir-usb driver
o USB: fix usb_unlink_urb() usage in ipaq driver
o USB: fix usb_unlink_urb() usage in digi_acceleport driver
o USB: fix usb_unlink_urb() usage in empeg driver
o USB: fix usb_unlink_urb() usage in mct_u232 driver
o USB: fix usb_unlink_urb() usage in omninet driver
o USB: fix usb_unlink_urb() usage in visor driver
o USB: fix usb_unlink_urb() usage in kl5kusb105 driver
o USB: fix usb_unlink_urb() usage in kobil_sct driver
o USB: fix usb_unlink_urb() usage in io_ti driver
o USB: fix usb_unlink_urb() usage in ftdi_sio driver
o USB: fix usb_unlink_urb() usage in keyspan_pda driver
o USB: fix usb_unlink_urb() usage in generic usb-serial driver
o Kobject Userspace Event Notification
o I2C: fix up __iomem marking for i2c bus drivers
o PCI: fix __iomem warnings in quirk code
o kevent: standardize on the event types
o USB: fix hcd-pci's __iomem warnings
o USB: fix up __iomem warnings in the ehci driver
o USB: fix up __iomem warnings in the ohci driver
o USB: fix up some minor sparse warnings in the uhci driver
o kevent: add block mount and umount support
o USB: oops, revert drivers/usb/core/message.c change
o USB: fix incorrect usage of usb_kill_urb in rtl8150 driver
o Put symbolic links between drivers and modules in the sysfs tree
o USB: add support for symlink from usb and usb-serial driver to its module in sysfs
o PCI: add "struct module *" to struct pci_driver to show symlink in sysfs for pci drivers
o I2C: change i2c-elektor.c driver from using pci_find_device()
o I2C: convert scx200_acb driver to not use pci_find_device
o PCI: remove pci_find_subsys() calls from cpufreq code
o PCI: remove pci_find_subsys() calls from acpi code
o PCI: make pci_find_subsys() static, as it should not be used anymore
o PCI: update the pci.txt documentation about pci_find_device and pci_find_subsys going away
o PCI: make pci_find_class() warn if in interrupt like all other find/get functions do
o PCI: add pci_get_class() to make a safe pci_find_class() like call
o PCI: clean up the comments in search.c to be correct
o PCI: remove pci_find_class() usage from arch specific files
o PCI: remove pci_find_class() usage from all drivers/ files
o PCI: delete the pci_find_class() function as it's unsafe in hotpluggable systems
o PCI: fix improper pr_debug() statement
o PCI: get rid of pci_find_device() from arch/i386/*
o PCI: remove pci_find_device() usages from drivers/pci/*
o PCI: fix __iomem * warnings for PCI msi core code
o PCI Hotplug: fix __iomem warnings in the compaq pci hotplug driver
o PCI Hotplug: fix __iomem warnings in the ibm pci hotplug driver
o PCI Hotplug: fix the rest of the drivers for __iomem and other sparse issues
o ibmasm: fix __iomem warnings
o PCI: Create new function to see if a pci device is present
o PCI: change cyrix.c driver to use pci_dev_present
o PCI Hotplug: Oops, didn't mean to apply the msi pci express patch, so revert it
o PCI: remove pci_module_init() usage from drivers/pci/hotplug/*
o PCI: clean up pci_dev_get() to be sane
o PCI: remove all usages of pci_dma_sync_sg as it's obsolete
o PCI: remove all usages of pci_dma_sync_single as it's obsolete
o PCI: fix up pci_register_driver() to stop lying in its return value
o PCI: audit all callers of pci_register_driver() to work properly
o PCI: pci_module_init() is identical to pci_register_driver() so just make it a #define
o PCI: remove pci_module_init() usage from drivers/usb/*
o kevent: add __bitwise kobject_action to help the compiler check for misusages
o USB: add endian markups to the ub driver
o USB: add bulk_in_size for usb-serial devices
o USB: add serial ipw driver
o PCI: fix up pci_save/restore_state in via-agp due to api change
o I2C: convert from pci_module_init to pci_register_driver for all i2c drivers
Gregory Kurz:
o fork() bug invalidates file descriptors
Guennadi Liakhovetski:
o tmscsim: remove redundant code
o ST34555N misbehaves on tagged INQUIRY commands - add to blacklist
o tmscsim: use mid-layer's decision for tag support
o tmscsim: remove internal command queue
o tmscsim: use block-layer tags
Guido Guenther:
o Mac swsusp driver fixes
Hanna V. Linder:
o PCI: Fix one missed pci_find_device
o PCI: Changed pci_find_device to pci_get_device for acpi.c
Hannes Reinecke:
o Driver Core: Handle NULL arg for put_device()
Harald Welte:
o [NETFILTER]: Add iptables CONNMARK match+target
o [NETFILTER]: Add iptables hashlimit match
o [NETFILTER]: Add iptables CLUSTERIP target, seq_file version
Haroldo Gamal:
o smbfs does not honor uid, gid, file_mode and dir_mode supplied by user mount
Heinz-Juergen Oertel:
o USB: usb/serial RM vendor/product id for ftdi_sio
Helmut Tschemernjak:
o [ATALK]: Add appletalk 32-bit ioctl emulation
Herbert Xu:
o USB: Fix hiddev devfs oops
o [TCP]: Create tcpdiag_dump_sock
o [TCP]: Make tcpdiag_bc_run take tcpdiag_entry
o [TCP]: Dump SYN_RECV sockets in tcpdiag
o [NET]: Make sure to copy TSO fields in copy_skb_header()
o [NETLINK]: Yield in netlink_broadcast when congested
o [TCP]: Fix new packet len calc in tcp_fragment()
o [XFRM]: Make {__,}xfrm_policy_check behave identically wrt. empty policy lists
o [XFRM]: Fix policy update bug when increasing priority of last policy
o [TCP]: Fix tcp_trim_head() calculations
Hideo Aoki:
o vm thrashing control tuning
o proc.txt cleanup
o vm thrashing control tuning CONFIG_SWAP=n build fix
Hirofumi Ogawa:
o FAT: use hlist_head for fat_inode_hashtable
o FAT: rewrite the cache for file allocation table lookup
o FAT: cache lock from per sb to per inode
o FAT: the inode hash from per module to per sb
o FAT: Fix the race bitween fat_free() and fat_get_cluster()
o FAT: remove debug_pr()
o FAT: merge fix
o FAT: check free_clusters value
o FAT: removal of C[FT]_LE_[WL] macro
o FAT: remove validity check of FAT first entry
Hirokazu Takata:
o m32r: trivial fix of smc91x.h
o m32r: ds1302 driver
o m32r: new CF/PCMCIA driver for m32r
o m32r: update include/asm-m32r/m32102.h
o m32r: AR camera driver
o m32r: SIO driver
o m32r: fix sys_tas system call for m32r
o m32r: update arch/m32r/mm/fault.c to fix a compile error
o m32r: fix a compile error of M32R SIO driver
o m32r: update SIO driver to use module_param()
Hugh Dickins:
o __set_page_dirty_nobuffers mappings
o lighten mmlist_lock
Ian Abbott:
o USB: Add B&B Electronics VID/PIDs to ftdi_sio
Ian Kent:
o autofs4: allow map update recognition
Ingo Molnar:
o module.h build fix
o i386 entry.S cleanups
o softirqs: fix latency of softirq processing
o fix the prof=schedule feature
o generic irq subsystem: core
o generic irq subsystem: x86 port
o generic irq subsystem: x86_64 port
o generic irq subsystem: ppc port
o generic irq subsystem: ppc64 port
o doc: remove references to hardirq.c
o fix & clean up zombie/dead task handling & preemption
o disk stats preempt safety
Jack Hammer:
o ServeRAID driver ( ips ) Version 7.10.18
Jamal Hadi Salim:
o [NET]: Add Mirred TC action
James Bottomley:
o Add scsi_target abstraction and place it in sysfs
o Add host and target transport class abstractions
o Make the SPI transport parameters operate at the target level
o Add bus signalling host attribute to spi transport class
o Fix up scsi_test_unit_ready() to work correctly with CD-ROMs
o fix undefined function msleep warning in osst
o fix printk warning in sg.c
o advansys build fix
o fix SPI transport attributes not showing up in sysfs
o add channel to struct scsi_target
o scsi: Add reset ioctl capability to ULDs
o remove old ifdefs aic79xx
o remove old ifdefs aic7xxx
o add .module to qla1280 template
o complete the bus_addr_t removal from aic7xxx
o Remove duplicate IDENTIFY from scsi.h
o Fix a100u2w compile error
o Add refcounting to scsi command allocation
o ncr53c8xx: remove integrity checking
o ncr53c8xx: move driver local quirks up to scsi blacklist
o mcr53c8xx: remove INQUIRY snooping and believe the mid-layer flags
o add device_configure to the transport classes
o ncr53c8xx: Convert to using transport classes
o Fix up 3w-xxxx after NULL removal mismerge
o scsi: fix host transport allocations
o 53c700: update driver for host spi class
o SCSI: Fix problems with non-power-of-two sector size discs
o SCSI: fix Suspend I/O block/unblock path
James Morris:
o xattr consolidation v3 - generic xattr API
o xattr consolidation v3 - LSM
o xattr consolidation v3 - ext3
o xattr consolidation v3 - ext2
o xattr consolidation v3 - devpts
o xattr consolidation v3 - tmpfs
o SELinux: allow all filesystems to specify fscreate mount option
o [CRYPTO]: Add Tnepres cipher support
James Smart:
o Allow LLDD's to fail slave alloc (non-existent slave)
o suspending I/Os to a device
Jan-Benedict Glaw:
o Document DEC VSXXX-AB digitizer as known working
Jean Delvare:
o I2C: Do not init global variables to 0
o I2C: Fix macro calls in chip drivers
o I2C: More verbose debug in w83781d detection
o I2C: Update Documentation/i2c/writing-clients
o I2C: Cleanup lm78 init
o I2C: Store lm83 and lm90 temperatures in signed
o I2C: Spare 1 byte in lm90 driver
o I2C: Fourth auto-fan control interface proposal
o I2C: Update Kconfig for AMD bus drivers
o I2C: Fix amd756 name
o I2C: Clean up i2c-amd756 and i2c-prosavage messages
o I2C: lm87 driver ported to Linux 2.6
Jean Tourrilhes:
o wireless-extension-v17-for-linus.patch
o wireless-drivers-update-for-we-17.patch
o WE-17 typo fix
o [IRDA]: Fix lmp_lsap_inuse()
o [IRDA]: Fix nsc-ircc dongle_id input
o [IRDA]: IrNET char dev alias
o [IRDA]: IAS safety comments
o [IRDA]: Adaptive discovery query timer
o [IRDA]: IrCOMM IAS object fix
o [IRDA]: via-ircc driver speed fixes
o [IRDA]: Debug module param
o [IRDA]: Stir driver usb reset fix
o [IRDA]: Stir driver suspend fix
o [IRDA]: Stir netdev and messages cleanups
Jeff Garzik:
o [netdrvr b44] update MODULE_AUTHORS
o [libata] add sata_uli driver for ULi (formerly ALi) SATA
o [libata sata_uli] add dev_select hook
o [libata] add AHCI driver
o [libata ahci] fix several bugs
o [libata ahci] more updates
Jeff Mahoney:
o ReiserFS: Cleanup internal use of bh macros
o ReiserFS: Cleanup access of journal (cosmetic)
o ReiserFS: Add I/O error handling to journal operations
o ReiserFS: Fix several missing reiserfs_write_unlock calls
o reiserfs: support for REISERFS_UNSUPPORTED_OPT notation
o reiserfs: allow user_xattr and acl options to be ignored, with warning
Jens Axboe:
o invalidate page race fix
o return full SCSI status byte in SG_IO
o switchable and modular io schedulers
o cfq-v2 I/O scheduler update
o convert jiffies <-> msecs for io schedulers
o move io scheduler kconfig entries
Jeremy Higdon:
o sg.c to warn about ambiguous data direction
o scsi: add blacklist attribute indicating no ULD attach
o add ability to set device queue depth to mptfusion
o per-port LED control for sata_vsc
Jesper Juhl:
o __copy_to_user return value checks in i2o_config.c
o [NET]: Add new sysfs attribute 'carrier' for net devices
o [ATM]: ambassador printk warning fix
Jesse Barnes:
o SCSI QLA not working on latest *-mm SN2
o USB: handle usb host allocation failures gracefully
o [IA64] mca.c: sparse cleanup
o [IA64] numa.c, discontig.c: sparse: use NULL, not 0
o [IA64-SGI] snsc.c: snsc needs asm/sn/io.h
o [IA64] fix sba_iommu build
o [IA64-SGI] sparse cleanups & misc fixes for sn2
o [IA64-SGI] more sparse I/O accessor fixes
John Hawkes:
o [IA64] top level scheduler domain for ia64
John Rose:
o PCI Hotplug: add host bridges to RPA hotplug subsystem
o PCI Hotplug: RPA dynamic addition/removal of PCI Host Bridges
o PPC64: Add pcibios_remove_root_bus
o PPC64: RPA dynamic addition/removal of PCI Host Bridges
o PCI Hotplug: RPA DLPAR - remove error check
o PCI Hotplug: rpaphp safe list traversal
John Stultz:
o USB: early usb handoff for 2.6
John W. Linville:
o [TG3]: Add MODULE_VERSION
o [B44]: Add MODULE_VERSION
Joshua Kwan:
o Disambiguate esp.c clones
Kai Mäkisara:
o avoid obsolete "scsi.h" APIs in st
KaiGai Kohei:
o atomic_inc_return() for i386
o atomic_inc_return() for x86_64
o atomic_inc_return() for arm
o atomic_inc_return() for arm26
o atomic_inc_return() for sparc64
Kay Sievers:
o export of SEQNUM to userspace (creates /sys/kernel)
Keith Owens:
o [IA64] Avoid a rare deadlock during unwind
o reference_init fix
Kenji Kaneshige:
o USB: add missing pci_disable_device for PCI-based USB HCD
o PCI: warn of missing pci_disable_device()
Kenneth W. Chen:
o Enable config_schedstats for all arches
Lennert Buytenhek:
o PCI: minor pci.ids update
Lev Makhlis:
o show aggregate per-process counters in /proc/PID/stat 2
Li Shaohua:
o PCI: Reorder some initialization code to allow resources to be proper allocated
Linus Torvalds:
o Add fake '__builtin_warning()' for the gcc case
o Older gcc's ICE on missing (unused) varags macro name
o Add copyright notice on ppc64 iomap files
o Wrap <linux/compiler.h> inside '#ifndef __ASSEMBLY__'
o Fix old-style fn declaration
o Don't use obsolete gcc named initializer syntax
o Fix pci config syscall definitions
o Fix posix timer direct user space access
o Update tty layer to not mix kernel and user pointers
o remap_pfn_range: make the region special
o Make drivers/char/mem.c use remap_pfn_range()
o Make core-dumps have all the relevant regions in it
o Fix up USB serial console for tty layer changes
o Linux 2.6.10-rc1
Luben Tuikov:
o Adding PCI ID tables to aic7xxx and aic79xxx
o aic7xxx and aic79xx: fix sleeping while holding a lock
Luca Risolia:
o USB: SN9C10x driver update
o USB: SN9C10x driver updates
Luiz Capitulino:
o USB: remove ugly code from usb/serial/usb-serial.c
o USB: missing check in usb/serial/usb-serial.c
o usb-serial: Moves the search in device list out of usb_serial_probe()
o usb-serial: create_serial() return value trivial fix
o usb-serial: return_serial() trivial cleanup
o usb-serial: usb_serial_register() cleanup
o usb-serial: Add module version information
o PCI: add missing checks in drivers/pci/probe.c
Maciej Soltysiak:
o [TCP]: Document tcp_tso_win_divisor in ip-sysctl.txt
Maciej W. Rozycki:
o "console=" parameter ignored
Manfred Spraul:
o rx checksum support for gige nForce ethernet
o slab: reduce fragmentation due to kmem_cache_alloc_node
Marcel Holtmann:
o [Bluetooth] Improve connection hash handling
o [Bluetooth] Fix race when unlinking incoming connections
o [Bluetooth] Let the CAPI free the SKB in the error case
o [Bluetooth] Add module parameter for disabling ISOC transfers
o [Bluetooth] Add security manager flags and options
o [Bluetooth] Stop TX task before notifying the driver
Marcelo Tosatti:
o Adjust alignment of pagevec structure
o Remove redundant AND from swp_type()
Margit Schubert-While:
o prism54 Code cleanup
o prism54 remove module params
o prism54 add WE17 support
o prism54 initial WPA support
o prism54 fix wpa_supplicant frequency parsing
o I2C: minor lm85 fix
o prism54 remove TRACE
o prism54 Bug in timeout scheduling
o prism54 print firmware version
o prism54 bug initialization/mgt_commit
Mark Haverkamp:
o aacraid: Detect non-committed array
o 2.6.9 aacraid: aac_count fix
o aacraid: dynamic dev update
o aacraid: Add get container name functionality
Mark Lord:
o Export ata_scsi_simulate() for use by non-libata drivers
Mark M. Hoffman:
o I2C/SMBus stub for driver testing
o i2c: Add Intel VRD 10.0 and AMD Opteron VID support
o i2c: sensors chip driver updates
o i2c: kill some sensors driver macro abuse
Markus Lidel:
o i2o: code beautifying and cleanup
o i2o: added support for Promise controllers
o i2o: new functions to convert messages to a virtual address
o i2o: quieten sparse 1-bit-bitfield warnings in i2o.h
o i2o: correct error code if bus is busy in i2o_scsi
o i2o: message conversion fix for le32_to_cpu parameters
Martin Schlemmer:
o Select cpio_list or source directory for initramfs image
Martin Schwidefsky:
o cleanup: move call to update_process_times
o cleanup: remove unused definitions from timex.h
o cleanup: time.h, times.h, timex.h and jiffies.h
Matt Domsch:
o EDD: use EXTENDED READ command, add CONFIG_EDD_SKIP_MBR
o idefloppy: suppress media not present errors
o modules: put srcversion checksum in each modinfo section
Matt Porter:
o ppc32: use gen550 for PPC44x progress/ppc-stub
o ppc32: add gen550.h
o ppc32: configure PPC440GX L2 cache based on CPU rev
o ppc32: remove bogus PPC44x prefetch workaround
o ppc32: fix ibm44x_common.c compile
Matthew Dharm:
o USB Storage: change how INQUIRY is fixed up
o USB storage: delayed device scanning
o USB Storage: ignore bogus residue values
o USB Storage: revert GetMaxLUN strictness
Matthew Dobson:
o sched_domains: Make SD_NODE_INIT per-arch #2
o sched: remove NODE_BALANCE_RATE definitions
o Create nodemask_t
Matthew Wilcox:
o sym2 2.1.18k
o Add SPI-5 constants to scsi.h
o PA-RISC sound update
Matthieu Castet:
o use of MODULE_DEVICE_TABLE in i2c busses driver
o bttv IRQ fix
Maximilian Attems:
o usb/tiglusb: insert set_current_state() before schedule_timeout()
o usb/dabusb: insert set_current_state() before schedule_timeout()
o list_for_each_entry: drivers-usb-core-devices.c
o list_for_each_entry: drivers-usb-serial-ipaq.c
o list_for_each_entry: drivers-usb-host-hc_sl811.c
o list_for_each_entry: drivers-usb-media-dabusb.c
o list_for_each_entry: drivers-usb-class-usb-midi.c
o list_for_each_entry: drivers-usb-class-audio.c
o scsi/mesh: replace schedule_timeout() with msleep()
o scsi/osst: replace schedule_timeout() with msleep()
o scsi/wd7000: replace schedule_timeout() with msleep()
o scsi/sd: replace schedule_timeout() with msleep()
o scsi/qla_init: replace schedule_timeout() with
o scsi/qla_os: replace schedule_timeout() with msleep()
o scsi/sata_sx4: replace schedule_timeout() with
o PCI list_for_each: arch-i386-pci-i386.c
o PCI list_for_each: arch-alpha-kernel-pci.c
o PCI list_for_each: arch-ia64-pci-pci.c
o PCI list_for_each: arch-ia64-sn-io-machvec-pci_bus_cvlink.c
o PCI list_for_each: arch-ppc64-kernel-pci.c
o PCI list_for_each: arch-ppc64-kernel-pci_dn.c
o PCI list_for_each: arch-ppc-kernel-pci.c
o PCI list_for_each: arch-sparc-kernel-pcic.c
o PCI pci_dev_b to list_for_each_entry: drivers-pci-setup-bus.c
o janitor: cpqarray remove unused include
o janitor: remove old ifdefs dmascc
o janitor: remove old ifdefs fasttimer
o janitor: list_for_each: drivers-char-drm-radeon_mem.c
o janitor: char/rio_linux: replace schedule_timeout() with msleep()/msleep_interruptible()
o janitor: char/sis-agp: replace schedule_timeout() with msleep()
o janitor: char/fdc-io: replace direct assignment with set_current_state()
o janitor: char/ipmi_si_intf: add set_current_state()
o janitor: char/sx: replace direct assignment with set_current_state()
o drivers/char: replace schedule_timeout() with msleep_interruptible()
o janitor: remove check_region from drivers/char/esp.c
o janitor: mark __init/__exit static drivers/net/ppp_deflate
o janitor: mark __init/__exit static drivers/net/bsd_comp
o janitor: fix-typo-arm-dma arch/arm26/machine/dma.c
o janitor: kill KERNEL_VERSION duplicate in videocodec.c
o janitor: video/radeon_base: replace MS_TO_HZ() with msecs_to_jiffies()
o janitor: video/radeonfb: remove MS_TO_HZ()
o janitor: drivers/media: replace schedule_timeout() with msleep()
o janitor: drivers/message: replace schedule_timeout() with msleep_interruptible()
o drivers/md: replace schedule_timeout() with msleep_interruptible()
o ieee1394: replace schedule_timeout() with msleep_interruptible()
o janitor: replace dprintk with pr_debug in drivers/scsi/tpam/
o janitor: isdn/icn: change units of ICN_BOOT_TIMEOUT1
o drivers/isdn: replace milliseconds() with msecs_to_jiffies()
o janitor: replace dprintk with pr_debug in microcode.c
o janitor: __FUNCTION__ string concatenation deprecated
o drivers: remove unused MOD_{DEC,INC}_USE_COUNT
Michael A. Halcrow:
o BSD Secure Levels LSM: add time hooks
o BSD Secure Levels LSM: core
o BSD Secure Levels LSM: documentation
Michael Hunold:
o DVB: update saa7146
o DVB: documentation update
o DVB: skystar2 dvb bt8xx update
o DVB: core update
o DVB: frontend conversion
o DVB: frontend conversion #2
o DVB: frontend conversion #3
o DVB: frontend conversion #4
o DVB: add frontend
o DVB: add frontend #2
o DVB: new driver for mobile USB Budget DVB-T devices
o DVB: misc driver updates
o DVB: frontend updates
o V4L: follow changes in saa7146
Mike Miller:
o cciss: SCSI API updates
o cciss: fixes for clustering
Natalie Protasevich:
o Incorrect PCI interrupt assignment on ES7000 for platform GSI
Neil Brown:
o nfsd4: nfsd oopsed when encountering a conflict with a local lock
o nfsd: separate a little of logic from fh_verify into new function
o nfsd4: don't take i_sem around call to ->getxattr
o nfsd: make sure getxattr inode op is non-NULL before calling it
o nfsd4: reference count stateowners
o nfsd4: take a reference to preserve stateowner through xdr replay code
o nfsd4: revert awkward extension of state lock over xdr for replay encoding
o nfsd4: fix race in xdr encoding of lock_denied response
o nfsd: remove incorrect stateid modification in nfsv4 open upgrade
o nfsd4: move open owner checks from nfsd4_process_open2 into new function
o nfsd: set OPEN_RESULT_LOCKTYPE_POSIX in open()
o nfsd4: move seqid decrement on reclaim to separate function
o nfsd4: reorganize "if" in nfsd4_process_open2 to make test clearer
o nfsd4: move open_upgrade code into a separate function
o nfsd4: move some nfsd4_process_open2 code to nfs4_new_open
o nfsd: clean up nfsd4_process_open2
o nfsd4: fix putrootfh return
o nfsd4: move code to truncate on open to separate function
o md: convert %Lu to %llu in printk
o lockd: remove hardcoded maximum NLM cookie length
Nick Piggin:
o sched: trivial sched changes
o sched: add CPU_DOWN_PREPARE notifier
o sched: integrate cpu hotplug and sched domains
o sched: sched add load balance flag
o sched: remove disjoint NUMA domains setup
o sched: IA64 add disjoint NUMA domain support
o sched: fix domain debug for isolcpus
o sched: enable SD_LOAD_BALANCE
o sched: hotplug add a CPU_DOWN_FAILED notifier
o sched: use CPU_DOWN_FAILED notifier
o sched: fixes for ia64 domain setup
o taint: fix forced rmmod
o taint on bad_page
Nicolas Pitre:
o smc91x: Revert 1.1923.3.58: "m32r: modify drivers/net/smc91x.c for
m32r"
o smc91x: Assorted minor cleanups
o smc91x: set the MAC addr from the smc_enable function
o smc91x: fold smc_setmulticast() into smc_set_multicast_list()
o smc91x: simplify register bank usage
o smc91x: move TX processing out of IRQ context entirely
o smc91x: use a work queue to reconfigure the phy from smc_timeout()
o smc91x: fix possible leak of the skb waiting for mem allocation
o smc91x: display pertinent register values from the timeout function
o smc91x: straighten SMP locking
o smc91x: cosmetics
o smc91x: fix SMP lock usage
o smc91x: more SMP locking fixes
o smc91x: fix compilation with DMA on PXA2xx
o smc91x: receives two bytes too many
o smc91x: release on-chip RX packet memory ASAP
o fix PXA270 compile errors
Nishanth Aravamudan:
o i2c-algo-ite: remove iic_sleep()
o i2c/i2c-mpc: replace schedule_timeout() with msleep_interruptible()
o usb/file_storage: replace schedule_timeout() with msleep_interruptible()
o usb/ati_remote: add set_current_state()
o usb/kaweth: reorder set_current_state() and schedule_timeout()
o usb/hid-core: add set_current_state() before schedule_timeout()
o usb/mdc800: cleanup set_current_state() around wait queues
o usb/uss720: replace schedule_timeout() with msleep_interruptible()
o pci hotplug/shpchp: replace schedule_timeout() with msleep_interruptible()
o pci hotplug/pciehp: replace schedule_timeout() with msleep_interruptible()
o pci hotplug/cpqphp: replace schedule_timeout() with msleep_interruptible()
o pci hotplug/cpqphp_ctrl: replace schedule_timeout() with msleep_interruptible()
o net/mac89x0: replace schedule_timeout() with msleep_interruptible()
o I2C: replace schedule_timeout() with msleep_interruptible() in
i2c-ibm_iic.c
o pmac_cpufreq msleep cleanup/fixes
Olaf Dabrunz:
o TIOCCONS security
Olaf Hering:
o mesh is ppc32-only
o [NET]: Allow CONFIG_NET=n on ppc64
o remove scsi ioctl from udf/lowlevel.c
Olaf Kirch:
o [NETFILTER]: Don't export common symbols from ipfwadm.ko
Oleg Nesterov:
o Fix show_trace() in irq context with CONFIG_4KSTACKS
o fix nosmp & pcibios_fixup_irqs() interaction
o detach_pid(): restore optimization
o detach_pid(): eliminate one find_pid() call
o copy_thread(): unneeded child_tid initialization
Oliver Neukum:
o USB: update of help text for hpusbscsi
o USB: switching microtek to usb_kill_urb
o USB: correct interrupt interval for kaweth
o USB: switching microtek to usb_kill_urb
o USB: maintainership of acm cdc
o USB: acm work around for misplaced
o additional documentation for power management
Olof Johansson:
o ppc64: fix CPU numa init code thinkos
Pablo Neira:
o [NETFILTER]: Fix removing invalid proc file
Paolo 'Blaisorblade' Giarrusso:
o uml: readd linux Makefile target
o use container_of() for rb_entry()
Pat Gefre:
o [IA64-SGI] Remove Altix I/O code (ready for re-org)
o [IA64-SGI] Add in Altix I/O code
o [IA64] qla1280.c Mod for Altix I/O add code
o [IA64-SGI] Fix issue with gemini TIO systems
o [IA64-SGI] Redundant BUG check
o [IA64-SGI] Fix a possible memory leak
o [IA64-SGI] make pci_root_ops non static
o [IA64-SGI] BUG_ON test was backwards
o [IA64-SGI] Fixes calling arg1 for bte_crb_error_handler()
o [IA64] export sn_dma_mapping_error for libata
o [IA64-SGI] Mod to allow functions other than zero to use virtual channel 1
Patrick McHardy:
o [IPV6]: Fix netdevice/inet6_dev reference leaks in ip6_route_add error paths
o [XFRM]: Apply policy checks to packets with a secpath when the policy list is empty
o [PKT_SCHED]: Fix netem qlen accounting
o [IPV4]: Fix inet6_dev reference leak in ndisc_dst_alloc error path
Patrick Mochel:
o [driver model] Change symbol exports to GPL only in drivers/base/bus.c
o [driver model] Change sybmols exports to GPL only in class.c
o [driver model] Change symbol exports to GPL only in core.c
o [driver model] Change symbol exports to GPL only in driver.c
o [driver model] Change symbol exports to GPL only in firmware.c
o [driver model] Change symbol exports to GPL only in platform.c
o [driver model] Change symbol exports to GPL only in sys.c
o [sysfs] Change symbol exports to GPL only in bin.c
o [sysfs] Change symbol exports to GPL only in dir.c
o [sysfs] Change symbol exports to GPL only in file.c
o [sysfs] Change symbol exports to GPL only in group.c
o [sysfs] Change symbol exports to GPL only in symlink.c
o [driver core] Change symbol exports to GPL only in power/main.c
o [driver core] Change symbol exports to GPL only in power/resume.c
o [driver core] Change symbol exports to GPL only in power/suspend.c
Paul Fulghum:
o ppp: terminate connection on hangup
o ppp: disconnect on hangup (synctty)
Paul Jackson:
o sched: make domain setup overridable
Paul Mackerras:
o ppc32: fix cpu voltage change delay
o ppc64: fix XICS startup function to enable as well
o PPC64 remove __ioremap_explicit() error message
o Fix PREEMPT_ACTIVE definition
Paul Mundt:
o sh: SH73180 subtype support
o sh: SH7705 subtype cleanup + 32k cache support
o sh: Use asm-offsets
o sh: consistent API cleanup
o sh: defconfig updates
o sh: DMA API updates
o sh: SCBRR calculation fixes for early printk()
o sh: EDOSK7705 board support
o sh: SH-4 optimized memcpy()
o sh: SH4-202 MicroDev board support
o sh: cleanup + merge
o sh: PCI updates
o sh: oprofile support for SH7750/SH7750S
o sh: Broken-out CPU subtype probing
o sh: SE73180 board support
o sh: CTP/PCI-SH03 board support
o sh: sh-sci updates
o sh: ST40 updates
Paulo Marques:
o kallsyms data size reduction / lookup speedup
Pavel Machek:
o USB Storage: Unusual_dev patch for Finepix 1300 and 1400's
o acpi proc: error handling
o swsusp: fix process start times after resume
o swsusp: add comments at critical places
o swsusp: Documentation update
o __init poisoning for i386
o Fix suspend/resume support in via-rhine2
Pekka Pietikäinen:
o b44: use bounce buffers to workaround chip DMA bug/limitations
Pete Zaitcev:
o USB: Fixes for ub in 2.4.9-rc1 from Oliver and Pat
o USB: Patch for 3 ub bugs in 2.6.9-rc1-mm4
o USB: Fixes for ub in 2.4.9-rc2-mm2
o USB: fix oops with latest ub driver in -mm tree
Peter Osterlund:
o DVD+RW support
o packet-writing: add credits
o CDRW packet writing support
o cdrom: buffer sizing fix
Peter Williams:
o CPU Scheduler: fix potential error in runqueue nr_uninterruptible count
Petko Manolov:
o USB: small rtl8150 patch
Petr Vandrovec:
o Remove big-endian mode from matroxfb
o Assorted matroxfb fixes
o Add VIDIOC_S_CTRL_OLD to matroxfb
Phil Dibowitz:
o USB Storage: Remove unusual_dev entry for IBM Storage Key
o USB Storage: Remove unusual_devs entries for Genesys Drives
o USB Storage: Fix Kyocera order
o USB Storage: unusual_dev modification
Phil Oester:
o doc: scsihosts parameter no longer exists
Randy Dunlap:
o i386/io_apic init section fixups
o [NET]: Fix sprintf type warnings on 64-bit in pktgen.c
o x86_64/io_apic init section fixups
o [TG3]: tg3_nvram_read_using_eeprom cannot be __init
o MTD: dilnetpc: use %p for ptr printk arg
o saa7134: discarded reference
o bt878: discarded reference
o cx88: discarded reference
Robin Holt:
o [IA64-SGI] Double spin_unlock in bte.c
o [IA64-SGI] Correct BTE notification timeouts on SN2
o [IA64-SGI] Distribute useage of BTE interfaces
Roger Luethi:
o PCI: remove driver private PCI state, 1 arg for pci_{save,restore}_state
Roland Dreier:
o kobject: add add_hotplug_env_var()
o USB: use add_hotplug_env_var() in core/usb.c
o ppc: fix build with O=$(output_dir)
Roland McGrath:
o make rlimit settings per-process instead of per-thread
o add WCONTINUED support to wait4 syscall
o fix PTRACE_ATTACH race with real parent's wait calls
o exec: fix posix-timers leak and pending signal loss
o move struct k_itimer out of linux/sched.h
Rudolf Marek:
o I2C: fix it8712 detection
Russell King:
o [ARM] Convert system ticker timer to sysdev model
o [ARM] Move OS timer suspend/resume from pm.c to time.c
o [ARM] Separate out footbridge DC21285 and ISA timer implementations
o [ARM] Fix Integrator timer implementation
o [SERIAL] Add FCR setting to serial8250_config structure
o [SERIAL] Convert TI16C750 flow control into a port capability
o [SERIAL] Add comment about frobbing the 950's ACR on TX disable
o [SERIAL] Clean up handling of LSR in receive function
o [SERIAL] Add explaination why we don't use RTS flow control
o [SERIAL] Make port autoprobing set up->capabilities
o [SERIAL] Add new port registration/unregistration functions
o [SERIAL] Convert 8250_pci to use new serial8250_register_port()
o [SERIAL] Keep trying to register our console device
o [ARM] Add netconsole support to ARM AM79C961A driver
o [ARM] Convert to constant-optimising udelay() implementation
o [ARM] Rehash iwmmxt signal handling
o [ARM] Clean up footbridge configuration
o [ARM] Move machine specific boot variables to separate makefile
o [ARM] Fix missed udelay usage - assembly needs to call __udelay now
o [ARM] Sanitise Footbridge machine class
o [ARM] Add generic RTC implementation
o [ARM] Add documentation for ARM kernel timer infrastructure
o [SERIAL] serial_reg.h update
o [ARM] Cleanup some quirks
o [ARM] Export find_{first,next}_bit_{l,b}e
o [ARM] Add seqlocking to timers
Rusty Russell:
o module_param_array() should take a pointer
Ryan S. Arnold:
o hvc_console fix to prevent oops and late hangup and write operations
Seth Rohit:
o add sys_setaltroot()
Sreenivas Bagalkote:
o megaraid 2.20.4: Fix a data corruption bug
o remove config_compat from Megaraid
Stefan Weinhuber:
o s390: z/VM log reader
Steffen Zieger:
o USB: Codemercs IO-Warrior support
Stelian Pop:
o A simple FIFO implementation
Stephan Fuhrmann:
o USB Storage: unusual_devs patch for new tekom entry
Stephan Walter:
o USB Storage: unusual_devs patch for winward music disk
Stephen C. Tweedie:
o ext3 directio block leak fix
Stephen Hemminger:
o b44: replace MODULE_PARM
o b44: use netdev_priv
o register_chrdev_region(), alloc_chrdev_region() const char
o [NET]: dst: use const in accessors
o [TCP]: use const in tcp.h
o [NET]: Replace dst_release refcount error with standard WARN_ON
Stephen Rothwell:
o ppc64: iSeries compile broken in 2.6.9-bk3
Suresh B. Siddha:
o share i386/x86_64 intel cache descriptors table
o Disable SW irqbalance/irqaffinity for E7520/E7320/E7525 v2
o no exec: i386 and x86_64 cleanups
o [IA64] fallback to swiotlb for consistent DMA mappings
Thayne Harbaugh:
o gen_init_cpio uses external file list
Thomas Gleixner:
o Shared Reed-Solomon ECC library
o Add DocBook documentation for MTD NAND drivers
o MTD updates for __iomem
o MTD char device access -- return data when ECC errors happen
o MTD: M-Systems DiskOnChip translation layer (NFTL): fix unused variable
o MTD: NAND flash driver updates
Thomas Graf:
o [PKT_SCHED]: Replace tc_stats with new gnet_stats in struct Qdisc
o [PKT_SCHED]: Use gnet_stats API to copy statistics into netlink message
o [PKT_SCHED]: Introduce gen_replace_estimator
o [PKT_SCHED]: Use generic rate estimator
o [PKT_SCHED]: Qdisc are not supposed to dump TCA_STATS themselves
o [PKT_SCHED]: CBQ; Destroy filters before destroying classes
o [PKT_SCHED]: Requeues statistics
o [PKT_SCHED]: Max TLV types cleanup
o [PKT_SCHED]: Add dump_stats qdisc op
o [PKT_SCHED]: CBQ: use dump_stats
o [PKT_SCHED]: RED: use dump_stats
o [PKT_SCHED]: Add dump_stats class op
o [PKT_SCHED]: CBQ: Use gnet_stats for class statistics
o [PKT_SCHED]: CBQ: Use dump_stats for class statistics dumping
o [PKT_SCHED]: CBQ: Use generic rate estimator
o [PKT_SCHED]: HTB: Use gnet_stats for class statistics
o [PKT_SCHED]: HTB: Use dump_stats for class statistics dumping
o [PKT_SCHED]: HTB: Remove unneeded rate estimator bits
o [PKT_SCHED]: HTB: Use gnet_stats for class statistics
o [PKT_SCHED]: HFSC: Use generic rate estimator
o [PKT_SCHED]: HFSC: Use dump_stats for class statistics dumping
o [PKT_SCHED]: ATM: Use gnet_stats for class statistics and dump them
Tom Rini:
o sh: fix EMBEDDED_RAMDISK with O=
o remove unused arch/sh/tools/machgen.sh
Tony Luck:
o [IA64] Allow -mtune=merced for gcc 3.4
o [IA64] uninitialised flags element could cause crashes
Ulrich Drepper:
o Simplify last lib/idr.c change
Urban Widmark:
o smbfs protocol fixes
Venkatesh Pallipadi:
o S3 suspend/resume with noexec v2
o Fix EDID_INFO in zero-page
o x86[64]: display phys_proc_id only when it is initialized
Vernon Mauery:
o PCI Hotplug: acpiphp extension fixes
Vladimir Grouzdev:
o xtime value may become incorrect
Vojtech Pavlik:
o USB: Fix oops in usblp driver
Werner Almesberger:
o x86_64: no TIOCSBRK/TIOCCBRK in ia32 emulation
William A. Adamson:
o nfs4 lease: add a lock manager copy lock callback
o nfs4 lease: add a lock manager release private callback
o nfs4 lease: add a lock manager break callback
o nfs4 lease: aeparate the lease initialization code
o nfs4 lease: move the f_delown processing
o nfs4 lease: separate the lease processsing code
o nfs4 lease: use the inode i_writecount
o nfs4 lease: export setlease
o nfs4 lease: export remove_lease
o nfs4 lease: add the new lock manager callbacks to the documentation
William Lee Irwin III:
o move waitqueue functions to kernel/wait.c
o standardize bit waiting data type
o consolidate bit waiting code patterns
o eliminate bh waitqueue hashtable
o eliminate inode waitqueue hashtable
o move wait ops' contention case completely out of line
o reduce number of parameters to __wait_on_bit() and
__wait_on_bit_lock()
o document wake_up_bit()'s requirement for preceding memory barriers
o pidhashing: rewrite alloc_pidmap()
o pidhashing: retain older vendor copyright
o pidhashing: lower PID_MAX_LIMIT for 32-bit machines
o pidhashing: enforce PID_MAX_LIMIT in sysctls
o procfs: fix task_mmu.c text size reporting
o make console_conditional_schedule() __sched and use cond_resched()
o report per-process pagetable usage
o profile: 512x Altix timer interrupt livelock fix
o sparc32: early tick_ops
o sparc32: add atomic_sub_and_test()
o vm: introduce remap_pfn_range() to replace remap_page_range()
o vm: convert references to remap_page_range() under arch/ and Documentation/ to remap_pfn_range()
o vm: convert users of remap_page_range() under drivers/ and net/ to use remap_pfn_range()
o vm: convert users of remap_page_range() under include/asm-*/ to use remap_pfn_range()
o vm: convert users of remap_page_range() under sound/ to use remap_pfn_range()
o PA-RISC io_remap_page_range() fix
Wim Van Sebroeck:
o [WATCHDOG] s3c2410_wdt.c-wdog-fix5.patch
o [WATCHDOG] v2.6.9-rc3 i8xx_tco.c-stop_reboot-patch
Wouter Van Hemel:
o USB: usb audio is for oss only
Yasuyuki Kozakai:
o [NETFILTER]: Fix multiple bugs in ip6rt.c
o [NETFILTER]: Fix checks in ip6t_multiport.c
o [NETFILTER]: Fix multiple bugs in ip6t_frag.c
Yoichi Yuasa:
o mips: added missing definition and fixed typo
o mips: fixed MIPS Makefile
Zwane Mwaikambo:
o Allow multiple inputs in alternative_input
o Update 'noapic' description
Quoted 10 lines
Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
It's not only Linux which has this problem. For some of my own regularly updated "projects" (i.e. a collection of scripts) I use an always increasing number, preferably date, and do not care at all about -pre, -post, -beta, -rc, -etc.
"2.6.10-27" (read: try #27)... sound funny.
Jan Engelhardt
Signature · 2 lines
Gesellschaft für Wissenschaftliche Datenverarbeitung Am Fassberg, 37077 Göttingen, www.gwdg.de
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 10 lines · Linus Torvalds
Ok,
Linux-2.6.10-rc1 is out there for your pleasure.I thought long and hard about the name of this release (*), since one of the main complaints about 2.6.9 was the apparently release naming scheme.
Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
rc is release candidate. Which means its close to a release. Shouldn't this be more a -test? -pre? count down? -rc-1 ? is this -1 or dash 1? :)
Well I think better stick with the count up way ...
Or is the time come, where the shall be a split to a real dev line ...
lg, clemens
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBeY90jBz/yQjBxz8RAq8/AKC211LmAE2UkvAGIX/vkR+9ILAWgQCfQk1A oIcOhIKixDUfjUo4DpokfYw=
=6UyI
-----END PGP SIGNATURE-----
Quoted 10 lines · Linus Torvalds
Ok,
Linux-2.6.10-rc1 is out there for your pleasure.I thought long and hard about the name of this release (*), since one of the main complaints about 2.6.9 was the apparently release naming scheme.
Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
Do the -rcs first, let them contain everything that should go into the next release.
And when you feel that you have released enough -rcs(Uh, whenever that is...) release the -pres.
They should only contain critical bugfixes before the final release.
Signature · 4 lines
Mvh / Best regards Espen Fjellvær Olsen [email protected] Norway
Quoted 14 lines · Espen Fjellvær Olsen
Quoted 10 lines · Linus Torvalds
Ok,
Linux-2.6.10-rc1 is out there for your pleasure.I thought long and hard about the name of this release (*), since one of the main complaints about 2.6.9 was the apparently release naming scheme.
Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
Quoted 5 lines
Do the -rcs first, let them contain everything that should go into the next release.
And when you feel that you have released enough -rcs(Uh, whenever that is...) release the -pres.
They should only contain critical bugfixes before the final release.
Well, several of us think that -pre's should come before the -rc's and not after them.
It appears that we should concentrate on the
NAME=Zonked Quokka
part of Makefile for our sanity.
Signature · 1 line
~Randy
Quoted 4 lines · Linus Torvalds
So to not overtax my poor brain, I'll just call them all -rc releases, and hope that developers see them as a sign that there's been stuff merged, and we should start calming down and seeing to the merged patches being stable soon enough..
Hehe, and a bunch of important (for me) ones that couldn't get in yet because they had to be rebased about twice a day with the current flood ;)
oh well, I'm working on them now...
Ben.
Quoted 8 lines · Benjamin Herrenschmidt
Quoted 4 lines · Linus Torvalds
So to not overtax my poor brain, I'll just call them all -rc releases, and hope that developers see them as a sign that there's been stuff merged, and we should start calming down and seeing to the merged patches being stable soon enough..
Hehe, and a bunch of important (for me) ones that couldn't get in yet
Damn right. If 2.6.10 doesn't boot on the G5 with i8042 and 8250 drivers built in, and doesn't sleep (well, more to the point doesn't resume) on my shinybook, I shall sulk :)
Signature · 1 line
dwmw2
Quoted 3 lines · David Woodhouse
Damn right. If 2.6.10 doesn't boot on the G5 with i8042 and 8250 drivers built in, and doesn't sleep (well, more to the point doesn't resume) on my shinybook, I shall sulk :)
Suspend is Shakespearean, "to sleep, perchance to dream." I don't know why people are still trying the fix suspend, it works perfectly on all my machines, I would like to see some work on wake-the-@-up at this point.
The sad part is that using apm and 2.4, all my laptops seem happy to sleep and wake when asked. One of the reasons I'm running 2.4 on the old ones, the new ones boot fast enought that I don't care.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Quoted 6 lines · Bill Davidsen
Quoted 3 lines · David Woodhouse
Damn right. If 2.6.10 doesn't boot on the G5 with i8042 and 8250 drivers built in, and doesn't sleep (well, more to the point doesn't resume) on my shinybook, I shall sulk :)
Quoted 8 lines
Suspend is Shakespearean, "to sleep, perchance to dream." I don't know why people are still trying the fix suspend, it works perfectly on all my machines, I would like to see some work on wake-the-@-up at this point.
The sad part is that using apm and 2.4, all my laptops seem happy to sleep and wake when asked. One of the reasons I'm running 2.4 on the old ones, the new ones boot fast enought that I don't care.
Well, for me, 2.6.9 *broke* wake up. Suspend still works fine, but I'm back to 2.6.9-rc4 to get working wake up.
Daniel
Quoted 9 lines · Daniel Gryniewicz
Quoted 7 lines · Bill Davidsen
Quoted 3 lines · David Woodhouse
Damn right. If 2.6.10 doesn't boot on the G5 with i8042 and 8250 drivers built in, and doesn't sleep (well, more to the point doesn't resume) on my shinybook, I shall sulk :)
Quoted 8 lines
Quoted 4 lines
Suspend is Shakespearean, "to sleep, perchance to dream." I don't know why people are still trying the fix suspend, it works perfectly on all my machines, I would like to see some work on wake-the-@-up at this point.
The sad part is that using apm and 2.4, all my laptops seem happy to sleep and wake when asked. One of the reasons I'm running 2.4 on the old ones, the new ones boot fast enought that I don't care.
Well, for me, 2.6.9 *broke* wake up. Suspend still works fine, but I'm back to 2.6.9-rc4 to get working wake up.
I think you missed my point... I said suspend works now work on wakeup. Same issue you have.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Quoted 21 lines · Linus Torvalds
Ok,
Linux-2.6.10-rc1 is out there for your pleasure.I thought long and hard about the name of this release (*), since one of the main complaints about 2.6.9 was the apparently release naming scheme.
Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
So to not overtax my poor brain, I'll just call them all -rc releases, and hope that developers see them as a sign that there's been stuff merged, and we should start calming down and seeing to the merged patches being stable soon enough..
[...]
Quoted 7 lines
Oh, and the _real_ name did actually change. It's not Zonked Quokka any more, that's so yesterday. Today we're Woozy Numbat! Get your order in!
Linus
(*) In other words, I had a beer and watched TV. Mmm... Donuts.
So change the naming to something like that:
linux-x.y.z.p
where
x = 2,
y = 6,
z = 1, 3, 5, ... => unstable - something like -rc or -rc-bk
z = 0, 2, 4, ... => stable
p - optional as with 2.6.8.1 - added to stable release when you need to correct some very stupid and very important bug,
added to unstable release - meaning new snapshot
So there will be:
2.6.10 (possibly 2.6.10.1, ... if 2.6.10 will be broken) 2.6.11.0
2.6.11.1
2.6.11.2
...
2.6.12
...
In this scheme you can not mark that you are going to release "stable" version quickly, but I do not think we need it. Or if you feel it is needed then start numbering p from 90, 91, ... 100, 101, ... for really near to stable -rcs.
Grzegorz Kulewski
Quoted 4 lines · Linus Torvalds
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
This should be easy: the cut-over should be when you're tempted to rename it 2.6.next. If you have no intention (or hope) of renaming 2.6.x-rc1 to 2.6.x, it is not a "release candidate" by definition.
What's the point? It serves as a signal that a) we're not accepting more big changes b) we think it's ready for primetime and needs serious QA c) when 2.6.next gets released, the _exact code_ has gone through a test cycle and we can have some confidence that there won't be any nasty 0-day bugs when we go to install 2.6.next on a production machine.
Quoted 1 line
(*) In other words, I had a beer and watched TV. Mmm... Donuts.
Please devote some more beer and TV to this problem after you release 2.6.10.
Signature · 1 line
Mathematics is the supreme nostalgia of our time.
Quoted 12 lines · Matt Mackall
Quoted 4 lines · Linus Torvalds
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
This should be easy: the cut-over should be when you're tempted to rename it 2.6.next. If you have no intention (or hope) of renaming 2.6.x-rc1 to 2.6.x, it is not a "release candidate" by definition.
Quoted 6 lines
What's the point? It serves as a signal that a) we're not accepting more big changes b) we think it's ready for primetime and needs serious QA c) when 2.6.next gets released, the
_exactcode_has gone through a test cycle and we can have some confidence that there won't be any nasty 0-day bugs when we go to install 2.6.next on a production machine.
I have this feeling Linus is laughing at us when he debates these arguments. Nonetheless I finally feel obliged to say a "release candidate" is a release candidate. It should only be called that if it is planned to be the real version, and the real version is _exactly_ the same bar the version number. If it isn't even planned to be released unmodified it's a -pre patch.
/me still hears Linus laughing. He's only been doing this for 13 years.
Cheers,
Con
Quoted 4 lines · Linus Torvalds
Quoted 4 lines
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
Quoted 9 lines · Matt Mackall
This should be easy: the cut-over should be when you're tempted to rename it 2.6.next. If you have no intention (or hope) of renaming 2.6.x-rc1 to 2.6.x, it is not a "release candidate" by definition. What's the point? It serves as a signal that a) we're not accepting more big changes b) we think it's ready for primetime and needs serious QA c) when 2.6.next gets released, the
_exactcode_has gone through a test cycle and we can have some confidence that there won't be any nasty 0-day bugs when we go to install 2.6.next on a production machine.
I'm sure you have a well-founded logically consistent self-consistent method of defining what release candidates are; unfortunately hordes of others do, too, and their notions are in turn all subtly inconsistent with yours and each other's, and they're all relatively vocal about them.
Quoted 1 line · Linus Torvalds
Quoted 1 line
(*) In other words, I had a beer and watched TV. Mmm... Donuts.
Quoted 2 lines · Matt Mackall
Please devote some more beer and TV to this problem after you release 2.6.10.
Give the emperor penguin a break. There's bound to be enough weighing on him as it is with just the usual barrage of technical issues. The new release process hasn't even been given a chance to fail yet as the two commercial distros with the largest userbases haven't even gotten to the point where they've both released 2.6 yet, and debian isn't using 2.6 as the install kernel yet either.
Quoted 1 line · Matt Mackall
Mathematics is the supreme nostalgia of our time.
It would be nice if this were qualified with something that distinguished the outlandish idealizations you're actually criticizing from real math, which makes no presumption that its axioms or hypotheses have any connection to reality, observations, or predictions thereof. The abuse you're speaking of is poor modelling for the sake of tractability of symbolic calculations, which has nothing to do with proof or logic.
-- wli
Hey guys, calm down, I meant "naming wars" in a silly kind of way, not the nasty kind.
The fact is, Linux naming has always sucked. Well, at least the versioning I've used. Others tend to be more organized. Me, I'm the "artistic" type, so I sometimes try to do something new, and invariably stupid.
The best suggestion so far has been to _just_ use another number, which makes sense considering my dislike for both -rc and -pre.
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".
More importantly, maybe we could all realize that it isn't actually that big of an issue ;)
Linus
Quoted 5 lines · Linus Torvalds
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".
I can probably live with that if you promise not to break the automated tools for a while.
Signature · 1 line
Mathematics is the supreme nostalgia of our time.
Quoted 3 lines · Matt Mackall
I can probably live with that if you promise not to break the automated tools for a while.
Ahh.. I just do it to keep you on your toes.
Don't get lazy on me now,
Linus
Quoted 10 lines · On Fri, 22 Oct 2004 20:38:47 -0500 Matt Mackall <[email protected]> wrote:
Quoted 5 lines · Linus Torvalds
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".
I can probably live with that if you promise not to break the automated tools for a while.
Indeed. All i really care about is keeping my robots happy. Call it whatever, just don't call me late for dinner. cliffw
Quoted 8 lines
Signature · 6 lines
Mathematics is the supreme nostalgia of our time. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Signature · 2 lines
The church is near, but the road is icy. The bar is far, but i will walk carefully. - Russian proverb
Quoted 12 lines · Linus Torvalds
Hey guys, calm down, I meant "naming wars" in a silly kind of way, not the nasty kind.
The fact is, Linux naming has always sucked. Well, at least the versioning I've used. Others tend to be more organized. Me, I'm the "artistic" type, so I sometimes try to do something new, and invariably stupid.
The best suggestion so far has been to _just_ use another number, which makes sense considering my dislike for both -rc and -pre.
Quoted 7 lines
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".
More importantly, maybe we could all realize that it isn't actually that big of an issue ;)
Besides... -pre and -rc additions do not sort correctly unless your sort routine has special cases to take care of it.
Quoted 19 lines · alan
Quoted 17 lines · Linus Torvalds
Hey guys, calm down, I meant "naming wars" in a silly kind of way, not the nasty kind.
The fact is, Linux naming has always sucked. Well, at least the versioning I've used. Others tend to be more organized. Me, I'm the "artistic" type, so I sometimes try to do something new, and invariably stupid.
The best suggestion so far has been to _just_ use another number, which makes sense considering my dislike for both -rc and -pre.
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".
Quoted 5 lines
Quoted 2 lines
More importantly, maybe we could all realize that it isn't actually that big of an issue ;)
Besides... -pre and -rc additions do not sort correctly unless your sort routine has special cases to take care of it.
I've got a good page or so of compare function in ketchup already, I'm loathe to teach it about -final though.
Signature · 1 line
Mathematics is the supreme nostalgia of our time.
Quoted 3 lines
The fact is, Linux naming has always sucked. Well, at least the versioning I've used. Others tend to be more organized. Me, I'm the "artistic" type, so I sometimes try to do something new, and invariably stupid.
Given that the versioning was supposedly <major>.<minor>.<patchlevel> and the difference between 2.4 and 2.6 was substantial, why not just bump <major> instead of the minor. Then we'd have 3.0, 3.1, 4.0, 4.1.1 (for stupid mistakes). Isn't it time we move off the 2.x series and start thinking of the 3.x series?
Signature · 1 line
Lab tests show that use of micro$oft causes cancer in lab animals
Quoted 9 lines · Wakko Warner
Quoted 3 lines
The fact is, Linux naming has always sucked. Well, at least the versioning I've used. Others tend to be more organized. Me, I'm the "artistic" type, so I sometimes try to do something new, and invariably stupid.
Given that the versioning was supposedly <major>.<minor>.<patchlevel> and the difference between 2.4 and 2.6 was substantial, why not just bump <major> instead of the minor. Then we'd have 3.0, 3.1, 4.0, 4.1.1 (for stupid mistakes). Isn't it time we move off the 2.x series and start thinking of the 3.x series?
Yes - lets stick to fewer numbers. They can count faster, instead of having a long string of them. I hope linux doesn't
end up like X. "X11R6.8.1" The "X" itself is a counter, although it is understandable if it never increments to "Y". But
that "11" doesn't change much, and then there are three more numbers. :-/
I think two numbers are enough. If "4.1" was a scre-up, release "4.2" instead of a "4.1.1". People shouldn�'t try to readtoo much information from the number structure - there are logs, docs and websites for that.
Helge Hafting
Salut,
Quoted 5 lines · Helge Hafting
Yes - lets stick to fewer numbers. They can count faster, instead of having a long string of them. I hope linux doesn't
end up like X. "X11R6.8.1" The "X" itself is a counter, although it is understandable if it never increments to "Y". But
that "11" doesn't change much, and then there are three more numbers. :-/
X11 is the name of the protocol: the X Protocol, version 11, as released by the MIT. There was an X10.
6.8.1 is the current X.Org release that we did because 6.8 turned out to have a nasty idiot bug.
Tonnerre
Followup to: <[email protected]> By author: Tonnerre <[email protected]> In newsgroup: linux.dev.kernel
Quoted 4 lines
Salut,
On Sun, Oct 24, 2004 at 03:33:33PM +0200, Helge Hafting wrote:
Quoted 9 lines
Quoted 5 lines
Yes - lets stick to fewer numbers. They can count faster, instead of having a long string of them. I hope linux doesn't
end up like X. "X11R6.8.1" The "X" itself is a counter, although it is understandable if it never increments to "Y". But
that "11" doesn't change much, and then there are three more numbers. :-/X11 is the name of the protocol: the X Protocol, version 11, as released by the MIT. There was an X10.
There also were a W, and and X1, X2, ... X11.
However, there is a tendency for numbers to get stuck (witness Linux 2.x). In particular, X11R6 got encoded in many places including pathnames for no good reason. Under the pre-R6 naming schemes we'd had R7 a long time ago.
-hpa
Quoted 17 lines · H. Peter Anvin
Followup to: <[email protected]> By author: Tonnerre <[email protected]> In newsgroup: linux.dev.kernelQuoted 4 lines
Salut,
On Sun, Oct 24, 2004 at 03:33:33PM +0200, Helge Hafting wrote:
Quoted 9 lines
Quoted 5 lines
Yes - lets stick to fewer numbers. They can count faster, instead of having a long string of them. I hope linux doesn't
end up like X. "X11R6.8.1" The "X" itself is a counter, although it is understandable if it never increments to "Y". But
that "11" doesn't change much, and then there are three more numbers. :-/X11 is the name of the protocol: the X Protocol, version 11, as released by the MIT. There was an X10.
Quoted 6 lines
There also were a W, and and X1, X2, ... X11.
However, there is a tendency for numbers to get stuck (witness Linux 2.x). In particular, X11R6 got encoded in many places including pathnames for no good reason. Under the pre-R6 naming schemes we'd had R7 a long time ago.
How true.
# pwd /usr/src2/uClibc-0.9.26 # grep -r X11R6 . ./ldso/ldso/readelflib1.c: UCLIBC_RUNTIME_PREFIX "usr/X11R6/lib:" ./utils/ldd.c: path = UCLIBC_RUNTIME_PREFIX "usr/X11R6/lib:" ./utils/ldconfig.c: scan_dir(UCLIBC_RUNTIME_PREFIX "/usr/X11R6/lib"); ./libpthread/linuxthreads/README.Xfree3.2:This file describes how to make a threaded X11R6. ./libpthread/linuxthreads/README.Xfree3.2:You need the source-code of XFree-3.2. I used the sources of X11R6.1 ./libpthread/linuxthreads/README.Xfree3.2:cp XF3.2/xc/lib/*/*.so.?.? /usr/X11R6/lib/ ./libpthread/linuxthreads/README.Xfree3.2:cd /usr/X11R6/lib/ ./Changelog: o Made the lib loader also support libs in /usr/X11R6/lib by default
This should be removed.
cd /usr/lib; ln -s /usr/X11R6/* .
or
echo /usr/X11R6/lib >>/etc/ld.so.conf
are the better ways to handle this
(I use first one)
--
vda
Quoted 22 lines · Denis Vlasenko
Quoted 12 lines · H. Peter Anvin
Followup to: <[email protected]> By author: Tonnerre <[email protected]> In newsgroup: linux.dev.kernelQuoted 8 lines · Helge Hafting
Quoted 5 lines
Yes - lets stick to fewer numbers. They can count faster, instead of having a long string of them. I hope linux doesn't
end up like X. "X11R6.8.1" The "X" itself is a counter, although it is understandable if it never increments to "Y". But
that "11" doesn't change much, and then there are three more numbers. :-/X11 is the name of the protocol: the X Protocol, version 11, as released by the MIT. There was an X10.
Quoted 6 lines
There also were a W, and and X1, X2, ... X11.
However, there is a tendency for numbers to get stuck (witness Linux 2.x). In particular, X11R6 got encoded in many places including pathnames for no good reason. Under the pre-R6 naming schemes we'd had R7 a long time ago.
How true.
Quoted 8 lines
This should be removed.
cd
/usr/lib; ln -s/usr/X11R6/*.
or
echo/usr/X11R6/lib>>/etc/ld.so.confare the better ways to handle this
(I use first one)
/usr/{bin,lib/X11 have been version-free symlinks since ages...
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 9 lines
Quoted 9 lines
Quoted 4 lines
However, there is a tendency for numbers to get stuck (witness Linux 2.x). In particular, X11R6 got encoded in many places including pathnames for no good reason. Under the pre-R6 naming schemes we'd had R7 a long time ago.
How true.
This should be removed.
Quoted 8 lines
Quoted 6 lines
cd
/usr/lib; ln -s/usr/X11R6/*.
or
echo/usr/X11R6/lib>>/etc/ld.so.confare the better ways to handle this
(I use first one)
/usr/{bin,lib/X11have been version-free symlinks since ages...
Why X server special cased at all?
Having /usr/XnnRmm was a mistake in the first place. --
vda
Salut,
Quoted 1 line · Denis Vlasenko
Having
/usr/XnnRmmwas a mistake in the first place.
BSD has /X11R6, whilst I'd agree that /opt/xorg is probably a lot more appropriate. If you want I can take this discussion back to the X.Org folks again, but I don't think it's actually going to change anything.
Tonnerre
Quoted 11 lines · Tonnerre
Salut,
Quoted 1 line · Denis Vlasenko
Having
/usr/XnnRmmwas a mistake in the first place.BSD has /X11R6, whilst I'd agree that
/opt/xorgis probably a lot more appropriate. If you want I can take this discussion back to the X.Org folks again, but I don't think it's actually going to change anything.
/opt/X (or /usr/X) is really what it probably should be.
-hpa
Quoted 8 lines · H. Peter Anvin
Quoted 7 lines · Tonnerre
Salut,
Quoted 1 line · Denis Vlasenko
Having
/usr/XnnRmmwas a mistake in the first place.
Quoted 6 lines
Quoted 4 lines
BSD has /X11R6, whilst I'd agree that
/opt/xorgis probably a lot more appropriate. If you want I can take this discussion back to the X.Org folks again, but I don't think it's actually going to change anything.
/opt/X(or/usr/X) is really what it probably should be.
Why there is any distinction between, say, gcc and X? KDE and Midnight Commander? etc... Why some of them go to /opt while others are spread across dozen of dirs? This seems to be inconsistent to me.
I won't push my solution to anyone, just going to show you how does it look:
# ls /usr/app -1 Linux-PAM-0.75 MPlayer-0.90rc4 SDL-1.2.6 acrobat-5.06 acroread-5.0.8 alsa-lib-0.9.0beta12 alsa-lib-0.9.7 alsa-utils-0.9.0beta12 alsa-utils-0.9.7 apache-1.3.24 atk-1.2.4 audiofile-0.2.3 audiogalaxy-0520 autofs-4.1.3 bash-2.05b bglibs-1.005 binutils-2.15.91.0.1 bridge-utils-0.9.6 bsdftpd-6.0-ssl-0.5.2 busybox-1.00-pre6 ...
Typical package under /usr/app:
# ls -l /usr/app/gcc-3.4.1 total 12 -r-xr-xr-x 1 root root 1429 Oct 25 13:39 !vda_install -r-xr-xr-x 1 root root 874 Sep 15 2003 !vda_install_root -r-xr-xr-x 1 root root 157 Aug 17 2003 !vda_ver drwxr-xr-x 2 root root 360 Oct 25 13:39 bin drwxr-xr-x 3 root root 72 Jul 15 16:54 include drwxr-xr-x 2 root root 224 Jul 15 16:54 info drwxr-xr-x 3 root root 336 Jul 15 16:54 lib drwxr-xr-x 3 root root 72 Jul 15 16:54 libexec drwxr-xr-x 4 root root 96 Jul 15 16:54 man
This is how it is made visible to the rest of system:
# ls -l /usr/lib /usr/bin | grep gcc-3.4.1 lrwxrwxrwx 1 root root 26 Oct 25 13:39 c++ -> /usr/app/gcc-3.4.1/bin/c++ lrwxrwxrwx 1 root root 26 Oct 25 13:39 cpp -> /usr/app/gcc-3.4.1/bin/cpp lrwxrwxrwx 1 root root 26 Oct 25 13:39 g++ -> /usr/app/gcc-3.4.1/bin/g++ lrwxrwxrwx 1 root root 26 Oct 25 13:39 gcc -> /usr/app/gcc-3.4.1/bin/gcc lrwxrwxrwx 1 root root 29 Oct 25 13:39 gccbug -> /usr/app/gcc-3.4.1/bin/gccbug lrwxrwxrwx 1 root root 27 Oct 25 13:39 gcov -> /usr/app/gcc-3.4.1/bin/gcov lrwxrwxrwx 1 root root 44 Oct 25 13:39 i386-pc-linux-gnu-c++ -> /usr/app/gcc-3.4.1/bin/i386-pc-linux-gnu-c++ lrwxrwxrwx 1 root root 44 Oct 25 13:39 i386-pc-linux-gnu-g++ -> /usr/app/gcc-3.4.1/bin/i386-pc-linux-gnu-g++ lrwxrwxrwx 1 root root 44 Oct 25 13:39 i386-pc-linux-gnu-gcc -> /usr/app/gcc-3.4.1/bin/i386-pc-linux-gnu-gcc lrwxrwxrwx 1 root root 50 Oct 25 13:39 i386-pc-linux-gnu-gcc-3.4.1 -> /usr/app/gcc-3.4.1/bin/i386-pc-linux-gnu-gcc-3.4.1 lrwxrwxrwx 1 root root 34 Oct 25 13:39 libiberty.a -> /usr/app/gcc-3.4.1/lib/libiberty.a lrwxrwxrwx 1 root root 34 Oct 25 13:39 libstdc++.a -> /usr/app/gcc-3.4.1/lib/libstdc++.a lrwxrwxrwx 1 root root 35 Oct 25 13:39 libstdc++.la -> /usr/app/gcc-3.4.1/lib/libstdc++.la lrwxrwxrwx 1 root root 35 Oct 25 13:39 libstdc++.so -> /usr/app/gcc-3.4.1/lib/libstdc++.so lrwxrwxrwx 1 root root 37 Oct 25 13:39 libstdc++.so.6 -> /usr/app/gcc-3.4.1/lib/libstdc++.so.6 lrwxrwxrwx 1 root root 41 Oct 25 13:39 libstdc++.so.6.0.1 -> /usr/app/gcc-3.4.1/lib/libstdc++.so.6.0.1 lrwxrwxrwx 1 root root 34 Oct 25 13:39 libsupc++.a -> /usr/app/gcc-3.4.1/lib/libsupc++.a lrwxrwxrwx 1 root root 35 Oct 25 13:39 libsupc++.la -> /usr/app/gcc-3.4.1/lib/libsupc++.la
It's pretty modular: I can remove and install packages as needed, I can go back to older versions to check regressions etc...
BTW today I just added uclibc and some uc-compiled apps to the mix. They coexist nicely with the rest of the system
(I needed only some almost trivial tricks)
uc-Midnight Commander is 3 times smaller than glibc one :) --
vda
Salut,
Quoted 3 lines · Denis Vlasenko
Why there is any distinction between, say, gcc and X? KDE and Midnight Commander? etc... Why some of them go to /opt while others are spread across dozen of dirs?
Well.
FHS specifies that everything needed to boot the system should got to /bin and /sbin. The base system (build system, etc.) should go to /usr. The rest should be /opt/itspackagename.
I'm not quite a FHS fan. I use libexec dirs, but I still have my build system under /usr (and my home under /usr/home), and the rest (X, KDE et al) lives under /opt.
Tonnerre
Quoted 9 lines · Tonnerre
Salut,
Quoted 3 lines · Denis Vlasenko
Why there is any distinction between, say, gcc and X? KDE and Midnight Commander? etc... Why some of them go to /opt while others are spread across dozen of dirs?
Well.
Quoted 7 lines
FHS specifies that everything needed to boot the system should got to /bin and /sbin. The base system (build system, etc.) should go to /usr. The rest should be
/opt/itspackagename.I'm not quite a FHS fan. I use libexec dirs, but I still have my build system under /usr (and my home under
/usr/home), and the rest (X, KDE et al) lives under /opt.
Hi,
In Gentoo everything goes to /usr/bin or /usr/sbin except very basic things that are instaled in /bin or /sbin and binary-only packages that are instaled in /opt (very good idea).
Yes, Linux (or UNIX) directory structure should be changed years ago but nobody (except GOBO Linux I think) is going to do it. That will require patching realy big amount of code and changing some standards. If somebody has time for it feel free to contact me, and I will tell him (or her) what should be changed to produce The New Directory Standard That Breaks Everything But Is The Best And Most Sane In The World (TM)... :-)
Grzegorz Kulewski
Salut,
Quoted 6 lines · Grzegorz Kulewski
Yes, Linux (or UNIX) directory structure should be changed years ago but nobody (except GOBO Linux I think) is going to do it. That will require patching realy big amount of code and changing some standards. If somebody has time for it feel free to contact me, and I will tell him (or her) what should be changed to produce The New Directory Standard That Breaks Everything But Is The Best And Most Sane In The World (TM)... :-)
This is not the case, thanks to autoconf and pkg-config. On one of my systems, I have all the binaries under /Library/..., and all the libs
under /Frameworks/..., and the doc goes under
/Library/Documentation/someplace...
It's not a problem any more, thanks to the ongoing modularization.
Tonnerre
Quoted 10 lines · Tonnerre
Salut,
Quoted 6 lines · Grzegorz Kulewski
Yes, Linux (or UNIX) directory structure should be changed years ago but nobody (except GOBO Linux I think) is going to do it. That will require patching realy big amount of code and changing some standards. If somebody has time for it feel free to contact me, and I will tell him (or her) what should be changed to produce The New Directory Standard That Breaks Everything But Is The Best And Most Sane In The World (TM)... :-)
Quoted 6 lines
This is not the case, thanks to autoconf and pkg-config. On one of my systems, I have all the binaries under /Library/..., and all the libs
under /Frameworks/..., and the doc goes under
/Library/Documentation/someplace...It's not a problem any more, thanks to the ongoing modularization.
Hi,
1. Not all packages use autoconf.
2. Not all packages use autoconf correctly.
3. Autoconf and others are broken in my opinion (yes they provide some good features but have very high amount of bad features or stupid concepts too). This is not only mine opinion btw.
4. Changing the directory structure just to rename /lib to /Library is not very ambituous... I can even call it strange...
5. I am thinking of changing directory structure (and some other things) some more... For example placing every package in its own dir - like /apps/gcc/3.4.2/<install date>/{bin,lib,...} and placing symlinks in /bin (or how to call it) to required files from packages bins (like RELINK), adding something like /apps/<package name>/<version>/<install date>/deps and keeping symlinks to all external libs/programs/scripts used by <package name> there, changing autoconf to ask not test for features and much more (= turning Linux standards upside down).
Grzegorz Kulewski
Quoted 3 lines · Grzegorz Kulewski
5. I am thinking of changing directory structure (and some other things) some more... For example placing every package in its own dir
- like /apps/gcc/3.4.2/<install date>/{bin,lib,...} and placing
I've been placing things in /opt/package/version for quite a while. I use a perl script to set the *PATH environment variables to point at whatever versions I choose for each package. I patched aclocal (of automake) to search in directories given by $ACLOCAL_PATH, but the patch has been ignored for several years, so I'm not expecting it to be picked up.
Signature · 2 lines
Måns Rullgård [email protected]
Quoted 6 lines · Måns Rullgård
Quoted 3 lines · Grzegorz Kulewski
5. I am thinking of changing directory structure (and some other things) some more... For example placing every package in its own dir
- like /apps/gcc/3.4.2/<install date>/{bin,lib,...} and placingI've been placing things in
/opt/package/versionfor quite a while.
That's essentially what the GoboLinux distribution does, except that it does it for everything down to and including core stuff like "sh" and "ls".
Quoted 2 lines
I use a perl script to set the *PATH environment variables to point at whatever versions I choose for each package.
If you have enough things installed you might run into problems with the size of PATH (perhaps unlikely on Linux, but I recall hitting the limit on Solaris at one point).
When I used to do this on Solaris, my most recent solution was to use GNU stow to create symlinks from a single prefix to all of the installed packages. Then I'd only need one additional entry in PATH, MANPATH, and so on. stow made it easy enough to add and remove packages, though there were trouble spots with duplicate files such as the emacs info directory.
If I recall correctly, in the GoboLinux case gcc 3.4.2 would be installed in "/Programs/GCC/3.4.2/{bin,lib,...}". A symlink from "/Programs/GCC/Current" to "3.4.2" would select that as the current version. The Current trees are symlinked into a single prefix (like I did with stow). Gobo has scripts to manage all of this. I believe "/bin" is a symlink to the bin directory in the main install prefix, but there are patches so that while "/bin" can be used for lookups it does not appear when you list "/".
-Dave Dodge
Quoted 12 lines · Dave Dodge
Quoted 6 lines · Måns Rullgård
Quoted 3 lines · Grzegorz Kulewski
5. I am thinking of changing directory structure (and some other things) some more... For example placing every package in its own dir
- like /apps/gcc/3.4.2/<install date>/{bin,lib,...} and placingI've been placing things in
/opt/package/versionfor quite a while.That's essentially what the GoboLinux distribution does, except that it does it for everything down to and including core stuff like "sh" and "ls".
Quoted 6 lines
Quoted 2 lines
I use a perl script to set the *PATH environment variables to point at whatever versions I choose for each package.
If you have enough things installed you might run into problems with the size of PATH (perhaps unlikely on Linux, but I recall hitting the limit on Solaris at one point).
At my university they were running a locally hacked version of tcsh to increase the maximum size of PATH to allow a similar setup.
Quoted 6 lines
When I used to do this on Solaris, my most recent solution was to use GNU stow to create symlinks from a single prefix to all of the installed packages. Then I'd only need one additional entry in PATH, MANPATH, and so on. stow made it easy enough to add and remove packages, though there were trouble spots with duplicate files such as the emacs info directory.
The advantage with setting the environment variables directly is that it's easy to switch between different versions of any package without changing anything on disk, and I can have different version selected in different xterms. A symlink based scheme doesn't allow this.
Quoted 8 lines
If I recall correctly, in the GoboLinux case gcc 3.4.2 would be installed in "/Programs/GCC/3.4.2/{bin,lib,...}". A symlink from "/Programs/GCC/Current" to "3.4.2" would select that as the current version. The Current trees are symlinked into a single prefix (like I did with stow). Gobo has scripts to manage all of this. I believe "/bin" is a symlink to the bin directory in the main install prefix, but there are patches so that while "/bin" can be used for lookups it does not appear when you list "/".
If there's one thing I detest, it is such hiding of files. The GUI in MacOSX does such things too, even /tmp is hidden there. It's visible from a shell though. I won't even mention mswindows. If a file exists, it should be visible, period. The standard hiding of .dot files is perfectly good enough without any extra hacks.
Signature · 2 lines
Måns Rullgård [email protected]
Quoted 2 lines · Måns Rullgård
Quoted 1 line · Dave Dodge
If I recall correctly, in the GoboLinux case
[...]
Quoted 6 lines
Quoted 3 lines
I believe "/bin" is a symlink to the bin directory in the main install prefix, but there are patches so that while "/bin" can be used for lookups it does not appear when you list "/".
If there's one thing I detest, it is such hiding of files. The GUI in MacOSX does such things too, even /tmp is hidden there.
I believe Gobo only has paths such as "/bin" for legacy compatibility (for example scripts starting with #!/bin/...). "/dev" is another case, since that isn't where Gobo puts its devices, but lots of things are going to assume they can use "/dev/zero" and "/dev/null".
Quoted 1 line
It's visible from a shell though.
Gobo actually does it in the kernel; whether that's better or worse depends on your point of view. There's a command-line tool "GoboHide" that provides a list of hidden things:
http://gobolinux.org/index.php?page=doc/articles/gobohide
I think all of the things hidden in a normal GoboLinux desktop are just legacy symlinks, and the real locations they point to are fully visible. Unlike MacOS, where the Finder ignores a lot of real directories and applications (I've been bitten there by "/tmp" myself).
-Dave Dodge
Quoted 8 lines · Dave Dodge
Quoted 2 lines · Måns Rullgård
Quoted 1 line · Dave Dodge
If I recall correctly, in the GoboLinux case
[...]
Quoted 4 lines
Quoted 3 lines
I believe "/bin" is a symlink to the bin directory in the main install prefix, but there are patches so that while "/bin" can be used for lookups it does not appear when you list "/".
Quoted 7 lines
Quoted 2 lines
If there's one thing I detest, it is such hiding of files. The GUI in MacOSX does such things too, even /tmp is hidden there.
I believe Gobo only has paths such as "/bin" for legacy compatibility (for example scripts starting with #!/bin/...). "/dev" is another case, since that isn't where Gobo puts its devices, but lots of things are going to assume they can use "
/dev/zero" and "/dev/null".
I don't quite see the point in breaking compatibility just for the sake of being different, or whatever their reasons may be. There is absolutely no technical justification for doing it that way.
Quoted 6 lines
Quoted 1 line
It's visible from a shell though.
Gobo actually does it in the kernel; whether that's better or worse depends on your point of view. There's a command-line tool "GoboHide" that provides a list of hidden things:
Quoted 7 lines
http://gobolinux.org/index.php?page=doc/articles/gobohide
I think all of the things hidden in a normal GoboLinux desktop are just legacy symlinks, and the real locations they point to are fully visible. Unlike MacOS, where the Finder ignores a lot of real directories and applications (I've been bitten there by "/tmp" myself).
On MacOSX you at least have the option to ignore the braindead GUI tools. Under the hood, it's largely POSIX compliant.
Signature · 2 lines
Måns Rullgård [email protected]
Quoted 7 lines · Tonnerre
Salut,
Quoted 3 lines · Denis Vlasenko
Why there is any distinction between, say, gcc and X? KDE and Midnight Commander? etc... Why some of them go to /opt while others are spread across dozen of dirs?
Quoted 6 lines
Well.
FHS specifies that everything needed to boot the system should got to /bin and /sbin. The base system (build system, etc.) should go to /usr. The rest should be
/opt/itspackagename.
...
The last phrase isn't exactly correct.
The FHS says:
Distributions may install software in /opt, but must not modify or delete software installed by the local system administrator without the assent of the local system administrator.
E.g. Debian installs nothing under /opt .
Quoted 1 line
Tonnerre
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 17 lines · Denis Vlasenko
Quoted 15 lines · H. Peter Anvin
Quoted 12 lines · Tonnerre
Salut,
Quoted 1 line · Denis Vlasenko
Having
/usr/XnnRmmwas a mistake in the first place.BSD has /X11R6, whilst I'd agree that
/opt/xorgis probably a lot more appropriate. If you want I can take this discussion back to the X.Org folks again, but I don't think it's actually going to change anything.
Quoted 7 lines
Quoted 1 line
/opt/X(or/usr/X) is really what it probably should be.Why there is any distinction between, say, gcc and X? KDE and Midnight Commander? etc... Why some of them go to /opt while others are spread across dozen of dirs? This seems to be inconsistent to me.
At one time Sun had the convention that things in /usr could be mounted ro on multiple machines. That worked, it predates Linux so Linux was the o/s which chose to go another way, and it covered the base things in a system.
That actually seems like a good way to split a networked environment, with /bin and /sbin having just enough to get the system up and mount /usr. I can't speak to why that is being done differently now.
I guess someone was nervous about mounting a local /usr/local on a (possibly) network mounted /usr and theu /opt, but that's a guess on my part as well.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Quoted 3 lines · Bill Davidsen
I guess someone was nervous about mounting a local
/usr/localon a (possibly) network mounted /usr and theu /opt, but that's a guess on my part as well.
/opt is structured, /usr/local is not; that's the big difference.
-hpa
Quoted 12 lines · Bill Davidsen
Quoted 5 lines · Denis Vlasenko
Why there is any distinction between, say, gcc and X? KDE and Midnight Commander? etc... Why some of them go to /opt while others are spread across dozen of dirs? This seems to be inconsistent to me.
At one time Sun had the convention that things in /usr could be mounted ro on multiple machines. That worked, it predates Linux so Linux was the o/s which chose to go another way, and it covered the base things in a system.
Quoted 7 lines
That actually seems like a good way to split a networked environment, with /bin and /sbin having just enough to get the system up and mount /usr. I can't speak to why that is being done differently now.
I guess someone was nervous about mounting a local
/usr/localon a (possibly) network mounted /usr and theu /opt, but that's a guess on my part as well.
Read-only /usr is required according to the FHS, and at least on Debian a read-only /usr works without problems.
A bigger problem might be to properly support it in the package manager.
cu
Adrian
[1]
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedQuoted 16 lines · Adrian Bunk
Quoted 15 lines · Bill Davidsen
Quoted 4 lines · Denis Vlasenko
Why there is any distinction between, say, gcc and X? KDE and Midnight Commander? etc... Why some of them go to /opt while others are spread across dozen of dirs? This seems to be inconsistent to me.
At one time Sun had the convention that things in /usr could be mounted ro on multiple machines. That worked, it predates Linux so Linux was the o/s which chose to go another way, and it covered the base things in a system.
That actually seems like a good way to split a networked environment, with /bin and /sbin having just enough to get the system up and mount /usr. I can't speak to why that is being done differently now.
Quoted 6 lines
Quoted 3 lines
I guess someone was nervous about mounting a local
/usr/localon a (possibly) network mounted /usr and theu /opt, but that's a guess on my part as well.Read-only /usr is required according to the FHS, and at least on Debian a read-only /usr works without problems.
Indeed. And that's what I use. In /etc/apt/apt.conf I have:
DPkg {
// Auto re-mounting of a readonly /usr
Pre-Invoke {"mount -o remount,rw /usr";};
Post-Invoke {"mount -o remount,ro /usr";};
}Quoted 1 line
A bigger problem might be to properly support it in the package manager.
Yep. Apt knows about it, but dpkg doesn't. And remounting /usr read-only fails if files are in use.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Quoted 13 lines · Geert Uytterhoeven
Quoted 3 lines · Adrian Bunk
Read-only /usr is required according to the FHS, and at least on Debian a read-only /usr works without problems.
Indeed. And that's what I use. In
/etc/apt/apt.confI have:DPkg { // Auto re-mounting of a readonly /usr Pre-Invoke {"mount -o remount,rw /usr";}; Post-Invoke {"mount -o remount,ro /usr";}; }
Quoted 4 lines
Quoted 1 line
A bigger problem might be to properly support it in the package manager.
Yep. Apt knows about it, but dpkg doesn't. And remounting /usr read-only fails if files are in use.
I was more thinking about the problems like a database upgrade requiring changes to e.g. the system tables of the database handled in the {pre,post}inst scripts. It even becomes more tricky since a postinst script might make changes to both /usr and such required actions.
These issues which require auditing of all packages are the real issue.
Quoted 3 lines
Gr{oetje,eeting}s,
Geert
cu
Adrian
Signature · 4 lines
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon SeedRe: The naming wars continue... [u]
In reply to H. Peter AnvinQuoted 8 lines · H. Peter Anvin
Quoted 7 lines · Tonnerre
Salut,
Quoted 1 line · Denis Vlasenko
Having
/usr/XnnRmmwas a mistake in the first place.
Quoted 7 lines
Quoted 4 lines
BSD has /X11R6, whilst I'd agree that
/opt/xorgis probably a lot more appropriate. If you want I can take this discussion back to the X.Org folks again, but I don't think it's actually going to change anything.
/opt/X(or/usr/X) is really what it probably should be.
Except if I am missing something, it is (or was) to be able to distinguish between versions that broke protocol compatibility ... so except if the protocol will never change again, it should really stay as is, and the apps should actually just start to use /usr/bin/X11 and /usr/lib/X11 that points to the latest or most stable instead of the versioned directories ...
Signature · 1 line
Martin Schlemmer
Re: The naming wars continue... [u]
Quoted 21 lines · Martin Schlemmer [c]
Quoted 10 lines · H. Peter Anvin
Quoted 8 lines · Tonnerre
Salut,
Quoted 1 line · Denis Vlasenko
Having
/usr/XnnRmmwas a mistake in the first place.Quoted 7 lines
Quoted 4 lines
BSD has /X11R6, whilst I'd agree that
/opt/xorgis probably a lot more appropriate. If you want I can take this discussion back to the X.Org folks again, but I don't think it's actually going to change anything.
/opt/X(or/usr/X) is really what it probably should be.
Quoted 6 lines
Except if I am missing something, it is (or was) to be able to distinguish between versions that broke protocol compatibility ... so except if the protocol will never change again, it should really stay as is, and the apps should actually just start to use
/usr/bin/X11and/usr/lib/X11that points to the latest or most stable instead of the versioned directories ...
This won't get fixed on lkml.
If you want to contribute in this area, try LSB/FHS etc. & Please do.
Signature · 1 line
~Randy
Re: The naming wars continue... [u]
Quoted 29 lines · Randy.Dunlap
Quoted 21 lines · Martin Schlemmer [c]
Quoted 10 lines · H. Peter Anvin
Quoted 8 lines · Tonnerre
Salut,
Quoted 1 line · Denis Vlasenko
Having
/usr/XnnRmmwas a mistake in the first place.Quoted 7 lines
Quoted 4 lines
BSD has /X11R6, whilst I'd agree that
/opt/xorgis probably a lot more appropriate. If you want I can take this discussion back to the X.Org folks again, but I don't think it's actually going to change anything.
/opt/X(or/usr/X) is really what it probably should be.Quoted 6 lines
Except if I am missing something, it is (or was) to be able to distinguish between versions that broke protocol compatibility ... so except if the protocol will never change again, it should really stay as is, and the apps should actually just start to use
/usr/bin/X11and/usr/lib/X11that points to the latest or most stable instead of the versioned directories ...
Quoted 3 lines
This won't get fixed on lkml.
If you want to contribute in this area, try LSB/FHS etc. & Please do.
While I appreciate the thought, I should admit that I was only trying to be the local smart-ass, so I have to decline to go on the LSB/FHS crusade :/ Maybe one of the others before me would be so kind.
PS: I probably should point out that my use of /usr/bin/X11 and
/usr/lib/X11 for the generic symlinks is not so generic, before I step on more toes ...
Thanks,
Signature · 1 line
Martin Schlemmer
Salut,
Quoted 1 line · H. Peter Anvin
There also were a W, and and X1, X2, ... X11.
I know. I didn't say there wasn't. They were all standards of the X protocol, however.
(Note, however, that there is a tiny difference in the command layout between the MIT X protocol specifiaction version 11 and the reality.)
Quoted 3 lines
However, there is a tendency for numbers to get stuck (witness Linux 2.x). In particular, X11R6 got encoded in many places including pathnames for no good reason.
Well, I'm driving my X11 from /opt/xorg and I don't have any problems yet. Just that the NVidia driver doesn't get it right, but I threw away my NVidia card in favor of a dual-core Voodoo 5 anyway.
Tonnerre
Quoted 7 lines · Tonnerre
Quoted 5 lines · Helge Hafting
Yes - lets stick to fewer numbers. They can count faster, instead of having a long string of them. I hope linux doesn't
end up like X. "X11R6.8.1" The "X" itself is a counter, although it is understandable if it never increments to "Y". But
that "11" doesn't change much, and then there are three more numbers. :-/
Quoted 5 lines
X11 is the name of the protocol: the X Protocol, version 11, as released by the MIT. There was an X10.
6.8.1 is the current X.Org release that we did because 6.8 turned out to have a nasty idiot bug.
What a coincidence: use s/X11R/2./ to convert from X11 to Linux :-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Salut,
Quoted 4 lines · Geert Uytterhoeven
Quoted 2 lines
6.8.1 is the current X.Org release that we did because 6.8 turned out to have a nasty idiot bug.
What a coincidence: use s/X11R/2./ to convert from X11 to Linux :-)
Yes, and it was even around the same time, just some days later IIRC. And the culprit was a TLA: it was XPM, not NFS.
Tonnerre
Quoted 3 lines · Linus Torvalds
More importantly, maybe we could all realize that it isn't actually that big of an issue ;)
Linus
Linus I agree it isn't a huge issue. The main thing for me is that I could just give a _real_ release candidate more testing - run it through some regression tests, make sure it functions OK on all my computers, etc. I expect this would be helpful for people with large sets of regression tests, and maybe those maintaining 'other' architectures too.
I understand there's always "one more" patch to go in, but now that we're doing this stable-development system, I think a week or two weeks or even three weeks to stabalize the release with only really-real-bugfixes can't be such a bad thing.
2.6.x-rc (rc for Ridiculous Count) can then be our development releases, and 2.6.x-rc (rc for Release Candidate) are then closer to stable releases (in terms of getting patches in).
Optionally, you could change Ridiculous Count to PRErelease to avoid confusion :)
Other than that I don't have much to complain about... so keep up the good work!
Nick
Quoted 16 lines · Nick Piggin
Linus I agree it isn't a huge issue. The main thing for me is that I could just give a _real_ release candidate more testing - run it through some regression tests, make sure it functions OK on all my computers, etc. I expect this would be helpful for people with large sets of regression tests, and maybe those maintaining 'other' architectures too.
I understand there's always "one more" patch to go in, but now that we're doing this stable-development system, I think a week or two weeks or even three weeks to stabalize the release with only really-real-bugfixes can't be such a bad thing.
2.6.x-rc (rc for Ridiculous Count) can then be our development releases, and 2.6.x-rc (rc for Release Candidate) are then closer to stable releases (in terms of getting patches in).
Quoted 5 lines
Optionally, you could change Ridiculous Count to PRErelease to avoid confusion :)
Other than that I don't have much to complain about... so keep up the good work!
I do agree that the pre and rc names gave a strong hint that (-pre) new features would be considered or (-rc) it's worth doing more serious testing. If Linux doesn't like this any more, perhaps some other way to indicate the same thing would be desirable. I admit that the kernel has gotten so good that I only try -rc (by whatever name) kernel, I'm not waiting for the next big thing. I think that's really good, actually.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Quoted 4 lines · Bill Davidsen
I do agree that the pre and rc names gave a strong hint that (-pre) new features would be considered or (-rc) it's worth doing more serious testing.
Well, I actually do try to _explain_ in the kernel mailing list annoucements what it going on.
One of the reasons I don't like "-rcX" vs "-preX" is that they are so meaningless. In contrast, when I actually do the write-up on a patch, I tend to explain what I expect to have changed, and if I feel we're getting ready for a release, I'll say something like
..
Ok,
trying to make ready for the real 2.6.9 in a week or so, so please give
this a beating, and if you have pending patches, please hold on to them for a bit longer, until after the 2.6.9 release. It would be good to have a 2.6.9 that doesn't need a dot-release immediately ;)
....
which is a hell of a lot more descriptive, in my opinion.
Which is just another reason why the name itself is not that meaningful. It can never carry the kind of information that people seem to _expect_ it to carry.
Linus
But not everyone reads LKML or the annoucement..a lot of people may just decide whether to try this out based on the name. They go to kernel.org from time to time and say: I'll test the next rc release.
"RC" has a very well-known meaning. It would make people scared if they find rc isn't stable, and lose a lot of potential testers. So why break it?
Even another meaningless name which doesn't collide with RC is better.
Quoted 4 lines
Which is just another reason why the name itself is not that meaningful.
It can never carry the kind of information that people seem to _expect_ it to carry.
Quoted 8 lines · Hua Zhong
But not everyone reads LKML or the annoucement..a lot of people may just decide whether to try this out based on the name. They go to kernel.org from time to time and say: I'll test the next rc release.
"RC" has a very well-known meaning. It would make people scared if they find rc isn't stable, and lose a lot of potential testers. So why break it?
I expect a "rc" to be a kind of beta - an attempt to get it right rather than experiment - but it may still be broken. Someone who want stability should try the latest point release (2.6.9) or fix release (2.6.9.x with the current system)
Helge Hafting
Quoted 24 lines · Linus Torvalds
Quoted 4 lines · Bill Davidsen
I do agree that the pre and rc names gave a strong hint that (-pre) new features would be considered or (-rc) it's worth doing more serious testing.
Well, I actually do try to _explain_ in the kernel mailing list annoucements what it going on.
One of the reasons I don't like "-rcX" vs "-preX" is that they are so meaningless. In contrast, when I actually do the write-up on a patch, I tend to explain what I expect to have changed, and if I feel we're getting ready for a release, I'll say something like
..
Ok,
trying to make ready for the real 2.6.9 in a week or so, so please give
this a beating, and if you have pending patches, please hold on to them for a bit longer, until after the 2.6.9 release. It would be good to have a 2.6.9 that doesn't need a dot-release immediately ;)
Quoted 3 lines
....
which is a hell of a lot more descriptive, in my opinion.
Yeah but try fitting that in the extraversion. Maybe we should use -hopstt(hold on patches, stress-test this) for this kind of stuff, and -beo (bring 'em on) for the "early" -rcX ... :)
Signature · 7 lines
Giuseppe "Oblomov" Bilotta
Can't you see
It all makes perfect sense
Expressed in dollar and cents
Pounds shillings and pence
(Roger Waters)Followup to: <[email protected]> By author: Giuseppe Bilotta <[email protected]> In newsgroup: linux.dev.kernel
Quoted 5 lines
Yeah but try fitting that in the extraversion. Maybe we should use -hopstt(hold on patches, stress-test this) for this kind of stuff, and -beo (bring 'em on) for the "early" -rcX ... :)
We could even spell them -pre and -rc.
-hpa
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 6 lines · H. Peter Anvin
Quoted 4 lines
Yeah but try fitting that in the extraversion. Maybe we should use -hopstt(hold on patches, stress-test this) for this kind of stuff, and -beo (bring 'em on) for the "early" -rcX ... :)
We could even spell them -pre and -rc.
Exactly.
If 2.4 works so well, why change it in 2.6?
Mind Booster Noori
- -- /* *************************************************************** */
Marcos Daniel Marado Torres AKA Mind Booster Noori
http://student.dei.uc.pt/~marado - [email protected]
() Join the ASCII ribbon campaign against html email, Microsoft
/\ attachments and Software patents. They endanger the World.
Sign a petition against patents: http://petition.eurolinux.org
/* *************************************************************** */ -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFBfwrymNlq8m+oD34RAlqzAJ4h8s7eS3Jfkz8lvbGvnf35hVN9FgCeJYyQ suVxn5dtr7sXQYN9FM/EVHM=
=9xz9
-----END PGP SIGNATURE-----
Quoted 18 lines · Linus Torvalds
Quoted 1 line · Bill Davidsen
I do agree that the pre and rc names gave a strong hint that (-pre) new features would be considered or (-rc) it's worth doing more serious testing.
Well, I actually do try to _explain_ in the kernel mailing list annoucements what it going on.
One of the reasons I don't like "-rcX" vs "-preX" is that they are so meaningless. In contrast, when I actually do the write-up on a patch, I tend to explain what I expect to have changed, and if I feel we're getting ready for a release, I'll say something like
..
Ok,
trying to make ready for the real 2.6.9 in a week or so, so please give
this a beating, and if you have pending patches, please hold on to them for a bit longer, until after the 2.6.9 release. It would be good to have a 2.6.9 that doesn't need a dot-release immediately ;)
Quoted 5 lines
....
which is a hell of a lot more descriptive, in my opinion.
Which is just another reason why the name itself is not that meaningful. It can never carry the kind of information that people seem to _expect_ it to carry.
I wasn't going to reply to this since it's your call and I've had my say, but since several others have, let me throw out one more idea on the off chance you like it:
Stop doing the pre's on the next version! After 2.6.10 comes 2.6.10.1 etc, which everyone can see are incremental changes to 2.6.10, and when you really mean it, then put out 2.6.11-rc1.
Did that strike a nerve?
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Quoted 1 line · Bill Davidsen
Stop doing the pre's on the next version!
There are no -pre's in 2.6, at least not till now.
Quoted 1 line
After 2.6.10 comes 2.6.10.1 etc, which everyone can see are incremental changes to 2.6.10, and when you really mean it, then put out 2.6.11-rc1.
2.6.z.w is already "reserved" for another kind of updates. You're proposing a system where you have:
2.6.10
2.6.10-???1
2.6.10-???2
2.6.10-???3
2.6.11-rc1
2.6.11-rc2
2.6.11-rc3
2.6.11
...
Or, in other words, you don't want Linus to "Stop doing the pre's", you're wanting exactly the same scheme 2.4 is using and works preety fine: just replace 10 by 11 in the '???' series, replace '???' by 'pre' and you have:
x.y.z
x.y.z+1-pre1
...
x.y.z+1-preN
x.y.z+1-rc1
2.4 model allways worked fine, we should stick with it instead of pulling our hair out trying to figure out how to solve the problem that is already solved.
Mind Booster Noori
- -- /* *************************************************************** */
Marcos Daniel Marado Torres AKA Mind Booster Noori
http://student.dei.uc.pt/~marado - [email protected]
() Join the ASCII ribbon campaign against html email, Microsoft
/\ attachments and Software patents. They endanger the World.
Sign a petition against patents: http://petition.eurolinux.org
/* *************************************************************** */ -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Made with pgp4pine 1.76
iD8DBQFBfw+JmNlq8m+oD34RAmsdAJwOMJz7GqtQV3zG/DJYz14pioNADACfTI3H fVfR9SmC8BxHpmT0B9rWVNk=
=avZN
-----END PGP SIGNATURE-----
Quoted 1 line · Bill Davidsen
Linus Torvalds wrote:
[snip]
Quoted 8 lines
Quoted 3 lines
Which is just another reason why the name itself is not that meaningful. It can never carry the kind of information that people seem to _expect_ it to carry.
I wasn't going to reply to this since it's your call and I've had my say, but since several others have, let me throw out one more idea on the off chance you like it:
Quoted 5 lines
Stop doing the pre's on the next version! After 2.6.10 comes 2.6.10.1 etc, which everyone can see are incremental changes to 2.6.10, and when you really mean it, then put out 2.6.11-rc1.
Did that strike a nerve?
2.6.10.1, etc. suggests important bug fixes for 2.6.10, *not* prereleases of 2.6.11. But... perhaps (with sufficient warning) the even/odd principle could be applied to the third number. So, this would happen:
2.6.even = release
2.6.even.x = release, with added bug/security fixes
2.6.odd = first (zeroth?) -pre/-rc release
2.6.odd.x = additional -pre/-rc releases
A more concrete example:
2.6.11-rc1, 2.6.11-rc2, 2.6.11-rc3, 2.6.11, 2.6.12-rc1, 2.6.12-rc2, 2.6.12 would become:
2.6.11, 2.6.11.1, 2.6.11.2, 2.6.12, 2.6.13, 2.6.13.1, 2.6.14
How does this sound? (It just occurred to me that this might break scripts, but it may be worth discussing anyway.)
-Barry K. Nathan <[email protected]>
Quoted 10 lines · Barry K. Nathan
Quoted 1 line · Bill Davidsen
Linus Torvalds wrote:
[snip]
Quoted 4 lines
Quoted 1 line
Which is just another reason why the name itself is not that meaningful. It can never carry the kind of information that people seem to _expect_ it to carry.
I wasn't going to reply to this since it's your call and I've had my say, but since several others have, let me throw out one more idea on the off chance you like it:
Quoted 8 lines
Quoted 3 lines
Stop doing the pre's on the next version! After 2.6.10 comes 2.6.10.1 etc, which everyone can see are incremental changes to 2.6.10, and when you really mean it, then put out 2.6.11-rc1.
Did that strike a nerve?
2.6.10.1, etc. suggests important bug fixes for 2.6.10, *not* prereleases of 2.6.11. But... perhaps (with sufficient warning) the even/odd principle could be applied to the third number. So, this would happen:
2.6.10.1 suggests nothing, that convention was used ONCE in the 2.6 series. I liked the -pre convention as it was, but Linus has dropped that in spite of several hundred instances of its use. From that I conclude that if Linus like 2.6.10.1 he will use it, and if not we will have -rc releases which aren't release candidates. His call.
I personally think it will slow development because some people tested the -rc releases harder, but that's not decided by vote.
Signature · 3 lines
-bill davidsen ([email protected]) "The secret to procrastination is to put things off until the last possible moment - but no longer" -me
Quoted 3 lines
Stop doing the pre's on the next version! After 2.6.10 comes 2.6.10.1 etc, which everyone can see are incremental changes to 2.6.10, and when you really mean it, then put out 2.6.11-rc1.
Oh no. We had a perfectly working scheme of pre's and rc's, why shall it be changed? This will break scripts for _zero_ gain.
Well, if Linus does not want pre's and wants to use rc's only, that's fine with me, but fourth digit
(or other such innovations) is not.
--
vda
Quoted 24 lines · Linus Torvalds
Quoted 4 lines · Bill Davidsen
I do agree that the pre and rc names gave a strong hint that (-pre) new features would be considered or (-rc) it's worth doing more serious testing.
Well, I actually do try to _explain_ in the kernel mailing list annoucements what it going on.
One of the reasons I don't like "-rcX" vs "-preX" is that they are so meaningless. In contrast, when I actually do the write-up on a patch, I tend to explain what I expect to have changed, and if I feel we're getting ready for a release, I'll say something like
..
Ok,
trying to make ready for the real 2.6.9 in a week or so, so please give
this a beating, and if you have pending patches, please hold on to them for a bit longer, until after the 2.6.9 release. It would be good to have a 2.6.9 that doesn't need a dot-release immediately ;)
Quoted 3 lines
....
which is a hell of a lot more descriptive, in my opinion.
Indeed. But you hide this kind of information very carefully. Announcing with a subject like this one isn't very descriptive. Also the majority of kernel downloaders probably don't read lkml at all. So how should they figure out?
It would be very helpful if you could please include at least your announcement in the changelog or some other file on kernel.org. The changelog as of now is probably technically correct, but way to specific and large for the average non kernel hacker - go ask someone who's happy to get a kernel compiled by himself.
I don't care that much about the whole development model and the numbering system as long as I can find the information above without reading hundreds of lkml lists daily. I guess most of the average users out there would think alike. You just don't address them right now.
Tom
ps:
using -rc suffix which everywhere else uses for release candidate isn't a good choice. The -pre and -rc known from earlier kernels were much more intuitive. Personally I'd even prefer something like x.y.LATEST - x.y.LATEST-test{1,2..} - x.y.NEXT-rc{1,2,..} - x.y.NEXT
Quoted 5 lines · On Wed, 27 Oct 2004, [email protected] wrote:
Quoted 2 lines
which is a hell of a lot more descriptive, in my opinion.
Indeed. But you hide this kind of information very carefully. Announcing with a subject like this one isn't very descriptive.
But that _wasn't_ in this idiotic thread.
The subject line of my announcement was
Subject: Linux 2.6.9-rc4 - pls test (and no more patches)
and the body was
Ok,
trying to make ready for the real 2.6.9 in a week or so, so please give
this a beating, and if you have pending patches, please hold on to them for a bit longer, until after the 2.6.9 release. It would be good to have a 2.6.9 that doesn't need a dot-release immediately ;)
The appended shortlog gives a pretty good idea of what has been going on. Mostly small stuff, with some architecture updates and an ACPI update thrown in for good measure.
(plus the shortlog).
Not exactly "hidden", was it?
And to everybody complaining about "-rcX" - people don't want to break existing scripts, so the naming possibilities are either "-pre" or "-rc". And we've used "-rc" for the whole 2.6.x series, so there had better be a _good_ reason to change the naming.
So far, nobody has had a good reason. People are just complaining, because this is an area where you can complain without actually having any real hard technical input. It's "easy" to have an opinion.
So guys, look at the big picture. Is this really worth worrying over?
Linus
Quoted 13 lines
The subject line of my announcement was
Subject: Linux 2.6.9-rc4 - pls test (and no more patches)
and the body was
Ok,
trying to make ready for the real 2.6.9 in a week or so, so please give
this a beating, and if you have pending patches, please hold on to them for a bit longer, until after the 2.6.9 release. It would be good to have a 2.6.9 that doesn't need a dot-release immediately ;)
Quoted 7 lines
The appended shortlog gives a pretty good idea of what has been going on. Mostly small stuff, with some architecture updates and an ACPI update thrown in for good measure.
(plus the shortlog).
Not exactly "hidden", was it?
To sum up, why don't you call everything before you reach this point -pre and then when you decide to write the mail and realise you want to say no more patches just check in patch calling it -rc ? you claim you don't know when to diffrentiate between -pre and -rc, (or maybe you don't care) well how do you decide to write the above e-mail? I think that would satisfy nearly everyone and I don't see what would be so different from your POV, but it is in the end up to you...
Quoted 4 lines
So far, nobody has had a good reason. People are just complaining, because this is an area where you can complain without actually having any real hard technical input. It's "easy" to have an opinion.
So guys, look at the big picture. Is this really worth worrying over?
There has been a fair bit of bike shedding going on... so I think we should use some sort of timber and paint it red...
Dave.
Quoted 3 lines · Dave Airlie
There has been a fair bit of bike shedding going on... so I think we should use some sort of timber and paint it red...
Ok, I nominate this for the strangest entry in the discussion so far.
Linus
Quoted 9 lines · Linus Torvalds
Quoted 3 lines · Dave Airlie
There has been a fair bit of bike shedding going on... so I think we should use some sort of timber and paint it red...
Ok, I nominate this for the strangest entry in the discussion so far.
Heh, yeah, glad I'm not the only one incapable of making sense of that. :)
Anyway, I've been reading this thread and just want to add my own small comments to it :
Personally I was a bit sceptical of the "new development model" at first, but as 2.6.x has progressed I've come to like it very much. I'm using 2.6 on a number of boxes, servers, workstations at work and my personal machine at work, and my impression is that it's the fastest kernel we've had so far, and it's stable (at least I've not had any major issues). So to me it seems to be working just fine.
Some people have been asking for a sepperate tree for all the experimental and unstable stuff, but as I see it that role is fulfilled by Andrews -mm tree.
Things go into -mm, then get a bit (or a lot in some cases) workout and then slowly migrate into the mainline (Linus) tree as they settle down and are proven to be stable. This is good since it keeps the stable kernel up-to-date feature wise, and stuff has a place to get fixed and stabilized before it moves to mainline, so mainline 2.6 is not a minefield of unstable changes (and I think Andrew is doing a very good job at this), but it's not a hugely out-of-date thing as it used to be with a sepperate 2.<odd number>.x development tree.
The people asking for a very stable 2.6.x.y.z.whatever tree are forgetting a few things in my oppinion;
First they seem to forget that point releases actually serve the role of "new and improved stable kernel", so 2.6.x is the new "maintainance release" of the 2.6.x-1 kernel.
Also they forget that there's a period of -rc releases before a point release where stability and incompatibility problems can be dealt with. They also forget that there's nothing stopping them from forking off 2.6.x at any point in time and maintaining their own "ultra stable" kernel based on that release (hopefully they would still merge their fixes into whatever is the current Linus kernel).
I'm starting to ramble, all I really want to say is that I think the current model works well - changes get testing in -mm before hitting mainline, and mainline is not lacking behind in fixes and features as badly as we've seen earlier with 2.4.x vs 2.5.x, 2.3.x vs 2.2.x and previous development branches. And I think Andrew, Linus and the other main kernel people are doing a very good job with the kernel atm.
--
Jesper Juhl
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
There has been a fair bit of bike shedding going on... so I think we should use some sort of timber and paint it red...
Ok, I nominate this for the strangest entry in the discussion so far.
Heh, yeah, glad I'm not the only one incapable of making sense of that. :)
I think Linus made sense of it :-),
for anyone that needs a explaination (takes all the fun out of it :-)
http://www.unixguide.net/freebsd/faq/16.19.shtml
Dave.
Whoops, wrong thread, This was actually meant more for the "new development model" thread, but whatever, it'll just have to stay here now :)
/Jesper Juhl
PS. Trimming CC as this is a fairly irrelevant little comment
Quoted 1 line · * Linus Torvalds ([email protected]) wrote:
However, for some reason four numbers just looks visually too obnoxious to
I agree, four numbers is *very* obnoxious, I mean, really, if for no other reason than *Oracle* uses four numbers. :)
Stephen
Quoted 5 lines · Stephen Frost
Quoted 1 line · * Linus Torvalds ([email protected]) wrote:
However, for some reason four numbers just looks visually too obnoxious to
I agree, four numbers is *very* obnoxious, I mean, really, if for no other reason than *Oracle* uses four numbers. :)
Actually Oracle uses (or at least displays) 5 numbers. :-)
e.g. The version currently in use where i work: 9.2.0.5.0
Bis denn
Signature · 4 lines
Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
Quoted 10 lines · * Matthias Schniedermeyer ([email protected]) wrote:
Quoted 5 lines · Stephen Frost
Quoted 1 line · * Linus Torvalds ([email protected]) wrote:
However, for some reason four numbers just looks visually too obnoxious to
I agree, four numbers is *very* obnoxious, I mean, really, if for no other reason than *Oracle* uses four numbers. :)
Actually Oracle uses (or at least displays) 5 numbers. :-)
e.g. The version currently in use where i work: 9.2.0.5.0
Eh, their directory structure is (or at least, was last I checked) based off of four numbers.
ie: /oracle/9.2.0.1
Stephen
Quoted 8 lines · Stephen Frost
Quoted 7 lines · * Matthias Schniedermeyer ([email protected]) wrote:
Quoted 5 lines · Stephen Frost
Quoted 1 line · * Linus Torvalds ([email protected]) wrote:
However, for some reason four numbers just looks visually too obnoxious to
I agree, four numbers is *very* obnoxious, I mean, really, if for no other reason than *Oracle* uses four numbers. :)
Quoted 8 lines
Quoted 3 lines
Actually Oracle uses (or at least displays) 5 numbers. :-)
e.g. The version currently in use where i work: 9.2.0.5.0
Eh, their directory structure is (or at least, was last I checked) based off of four numbers.
ie: /oracle/9.2.0.1
The directory is a "user-supplied" value. AFAIR (last time i installed an oracle-client myself is about 2 years ago (i never had to install a server)) the "default" is/was something like: /oracle/OraHome1
My DBA collegues use a default of first 3 numbers without delimiters
ie: /server/oracle/920
When i connect to a server with sqlplus i get this:
- snip -
Connected to:
Oracle9i Release 9.2.0.5.0 - 64bit Production
JServer Release 9.2.0.5.0 - Production
- snip -
Oracle shows 5 numbers.
Bis denn
Signature · 4 lines
Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous.
Quoted 1 line · In article <[email protected]> you wrote:
The directory is a "user-supplied" value.
Actually yes and no. With 10g, the "product" directory contain the (3 digits) version number (unrelated the actual ora home).
The different positions are well defined according to oracle, releases have changes in the first 4 positions, where the first is the major product version, the second is the release, the third are platform independend features. The base release for 10g was 10.1.0.2, and the first patchset is 10.1.0.3
Quoted 2 lines
My DBA collegues use a default of first 3 numbers without delimiters
ie: /server/oracle/920
This has a bit changed with 10g.
Greetings
Bernd
Signature · 2 lines
eckes privat - http://www.eckes.org/ Project Freefire - http://www.freefire.org/
Salut,
Quoted 2 lines · Stephen Frost
I agree, four numbers is *very* obnoxious, I mean, really, if for no other reason than *Oracle* uses four numbers. :)
$ ld --version | head -1 GNU ld version 2.15.91.0.2 $
Tonnerre
Quoted 1 line · * Linus Torvalds ([email protected]) wrote:
Quoted 1 line
However, for some reason four numbers just looks visually too obnoxious to
Quoted 2 lines · Stephen Frost
I agree, four numbers is *very* obnoxious, I mean, really, if for no other reason than *Oracle* uses four numbers. :)
I swear I had nothing to do with it.
-- wli
Quoted 4 lines · Linus Torvalds
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all agree that it stands for "Ridiculous Count" rather than "Release Candidate".
Naah... That's too boring.
I think we should have several different annotations, to denote how stable the tarball is supposed to be, and how close we are to a final release. Say:
Raw Code, or Revamp & Catch-up: the sort of thing you'd get right after the huge number of changesets we saw go in right after 2.6.9. Depending on whether it contains mostly incremental changes or major rework of internals, you'd go with the former or the latter.
Really Churning: more of the same, but not with such a big back-log from waiting for the previous release.
Rapidly Changing: still accepting a large number of patches, fixing bugs, adding features, whatever, but not as much of a dump of never-tested-together patches as Raw Code tarballs.
Run with Care: sort of the same as above, but used to explicitly mark tarballs in which patches that add significant risk of introducing memory, disk or government corruption.
Ready or Close: as we approach a stable release, we stop merging new features, and focus on installing only serious bug fixes.
Release Cuality: if it works, it becomes the final release. No known bugs, except for typos ;-)
Signature · 3 lines
Alexandre Oliva http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org}Quoted 3 lines · Alexandre Oliva
Release Cuality: if it works, it becomes the final release. No known bugs, except for typos ;-)
LOL.
Linus
Quoted 2 lines · Linus Torvalds
However, for some reason four numbers just looks visually too obnoxious to me
If you do something Really Big it's time to call the kernel 3.whatever. If not, the new release management scheme suggests that the release numbers are likely to stay within the 2.6 frame anyway.
Thus, the .6 is superfluous and can be dropped. Bingo, you have three numbers again.
Signature · 1 line
Matthias Urlichs | {M:U} IT Design @ m-u-it.de | [email protected]Quoted 17 lines · William Lee Irwin III
Quoted 4 lines · Linus Torvalds
Quoted 4 lines
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
Quoted 9 lines · Matt Mackall
This should be easy: the cut-over should be when you're tempted to rename it 2.6.next. If you have no intention (or hope) of renaming 2.6.x-rc1 to 2.6.x, it is not a "release candidate" by definition. What's the point? It serves as a signal that a) we're not accepting more big changes b) we think it's ready for primetime and needs serious QA c) when 2.6.next gets released, the
_exactcode_has gone through a test cycle and we can have some confidence that there won't be any nasty 0-day bugs when we go to install 2.6.next on a production machine.
Quoted 4 lines
I'm sure you have a well-founded logically consistent self-consistent method of defining what release candidates are; unfortunately hordes of others do, too, and their notions are in turn all subtly inconsistent with yours and each other's, and they're all relatively vocal about them.
Mine is the trivial one: a release candidate is something that is intended as a candidate for release. I'm not suggested anything about requirements for code quality, yadda yadda, just that there's an intent to release the release candidates should they pass muster. That does not appear to be the intent with most 2.6-rc of late.
Quoted 8 lines · Linus Torvalds
Quoted 1 line
Quoted 1 line
(*) In other words, I had a beer and watched TV. Mmm... Donuts.
Quoted 2 lines · Matt Mackall
Please devote some more beer and TV to this problem after you release 2.6.10.
Give the emperor penguin a break.
But I did! He's got until after 2.6.10.
(yes, that probably warrants a smiley)
Quoted 9 lines · Matt Mackall
Quoted 1 line
Mathematics is the supreme nostalgia of our time.
It would be nice if this were qualified with something that distinguished the outlandish idealizations you're actually criticizing from real math, which makes no presumption that its axioms or hypotheses have any connection to reality, observations, or predictions thereof. The abuse you're speaking of is poor modelling for the sake of tractability of symbolic calculations, which has nothing to do with proof or logic.
Actually just the opposite. It's more about Godel and Whitehead than Feynmann in my interpretation.
Signature · 1 line
Mathematics is the supreme nostalgia of our time.
Quoted 6 lines · William Lee Irwin III
Quoted 6 lines
It would be nice if this were qualified with something that distinguished the outlandish idealizations you're actually criticizing from real math, which makes no presumption that its axioms or hypotheses have any connection to reality, observations, or predictions thereof. The abuse you're speaking of is poor modelling for the sake of tractability of symbolic calculations, which has nothing to do with proof or logic.
Quoted 2 lines · Matt Mackall
Actually just the opposite. It's more about Godel and Whitehead than Feynmann in my interpretation.
"The notion of a perfectly modellable world is dead" and branding a field with the sins of those who misapplied it is not difficult to understand. Worse yet, it's even arguable that even the idealizations were done in full cognizance of their limited validity. Whatever else you're reading into it is not there. I suppose in this and the instance of some religiously-oriented .sig's there is little or no recourse.
-- wli
Quoted 7 lines · Linus Torvalds
Linux-2.6.10-rc1 is out there for your pleasure.
I thought long and hard about the name of this release (*), since one of the main complaints about 2.6.9 was the apparently release naming scheme. Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
Quoted 8 lines
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
So to not overtax my poor brain, I'll just call them all -rc releases, and hope that developers see them as a sign that there's been stuff merged, and we should start calming down and seeing to the merged patches being stable soon enough..
AFAICT the point is being able to refer to it by name and the only relevant property of the name is that it's distinct from all others. This does as well as most any other scheme giving each unique names. I'd be fine with nightly point releases, though I don't insist.
Quoted 8 lines · Linus Torvalds
So without any further ado, here's 2.6.10-rc1 in testing. A fair number of patches that were waiting for 2.6.9 to be out are in here, ranging all over the map: merges from -mm, network (and net driver) updates, SATA stuff, bluetooth, SCSI, device models, janitorial, you name it. Oh, and the _real_ name did actually change. It's not Zonked Quokka any more, that's so yesterday. Today we're Woozy Numbat! Get your order in!
Linus
(*) In other words, I had a beer and watched TV. Mmm... Donuts.
Sounds like a good way to come up with a new name to me. Cheers!
-- wli
Hi.
Quoted 2 lines · Linus Torvalds
Oh, and the _real_ name did actually change. It's not Zonked Quokka any more, that's so yesterday. Today we're Woozy Numbat! Get your order in!
I vote for a Klassy Kiwi release :>
Nigel
Signature · 7 lines
Nigel Cunningham Pastoral Worker Christian Reformed Church of Tuggeranong PO Box 1004, Tuggeranong, ACT 2901 Everyone lives by faith. Some people just don't believe it. Want proof? Try to prove that the theory of evolution is true.
Quoted 7 lines · Nigel Cunningham
Hi.
Quoted 2 lines · Linus Torvalds
Oh, and the _real_ name did actually change. It's not Zonked Quokka any more, that's so yesterday. Today we're Woozy Numbat! Get your order in!
I vote for a Klassy Kiwi release :>
What is this real name good for? Is it "useful" in any way? I can not remember where I could have seen it except in the Makefile...
Signature · 4 lines
Christian Hesse geek by nature linux by choice
Quoted 10 lines · Christian Hesse
Quoted 7 lines · Nigel Cunningham
Hi.
Quoted 2 lines · Linus Torvalds
Oh, and the _real_ name did actually change. It's not Zonked Quokka any more, that's so yesterday. Today we're Woozy Numbat! Get your order in!
I vote for a Klassy Kiwi release :>
What is this real name good for?
ssssh. Don't tell them I told you, but it's what keeps all those little penguins alive inside the harsh and treacherous confines of such a small kernel. Really, I'm surprised animal welfare isn't on the case.
Cheers,
Jon.
P.S. My cat is getting used to the giant stuffed tux I bought at Linux World. He initially wasn't sure whether it was to replace him in our affections or whether it should be attacked and eaten, but is now happy to share the sofa with him.
Re: The naming wars continue... - net/ipv4/netfilter/ipt_hashlimit.c does not build
In reply to Linus TorvaldsQuoted 2 lines · Linus Torvalds
Ok,
Linux-2.6.10-rc1 is out there for your pleasure.
CC [M] net/ipv4/netfilter/ipt_hashlimit.onet/ipv4/netfilter/ipt_hashlimit.c: In function `__dsthash_find':net/ipv4/netfilter/ipt_hashlimit.c:124: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c: In function __dsthash_free':net/ipv4/netfilter/ipt_hashlimit.c:173: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c: In function htable_selective_cleanup':net/ipv4/netfilter/ipt_hashlimit.c:261: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:261: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c:261: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:269: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:269: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:269: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c: In function `hashlimit_match':net/ipv4/netfilter/ipt_hashlimit.c:460: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:460: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c:460: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:469: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:469: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:469: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c:482: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:482: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:482: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c:493: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:493: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:493: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c:497: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:497: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:497: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c: In function dl_seq_start':net/ipv4/netfilter/ipt_hashlimit.c:572: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:572: error: structure has no member named l' net/ipv4/netfilter/ipt_hashlimit.c:572: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c: In function dl_seq_stop':net/ipv4/netfilter/ipt_hashlimit.c:606: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:606: error: structure has no member named locked_by' net/ipv4/netfilter/ipt_hashlimit.c:606: error: structure has no member named `l' make[3]: *** [net/ipv4/netfilter/ipt_hashlimit.o] Error 1
make[2]: *** [net/ipv4/netfilter] Error 2
make[1]: *** [net/ipv4] Error 2
make: *** [net] Error 2
--
Eyal Lebedinsky ([email protected]) <http://samba.org/eyal/>
Re: The naming wars continue... - net/ipv4/netfilter/ipt_hashlimit.c does not build
Quoted 4 lines · Eyal Lebedinsky
CC [M]
net/ipv4/netfilter/ipt_hashlimit.onet/ipv4/netfilter/ipt_hashlimit.c: In function `__dsthash_find':net/ipv4/netfilter/ipt_hashlimit.c:124: error: structure has no member named `locked_by'
Yes. Disable NETFILTER_DEBUG for now.
Linus
Quoted 10 lines · Linus Torvalds
Linux-2.6.10-rc1 is out there for your pleasure.
I thought long and hard about the name of this release (*), since one of the main complaints about 2.6.9 was the apparently release naming scheme.
Should it be "-rc1"? Or "-pre1" to show it's not really considered release quality yet? Or should I make like a rocket scientist, and count _down_ instead of up? Should I make names based on which day of the week the release happened? Questions, questions..
Quoted 4 lines
And the fact is, I can't see the point. I'll just call it all "-rcX", because I (very obviously) have no clue where the cut-over-point from "pre" to "rc" is, or (even more painfully obviously) where it will become the final next release.
When you (Linus) think a release is ready to be released, call it -rc1. If you did your job correctly, you can just sit and wait for a few days and release the -rc1 as a new kernel.
In the real world though, some bugs may crop up, so you'd be forced to release a rc2. Which in turn may be released unchanged as the final kernel.
Releases prior to a release candidate can be called whatever you like. I'd choose -preX ;-)
Signature · 1 line
Erik Hensema <[email protected]>
Quoted 1 line · Linus Torvalds
(*) In other words, I had a beer and watched TV. Mmm... Donuts.
seems to be a good opportunity even though I'm a bit late, but could you please include this patch, written by Heikki Linnakangas?
http://mareichelt.de/pub/boot-off-usb/boot-off-usb-2.patch
applies cleanly to 2.6.7 vanilla, thus making boot off usb devices possible
Signature · 1 line
Bastard Administrator in $hell
diff -c init/do_mounts.c init.orig/do_mounts.c
*** init/do_mounts.c Tue Oct 5 22:16:54 2004
--- init.orig/do_mounts.c Wed Jun 16 08:19:13 2004
***************
*** 272,285 ****
return 0;
}
! static int first_try = 1;
!
! int __init mount_block_root(char *name, int flags)
{
char *fs_names = __getname();
char *p;
char b[BDEVNAME_SIZE];
- int success;
get_fs_names(fs_names);
retry:
--- 272,282 ----
return 0;
}
! void __init mount_block_root(char *name, int flags)
{
char *fs_names = __getname();
char *p;
char b[BDEVNAME_SIZE];
get_fs_names(fs_names);
retry:
***************
*** 287,293 ****
int err = do_mount_root(name, p, flags, root_mount_data); switch (err) {
case 0:
- success = 1;
goto out;
case -EACCES:
flags |= MS_RDONLY;
--- 284,289 ----
***************
*** 295,320 ****
case -EINVAL:
continue;
}
! /* Print out a warning on the first attempt */
! if(first_try) {
! first_try = 0;
! /*
! * Allow the user to distinguish between failed sys_open
! * and bad superblock on root device.
! */
! __bdevname(ROOT_DEV, b);
!
! printk("VFS: Cannot open root device \"%s\" or %s\n",
root_device_name, b);
! printk("Retrying. Please verify the \"root=\" boot option.\n");
! }
! success = 0;
! goto out;
}
panic("VFS: Unable to mount root fs on %s", __bdevname(ROOT_DEV, b));
out:
putname(fs_names);
- return success;
}
#ifdef CONFIG_ROOT_NFS
--- 291,310 ----
case -EINVAL:
continue;
}
! /*
! * Allow the user to distinguish between failed sys_open
! * and bad superblock on root device.
! */
! __bdevname(ROOT_DEV, b);
! printk("VFS: Cannot open root device \"%s\" or %s\n",
root_device_name, b);
! printk("Please append a correct \"root=\" boot option\n");
!
! panic("VFS: Unable to mount root fs on %s", b);
}
panic("VFS: Unable to mount root fs on %s", __bdevname(ROOT_DEV, b));
out:
putname(fs_names);
}
#ifdef CONFIG_ROOT_NFS
***************
*** 360,366 ****
}
#endif
! int __init mount_root(void)
{
#ifdef CONFIG_ROOT_NFS
if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR) {
--- 350,356 ----
}
#endif
! void __init mount_root(void)
{
#ifdef CONFIG_ROOT_NFS
if (MAJOR(ROOT_DEV) == UNNAMED_MAJOR) {
***************
*** 384,390 ****
}
#endif
create_dev("/dev/root", ROOT_DEV, root_device_name);
! return mount_block_root("/dev/root", root_mountflags);
}
/*
--- 374,380 ----
}
#endif
create_dev("/dev/root", ROOT_DEV, root_device_name);
! mount_block_root("/dev/root", root_mountflags);
}
/*
***************
*** 398,427 ****
md_run_setup();
! do {
! if (saved_root_name[0]) {
! root_device_name = saved_root_name;
! ROOT_DEV = name_to_dev_t(root_device_name);
! if (strncmp(root_device_name, "/dev/", 5) == 0)
! root_device_name += 5;
! }
!
! is_floppy = MAJOR(ROOT_DEV) == FLOPPY_MAJOR;
!
! if (initrd_load())
! break;
! if (is_floppy && rd_doload && rd_load_disk(0))
! ROOT_DEV = Root_RAM0;
! if(mount_root())
! break;
! /* Mounting root failed. Retry after a small delay */
! set_current_state(TASK_INTERRUPTIBLE);
! schedule_timeout(1*HZ);
! } while(1);
umount_devfs("/dev");
sys_mount(".", "/", NULL, MS_MOVE, NULL);
sys_chroot(".");
--- 388,410 ----
md_run_setup();
! if (saved_root_name[0]) {
! root_device_name = saved_root_name;
! ROOT_DEV = name_to_dev_t(root_device_name);
! if (strncmp(root_device_name, "/dev/", 5) == 0)
! root_device_name += 5;
! }
! is_floppy = MAJOR(ROOT_DEV) == FLOPPY_MAJOR;
! if (initrd_load())
! goto out;
! if (is_floppy && rd_doload && rd_load_disk(0))
! ROOT_DEV = Root_RAM0;
+ mount_root();
+ out:
umount_devfs("/dev");
sys_mount(".", "/", NULL, MS_MOVE, NULL);
sys_chroot(".");
diff -c init/do_mounts.h init.orig/do_mounts.h
*** init/do_mounts.h Tue Oct 5 22:10:30 2004
--- init.orig/do_mounts.h Wed Jun 16 08:19:37 2004
***************
*** 11,18 ****
dev_t name_to_dev_t(char *name);
void change_floppy(char *fmt, ...);
! int mount_block_root(char *name, int flags);
! int mount_root(void);
extern int root_mountflags;
extern char *root_device_name;
--- 11,18 ----
dev_t name_to_dev_t(char *name);
void change_floppy(char *fmt, ...); ! void mount_block_root(char *name, int flags); ! void mount_root(void);
extern int root_mountflags;
extern char *root_device_name;
Quoted 3 lines · Linus Torvalds
However, for some reason four numbers just looks visually too obnoxious to me, so as I don't care that much, I'll just use "-rc", and we can all
Drop the '2.'. What would make you go from 2 to 3 and realistically, is it likely to happen?
In any case, if you replace the '-rc' suffix with just a number it will be interpreted as 2.x.y.1 is better than 2.x.y which is a nonsense. The "-rc" nomenclature makes it clear that the release will be 2.x.y
Quoted 1 line
o generic acl support for ->permission
..
Quoted 1 line
o xattr consolidation v3 - generic xattr API
Jeff, you'd been doing most reiserfs work lately - any chance to convert reiserfs to these generic APIs? Once we have all filesystems converted over maintaince will be much simpler. Take a look at ext2, ext3, or jfs on how to use them - I'll do xfs in the meantime.
Quoted 3 lines · Christoph Hellwig
Jeff, you'd been doing most reiserfs work lately
good stuff you are smoking, yes?
generic hardirq code in 2.6.10-rc1
In reply to Linus TorvaldsQuoted 5 lines
o generic irq subsystem: core
o generic irq subsystem: x86 port
o generic irq subsystem:x86_64port
o generic irq subsystem: ppc port
o generic irq subsystem: ppc64 port
Btw, it would be nice if all architectures that have more or less a copy of the i386 irq.c could switch to the generic code.
That would be: alpha,ia64, m32r, mips, sh, sh64, um, v850
and possibly cris (it currently has a simplified version)
Re: generic hardirq code in 2.6.10-rc1
Quoted 4 lines · Christoph Hellwig
Btw, it would be nice if all architectures that have more or less a copy of the i386
irq.ccould switch to the generic code.That would be: alpha,ia64, m32r, mips, sh, sh64, um, v850
Er, yeah, hold on (speaking for v850, I generally only ever look at real releases and try to update for the next one).
-Miles
Signature · 3 lines
`...the Soviet Union was sliding in to an economic collapse so comprehensive that in the end its factories produced not goods but bads: finished products less valuable than the raw materials they were made from.' [The Economist]
Re: generic hardirq code in 2.6.10-rc1
Quoted 8 lines · Miles Bader
Quoted 4 lines · Christoph Hellwig
Btw, it would be nice if all architectures that have more or less a copy of the i386
irq.ccould switch to the generic code.That would be: alpha,ia64, m32r, mips, sh, sh64, um, v850
Er, yeah, hold on (speaking for v850, I generally only ever look at real releases and try to update for the next one).
It's not urgent anyway - the old code continues to work, it'd just be nicer if as many as possible architectures used the common code.
PATCH 1/1 2.6.10-rc1: SCSI aacraid warning
In reply to Linus TorvaldsQuoted 8 lines · Linus Torvalds
...
Summary of changes from v2.6.9 to v2.6.10-rc1
============================================
...
Mark Haverkamp:
...
o aacraid: dynamic dev update
...
This causes the following warning with a recent gcc:
<-- snip -->
...
CC drivers/scsi/aacraid/aachba.odrivers/scsi/aacraid/aachba.c: In function `aac_scsi_cmd':drivers/scsi/aacraid/aachba.c:1140: warning: integer constant is too large for "long" type
...
<-- snip -->
The fix is simple:
drivers/scsi/aacraid/aachba.c renamed from drivers/scsi/aacraid/aachba.c.old +1 -1
@@ -1137,7 +1137,7 @@char *cp;dprintk ((KERN_DEBUG "READ CAPACITY command.\n" )); -if (fsa_dev_ptr[cid].size <=0x100000000 ) +if (fsa_dev_ptr[cid].size <=0x100000000ULL ) capacity = fsa_dev_ptr[cid].size -1 ;else capacity = (u32)-1 ;
Re: [patch] 2.6.10-rc1: SCSI aacraid warning
Quoted 32 lines · Adrian Bunk
Quoted 8 lines · Linus Torvalds
...
Summary of changes from v2.6.9 to v2.6.10-rc1
============================================
...
Mark Haverkamp:
...
o aacraid: dynamic dev update
...This causes the following warning with a recent gcc:
<-- snip -->
...
CCdrivers/scsi/aacraid/aachba.odrivers/scsi/aacraid/aachba.c: In function `aac_scsi_cmd':drivers/scsi/aacraid/aachba.c:1140: warning: integer constant is too large for "long" type
...<-- snip -->
The fix is simple:
Signed-off-by Adrian Bunk <[email protected]>
drivers/scsi/aacraid/aachba.c line 1143
Quoted 8 lines
drivers/scsi/aacraid/aachba.c renamed from drivers/scsi/aacraid/aachba.c.old +1
-1@@ -1137,7 +1137,7 @@char *cp;dprintk ((KERN_DEBUG "READ CAPACITY command.\n" )); -if (fsa_dev_ptr[cid].size <=0x100000000 ) +if (fsa_dev_ptr[cid].size <=0x100000000ULL ) capacity = fsa_dev_ptr[cid].size -1 ;else capacity = (u32)-1 ;
Sorry about that, I have it fixed in my working version. I must have forgotten to add it to the patch.
Signature · 1 line
Mark Haverkamp <[email protected]>
Re: [patch] 2.6.10-rc1: SCSI aacraid warning
Quoted 14 lines · Mark Haverkamp
Quoted 13 lines · Adrian Bunk
Quoted 8 lines · Linus Torvalds
...
Summary of changes from v2.6.9 to v2.6.10-rc1
============================================
...
Mark Haverkamp:
...
o aacraid: dynamic dev update
...This causes the following warning with a recent gcc:
[ ... ]
Quoted 2 lines
Sorry about that, I have it fixed in my working version. I must have forgotten to add it to the patch.
Actually looking back, I did fix this in a recent patch that I sent to James titled
"[PATCH] 2.6.9 aacraid: Support ROMB RAID/SCSI mode" on October 21.
Mark.
Signature · 1 line
Mark Haverkamp <[email protected]>