On Thu, 3 May 2007 13:34:29 +0800 WANG Cong <[EMAIL PROTECTED]> wrote:
>
> Fix this warning:
> drivers/usb/misc/sisusbvga/sisusb_con.c:1436: warning: initialization from
> incompatible pointer type
>
>
> Signed-off-by: WANG Cong <[EMAIL PROTECTED]>
> ---
>
> Compiling test past.;)
>
On Wed, May 02, 2007 at 06:56:09PM -0700, Jeremy Fitzhardinge wrote:
> This fixes two bugs:
> - the stack allocation must be marked __cpuinit, since it gets called
>on resume as well.
> - presumably the interrupt stack should be freed on unplug if its
>going to get reallocated on every
On Thu, May 03, 2007 at 02:20:32PM +1000, Rusty Russell wrote:
>On Thu, 2007-05-03 at 11:57 +0800, WANG Cong wrote:
>> On Thu, May 03, 2007 at 09:00:48AM +1000, Rusty Russell wrote:
>> >Thanks for the patch. This omission (in several places) was
>> >deliberate. We can't really do anything
Fix this warning:
drivers/usb/misc/sisusbvga/sisusb_con.c:1436: warning: initialization from
incompatible pointer type
Signed-off-by: WANG Cong <[EMAIL PROTECTED]>
---
Compiling test past.;)
--- linux-2.6.21-rc7-mm2/drivers/usb/misc/sisusbvga/sisusb_con.c.orig
2007-05-03
From: Randy Dunlap <[EMAIL PROTECTED]>
librs docbook typo fixes.
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
---
Documentation/DocBook/librs.tmpl | 16
1 file changed, 8 insertions(+), 8 deletions(-)
--- linux-2621-g4.orig/Documentation/DocBook/librs.tmpl
+++
On Sunday 18 February 2007 02:04, Dmitry Torokhov wrote:
> Hi Linus,
>
> Please consider pulling from:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
>
> or
> master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
>
> to receive updates
On Wednesday 02 May 2007 18:49, Mike Frysinger wrote:
> uinput.h relies on structures only found in input.h, so pull in the header
>
> Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
> ---
> diff --git a/include/linux/uinput.h b/include/linux/uinput.h
> index 1fd61ee..a6c1e8e 100644
> ---
From: Tony Breeds <[EMAIL PROTECTED]>
[LGUEST] Look in object dir for .config
If you build with make O= then .config isn't in ../../, this patch
goes partway to making sure that you don't dirty the source tree.
Signed-off-by: Tony Breeds <[EMAIL PROTECTED]>
---
On Wed, May 02, 2007 at 02:59:11PM -0700, H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
> >
> > So the bzImage structure is currently:
> >
> >1. old-style boot sector
> >2. old-style boot info, followed by 0xaa55 at the end of the sector
> >3. the HdrS boot param block
> >4.
William Lee Irwin III wrote:
>> That's odd. The ->load_weight changes should've improved that quite
>> a bit. There may be something slightly off in how lag is computed,
>> or maybe the O(n) lag issue Ying Tang spotted is biting you.
On Thu, May 03, 2007 at 06:51:43AM +0300, Al Boldi wrote:
> Is
On Tue, 1 May 2007 02:10:34 +0200 (CEST) Roman Zippel <[EMAIL PROTECTED]> wrote:
> This finally renames the thread_info field in task structure to stack,
> so that the assumptions about this field are gone and archs have more
> freedom about placing the thread_info structure.
It's been a year or
Chuck Ebbert wrote:
CONFIG_HPET_EMULATE_RTC=y
Did you try without that?
Just did. Still hangs same way; strace shows /sbin/hwclock dying after
hundreds of RTC_RD_TIME. And now /proc/interrupts shows no rtc
interrupts being generated (expected, I gues). Seems to take longer
On Thu, May 03, 2007 at 12:43:43AM +0200, Christian Hesse wrote:
> Hi James, hi everybody,
>
> playing with iwlwifi I try to patch it into the kernel and to build it from
> there. But I have a problem with the build system.
>
> The file drivers/net/wireless/mac80211/Makefile contains one single
This week's special:
--
- New Database : American Chiropractor's Offices -
--
Fields: Chiropractor/Clinic Name, Postal Address, Phone, Fax, Email and Website
Date Created: Apr 5, 2007
Format: MS
On Mon, 30 Apr 2007 16:48:29 -0600 dann frazier <[EMAIL PROTECTED]> wrote:
> hey,
> I noticed that the moxa input checking security bug described by
> CVE-2005-0504 appears to remain unfixed upstream.
>
> The issue is described here:
>
On Thu, 2007-05-03 at 11:57 +0800, WANG Cong wrote:
> On Thu, May 03, 2007 at 09:00:48AM +1000, Rusty Russell wrote:
> > Thanks for the patch. This omission (in several places) was
> >deliberate. We can't really do anything sensible if the user unmapped
> >the page. I assume you saw a gcc
The last several kernels I have built all have the following warning in them:
WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from
.text between 'is386'
(at offset 0xc0401171) and 'check_x87'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text
The last several kernels I have built all have the following warning in them:
WARNING: vmlinux - Section mismatch: reference to .init.text:start_kernel from
.text between 'is386'
(at offset 0xc0401171) and 'check_x87'
WARNING: vmlinux - Section mismatch: reference to .init.text: from .text
On Thu, May 03, 2007 at 01:01:08AM +0200, Stefan Richter wrote:
> Christoph Hellwig wrote:
> >> +fw-core-objs := fw-card.o fw-topology.o fw-transaction.o fw-iso.o \
> >> + fw-device.o fw-cdev.o
> >
> > fw-core-y += ..
> >
>
> Like such?
Yes - the latter is much more readable.
Sam
>
From: Tim Hockin <[EMAIL PROTECTED]>
Background:
/dev/mcelog is typically polled manually. This is less than optimal for
situations where accurate accounting of MCEs is important. Calling
poll() on /dev/mcelog does not work.
Description:
This patch adds support for poll() to /dev/mcelog.
On Thu, May 03, 2007 at 09:00:48AM +1000, Rusty Russell wrote:
>On Thu, 2007-05-03 at 03:33 +0800, WANG Cong wrote:
>> Hi Rusty!
>>
>> I found you forgot to check the return value of copy_from_user, and
>> here is the fix for drivers/lguest/interrupts_and_traps.c.
>>
>> Signed-off-by: WANG Cong
William Lee Irwin III wrote:
> Con Kolivas wrote:
> >> Looks good, thanks. Ingo's been hard at work since then and has v8 out
> >> by now. SD has not changed so you wouldn't need to do the whole lot of
> >> tests on SD again unless you don't trust some of the results.
>
> On Thu, May 03, 2007 at
On 5/1/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
Fair enough, it is a bit of an ugly thing. And I see no measurements there
on what the overall speedup was for any workload.
Ken, which memory model was in use? sparsemem?
discontigmem with config_numa on.
-
To unsubscribe from this list:
David Chinner wrote:
> On Tue, May 01, 2007 at 01:43:18PM -0700, Cabot, Mason B wrote:
> > I've been testing the NAS performance of ext3/Openfiler 2.2 against
> > NTFS/WinXP and have found that NTFS significantly outperforms ext3 for
> > video workloads. The Windows CIFS client will attempt a
Robert P. J. Day wrote:
> again, this list contains some CONFIG_ variables that aren't
> technically dead, but *really* should be renamed to not be confused
> with Kconfig variables. there are, however, legitimately dead ones in
> the following in places:
Please post to netdev for networking
On Wed, May 02, 2007 at 11:06:34PM +0530, Srivatsa Vaddagiri wrote:
There is also p->wait_runtime which is taken into account when
calculating p->fair_key. So if p3 had waiting in runqueue for long
before, it can get to run quicker than 10ms later.
Virtual time is time from the
Li, Tong N wrote:
Thanks for the excellent explanation. I think EEVDF and many algs alike
assume global ordering of all tasks in the system (based on virtual
time), whereas CFS does so locally on each processor and relies on load
balancing to achieve fairness across processors. It'd achieve
Okay, what's this message all about,
and how do I get rid of it?
During early boot:
drivers/rtc/hctosys.c: unable to open rtc device (rtc)
My kernel .config file is attached.
Thanks
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.21.1-cfs-v8
# Wed May 2
On Wednesday 02 May 2007 18:04, Greg KH wrote:
> On Wed, May 02, 2007 at 05:03:05PM +0200, Jan Kratochvil wrote:
> > The USB_DEVICE_INTERFACE_PROTOCOL will allow to match one interface
> > protocol of vendor specific device.
> > This macro is used in patch adding support for xbox360 to xpad.c
> >
On Wednesday 02 May 2007 11:05, Jan Kratochvil wrote:
>
> +config XPAD_FF
> + default n
Please don't default to anything.
>
> +#ifdef CONFIG_XPAD_FF
> +/**
> + * xpad_irq_out
> + */
Comments are welcome when they say something...
> +static void xpad_irq_out(struct urb *urb)
> +{
On Tue, 01 May 2007 11:59:46 -0700 Chandramouli Narayanan wrote:
> EFI x86_64 build option is added to the kernel configuration.
Hi Mouli,
Can you share EFI code as much as possible among ia64, i386,
and x86_64 instead of duplicating it?
A diffstat patch summary would be Good.
(see
Hi,
As encouraged by some of you, I have started implementing EEVDF.
However, I am quite new in this area, and may not be experienced enough
to get it through quickly. The main problems, I am facing now ,is how
to treat the semantics of yeild() and yield_to(). I probably will throw
a lot
Hi Jan,
On Wednesday 02 May 2007 11:01, Jan Kratochvil wrote:
> This changes are expected to simplify further improves of this driver,
> We will need to add information if the driver is xbox360 device or not.
>
> Second option was to simply add u8 is_360, but what if we'll need to know
> if
Thomas Gleixner wrote:
..
I try to come up with something, but I'm travelling tomorrow, so it
might be not before end of week.
Thanks, Thomas.
I believe we definitely want to nail this down before 2.6.22-final,
but there's a good workaround in the interim (CONFIG_DETECT_SOFTLOCKUP=y)
and
On Wed, May 02, 2007 at 06:56:09PM -0700, Jeremy Fitzhardinge wrote:
>> +static void __cpuinit __free_irqstack(int cpu, void *stk)
>> +{
>> +int i;
>> +
>> +if (!cpu)
>> +return;
>> +
>> +unmap_vm_area(per_cpu(irqstack_area, cpu));
>> +
>> +for (i = 0; i <
Ulrich Drepper wrote:
> Andi Kleen wrote:
>> Nope. SSE3 != SSSE3. The additional S means Supplemential.
>>
>> It's probably because the few changes didn't justify a SSE4
>
> OK, the problem is that the actual sse3 bit is misnamed. According to
> Intel's docs bit 0 of ECX is "sse", the kernel
On Wed, May 02, 2007 at 06:56:09PM -0700, Jeremy Fitzhardinge wrote:
> +static void __cpuinit __free_irqstack(int cpu, void *stk)
> +{
> + int i;
> +
> + if (!cpu)
> + return;
> +
> + unmap_vm_area(per_cpu(irqstack_area, cpu));
> +
> + for (i = 0; i <
On Wed, May 02, 2007 at 08:47:13PM +0100, James Simmons wrote:
> Will we see nubus ported over to the driver model soon :-)
I think it will happen eventually. However, my first priority
personally is to get the macio code working on non-PCI macs
to get the onboard stuff onto the driver model. I
From: Randy Dunlap <[EMAIL PROTECTED]>
Fix sysfs printk format warning:
fs/sysfs/bin.c:62: warning: format '%d' expects type 'int', but argument 4 has
type 'size_t'
Signed-off-by: Randy Dunlap <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
fs/sysfs/bin.c |2
Andi Kleen wrote:
>
> I agree; that code can all go.
>
> What also seems to miss are the early CPUID checks I recently added
> and which x86-64 has for some time.
>
I probably need to rebase against your tree. It makes more sense, anyway.
Either way, I just added a pretty decent framework
From: Rolf Eike Beer <[EMAIL PROTECTED]>
Above and below we talk about my_midlayer_create_something, I assume that is
also meant here.
Signed-off-by: Rolf Eike Beer <[EMAIL PROTECTED]>
Signed-off-by: Tejun Heo <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
Declaring an array of PAGE_SIZE does bad things for people running with
4k stacks...
Thanks to Tilman Schmidt for tracking this down.
Cc: Tilman Schmidt <[EMAIL PROTECTED]>
Cc: Kay Sievers <[EMAIL PROTECTED]>
Signed-off-by: Greg Kroah-Hartman <[EMAIL PROTECTED]>
---
drivers/base/core.c |7
From: Jean Delvare <[EMAIL PROTECTED]>
In platform_device_del(), we currently delete the device resources
first, then we delete the device itself. This causes a (minor) bug to
occur when one unregisters a platform device before unregistering its
platform driver, and the driver is requesting (in
Here are a bunch of PCI patches against your 2.6.21 git tree.
They contain:
- pci hotplug driver updates
- MSI reworks and cleanups to try to get the PPC MSI code merged
eventually
- removal of unneeded pci.h inclusion (the majority of all of
the
Here are some more driver core patche for 2.6.21.
They contain:
- fix a problem with blowing up the stack in ugly ways.
- compile warning fix
- documentation update
- remove 'struct subsystem' from the tree as it's pointless. It
only contained one field,
Rene Herman wrote:
>
> It also provides them as VESA modes yes.
OK, so no work needed.
-hpa
-
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
On Wed, 2007-05-02 at 14:09 -0700, H. Peter Anvin wrote:
> Jeremy Fitzhardinge wrote:
> >
> > Hm, that's unfortunate. How about an ELF file wrapped in some other
> > container, so that we can easily extract a properly formed ELF file?
> >
>
> Effectively the same thing as changing the magic
This fixes two bugs:
- the stack allocation must be marked __cpuinit, since it gets called
on resume as well.
- presumably the interrupt stack should be freed on unplug if its
going to get reallocated on every plug.
[ Only non-vmalloced stacks tested. ]
Signed-off-by: Jeremy Fitzhardinge
Hi,
I need 2 consoles for 2 individual serial ports that is registered by
register_console(). The console for the 1st serial port is registered at
first. I can see the output from the serial port #1 before the console
for the 2nd serial port is registered. However, I saw duplicated output
Hugh Dickins wrote:
On Wed, 2 May 2007, Nick Piggin wrote:
[snip]
More on-topic, since you suggest doing more within vmtruncate_range
than the filesystem: no, I'm afraid that's misdesigned, and I want
to move almost all of it into the filesystem ->truncate_range.
Because, if what
I needed to recompress some files from .bz2 to .gz so I setup a script to
do
bunzip2 -c $file.bz2 |gzip -9 >$file.gz
I expected that the two CPU heavy processes would end up on different
cpu's and spend a little time shuffling data between the two cpu's on a
system (dual core opteron)
Hi,
On Tuesday 01 May 2007 22:49, Christoph Hellwig wrote:
> Btw, is there any chance you could update m68k to use the generic
> irq code? The only architectures that don't have a conversion
> in progress are m68k, m68knommu and arm26
I haven't looked seriously into it since it was pretty much
On Wed, 2007-05-02 at 12:11 -0500, Kevin Corry wrote:
> Change the powerpc version of topology_init() from an __initcall to
> a subsys_initcall to match all other architectures.
>
> Signed-off-by: Kevin Corry <[EMAIL PROTECTED]>
>
> Index: linux-2.6.21/arch/powerpc/kernel/sysfs.c
>
On Wed, 2 May 2007, Miguel Sousa Filipe wrote:
On 5/2/07, Diego Calleja <[EMAIL PROTECTED]> wrote:
El Wed, 2 May 2007 20:18:55 +0100, "Miguel Sousa Filipe"
<[EMAIL PROTECTED]> escribió:
> I find it high irritanting having two kernel interfaces and two
> userland tools that provide the
Con Kolivas wrote:
>> Looks good, thanks. Ingo's been hard at work since then and has v8 out by
>> now. SD has not changed so you wouldn't need to do the whole lot of tests
>> on SD again unless you don't trust some of the results.
On Thu, May 03, 2007 at 02:11:39AM +0300, Al Boldi wrote:
> Well,
Hi.
Just to let anyone interested know, an updated PS3 Linux
Distributor's Starter Kit (v1.3) was released.
The release note is here:
http://www.kernel.org/pub/linux/kernel/people/geoff/cell/CELL-Linux-CL_20070425-ADDON/README-e.txt
And the CD-ROM iso image is here (238 MiB):
Kritian wrote:
> Olaf Hering wrote:
> > On Tue, May 01, Kristian H?gsberg wrote:
> >
> >> drivers/firewire/Kconfig | 60 ++
> >
> > NACK.
> > Upgrade the current drivers/ieee1394/ with the new code, and keep all
> > existing module names.
>
> What's your reasoning here? Having
Hugh Dickins wrote:
On Wed, 2 May 2007, Nick Piggin wrote:
Yes, but IIRC I put that in because there was another check in
SLES9 that I actually couldn't put in, but used this one instead
because it also caught the bug we saw.
...
This was actually a rare corruption that is also in 2.6.21, and
On Wed, May 02, 2007 at 03:46:21PM -0400, Chris Mason wrote:
> On Thu, May 03, 2007 at 01:44:14AM +1000, David Chinner wrote:
> > On Tue, May 01, 2007 at 01:43:18PM -0700, Cabot, Mason B wrote:
> > > Hello all,
> > >
> > > I've been testing the NAS performance of ext3/Openfiler 2.2 against
> > >
Christoph Hellwig wrote:
+ for (i = 0; i < buffer->page_count; i++) {
+ buffer->pages[i] = alloc_page(GFP_KERNEL | GFP_DMA32 |
__GFP_ZERO);
+ if (buffer->pages[i] == NULL)
+ goto out_pages;
+
+ address =
Chuck Ebbert wrote:
Well, turns out this is a heisenbug. Which is good, since it means the
nop patch didn't change anything.
Try leaving the spinlocks and just disabling the callbacks. And maybe
enable spinlock debugging...
I tried removing all the spinlocks inside the interrupt
Newer version coming in a while. Testing.
On 4/30/07, Tim Hockin <[EMAIL PROTECTED]> wrote:
From: Tim Hockin <[EMAIL PROTECTED]>
Background:
/dev/mcelog is typically polled manually. This is less than optimal for
situations where accurate accounting of MCEs is important. Calling
poll()
On Wednesday, May 2, 2007 4:45 pm Robert Hancock wrote:
> Jesse Barnes wrote:
> > On Wednesday, May 2, 2007 7:34 am Robert Hancock wrote:
> >> Jesse Barnes wrote:
> >>> On Tuesday, May 01, 2007, Jesse Barnes wrote:
> > I'm testing it now on my 965...
>
> Bah... nevermind Robert, I
Jesse Barnes wrote:
On Wednesday, May 2, 2007 7:34 am Robert Hancock wrote:
Jesse Barnes wrote:
On Tuesday, May 01, 2007, Jesse Barnes wrote:
I'm testing it now on my 965...
Bah... nevermind Robert, I see you're doing this already in
pci_mmcfg_reject_broken. I'm about to reboot & test now.
Srivatsa Vaddagiri wrote:
I briefly went thr' the paper and my impression is it expect each task
to specify the length of each new request it initiates. Is that correct?
No, the timeslice l_i here serves as a granularity control w.r.t
responsiveness (or latency depends on how you interpret
On Thu, 3 May 2007 00:00:28 +0200 Hans-Jürgen Koch wrote:
> Am Mittwoch 02 Mai 2007 schrieb Randy Dunlap:
> > On Wed, 2 May 2007 10:41:35 +0200 Hans-Jürgen Koch wrote:
> > > Am Mittwoch 02 Mai 2007 01:42 schrieb Randy Dunlap:
> > > > > +The Userspace I/O HOWTO
> > > >
> > > > Most of this reads
On Wed, 2007-05-02 at 15:44 -0700, David Miller wrote:
>
> Chrstopher, I really really would like you to post these patches early
> and often to [EMAIL PROTECTED] especially because you are
> touching the TCP code.
You're right, I should have sent this to netdev as well. I'm Sorry.
As for
On 05/03/2007 12:59 AM, H. Peter Anvin wrote:
Rene Herman wrote:
Checking here, and mine also has 132x25 as BIOS mode 0x14 in addition to
0x55. Probably also not universal, and 0x54 (132x43) doesn't seem to be
repeated. Unfortunate that Qemu/Bocks don't have the VESA text modes.
Does it
On Wed, 2 May 2007 19:11:04 -0400
Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
> > I didn't know that this was the plan.
> >
> > The problem I have with this is that once we've merged one part, we're
> > committed to merging the other parts even though we haven't seen them yet.
> >
> > What
Hi All,
This patch changes the interrupt enable sequence for the sunzilog driver
so that interrupts are not enabled untill after the interrupt handler has
been installed. If this is not done, some SS1 and SS2 sun4c systems panic
on un-handled interrupt before the handler gets installed
On Wed, 2 May 2007 16:06:35 -0700 Andrew Morton wrote:
> On Wed, 02 May 2007 15:56:48 -0700
> Randy Dunlap <[EMAIL PROTECTED]> wrote:
>
> > Andrew Morton wrote:
> > > On Wed, 2 May 2007 15:35:56 -0700
> > > Randy Dunlap <[EMAIL PROTECTED]> wrote:
> > >
> > >> From: Randy Dunlap <[EMAIL
* Andrew Morton ([EMAIL PROTECTED]) wrote:
> On Wed, 2 May 2007 16:36:27 -0400
> Mathieu Desnoyers <[EMAIL PROTECTED]> wrote:
>
> > * Christoph Hellwig ([EMAIL PROTECTED]) wrote:
> > > On Wed, May 02, 2007 at 09:47:07AM -0700, Andrew Morton wrote:
> > > > > That doesn't constitute using it.
> > >
the isdn_divertif contains kernel-only references so ive wrapped them in
__KERNEL__ and add proper #include statements
Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
---
diff --git a/include/linux/Kbuild b/include/linux/Kbuild
index 4ff0f57..ab2aaa2 100644
--- a/include/linux/Kbuild
+++
Hugh Dickins wrote:
> On Wed, 2 May 2007, Phillip Susi wrote:
> > Hugh Dickins wrote:
> > > tmpfs doesn't store its stuff in the page cache twice: that's true,
> > > and I didn't mean to imply otherwise. But tmpfs doesn't contain any
> > > support for rom memory: you'd have to copy from rom to
Con Kolivas wrote:
> On Monday 30 April 2007 18:05, Michael Gerdau wrote:
> > meanwhile I've redone my numbercrunching tests with the following
> > kernels: 2.6.21.1 (mainline)
> > 2.6.21-sd046
> > 2.6.21-cfs-v6
> > running on a dualcore x86_64.
> > [I will run the same test with
Arnd Bergmann wrote:
The same function contains a copy_from_user(), which cannot
be called with interrupts disabled, so yes, I am very certain
it will not change.
Good point.
--
Paul
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
On Wed, 02 May 2007 15:56:48 -0700
Randy Dunlap <[EMAIL PROTECTED]> wrote:
> Andrew Morton wrote:
> > On Wed, 2 May 2007 15:35:56 -0700
> > Randy Dunlap <[EMAIL PROTECTED]> wrote:
> >
> >> From: Randy Dunlap <[EMAIL PROTECTED]>
> >>
> >> Based on ace_dump_mem() from Grant Likely for the Xilinx
Eric Anholt wrote:
On Thu, 2007-04-26 at 16:55 +1000, Dave Airlie wrote:
Hi,
The patch is too big to fit on the list and I've no idea how we could
break it down further, it just happens to be a lot of new code..
H. Peter Anvin wrote:
> I don't know if that would break any programs that are currently
> bypassing the setup. The existing setup protocol definitely allows
> invoking an entry point which isn't 0x10 (rather, the 32-bit
> entrypoint is defined by code32_start); I'm not sure how Eric's
>
Christoph Hellwig wrote:
>> +fw-core-objs := fw-card.o fw-topology.o fw-transaction.o fw-iso.o \
>> +fw-device.o fw-cdev.o
>
> fw-core-y += ..
>
Like such?
--- linux.orig/drivers/usb/core/Makefile
+++ linux/drivers/usb/core/Makefile
@@ -2,17 +2,12 @@
# Makefile for USB Core files and
Thomas Gleixner wrote:
> On Wed, 2007-05-02 at 02:22 -0300, Davi Arnaut wrote:
>> plain text document attachment (pollfs-timer.patch)
>> Per file descriptor high-resolution timers. A classic unix file interface for
>> the POSIX timer_(create|settime|gettime|delete) family of functions.
>>
>>
On Thu, 2007-05-03 at 03:33 +0800, WANG Cong wrote:
> Hi Rusty!
>
> I found you forgot to check the return value of copy_from_user, and
> here is the fix for drivers/lguest/interrupts_and_traps.c.
>
> Signed-off-by: WANG Cong <[EMAIL PROTECTED]>
Hi Wang!
Thanks for the patch. This
Rene Herman wrote:
> On 05/03/2007 12:11 AM, H. Peter Anvin wrote:
>
>> The problem is to detect the ones that have it from the ones that don't.
>
> Checking here, and mine also has 132x25 as BIOS mode 0x14 in addition to
> 0x55. Probably also not universal, and 0x54 (132x43) doesn't seem to be
Zachary Amsden wrote:
> With this patch, /sbin/hwclock no longer hangs my AMD64 machine when run
> after reaching multiuser. What I don't understand is why. I have the
> RTC based sound sequencer timer as a module, but not loaded, and the
> error message I added to indicate broken rtc control
Andi Kleen wrote:
> Nope. SSE3 != SSSE3. The additional S means Supplemential.
>
> It's probably because the few changes didn't justify a SSE4
OK, the problem is that the actual sse3 bit is misnamed. According to
Intel's docs bit 0 of ECX is "sse", the kernel uses "pni". Too bad.
--
➧ Ulrich
> The old IDE driver for JMicron didn't work well for me either,
> running on Kubuntu Edgy 2.6.17. It would find the PATA DVD drive,
> and work okay for the first half of a DVD movie playback, and then go bonkers.
"go bonkers" being ? (and did you keep any dumps of it ?)
>
> I eventually gave
Andrew Morton wrote:
On Wed, 2 May 2007 15:35:56 -0700
Randy Dunlap <[EMAIL PROTECTED]> wrote:
From: Randy Dunlap <[EMAIL PROTECTED]>
Based on ace_dump_mem() from Grant Likely for the Xilinx
SystemACE CompactFlash interface.
Add hex_dumper() to lib/hexdump.c and linux/kernel.h.
This patch
On 05/03/2007 12:11 AM, H. Peter Anvin wrote:
The problem is to detect the ones that have it from the ones that don't.
Checking here, and mine also has 132x25 as BIOS mode 0x14 in addition to
0x55. Probably also not universal, and 0x54 (132x43) doesn't seem to be
repeated. Unfortunate that
William Lee Irwin III wrote:
>> +unsigned long __kvaddr_to_paddr(unsigned long kvaddr)
>> +{
>> +if (high_memory)
>> +BUG_ON(kvaddr >= VMALLOC_START);
>> +else
>> +BUG_ON(kvaddr >= (unsigned long)__va(MAXMEM));
>> +return kvaddr - PAGE_OFFSET;
>> +}
On Wed, May
Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
---
diff --git a/include/linux/quota.h b/include/linux/quota.h
index 77db80a..6243982 100644
--- a/include/linux/quota.h
+++ b/include/linux/quota.h
@@ -44,8 +44,6 @@
typedef __kernel_uid32_t qid_t; /* Type in which we store ids in memory */
uinput.h relies on structures only found in input.h, so pull in the header
Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
---
diff --git a/include/linux/uinput.h b/include/linux/uinput.h
index 1fd61ee..a6c1e8e 100644
--- a/include/linux/uinput.h
+++ b/include/linux/uinput.h
@@ -32,6 +32,8 @@
On Thursday 03 May 2007 00:41:22 Ulrich Drepper wrote:
> Note the extra 's'. We use "sse" and "sse2", but "ssse3". I assume
> it's a typo.
Nope. SSE3 != SSSE3. The additional S means Supplemential.
It's probably because the few changes didn't justify a SSE4
-Andi
-
To unsubscribe from this
On Thursday 03 May 2007, Paul Fulghum wrote:
> >> +
> >> +spin_lock_irqsave(>lock, flags);
> >
> > no need for _irqsave, just use spin_{,un}lock_irq() when you know that
> > interrupts are enabled.
>
> That makes me a little uneasy. The locking
> mechanisms (and just about everything else)
On Wed, 2 May 2007 15:35:56 -0700
Randy Dunlap <[EMAIL PROTECTED]> wrote:
> From: Randy Dunlap <[EMAIL PROTECTED]>
>
> Based on ace_dump_mem() from Grant Likely for the Xilinx
> SystemACE CompactFlash interface.
>
> Add hex_dumper() to lib/hexdump.c and linux/kernel.h.
>
> This patch adds the
On Thursday 03 May 2007 01:41:22 Ulrich Drepper wrote:
> Note the extra 's'. We use "sse" and "sse2", but "ssse3". I assume
> it's a typo.
This might not be a typo see http://en.wikipedia.org/wiki/SSSE3
Regards,
ismail
signature.asc
Description: This is a digitally signed message part.
Andi Kleen wrote:
if (type && ei->type != type)
@@ -148,6 +178,29 @@ int __init e820_all_mapped(unsigned long
unsigned long __init find_e820_area(unsigned long start, unsigned long end, unsigned size)
{
int i;
+ if (efi_enabled) {
+ efi_memory_desc_t *md;
Please
Hi James, hi everybody,
playing with iwlwifi I try to patch it into the kernel and to build it from
there. But I have a problem with the build system.
The file drivers/net/wireless/mac80211/Makefile contains one single line:
obj-$(CONFIG_IWLWIFI) += iwlwifi/
When CONFIG_IWLWIFI=m in
Chrstopher, I really really would like you to post these patches early
and often to [EMAIL PROTECTED] especially because you are
touching the TCP code.
You aren't doing this, for several rounds, and just submitting your
stuff directly to Linus, Andrew, and lkml, and it's starting to annoy
me
Note the extra 's'. We use "sse" and "sse2", but "ssse3". I assume
it's a typo.
Signed-off-by: Ulrich Drepper <[EMAIL PROTECTED]>
--- arch/i386/kernel/cpu/proc.c 2007-02-15 11:21:18.0 -0800
+++ arch/i386/kernel/cpu/proc.c-new 2007-05-02 15:31:17.0 -0700
@@ -46,7 +46,7 @@
On Mon, 19 Mar 2007, Nicolas Boichat wrote:
Rudolf Marek wrote:
Hello all,
I'm CCing all interested parties, if some isn't please tell!
On URL bellow is current version of coretemp driver.
http://ssh.cz/~ruik/patches/
Small glitch in coretemp_init:
printk(KERN_NOTICE DRVNAME ": This
1 - 100 of 1184 matches
Mail list logo
