Richard, Would you accept the addition of brightness_get to the led class? Please look at the first patch in this small patch set series. I need it for thinkpad-acpi... The other two patches to thinkpad-acpi are included for reference on how I intend to useg the new brightness_get stuff, and also the hardware acceleration for led flashing. While the thinkpad-acpi patches do work, it is unlikely to apply cleanly since it is from the tip of my thinkpad-acpi development tree :) They are NOT to...

Some led hardware allows drivers to query the led state, and this patch adds a hook to let the led class take advantage of that information when available. Without this functionality, when access to the led hardware is not exclusive (i.e. firmware or hardware might change its state behind the kernel's back), reality goes out of sync with the led class' idea of what the led is doing, which is annoying at best. Behaviour for drivers that do not or cannot read the led status is unchanged. Signed...

This patch fixes the following compile error: <-- snip --> ... CC arch/xtensa/kernel/syscall.o In file included from /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/xtensa/kernel/syscall.c:39: include2/asm/unistd.h:681: error: 'sys_timerfd' undeclared here (not in a function) make[2]: *** [arch/xtensa/kernel/syscall.o] Error 1 <-- snip --> Signed-off-by: Adrian Bunk <bunk@kernel.org> --- a42376eff20647fda6dc1bde20e793f9b4001c39 diff --git a/include/asm-xtensa/...

Commit 9e2779fa281cfda13ac060753d674bbcaa23367e broke parisc: <-- snip --> ... CC arch/parisc/kernel/asm-offsets.s In file included from include/asm/pgtable.h:13, from arch/parisc/kernel/asm-offsets.c:36: include/linux/mm.h: In function 'is_vmalloc_addr': include/linux/mm.h:243: error: 'VMALLOC_START' undeclared (first use in this function) include/linux/mm.h:243: error: (Each undeclared identifier is reported only once include/linux/mm.h:243: error: for each fun...

<big sigh of relief> So I do not have to worry about it? --

Commit 3062fc67dad01b1d2a15d58c709eff946389eca4 broke sparc: <-- snip --> ... CC init/do_mounts.o In file included from include/linux/mm.h:39, from include/linux/memcontrol.h:24, from include/linux/swap.h:8, from include/linux/suspend.h:7, from init/do_mounts.c:6: include/asm/pgtable.h:344: warning: parameter names (without types) in function declaration include/asm/pgtable.h:345: warning: parameter names (witho...

Signed-off-by: Adrian Bunk <bunk@kernel.org> --- deb88131c2fcc3076121597463153979aba9062d diff --git a/drivers/ide/legacy/gayle.c b/drivers/ide/legacy/gayle.c index 9d3851d..b7d8109 100644 --- a/drivers/ide/legacy/gayle.c +++ b/drivers/ide/legacy/gayle.c @@ -94,7 +94,7 @@ static int gayle_ack_intr_a1200(ide_hwif_t *hwif) static void __init gayle_setup_ports(hw_regs_t *hw, unsigned long base, unsigned long ctl, unsigned long irq_port, - ide_ack_intr_t *ack_intr); + ...

[PATCH] sata_mv: fix loop with last port commit f351b2d638c3cb0b95adde3549b7bfaf3f991dfa sata_mv: Support SoC controllers cause panic: scsi 4:0:0:0: Direct-Access ATA HITACHI HDS7225S V44O PQ: 0 ANSI: 5 sd 4:0:0:0: [sde] 488390625 512-byte hardware sectors (250056 MB) sd 4:0:0:0: [sde] Write Protect is off sd 4:0:0:0: [sde] Mode Sense: 00 3a 00 00 sd 4:0:0:0: [sde] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA sd 4:0:0:0: [sde] 488390625 512-byte hardw...

On Thu, 7 Feb 2008 23:36:01 +0100 but chances are that in a year's time someone will come along and helpfully make this const again. Maybe we should annotate such sites with #define cant_make_me_const_ask_sam_why /**/ to avoid this.. --

Has anyone else seen extraordinarily large sizes in /proc/mtrr output? We're running v2.6.24 on some Tyan S5383 dual-socket systems with the following characteristics: - qty(1) Intel(R) Xeon(R) CPU E5345 @ 2.33GHz (quad-core, the other socket is unoccupied) - 32GB RAM (qty(16) 2GB DIMMS) - MTRR Discrete ENABLED in the BIOS - PCI Memory Hole set to 512MB in the BIOS (other options are 256MB, 1GB and 2GB, all of which produce similar results) - CONFIG_MTRR, CONFIG_SMP and CONFIG_MC...

Please, when mentioning hex numbers, also do the one-liner shortlog. I realize that in gitk (or even just with two terminal windows open and a git repository) it's trivial to just follow the link and see what that commit was, but even you're just doing a "git log" or more commonly if you read the commit log somewhere else (like a mail gateway that posts them automatically when I apply things), it's really much more readable if you were to say something like: Commit ad7f71674ad7c3c446...

CONFIG_COMPAT_BRK=y means that heap randomization is turned off, so it's *always* a safe choice. I assume the help text is trying to say that if one does not run ancient binaries, then enabling heap randomization is safe. Signed-off-by: Roland Dreier <rolandd@cisco.com> --- diff --git a/init/Kconfig b/init/Kconfig index 95ac265..242ce32 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -565,7 +565,7 @@ config COMPAT_BRK disabled, and can be overriden runtime by setting /proc/sys/k...

See? It even has completely useless help text. Does WMI stand for Windows Management Instrumentation? It is some server management feature? What is it good for? Pavel WMI (EXPERIMENTAL) (ACPI_WMI) [N/m/y/?] (NEW) ? This driver adds support for the ACPI-WMI mapper device (PNP0C14) found on some systems. NOTE: You will need another driver or userspace application on top of this to actually use anything defined in the ACPI-WMI mapper. -- (english) [ message continues ]

+ACPI-WMI mapping driver + +Copyright (C) 2007-2008 Carlos Corbacho <carlos@strangeworlds.co.uk> + +Updated: 5th February 2008 + +1) About this guide + +This guide is a basic introduction on how to interact with the ACPI-WMI mapper +driver in the kernel - it presumes you already have a basic knowledge of +ACPI-WMI, ACPI and the hardware you are writing the driver for. + +2) What is ACPI-WMI + +At its simplest, ACPI-WMI is a proprietary extension to the ACPI specification...

While the kconfig text is supposed to say 'what' something is, the more valuable piece of information it provides is *why* one would want to enable it. Do you have list of hardware/platforms that require this feature to get the hardware to work? (acer abc123, tcm1100 xyz) If so, providing that information to the user/distributions is the right first step. Tell them why they want this feature. Better, if there are kernel drivers that require this (and currently only those drivers), then have th...

Following patch introduce HAVE_IDE to support flexible per arch or even per. sub-arch configuration of IDE support. This patch is needed to allow arm to use the generic drivers/Kconfig file. Introducing HAVE_IDE so each arch explicit select HAVE_IDE if supported allowed us to get rid of HAS_IOMEM which is anyway overloaded. And doing it this way is a much better way to document which architectures that supports IDE. Furthermore the decision if IDE is supported or not is distributed. Consider se...

Hi, With a lot of help from Ingo Molnar and Pekka Enberg over the last couple of weeks, we've been able to produce a new version of kmemcheck! General description: kmemcheck is a patch to the linux kernel that detects use of uninitialized memory. It does this by trapping every read and write to memory that was allocated dynamically (e.g. using kmalloc()). If a memory address is read that has not previously been written to, a message is printed to the kernel log. Changes since v2: - Don't use ...

Hello, Thank you for taking the time to look at this patch! I don't understand. This is the point, __GFP_NOTRACK _can_ be passed to slab functions like kmalloc. By default, when kmemcheck is enabled in the config, all other allocations will be tracked implicitly. The notrack flag exists to exempt certain (critical) allocations from this The cache_cache is needed so that we have somewhere to allocate kmem_cache objects from. These objects are accessed from kmemcheck in the page fault hand...

Ok, then I think we are still talking about different things :-) The tracking that kmemcheck does is actually a byte-for-byte tracking of whether memory has been initialized or not. Think of it as valgrind for the kernel. We do this by "hiding" pages (marking them non-present for for MMU) and taking the page faults, which effectively tells us what memory is being attempted to be read from or written to. (This generally means that the tracking that kmemcheck does is page-granular, but we can hel...

Applies on top of kmemcheck patch. Fixes/silences some reports of use of uninitialized memory. From: Ingo Molnar <mingo@elte.hu> Signed-off-by: Vegard Nossum <vegard.nossum@gmail.com> diff --git a/include/asm-generic/siginfo.h b/include/asm-generic/siginfo.h index 8786e01..b70cd97 100644 --- a/include/asm-generic/siginfo.h +++ b/include/asm-generic/siginfo.h @@ -278,11 +278,19 @@ void do_schedule_next_timer(struct siginfo *info); static inline void copy_siginfo(struct siginfo ...

I'll try applying the patch to a freshly downloaded git-tree. Shall I try another compiler? I have at least these two: gcc version 3.4.6 (Ubuntu 3.4.6-6ubuntu2) gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2) in addition to the self-compiled 4.2.3 I used for the tests. -- Hilsen Harald. --

I just re-downloaded an re-patched and re-compiled (with gcc 4.2.3), and now the kernel boots. I must have screwed up the previous patching. It now works, with Fujita's patch applied. -- Hilsen Harald --

Is this actually Enables/disables? I.e., is this actually pr_debug=<int> ? --- ~Randy --

-make pptp_msg_name dependent on CONFIG_PR_DEBUG_DYNAMIC Signed-off-by: Jason Baron <jbaron@redhat.com> --- net/netfilter/nf_conntrack_pptp.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/net/netfilter/nf_conntrack_pptp.c b/net/netfilter/nf_conntrack_pptp.c index b5cb8e8..2be92bd 100644 --- a/net/netfilter/nf_conntrack_pptp.c +++ b/net/netfilter/nf_conntrack_pptp.c @@ -65,7 +65,7 @@ void struct nf_conntrack_expect *exp) __read_mostly; EXPORT_S...

hi, make the pr_debug() function dependent upon the new immediate infrastruture. Thus, b/c of the low runtime impact, we can dynamically enable/disable pr_debug withoug recompiling. Patch allows 'pr_debug=0/1' on the command line or via /proc/sys/debug/pr_debug. thanks, -Jason --