Andrew Morton [Wed, 4 Feb 2004 02:48:21 +0000 (18:48 -0800)]
[PATCH] u_int32_t causes cross-compile problems
From: Pratik Solanki <pratik.solanki@timesys.com>
I came across this C standards issue while cross-compiling the Linux kernel
with gcc on Solaris. The file gen_crc32table.c uses the non-standard type
u_int32_t. It's possible that the host machine's sys/types.h does not
define u_int32_t. The attached patch replaces u_int32_t with the POSIX
standard uint32_t and includes POSIX inttypes.h instead of sys/types.h.
Andrew Morton [Wed, 4 Feb 2004 02:48:12 +0000 (18:48 -0800)]
[PATCH] fix menuconfig choice item help display
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
Anders Gustafsson <andersg@0x63.nu>
Roman Zippel <zippel@linux-m68k.org>
This patch fixes menuconfig so it can display help text for individual
choice group config entries.
Previously it would only display the help text attached to the "choice"
item. There was no way to display the help attached to individual config
entries inside the choice group. Typically, the "choice" item has no help
text, and all the useful help is attached to the individual entries, so
this was a bit of a problem.
Andrew Morton [Wed, 4 Feb 2004 02:48:03 +0000 (18:48 -0800)]
[PATCH] /proc/stat:btime fix
From: George Anzinger <george@mvista.com>,
Petri Kaukasoina <kaukasoi@elektroni.ee.tut.fi>
btime in /proc/stat does not stay constant but decreases at a rate of 15
secs/day, because we're assuming that HZ is exactly 100. Use the correct
adjustments to fix that up.
Andrew Morton [Wed, 4 Feb 2004 02:47:54 +0000 (18:47 -0800)]
[PATCH] Fine tune the time conversion to eliminate conversion errors.
From: George Anzinger <george@mvista.com>
The time conversion code is erroring on the side of a bit too small. The
attached patch forces any error to be on the high side. The current code will
convert 1 nanosecond to zero jiffies (standard says that should be 1). It also
is around 1 nanosecond late on each roll to the next jiffie.
I have done some error checks with this patch applied and get the following
errors in PPB ( Parts Per Billion):
Andrew Morton [Wed, 4 Feb 2004 02:47:35 +0000 (18:47 -0800)]
[PATCH] try reiserfs before other filesystems
reiserfs places its superblock in weird places which can result in false
positives and various printks when other filesystems probe a resierfs
filesystem.
Andrew Morton [Wed, 4 Feb 2004 02:46:42 +0000 (18:46 -0800)]
[PATCH] oprofile, typo in alpha driver
From: Philippe Elie <phil.el@wanadoo.fr>
Unless I miss something this look like a typo, one user reported to get
error from the daemon: 'Unknown event for counter 1' (alpha ev6) and the
behavior was better but not completly sane after trying this patch: he get
spurious event for counter 1 when enabling only counter 0 but rarely now.
No alpha box to test this.
Andrew Morton [Wed, 4 Feb 2004 02:46:33 +0000 (18:46 -0800)]
[PATCH] oprofile per-cpu buffer overrun
From: Philippe Elie <phil.el@wanadoo.fr>
In a ring buffer controlled by a read and write positions we can't use
buffer_size but only buffer_size - 1 entry, the last free entry act as a
guard to avoid write pos overrun. This bug was hidden because the writer,
oprofile_add_sample(), request one more entry than really needed.
Andrew Morton [Wed, 4 Feb 2004 02:46:26 +0000 (18:46 -0800)]
[PATCH] console cleanup
From: Sam Ravnborg <sam@ravnborg.org>,
Ben Collins <bcollins@debian.org>
Fix up the console makefiles and logo generation.
1) To make output look like the rest of the kernel build.
2) To avoid make utilising chained rules, and therefore issuing a 'rm
drivers/video/logo/linux_logo.c ...' during the build.
I have previously submitted a few patches for logo/Makefile, but this is the
first one that actually address the problems I have seen in a proper way.
And no, I did not like such a simple thing to look that complicated, the
other option was to list too many files or to use other types of kbuild/make
magic.
Andrew Morton [Wed, 4 Feb 2004 02:45:42 +0000 (18:45 -0800)]
[PATCH] Zero last byte of mount option page.
From: James Morris <jmorris@redhat.com>
Here's a patch which zeroes the last byte of the mount option data copied
from userspace during mount(2).
For filesystems which parse mount options as strings (the majority), lack
of a zero terminator could cause the page to be overrun. The source code
comments specify that the maximum size of the mount data is PAGE_SIZE-1, so
this patch will not affect any valid binary-formatted mount data.
Andrew Morton [Wed, 4 Feb 2004 02:45:33 +0000 (18:45 -0800)]
[PATCH] posix_timers fixes
From: George Anzinger <george@mvista.com>
- Removes C++ comment in favor of C style.
- Removes the special treatment for MIPS SIGEV values. We only require
(and error if this fails) that the SIGEV_THREAD_ID value not share bits
with the other SIGEV values. Note that mips has yet to define this value
so when they do...
- Corrects the check for the signal range to be from 1 to SIGRTMAX
inclusive.
- Adds a check to verify that kmem_cache_alloc() actually returned a timer,
error if not.
- Fixes a bug in timer_gettime() where the incorrect value was returned if
a signal was pending on the timer OR the timer was a SIGEV_NONE timer.
Andrew Morton [Wed, 4 Feb 2004 02:45:24 +0000 (18:45 -0800)]
[PATCH] Better "Losing Ticks" Error Message
From: timothy parkinson <t@timothyparkinson.com>
Seems like a lot of people see the below error message, but aren't quite
sure why it happens or how to fix it. I sure didn't. Here's my attempt at
remedying that.
Andrew Morton [Wed, 4 Feb 2004 02:45:06 +0000 (18:45 -0800)]
[PATCH] Remove memblks from the kernel
From: "Martin J. Bligh" <mbligh@aracnet.com>
This patch removes memblks from the kernel ... we don't use them, and the
NUMA API that was planning to use them when they were originally designed
isn't going to use them anymore. They're just unnecessary added complexity
now ... time for them to go.
There's a slight complication in that ia64 uses something with a similar
name for part of its memory layout, but Jes Sorensen kindly untangled them
from each other for us. The patch with his modifications is below. Jes
tested it on ia64, and I testbuilt it with every config in my arsenal.
Andrew Morton [Wed, 4 Feb 2004 02:44:56 +0000 (18:44 -0800)]
[PATCH] remove SIIG combo cards PCI ids from parport_pc
From: Andrey Panin <pazke@donpac.ru>
support for SIIG made serial/parallel conbo cards was moved to
parport_serial driver some months ago, but their PCI ids still remain in
parport_pc PCI device table. Attached patch removes them.
Andrew Morton [Wed, 4 Feb 2004 02:44:47 +0000 (18:44 -0800)]
[PATCH] /proc/paritions: omit removable media
From: Neil Brown <neilb@cse.unsw.edu.au>
If programs like mount use /proc/partitions to find filesystems based on
labels, then surely we want md devices in there as they often contain
filesystems.
If the problem is that mount-by-label takes forever with removable media
then surely the "right" approch is the following patch, and then actually
set this flag on the "floppy.c" device. (It is already set for ide-floppy
and sd devices).
Andrew Morton [Wed, 4 Feb 2004 02:44:38 +0000 (18:44 -0800)]
[PATCH] md: Change the way the name of an md device is printed in error messages.
From: NeilBrown <neilb@cse.unsw.edu.au>
Instead of using ("md%d", mdidx(mddev)), we now use ("%s", mdname(mddev))
where mdname is the disk_name field in the associated gendisk structure.
This allows future flexability in naming.
Andrew Morton [Wed, 4 Feb 2004 02:44:11 +0000 (18:44 -0800)]
[PATCH] md: Move the test in preferred_minor to where it is used.
From: NeilBrown <neilb@cse.unsw.edu.au>
A RAID superblock can indicate which minor number the array should be
assembled under. As this is only meaningful when doing auto-start, we move
the test for it being in the valid range to the place where auto-start
happens. When an array is started any other way, it doesn't matter what
value is here.
Andrew Morton [Wed, 4 Feb 2004 02:43:53 +0000 (18:43 -0800)]
[PATCH] Fix deep stack usage in ncpfs
From: Petr Vandrovec <vandrove@vc.cvut.cz>
Arjan van de Ven pointed out to me there are no checks on name component
lengths in ncpfs, so potentially 4KB regions could be allocated on stack,
leading to the user controlled stack overflow.
It was using variable-sized arrays, so this snuck past the static
stack-usage checking tools.
As NCP is limited to 255 bytes on components, we can simple limit these
local variables to 256 bytes, and after this stack usage looks more
acceptable. Length checking occurs inside ncp_vol2io, during
iocharset->codepage conversion.
As a side effect support for multibyte codepages now works as it should,
instead of returning -EINVAL whenever filename in 'codepage' encoding was
longer than in 'iocharset'.
Other part fixes typo where atime change updated ctime and not atime field.
Andrew Morton [Wed, 4 Feb 2004 02:43:35 +0000 (18:43 -0800)]
[PATCH] initialise cpu_vm_mask in init_mm
From: Anton Blanchard <anton@samba.org>
Some architectures use cpu_vm_mask to optimise TLB flushes. On ppc64 we
are now using a common flush infrastructure that handles both userspace and
kernelspace (vmalloc) pages. In order to avoid triggering this
optimisation we need to mark the init mm as having scheduled on all cpus.
Things currently work by luck (we check for the cpu only having run on the
local cpu, and the field is initialised to 0), but it would be safer to
initialise it CPU_MASK_ALL.
Andrew Morton [Wed, 4 Feb 2004 02:43:18 +0000 (18:43 -0800)]
[PATCH] remove valid_addr_bitmap
From: William Lee Irwin III <wli@holomorphy.com>
->valid_addr_bitmap is initialized nowhere. Any kern_addr_valid() testing
it returns 0 unconditionally.
This patch converts kern_addr_valid() implementations using it to return 0
as per the above and removes it from structures and zone initialization.
Untested (not even compiletested), though a similar patch also nuking
d_validate() was in use in -wli for several months.
Andrew Morton [Wed, 4 Feb 2004 02:43:00 +0000 (18:43 -0800)]
[PATCH] fix blockdev --getro for sr, sd, ide-floppy
From: John McKell <mckellj@iomega.com>
This 2.6.1 patch works by setting gendisk->policy to the correct value
during initialization as the various drivers decide whether or not the disk
is writeable. This patch persuades "blockdev --getro ..." to correctly
report the read-only state of a newly inserted disk. This patch applies to
sr.c, sd.c and ide-floppy.c. ide-cd.c already has this functionality built
into it.
Using an Iomega Zip drive as the test case...
Without the patch, I always see:
$ sudo blockdev --getro /dev/sda
0
$
That's only correct for writeable disks though. Only when the patch
is applied do I see a write-protected disk described correctly:
Andrew Morton [Wed, 4 Feb 2004 02:42:42 +0000 (18:42 -0800)]
[PATCH] Make naming of parititions in sysfs match /proc/partitions.
From: Neil Brown <neilb@cse.unsw.edu.au>
In fs/partitions/check.c there are two pieces of code that add a
partition number to a block-device name:
- the 'disk_name' function
- a snprintf in add_partitions.
'disk_name' inserts a 'p' before the partition number if the device
name ends with a digit. The snprintf in add_partitions doesn't.
This patch rectifies this anomoly so that names in sysfs can be
parsed more reliably.
This has been extensively discussed. It will probably break the external
`iostat' tool. But only for disks whose name ends in a digit, which appears
to be only DAC960.
Andrew Morton [Wed, 4 Feb 2004 02:41:50 +0000 (18:41 -0800)]
[PATCH] vmalloc address offset fix
From: Anton Blanchard <anton@samba.org>
Paul wrote a patch to use some of the rmap infrastructure to flush TLB
entries on ppc64. When testing it we found a problem in vmalloc where it
sets up the pte -> address mapping incorrectly. We clear the top bits of
the address but then forget to pass in the full address to
pte_alloc_kernel. The end result is the address in page->index is
truncated.
I fixed it in a similar way to how zeromap_pmd_range etc does it. I'm
guessing no one uses the rmap hooks on vmalloc pages yet, so havent seen
this problem.
Andrew Morton [Wed, 4 Feb 2004 02:41:41 +0000 (18:41 -0800)]
[PATCH] Allow software_suspend to fail
From: Pavel Machek <pavel@ucw.cz>
software_suspend() can fail for quite a lot of reasons (for example not
enough swapspace). However current interface returned void, so you could
not propagate error back to userland. This fixes it. Plus
__read_suspend_image() is only done during init time, so we might as well
mark it __init.
Andrew Morton [Wed, 4 Feb 2004 02:41:31 +0000 (18:41 -0800)]
[PATCH] Trivial cleanups for swsusp
From: Pavel Machek <pavel@ucw.cz>
This kills unused part of struct and fixes spelling.
It also fixes codingstyle a bit, converts "can not happen" panic into BUG_ON
(fill_suspend_header() allocates no memory so panic is meaningless) and adds
check for sizeof (struct link) [if that is not PAGE_SIZE, we have *bad*
problem, better check early].
Andrew Morton [Wed, 4 Feb 2004 02:41:10 +0000 (18:41 -0800)]
[PATCH] EDD: read disk80 MBR signature, export through edd module
From: Matt Domsch <Matt_Domsch@dell.com>
There are 4 bytes in the MSDOS master boot record, at offset 0x1b8,
which may contain a per-system-unique signature. By first writing a unique
signature to each disk in the system, then rebooting, and then reading the
MBR to get the signature for the boot disk (int13 dev 80h), userspace may
use it to compare against disks it knows as named /dev/[hs]d[a-z], and thus
determine which disk is the BIOS boot disk, thus where the /boot, / and
boot loaders should be placed.
This is useful in the case where the BIOS is not EDD3.0 compliant, thus
doesn't provide the PCI bus/dev/fn and IDE/SCSI location of the boot disk,
yet you need to know which disk is the boot disk. It's most useful in OS
installers.
This patch retrieves the signature from the disk in setup.S, stores it in a
space reserved in the empty_zero_page, copies it somewhere safe in setup.c,
and exports it via /sys/firmware/edd/int13_disk80/mbr_signature in edd.c.
Code is covered under CONFIG_EDD=[ym].
Andrew Morton [Wed, 4 Feb 2004 02:40:32 +0000 (18:40 -0800)]
[PATCH] add readX_relaxed() interface
From: jbarnes@sgi.com (Jesse Barnes)
Here's the patch to add the new _relaxed variants for PIO read accesses.
It's been ack'd by gregkh and Grant Grundler, and I think it's ready to
go.
PCI ordering rules also guarantee that PIO read responses arrive after any
outstanding DMA writes on that bus, since for some devices the result of a
readb() call may signal to the driver that a DMA transaction is complete. In
many cases, however, the driver may want to indicate that the next readb()
call has no relation to any previous DMA writes performed by the device. The
driver can use the readb_relaxed() for these cases, although only some
platforms will honor the relaxed semantics.
Andrew Morton [Wed, 4 Feb 2004 02:40:05 +0000 (18:40 -0800)]
[PATCH] bitmap parsing/printing routines, version 4
From: Joe Korty <joe.korty@ccur.com>
1) the version in 2.6.1 is broken, doesn't work on 64bit big endian
machines at all. This needed fixing. I thought it best to fix by
rewriting the printer/parser with an algorithm that is naturally endian &
sizeof(long) resistant.
2) I wanted all digits to print, eg, 0000ffff,00000004 not ffff,4.
3) I wanted exactly NR_CPUS bits to print (or whatever the bitmap size is
in bits, and not have what is displayed rounded up to the nearest full
byte, as the current version did.
4) The bitmap printer and parser should be part of bitmap.[ch] with syntax
and semantics to match. The original lib/mask.c versions did not
recognize this commonality.
Andrew Morton [Wed, 4 Feb 2004 02:39:47 +0000 (18:39 -0800)]
[PATCH] gcc-3.5: arch/i386/kernel/traps.c
++nmi_count(cpu);
arch/i386/kernel/traps.c: In function `do_nmi':
arch/i386/kernel/traps.c:552: error: invalid lvalue in increment
and
include/linux/netdevice.h: In function `__netif_rx_schedule':
include/linux/netdevice.h:818: error: invalid lvalue in assignment
include/linux/netdevice.h: In function `netif_rx_reschedule':
include/linux/netdevice.h:842: error: invalid lvalue in assignment
This fix will probably reintroduce unused variable warnings...
Andrew Morton [Wed, 4 Feb 2004 02:39:30 +0000 (18:39 -0800)]
[PATCH] gcc-3.5: drivers/video/cfbimgblt.c
drivers/video/cfbimgblt.c: In function `color_imageblit':
drivers/video/cfbimgblt.c:140: error: invalid lvalue in assignment
drivers/video/cfbimgblt.c: In function `slow_imageblit':
drivers/video/cfbimgblt.c:206: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:39:20 +0000 (18:39 -0800)]
[PATCH] gcc-3.5: drivers/video/riva/fbdev.c
drivers/video/riva/fbdev.c: In function `rivafb_load_cursor_image':
drivers/video/riva/fbdev.c:498: error: invalid lvalue in increment
drivers/video/riva/fbdev.c:499: error: invalid lvalue in increment
drivers/video/riva/fbdev.c: In function `rivafb_imageblit':
drivers/video/riva/fbdev.c:1440: error: invalid lvalue in increment
drivers/video/riva/fbdev.c:1449: error: invalid lvalue in increment
Andrew Morton [Wed, 4 Feb 2004 02:38:45 +0000 (18:38 -0800)]
[PATCH] gcc-3.5: advansys.c
drivers/scsi/advansys.c: In function `advansys_reset':
drivers/scsi/advansys.c:6022: error: invalid lvalue in assignment
drivers/scsi/advansys.c:6045: error: invalid lvalue in assignment
drivers/scsi/advansys.c: In function `advansys_interrupt':
drivers/scsi/advansys.c:6314: error: invalid lvalue in assignment
drivers/scsi/advansys.c: In function `asc_scsi_done_list':
drivers/scsi/advansys.c:6386: error: invalid lvalue in assignment
drivers/scsi/advansys.c: In function `asc_enqueue':
drivers/scsi/advansys.c:7437: error: invalid lvalue in assignment
drivers/scsi/advansys.c:7445: error: invalid lvalue in assignment
drivers/scsi/advansys.c:7448: error: invalid lvalue in assignment
drivers/scsi/advansys.c: In function `asc_dequeue_list':
drivers/scsi/advansys.c:7569: error: invalid lvalue in assignment
drivers/scsi/advansys.c: In function `asc_rmqueue':
drivers/scsi/advansys.c:7647: error: invalid lvalue in assignment
drivers/scsi/advansys.c:7648: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:38:36 +0000 (18:38 -0800)]
[PATCH] gcc-3.5: drivers/scsi/53c700
In file included from drivers/scsi/53c700.c:140:
drivers/scsi/53c700.h: In function `NCR_700_set_SXFER':
drivers/scsi/53c700.h:106: error: invalid lvalue in assignment
drivers/scsi/53c700.h:107: error: invalid lvalue in assignment
drivers/scsi/53c700.h: In function `NCR_700_set_depth':
drivers/scsi/53c700.h:116: error: invalid lvalue in assignment
drivers/scsi/53c700.h:117: error: invalid lvalue in assignment
drivers/scsi/53c700.h: In function `NCR_700_set_flag':
drivers/scsi/53c700.h:137: error: invalid lvalue in assignment
drivers/scsi/53c700.h: In function `NCR_700_clear_flag':
drivers/scsi/53c700.h:142: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:38:09 +0000 (18:38 -0800)]
[PATCH] gcc-3.5: PCMCIA
include/pcmcia/mem_op.h: In function `copy_from_pc':
include/pcmcia/mem_op.h:85: error: invalid lvalue in assignment
include/pcmcia/mem_op.h:85: error: invalid lvalue in assignment
include/pcmcia/mem_op.h: In function `copy_to_pc':
include/pcmcia/mem_op.h:97: error: invalid lvalue in assignment
include/pcmcia/mem_op.h:97: error: invalid lvalue in assignment
include/pcmcia/mem_op.h: In function `copy_pc_to_user':
include/pcmcia/mem_op.h:109: error: invalid lvalue in assignment
include/pcmcia/mem_op.h:109: error: invalid lvalue in assignment
include/pcmcia/mem_op.h: In function `copy_user_to_pc':
include/pcmcia/mem_op.h:124: error: invalid lvalue in assignment
include/pcmcia/mem_op.h:124: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:38:01 +0000 (18:38 -0800)]
[PATCH] gcc-3.5: DVB
drivers/media/dvb/frontends/ves1820.c: In function `ves1820_setup_reg0':
drivers/media/dvb/frontends/ves1820.c:244: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:244: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c: In function `ves1820_attach':
drivers/media/dvb/frontends/ves1820.c:541: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:541: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:544: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:544: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:545: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:545: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:546: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:546: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:547: error: invalid lvalue in assignment
drivers/media/dvb/frontends/ves1820.c:547: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:36:59 +0000 (18:36 -0800)]
[PATCH] gcc-3.5: drivers/atm/he.c
drivers/atm/he.c: In function `he_init_one':
drivers/atm/he.c:383: error: invalid lvalue in assignment
drivers/atm/he.c: In function `he_open':
drivers/atm/he.c:2364: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:36:50 +0000 (18:36 -0800)]
[PATCH] gcc-3.5: drivers/atm/idt77105.c
drivers/atm/idt77105.c: In function `idt77105_start':
drivers/atm/idt77105.c:268: error: invalid lvalue in assignment
drivers/atm/idt77105.c: In function `idt77105_stop':
drivers/atm/idt77105.c:346: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:36:41 +0000 (18:36 -0800)]
[PATCH] gcc-3.5: drivers/atm/eni.c
drivers/atm/eni.c: In function `eni_close':
drivers/atm/eni.c:1878: error: invalid lvalue in assignment
drivers/atm/eni.c: In function `eni_open':
drivers/atm/eni.c:1894: error: invalid lvalue in assignment
drivers/atm/eni.c:1905: error: invalid lvalue in assignment
drivers/atm/eni.c: In function `eni_init_one':
drivers/atm/eni.c:2233: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:36:23 +0000 (18:36 -0800)]
[PATCH] gcc-3.5: drivers/atm/fore200e.c
drivers/atm/fore200e.c: In function `fore200e_open':
drivers/atm/fore200e.c:1420: error: invalid lvalue in assignment
drivers/atm/fore200e.c: In function `fore200e_register':
drivers/atm/fore200e.c:2485: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:36:05 +0000 (18:36 -0800)]
[PATCH] gcc-3.5: iphase.c
drivers/atm/iphase.c: In function `open_tx':
drivers/atm/iphase.c:1757: error: invalid lvalue in assignment
drivers/atm/iphase.c: In function `ia_close':
drivers/atm/iphase.c:2674: error: invalid lvalue in assignment
drivers/atm/iphase.c: In function `ia_open':
drivers/atm/iphase.c:2687: error: invalid lvalue in assignment
drivers/atm/iphase.c:2703: error: invalid lvalue in assignment
drivers/atm/iphase.c: In function `ia_init_one':
drivers/atm/iphase.c:3199: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:35:56 +0000 (18:35 -0800)]
[PATCH] gcc-3.5: intermezzo
fs/intermezzo/dir.c: In function `presto_prep':
fs/intermezzo/intermezzo_fs.h:414: sorry, unimplemented: inlining failed in call to 'presto_is_read_only': function body not available
fs/intermezzo/presto.c: In function `izo_mark_cache':
fs/intermezzo/presto.c:341: error: invalid lvalue in assignment
fs/intermezzo/presto.c:342: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:35:28 +0000 (18:35 -0800)]
[PATCH] gcc-3.5: vxfs fixes
fs/freevxfs/vxfs.h:33:10: warning: extra tokens at end of #ident directive
fs/freevxfs/vxfs_extern.h:75: sorry, unimplemented: inlining failed in call to 'vxfs_put_page': function body not available
Andrew Morton [Wed, 4 Feb 2004 02:35:18 +0000 (18:35 -0800)]
[PATCH] gcc-3.5: zatm.c fix
drivers/atm/zatm.c: In function `zatm_close':
drivers/atm/zatm.c:1371: error: invalid lvalue in assignment
drivers/atm/zatm.c: In function `zatm_open':
drivers/atm/zatm.c:1386: error: invalid lvalue in assignment
drivers/atm/zatm.c:1398: error: invalid lvalue in assignment
drivers/atm/zatm.c: In function `zatm_module_init':
drivers/atm/zatm.c:1600: error: invalid lvalue in assignment
Andrew Morton [Wed, 4 Feb 2004 02:34:51 +0000 (18:34 -0800)]
[PATCH] gcc-3.5: i810_accel fix
drivers/video/i810/i810_accel.c: In function `i810fb_init_ringbuffer':
drivers/video/i810/i810_accel.c:30: sorry, unimplemented: inlining failed in call to 'flush_cache': function body not available
Andrew Morton [Wed, 4 Feb 2004 02:34:42 +0000 (18:34 -0800)]
[PATCH] gcc-3.5: parport warnings
drivers/pnp/pnpbios/core.c: In function `pnpbios_probe_system':
drivers/pnp/pnpbios/core.c:438: warning: use of cast expressions as lvalues is deprecated
Andrew Morton [Wed, 4 Feb 2004 02:34:33 +0000 (18:34 -0800)]
[PATCH] gcc-3.5: sound/core/seq/seq_clientmgr.c
sound/core/seq/seq_clientmgr.c: In function `snd_seq_open':
sound/core/seq/seq_clientmgr.c:331: warning: use of cast expressions as lvalues is deprecated
Andrew Morton [Wed, 4 Feb 2004 02:34:24 +0000 (18:34 -0800)]
[PATCH] More 3.4 compilation fixes
From: Jan Hubicka <jh@suse.cz>
GCC now converts sprintf (a,"%s",b) to strcpy. This lose on kernel as
strcpy is not inlined and not present in library, so one gets linker
failure. It seems to make sense to apply this optimization by hand.
Andrew Morton [Wed, 4 Feb 2004 02:34:15 +0000 (18:34 -0800)]
[PATCH] Fix inlining failure (all GCCs) in parport
From: Jan Hubicka <jh@suse.cz>
GCC never inline extern inline function redefined by new body (because it is
not clear what body one should choose)
parport contains such duplicated functions for apparently no good reasons.
Both copies differ slightly, not sure whether it is intentional or just
garbage.
projects / linux / log