On Monday 05 February 2007 23:50, Siddha, Suresh B wrote:
> On Mon, Feb 05, 2007 at 06:19:59PM +0100, Andreas Herrmann wrote:
> > o added check to restrict base address to 36 bit on i386
>
> Why is this? It can go upto implemented physical bits, right?
In theory it can, but Linux doesn't support
On Monday 05 February 2007 22:35, Andrew Morton wrote:
> On Sun, 04 Feb 2007 13:39:40 -0500
> David Moore <[EMAIL PROTECTED]> wrote:
>
> > From: David Moore <[EMAIL PROTECTED]>
> >
> > Adds missing call to phys_to_virt() in the
> > lib/swiotlb.c:swiotlb_sync_sg() function. Without this change,
* Eric W. Biederman <[EMAIL PROTECTED]> wrote:
> When making the interrupt vectors per cpu I failed to handle a case
> during irq migration. If the same interrupt comes in while we are
> servicing the irq but before we migrate it the pending bit in the
> local apic IRR register will be set
On Mon, 2007-02-05 at 17:37 +0100, John wrote:
> Ingo Molnar wrote:
>
> > John wrote:
> >
> >> John Stultz wrote:
> >>
> >>> Also do check the -rt tree as Ingo suggested. I mis-read your earlier
> >>> email and thought you were running it.
> >>
> >> I've been pulling my hair over a related
Vivek Goyal <[EMAIL PROTECTED]> writes:
> On Mon, Feb 05, 2007 at 10:38:30PM -0800, H. Peter Anvin wrote:
>> Vivek Goyal wrote:
>> >
>> >That time, grub was working fine but lilo had broken on one of Andrew's
>> >machine. I could not reproduce the problem on my setup and had no clue what
>> >was
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Tue, Feb 06, 2007 at 10:28:56AM +0400, Manu Abraham wrote:
> On 2/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> >On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler
> ><[EMAIL PROTECTED]> wrote:
> >
> >> On Mon, Feb 05, 2007 at 09:55:28PM
On Tue, Feb 06, 2007 at 10:28:56AM +0400, Manu Abraham wrote:
> On 2/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
> >On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler
> ><[EMAIL PROTECTED]> wrote:
> >
> >> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> >> ...
> >> > >
Robert Hancock wrote:
>
> It looks like wbsd is being loaded first, which being a nice PnP device
> sees that IRQ 6 is available and grabs it. Then the we try to load the
> floppy module (which is hard-coded to use IRQ 6) which fails because
> wbsd already owns IRQ6 (which is fine, there's no
On Mon, Feb 05, 2007 at 10:38:30PM -0800, H. Peter Anvin wrote:
> Vivek Goyal wrote:
> >
> >That time, grub was working fine but lilo had broken on one of Andrew's
> >machine. I could not reproduce the problem on my setup and had no clue what
> >was the issue. Hence got rid of ELF header from
On Sun, Feb 04, 2007 at 07:59:47PM +0100, Pierre Ossman wrote:
> Hi Greg,
>
> Although I am a bit of a cynic, I really hope that this endeavor works
> the way you hope.
>
> I'd also like to offer my services to this quest of yours. If you get
> any SD, MMC or SDIO requests, feel free to pass
On Mon, Feb 05, 2007 at 04:24:21PM +0100, Jiri Slaby wrote:
> Greg KH napsal(a):
> >On Sun, Feb 04, 2007 at 08:08:32PM +0100, Miguel Ojeda wrote:
> >>On 2/4/07, Greg KH <[EMAIL PROTECTED]> wrote:
> >>>Just let me know if you are interested in participating, and what types
> >>>of devices you wish
Vivek Goyal wrote:
That time, grub was working fine but lilo had broken on one of Andrew's
machine. I could not reproduce the problem on my setup and had no clue what
was the issue. Hence got rid of ELF header from bzImage which was non-essential
stuff for relocatable kernel. But that issue
Gene Heskett wrote:
On Monday 05 February 2007 18:30, Jesper Juhl wrote:
And this is almost OT for this, but I'd like to interject here that in
recent history, it has been very very difficult to properly access LSN0
of a floppy. Some formats, such as those laid down by a WD-1773 floppy
On Mon, Feb 05, 2007 at 10:16:59PM -0800, H. Peter Anvin wrote:
> Vivek Goyal wrote:
> >
> >I don't know much about Gujin, but advantage here seems to be that it has
> >capability to load elf files and that's why the attempt to turn kernel
> >binary
> >into a compressed elf image. Why don't we
On 2/6/07, Andrew Morton <[EMAIL PROTECTED]> wrote:
On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> ...
> > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR-
On Mon, Feb 05, 2007 at 10:03:31PM -0700, Grant Grundler wrote:
> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> ...
> > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > > Stepping- SERR- FastB2B-
> > > Status: Cap- 66MHz- UDF- FastB2B- ParErr-
On Mon, Feb 05, 2007 at 08:09:58PM -0500, Theodore Tso wrote:
> On Mon, Feb 05, 2007 at 11:21:34PM +, David Woodhouse wrote:
> > But Alan makes a reasonable suggestion -- we could work around this in
> > the tools too.
>
> I wouldn't call it "work around this" in the tools. It's a useful
>
Vivek Goyal wrote:
I don't know much about Gujin, but advantage here seems to be that it has
capability to load elf files and that's why the attempt to turn kernel binary
into a compressed elf image. Why don't we then simply add an ELF header to
bzImage and Gujin and any ELF loader including
On Monday 05 February 2007 18:30, Jesper Juhl wrote:
And this is almost OT for this, but I'd like to interject here that in
recent history, it has been very very difficult to properly access LSN0
of a floppy. Some formats, such as those laid down by a WD-1773 floppy
controller, do indeed use
On Mon, Feb 05, 2007 at 09:17:52PM +, David Woodhouse wrote:
> On Mon, 2007-02-05 at 08:58 -0800, Linus Torvalds wrote:
> > More importantly, some things that *are* visible probably shouldn't be, or
> > should perhaps only be in expert mode (aka "EMBEDDED").
>
> I've heard some fairly stupid
On Thu, 2007-02-01 at 13:12 +0300, Evgeniy Polyakov wrote:
> Generic event handling mechanism.
The patch applied cleanly to 2.6.20 final, but I got a build error:
CC kernel/kevent/kevent.o
CC kernel/kevent/kevent_user.o
CC kernel/kevent/kevent_timer.o
CC
On Mon, Feb 05, 2007 at 09:40:08PM +0100, Jan Engelhardt wrote:
>
> On Feb 5 2007 18:32, Christoph Hellwig wrote:
> >
> >in two recent discussions (file_list_lock scalability and remount r/o
> >on suspend) I stumbled over this emergency remount feature. It's not
> >actually useful because it
On Tue, Feb 06, 2007 at 06:49:05AM +0100, Nick Piggin wrote:
> > - If the get_user() doesn't fault, and if we're copying from and to the
> > same page, we know that we've locked it, so nobody will be able to unmap
> > it while we're copying from it.
> >
> > Close, but no cigar! This is still
On Mon, Feb 05, 2007 at 09:30:06PM -0800, Andrew Morton wrote:
> On Tue, 6 Feb 2007 05:41:46 +0100 Nick Piggin <[EMAIL PROTECTED]> wrote:
> > >
> > > Not necessarily -- they could read from one part of a page and write to
> > > another. I see this as the biggest data corruption problem.
>
> The
On Mon, 5 Feb 2007 22:03:31 -0700 Grant Grundler <[EMAIL PROTECTED]> wrote:
> On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
> ...
> > > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > > Stepping- SERR- FastB2B-
> > > Status: Cap- 66MHz- UDF- FastB2B-
On Tue, 6 Feb 2007 05:41:46 +0100 Nick Piggin <[EMAIL PROTECTED]> wrote:
> On Tue, Feb 06, 2007 at 03:25:49AM +0100, Nick Piggin wrote:
> > On Sun, Feb 04, 2007 at 10:36:20AM -0800, Andrew Morton wrote:
> > > On Sun, 4 Feb 2007 16:10:51 +0100 Nick Piggin <[EMAIL PROTECTED]> wrote:
> > >
> > > >
On Mon, Feb 05, 2007 at 04:37:43PM -0800, H. Peter Anvin wrote:
> First of all, if sending attached patches, *MAKE SURE* they're text/plain.
>
> >diff -uprN -X linux-2.6.20/Documentation/dontdiff
> >linux-2.6.20/arch/i386/kernel/setup.c
> >linux-2.6.20-gujin/arch/i386/kernel/setup.c
> >---
On Monday February 5, [EMAIL PROTECTED] wrote:
> On Mon, 05 Feb 2007 20:08:39 -0800 "Kai" <[EMAIL PROTECTED]> wrote:
>
> You hit two bugs. It seems that raid5 is submitting BIOs which are larger
> than the device can accept. In response someone (probably the block layer)
> caused a page to come
On Tue, 06 Feb 2007 16:11:16 +1100 Rusty Russell <[EMAIL PROTECTED]> wrote:
>
> Patches welcome (but note that I've started a new lguest patch repo at
> http://lguest.kernel.org/patches).
Presumably you mean lguest.ozlabs.org ...
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
On 2/6/07, Grant Grundler <[EMAIL PROTECTED]> wrote:
On Mon, Feb 05, 2007 at 05:09:01AM +0400, Manu Abraham wrote:
> Hi,
>
> I get this error on booting up 2.6.20 (Similar error on 2.6.17.7 also,
> the message is slightly different in 2.6.17.7)
>
> PCI Cannot allocate resource region 2 of device
On Mon, 2007-02-05 at 20:54 -0800, Zachary Amsden wrote:
> Rusty Russell wrote:
> > Indeed, I'm expecting to push lguest this week, and this code will
> > effect me, so I'd like to see this in a -mm soon...
>
> Yes, I took a look at the lguest changes today and I think these won't
> generate
While looking at another bug a while ago, I noticed that in 2.6 at
least, set_device_ro() sets the policy on the hd_struct to mark it
readonly, but it appears that IO is only really blocked from userspace,
via generic_write_checks().
There are bdev_read_only() checks in other places, but
On Mon, Feb 05, 2007 at 09:55:28PM -0700, Grant Grundler wrote:
...
> > Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> > Stepping- SERR- FastB2B-
> > Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> > SERR+ > Latency: 0, Cache Line Size 0c
>
On Mon, Feb 05, 2007 at 05:09:01AM +0400, Manu Abraham wrote:
> Hi,
>
> I get this error on booting up 2.6.20 (Similar error on 2.6.17.7 also,
> the message is slightly different in 2.6.17.7)
>
> PCI Cannot allocate resource region 2 of device :02:0a.0
> PCI Error while updating region
Rusty Russell wrote:
On Mon, 2007-02-05 at 19:52 -0800, Zachary Amsden wrote:
A bunch of VMI and paravirt-ops bugfixes for upstream. Also, fix the
timer code to work for 2.6.21, which had a number of changes.
These should mostly be non-controversial and beneficial to all the
paravirt-ops
On Tue, Feb 06, 2007 at 03:25:49AM +0100, Nick Piggin wrote:
> On Sun, Feb 04, 2007 at 10:36:20AM -0800, Andrew Morton wrote:
> > On Sun, 4 Feb 2007 16:10:51 +0100 Nick Piggin <[EMAIL PROTECTED]> wrote:
> >
> > > They're not likely to hit the deadlocks, either. Probability gets more
> > > likely
On Mon, 05 Feb 2007 20:08:39 -0800 "Kai" <[EMAIL PROTECTED]> wrote:
> I booted up the new kernel version, 2.6.20; I pretty much copied over my
> .config that worked in 2.6.19.2, that has worked correctly since that
> version came out... I looked through the menuconfig to see if any new
> options
On Mon, 2007-02-05 at 19:52 -0800, Zachary Amsden wrote:
> A bunch of VMI and paravirt-ops bugfixes for upstream. Also, fix the
> timer code to work for 2.6.21, which had a number of changes.
>
> These should mostly be non-controversial and beneficial to all the
> paravirt-ops work.
Indeed, I'm
Sorry I've been slow in giving you feedback on kwatch.
> I'll be happy to move this over to the utrace setting, once it is merged.
> Do you think it would be better to include the current version of kwatch
> now or to wait for utrace?
>
> Roland, is there a schedule for when you plan to get
Zachary Amsden wrote:
#include "mach_timer.h"
@@ -102,9 +103,6 @@ unsigned long long sched_clock(void)
{
unsigned long long this_offset;
- if (unlikely(custom_sched_clock))
- return (*custom_sched_clock)();
-
/*
* Fall back to jiffies if there's no
Because timer code moves around, and we might eventually move our init to a
late_time_init hook, save and restore IRQs around this code because it is
definitely not interrupt safe.
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
diff -r dd4d4324a5b3 arch/i386/kernel/vmitime.c
---
On Mon, 5 Feb 2007 12:08:29 +0100 Lukas Hejtmanek <[EMAIL PROTECTED]> wrote:
> Hello,
>
> playing with my java application that sends data into network I got the
> following oops. I got also similar oops in interrupt handler but such
> situation results in kernel panic so I'm unable to provide
Deliberate register clobber around performance critical inline code is great for
testing, bad to leave on by default. Many people ship with DEBUG_KERNEL turned
on, so stop making DEBUG_PARAVIRT default on.
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
diff -r 3a8033f42ecf
Provide a PT map hook for HIGHPTE kernels to designate where they are mapping
page tables. This information is required so the physical address of PTE
updates can be determined; otherwise, the mm layer would have to carry the
physical address all the way to each PTE modification callsite, which
Provide a paravirtualized way to get the CPU clock frequency; this allows much
of the code in tsc.c to be shared between all paravirt implementations.
Subject: Add a CPU KHZ calibration function to paravirt-ops
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
diff -r a08f195aa92a
Failure to use real-time delay here causes the keyboard to become demonically
possessed in the event of a kernel crash, with wildly blinking lights and
unpredictable behavior. This has resulted in several injuries.
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
diff -r 10fac6d484e2
Profile_pc was broken when using paravirtualization because the
assumption the kernel was running at CPL 0 was violated, causing
bad logic to read a random value off the stack.
The only way to be in kernel lock functions is to be in kernel
code, so validate that assumption explicitly by checking
Kprobes bugfix for paravirt compatibility - RPL on the CS when inserting
BPs must match running kernel.
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
CC: Eric Biederman <[EMAIL PROTECTED]>
diff -r fad1c2108c13 arch/i386/kernel/kprobes.c
--- a/arch/i386/kernel/kprobes.cFri Feb 02
The time initialization changed for i386 when some code moved into time_init.
This made it no longer possible to override the PIT / HPET, which broke
paravirt guests.
Subject: Fix PIT override bug for paravirt
Signed-off-by: Zachary Amsden <[EMAIL PROTECTED]>
diff -r acd12d5196c7
Fix the VMI-Timer no-idle-hz code.
Do not setup a one shot alarm if we are keeping the periodic alarm
armed. Additionally, since the periodic alarm can be run at a lower
rate than HZ, let's fixup the guard to the no-idle-hz mode appropriately.
This fixes the bug where the no-idle-hz mode might
diff -r 3e746c0ebcdf arch/i386/kernel/paravirt.c
--- a/arch/i386/kernel/paravirt.c Fri Feb 02 13:54:53 2007 -0800
+++ b/arch/i386/kernel/paravirt.c Fri Feb 02 15:27:50 2007 -0800
@@ -32,6 +32,7 @@
#include
#include
#include
+#include
/* nop stub */
static void
Highres timers no longer breaks with VMI turned on because the
required function is now exported even with hrtimers turned on.
Until hrtimers becomes the default for i386, we must still support
both timer modes, NO_HZ, and also NO_IDLE_HZ, which is paravirt
specific.
Signed-off-by: Zachary Amsden
A bunch of VMI and paravirt-ops bugfixes for upstream. Also, fix the
timer code to work for 2.6.21, which had a number of changes.
These should mostly be non-controversial and beneficial to all the
paravirt-ops work.
Zach <[EMAIL PROTECTED]>
-
To unsubscribe from this list: send the line
Hi folks,
Update the MAINTAINERS file change. Thanks Aubrey for pointing out this old
MAINTAINERS file.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
Documentation/blackfin/00-INDEX | 11 ++
Documentation/blackfin/Filesystems | 169 +++
On Mon, Feb 05, 2007 at 10:28:34PM -0500, Len Brown wrote:
> > On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
>
> > > >> 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
> > > >> with linux-2.6.20-rc kernels. The system reboots instead.
> > > >> I've checked
> On Tue, Jan 02, 2007 at 12:41:59AM +0100, Berthold Cogel wrote:
> > >> 'shutdown -h now' doesn't work for my system (Acer Extensa 3002 WLMi)
> > >> with linux-2.6.20-rc kernels. The system reboots instead.
> > >> I've checked linux-2.6.19.1 with an almost identical .config file
> > >>
On Monday 05 February 2007 11:02, Christoph Hellwig wrote:
> On Mon, Feb 05, 2007 at 10:58:26AM -0800, Trond Myklebust wrote:
> > On Mon, 2007-02-05 at 18:44 +, Christoph Hellwig wrote:
> > > Just FYI: Al was very opposed to the idea of passing the vfsmount to
> > > the vfs_ helpers, so you
Hi everyone,
This is the documents patch for Blackfin arch, also includes the MAINTAINERS
file change.
Thank Mike, I update this patch and regenerate it in -p1 format.
Sorry for starting a new thread, because I switch to a new email client.
Signed-off-by: Bryan Wu <[EMAIL PROTECTED]>
---
Hi everyone,
This is the serial driver supports Blackfin processors. It is designed for the
serial core framework.
Thanks Alan and Aubrey. Aubrey update the patch according Alan's review.
Sorry for start a new thread, because I change a new email client.
Signed-off-by: Bryan Wu <[EMAIL
I'm seeing this on bootup on my laptop with recent kernels (currently
2.6.20-rc6-mm3):
Floppy drive(s): fd0 is 1.44M
IRQ handler type mismatch for IRQ 6
current handler: wbsd
[] setup_irq+0x194/0x1ac
[] floppy_hardint+0x0/0xc0 [floppy]
[] request_irq+0x7c/0x98
[] init_module+0x546/0xe15
On Mon, 05 Feb 2007 20:55:35 -0600 Robert Hancock <[EMAIL PROTECTED]> wrote:
> Seeing these BUGs on 2.6.20-rc6-mm3 when mounting an NTFS partition. I
> saw some reports of something like this on -mm1, was this supposed to be
> patched already?
>
> BUG: at arch/i386/mm/highmem.c:52
Dear Igmar Palsenberg,
I can not make sure it is hardware problem, but I have interest in this
case's reproducing.
If you tell me your platform's construction, I will try it and give you good
solution.
Does your RAID adapter's firmware version work on 1.42?
Areca firmware had fix some
Seeing these BUGs on 2.6.20-rc6-mm3 when mounting an NTFS partition. I
saw some reports of something like this on -mm1, was this supposed to be
patched already?
BUG: at arch/i386/mm/highmem.c:52 kmap_atomic()
[] kmap_atomic+0xb4/0x1cd
[] ntfs_end_buffer_async_read+0x276/0x2db [ntfs]
[]
Hi Alan,
On 2/5/07, Alan <[EMAIL PROTECTED]> wrote:
Likewise - why this not locks ?
Other than the locking bits looks ok, although has rather a lot of ifdefs
Thanks to point it out. It should be fixed in the coming patch.
Thanks,
-Aubrey
-
To unsubscribe from this list: send the line
Dear Francois:
Thanks for your reply. I gave my idea about your questions with the the
key word "ANS_2".
If you have further questions, please raise them.
Best Regards,
Edward 2007/02/06
Francois Romieu 提到:
>許恆嘉 <[EMAIL PROTECTED]> :
>[...]
>
>
static struct pci_device_id
On Monday 05 February 2007 11:50, Chris Wright wrote:
> This kind of change (or perhaps straight to struct path) is definitely
> needed from AA.
I tried struct path; in terms of code size it doesn't seem worth it. We could
get identical code out of it as if we were passing the dentry and
On Sun, Feb 04, 2007 at 10:36:20AM -0800, Andrew Morton wrote:
> On Sun, 4 Feb 2007 16:10:51 +0100 Nick Piggin <[EMAIL PROTECTED]> wrote:
>
> > They're not likely to hit the deadlocks, either. Probability gets more
> > likely after my patch to lock the page in the fault path. But practially,
> >
On Monday 05 February 2007 10:44, Christoph Hellwig wrote:
> Looking at the actual patches I see you're lazy in a lot of places.
> Please make sure that when you introduce a vfsmount argument somewhere
> that it is _always_ passed and not just when it's conveniant. Yes, that's
> more work, but
Hi everyone,
This is the Blackfin architecture patch against Linux kernel 2.6.20, again.
As we promised, some issues are fixed in the latest release with the help from
LKML.
The blackfin-arch patch is at
On Sun, Feb 04, 2007 at 05:40:35PM +, Anton Altaparmakov wrote:
> On Sun, 4 Feb 2007, Andrew Morton wrote:
> > truncate's OK: we're holding i_mutex.
>
> How about excluding readpage() (in addition to truncate if Nick is right
> and some cases of truncate do not hold i_mutex) with an extra
On 2/5/07, Randy Dunlap <[EMAIL PROTECTED]> wrote:
I can't access this patch file. (no, don't attach it for the mailing
list)
please try this:
http://blackfin.uclinux.org/gf/download/frsrelease/25/2501/blackfin-arch-linux-2.6.20.patch
as it gets tweaked, the magic id # gets incremented :/
Resending since I didn't receive any replies on this.
Could somebody please tell me if this is planned? Is there some hardware
bug that needs to be worked around this way? Is there some problem with
the disk? Should changing controller (for example) to VIA based one help?
Or is it some bug in
On Mon, 5 Feb 2007 02:28:40 -0500 Wu, Bryan wrote:
> Hi everyone,
>
> This is the Blackfin architecture patch against Linux kernel 2.6.20,
> again. As we promised, some issues are fixed in the latest release with
> the help from lkml.
>
> The blackfin-arch patch is at
>
we don't actually use anything from asm-m68k/page.h in asm-m68k/user.h, so
don't bother including it
Signed-off-by: Mike Frysinger <[EMAIL PROTECTED]>
---
--- a/include/asm-m68k/user.h
+++ b/include/asm-m68k/user.h
@@ -1,8 +1,6 @@
#ifndef _M68K_USER_H
#define _M68K_USER_H
-#include
-
/*
Hi.
On Mon, 2007-02-05 at 19:10 -0600, hackmiester (Hunter Fuller) wrote:
> On 4 February 2007, at 07:12, Jiri Slaby wrote:
>
> >
> > Back to C!
>
> This is a bit off topic, but what does this message mean? Is it
> referring to the programming language?
It's just saying that the lowlevel
kbuild: improve option checking, Kbuild.include cleanup
GNU binutils, root users, tmpfiles, external modules ro builds must
be fixed to do the right thing now.
Cc: Roman Zippel <[EMAIL PROTECTED]>
Cc: Sam Ravnborg <[EMAIL PROTECTED]>
Cc: Horst Schirmeier <[EMAIL PROTECTED]>
Cc: Jan Beulich
scripts: replace gawk, head, bc with shell, update
Replacing overhead of using some (external) programs
instead of good old `sh'.
Cc: Roman Zippel <[EMAIL PROTECTED]>
Cc: Sam Ravnborg <[EMAIL PROTECTED]>
Cc: William Stearns <[EMAIL PROTECTED]>
Cc: Martin Schlemmer <[EMAIL PROTECTED]>
kbuild: correctly skip tilded backups in localversion files
Tildes as in path as in filenames are handled correctly now:
only files, containing tilde '~', are backups, thus are not valid.
[KJ]:
Definition of `space' was removed, scripts/Kbuild.include has one.
That definition was taken
Due to almost zer0 activity, this may be last attempt.
--
-
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/
Since my commit 8252bbb1363b7fe963a3eb6f8a36da619a6f5a65 in 2.6.20-rc1,
host devices have a dummy driver attached. Alas the driver was not
registered before use if ieee1394 was loaded with disable_nodemgr=1.
Signed-off-by: Stefan Richter <[EMAIL PROTECTED]>
---
Update: - work without extern
The /proc/interrupts timer entry is dangling a little. With PREEMPT_RT
the entry doesn't get updated ..
My system after two hours uptime,
CPU0 CPU1
0: 56 0 IO-APIC-edge timer
1: 2 0 IO-APIC-edge i8042
4: 1450
On 4 February 2007, at 07:12, Jiri Slaby wrote:
Back to C!
This is a bit off topic, but what does this message mean? Is it
referring to the programming language?
Also, when I swsusp my machine, why does it print "Linu" at the top
of the screen? Not "Linux," but "Linu..."
--
On Mon, Feb 05, 2007 at 11:21:34PM +, David Woodhouse wrote:
> But Alan makes a reasonable suggestion -- we could work around this in
> the tools too.
I wouldn't call it "work around this" in the tools. It's a useful
feature we can add in the tools for developers who aren't men enough
to
Powerpc move of_irq_to_resource from prom.h to prom_parse.c
Sorry for the lack of information, it got cut in the previous messages.
Let's start all over again :
In the powerpc architecture, of_irq_to_resource, currently sitting in
prom.h, needs irq_of_parse_and_map and NO_IRQ from
On 2/5/07, Stefan Richter <[EMAIL PROTECTED]> wrote:
It's my oversight, see patch.
Yes, this fixes things. Thanks!
--
Robert Crocombe
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, 05 Feb 2007 18:35:06 -0600
Robert Hancock <[EMAIL PROTECTED]> wrote:
> Daniel Barkalow wrote:
> > On Sun, 4 Feb 2007, Robert Hancock wrote:
> >
> >> Something's busted with forcedeth in 2.6.20-rc6-mm3 for me relative to
> >> 2.6.20-rc6. There's no errors in dmesg, but it seems no packets
On Mon, 2007-02-05 at 16:28 -0800, Carl Love wrote:
> This is the first update to the patch previously posted by Maynard
> Johnson as "PATCH 4/4. Add support to OProfile for profiling CELL".
>
> There are still a few items from the comments being discussed
> specifically how to profile the
On Mon, Feb 05, 2007 at 04:27:44PM -0800, Scot McKinley wrote:
> Finally, it is agreed that neg-errno is a much better approach for the
> return code. The threading/concurrency issues associated w/ the current
> unix errno has always been buggy area for Oracle Networking code.
As Scot
I wrote:
> @@ -1132,6 +1132,7 @@ static int __init ieee1394_init(void)
> }
> }
>
> + ret = driver_register(_mid_layer_driver);
> ret = class_register(_host_class);
> if (ret < 0)
> goto release_all_bus;
I think I make that a
From: Scot McKinley <[EMAIL PROTECTED]>
Date: Mon, 05 Feb 2007 16:27:44 -0800
> As Joel mentioned earlier, from an Oracle perspective, one of the key
> things we are looking for is a nice clean *common* wait point.
How much investigation have the Oracle folks (besides Zach :-) done
into
On Tue, 6 Feb 2007 00:28:50 +0100 Jesper Juhl wrote:
>
> This is a basic CodingStyle cleanup for drivers/block/floppy.c
>
> There are no functional changes in this patch.
>
> Signed-off-by: Jesper Juhl <[EMAIL PROTECTED]>
> ---
>
> floppy.c | 203
Mathieu Desnoyers writes:
> * Benjamin Herrenschmidt ([EMAIL PROTECTED]) wrote:
> > On Mon, 2007-02-05 at 09:29 -0500, Mathieu Desnoyers wrote:
> > > Missing include in include/asm-powerpc/prom.h
> > >
> > > include/asm-powerpc/prom.h needs to include asm/irq.h because it uses
> > >
Carl Love writes:
> This is the first update to the patch previously posted by Maynard
> Johnson as "PATCH 4/4. Add support to OProfile for profiling CELL".
Is it really necessary to keep posting all these messages to three
lists? Wouldn't cbe-oss-dev be sufficient?
Paul.
-
To unsubscribe
Hi.
On Mon, 2007-02-05 at 18:32 +0100, Christoph Hellwig wrote:
> Hi there,
>
> in two recent discussions (file_list_lock scalability and remount r/o
> on suspend) I stumbled over this emergency remount feature. It's not
> actually useful because it tries a potentially dangerous remount
>
On Monday 05 February 2007 10:44, Christoph Hellwig wrote:
> Just FYI: Al was very opposed to the idea of passing the vfsmount to
> the vfs_ helpers, so you should discuss this with him.
The vfs_ helper functions are the ones calling the lsm hooks in many cases.
Any lsm that makes pathname
On 6 Feb, Stefan Richter wrote:
> Robert Crocombe wrote:
>> moving to anything more recent than 2.6.19
>> means ohci1394 is non-functional (no 1394 hosts are detected) and the
>> module cannot be removed.
Not using the option disable_nodemgr=1 should avoid the bug.
>> I have narrowed it down to
First of all, if sending attached patches, *MAKE SURE* they're text/plain.
diff -uprN -X linux-2.6.20/Documentation/dontdiff
linux-2.6.20/arch/i386/kernel/setup.c
linux-2.6.20-gujin/arch/i386/kernel/setup.c
--- linux-2.6.20/arch/i386/kernel/setup.c 2007-02-04 18:44:54.0
+
Daniel Barkalow wrote:
On Sun, 4 Feb 2007, Robert Hancock wrote:
Something's busted with forcedeth in 2.6.20-rc6-mm3 for me relative to
2.6.20-rc6. There's no errors in dmesg, but it seems no packets ever get
received and so the machine can't get an IP address. I tried reverting all the
-mm
? <[EMAIL PROTECTED]> :
[...]
> >>static struct pci_device_id rtl8169_pci_tbl[] = {
> >>- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8129), 0, 0, RTL_CFG_0 },
> >>- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8136), 0, 0, RTL_CFG_2 },
> >>- { PCI_DEVICE(PCI_VENDOR_ID_REALTEK, 0x8167), 0, 0, RTL_CFG_0
On Mon, 5 Feb 2007, Davide Libenzi wrote:
> On Mon, 5 Feb 2007, Linus Torvalds wrote:
>
> > Indeed. One word is *exactly* what a normal system call returns too.
> >
> > That said, normally we have a user-space library layer to turn that into
> > the "errno + return value" thing, and in the
1 - 100 of 938 matches
Mail list logo
