From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Subject: [PATCH] amd74xx: use ide_get_pair_dev() helper There should be no functional changes caused by this patch. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> --- updates for pata-2.6 tree drivers/ide/amd74xx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) Index: b/drivers/ide/amd74xx.c =================================================================== --- a/drivers/ide/amd74xx.c +++ ...

From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Subject: [PATCH] cmd64x: use ide_get_pair_dev() helper There should be no functional changes caused by this patch. Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> --- drivers/ide/cmd64x.c | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) Index: b/drivers/ide/cmd64x.c =================================================================== --- a/drivers/ide/cmd64x.c +++ b/drivers/ide/cmd64x.c @@ -138,10 +138,12 ...

From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Subject: [PATCH] ide: NUMA aware allocation of host and port structures kzalloc() -> kzalloc_node() in ide_host_alloc(). Signed-off-by: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> --- drivers/ide/ide-probe.c | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) Index: b/drivers/ide/ide-probe.c =================================================================== --- a/drivers/ide/ide-probe.c +++ ...

From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com> Subject: [PATCH] ide: add port and host iterators Add ide_port_for_each_dev() / ide_host_for_each_port() iterators and update IDE code to use them. While at it: - s/unit/i/ variable in ide_port_wait_ready(), ide_probe_port(), ide_port_tune_devices(), ide_port_init_devices_data(), do_reset1(), ide_acpi_set_state() and scc_dma_end() - s/d/i/ variable in ide_proc_port_register_devices() There should be no functional changes caused by ...

Hi I have been experiencing some occasional errors in bttv using kernel 2.6.20.1, we suspect could either be: - hardware memory problem - software memory problem - IRQ conflict with wireless WIFI driver (zd1211 module below) Can someone assist by looking at this stack trace: -------------------------------------------------------- Dec 20 18:28:00 localhost kernel: BUG: unable to handle kernel paging request at virtual address fdedaf8f Dec 20 18:28:00 localhost kernel: printing eip: Dec ...

Ok, will try the latest kernel to see if that fixes it. 2.6.20.1 was actually the latest kernel when I rolled it out to these machines. The IRQ Lockup messages have never caused any problems to the the application, but only recently I caught the stack trace. Of course I may have missed catching these stack traces in the past, but they are rare. Thanks again for your input. Regards Keith --

It's been some time now since Max K. brought up the complete processor isolation discussion. I know his original patch was NAK'd but some work on this was put into cpusets. I'm unclear as to what actually has been or will be implemented. The 2 things I'm most interested in are work queues, and local timer interrupts. Is it yet possible to isolate a processor from either of these 2 things with recent kernels? The kernel doc concerning cpusets doesn't seem to clarify this for me. The Process ...

From OHCI-1394 1.1 clause 10.4.3: "If more than one IR DMA context specifies receives for packets from the same isochronous channel, the context destination for that channel's packets is undefined." Any userspace client and in the future also kernelspace clients can allocate IR DMA contexts for any channel. We don't want them to interfere with each other, hence it is preferable to return -EBUSY if allocation of a second context for a channel is attempted. Notes: - This limitation is ...

- Make sure par->next_line is always set (this was done for Falcon only), as all the text console drawing operations need a valid par->next_line, - Make sure fix->line_length is always set, as some userspace applications need it because they don't have fallback code for the case where it's zero. Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> --- drivers/video/atafb.c | 12 ++++++++---- 1 file changed, 8 insertions(+), 4 deletions(-) --- a/drivers/video/atafb.c +++ ...

- Improve comments and naming - Use void * for arbitrary pointers - Use a union to represent pixels/words, to avoid casts Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> --- drivers/video/c2p.c | 80 +++++++++++++++++++++++++++------------------------- drivers/video/c2p.h | 6 +-- 2 files changed, 45 insertions(+), 41 deletions(-) --- a/drivers/video/c2p.c +++ b/drivers/video/c2p.c @@ -54,7 +54,7 @@ static inline u32 get_mask(int n) return 0; } -#define ...

Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> --- drivers/video/Makefile | 2 drivers/video/amifb.c | 6 - drivers/video/c2p.c | 151 ------------------------------------------- drivers/video/c2p.h | 6 - drivers/video/c2p_planar.c | 156 +++++++++++++++++++++++++++++++++++++++++++++ 5 files changed, 163 insertions(+), 158 deletions(-) --- a/drivers/video/Makefile +++ b/drivers/video/Makefile @@ -28,7 +28,7 @@ obj-$(CONFIG_FB_DDC) += ...

Hello, This patchset introduces a new stackable filesystem: DazukoFS. SUMMARY DazukoFS is a stackable filesystem that provides functionality allowing userspace applications to perform online file access control. When a file is accessed on DazukoFS, registered userspace processes will be notified and given the opportunity to allow or deny the access. To help a registered process make its decision, it receives a read-only open file descriptor to the file being accessed. DazukoFS uses ...

Patch 2: Creates /dev/dazukofs.0 for userspace applications to perform file access control. At this point, all applications are considered to be working together (in the same group). Patched against 2.6.28-rc9. Signed-off-by: John Ogness <dazukocode@ogness.net> --- Documentation/filesystems/dazukofs.txt | 89 +++ fs/Kconfig | 3 fs/dazukofs/Makefile | 3 fs/dazukofs/dev.c | 85 +++ ...

Patch 4: Adds a new (optional) command to allow registered processes to be tracked. The tracking allows processes to be automatically unregistered if they crash and also allows groups to be automatically deleted if no more processes are registered. Patched against 2.6.28-rc9. Signed-off-by: John Ogness <dazukocode@ogness.net> --- Documentation/filesystems/dazukofs.txt | 24 ++++- fs/dazukofs/ctrl_dev.c | 15 ++- fs/dazukofs/event.c ...

Please make such cast cascades explicit: | struct dazukofs_inode_info *info = container_of(...); | info->lower_inode = lower_inode; You mix rather different coding styles through the whole code. Also why Why do you push anything out in other functions while making it explicit would make it much easier readable? Bastian -- Killing is stupid; useless! -- McCoy, "A Private Little War", stardate 4211.8 --

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAklOUWIACgkQFz+XezW6HD6q+ACgo/UVaCVJ5BUz/8wnmf4KPqYy uw4AoLDguyeGdEYWJLhvrFMF5CZm0EIw =Md4G -----END PGP SIGNATURE-----

This patch uses request_firmware() to download the firmware to the card. It seems that some of my previous patches (including an earlier and not working version of this) are missing from your tree so they are also included here again. This code is more compact than the original as it reads all the meta data from the firmware file instead of having it hard coded. In addition some 32/64 bit dependent code was removed. I was able to test it on an actual board and verify that it indeed works. If ...

Impact: cleanup, driver name in alhabetical order We are facing problems while we prepare patch for firmware as we add new stuff at the end. As per David Woodhouse suggestion, I am arranging WHENCE to aplhabetical order by driver name to avoid conflicts. Thanks to my son Gurchet Singh to help me in arranging driver names in alphabetical order. Signed-off-by: Jaswinder Singh <jaswinder@infradead.org> --- firmware/WHENCE | 314 ++++++++++++++++++++++++++++--------------------------- 1 files ...

Subject: [PATCH] m68k: Kill several external declarations in source files - Replace external declarations by proper includes where availiable. The accesses to some symbols had to be modified, as before they were declared using e.g. "extern int _end", while asm-generic/sections.h uses e.g. "extern char _end[]" - Remove unused or superfluous external declarations Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org> --- Shall I cherry pick this into my for-next branch ...

I think this one has a fix in x86.git: http://lkml.org/lkml/2008/12/18/224 --

From: David Brownell <dbrownell@users.sourceforge.net> The recent "simplify spi_write_then_read()" patch included a small regression from the 2.6.27 behavior with its performance win. All SPI transfers are full duplex, and are packaged as half duplex by either discarding the data that's read ("write only"), or else by writing zeroes ("read only"). That patch wasn't ensuring that zeroes were getting written out during the "half duplex read" part of the transaction; instead, old RX bits were ...

See here: http://lkml.org/lkml/2008/9/21/17 for a patch that allows arbitrary baud rate. -- Matan Ziv-Av. matan@svgalib.org --

Just installed today's git on my workstation and my Logitech USB Mouse only wants to move vertically around the centre of the monitor. I have no clue where to look - all I know is that it works with the 2.6.27 and various 2.6.28-rcs prior to this one. Parag [parag@xw6600 ~]$ diff Xorg.0.log.not.working /var/log/Xorg.0.log |grep Logi < (II) config/hal: Adding input device Logitech USB Receiver < (**) Logitech USB Receiver: always reports core events < (**) Logitech USB Receiver: Device: ...

Could you please provide vendor and product IDs of this device? (lsusb -v will tell you). -- Jiri Kosina SUSE Labs --

From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> Date: Fri, 19 Dec 2008 13:33:46 -0800 Subject:[RFC][PATCH 1/6][v3] Remove 'handler' parameter to tracehook functions Based on an earlier patch submitted by Oleg Nesterov and comments from Roland McGrath (http://lkml.org/lkml/2008/11/19/258). The handler parameter is currently unused in the tracehook functions. Besides, the tracehook functions are called with siglock held, so the functions can check the handler if they later need ...

From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> Date: Sat, 20 Dec 2008 12:27:47 -0800 Subject: [RFC][PATCH 3/6][v3] Define/set SIGNAL_UNKILLABLE_FROM_NS Define and set the SIGNAL_UNKILLABLE_FROM_NS flags for container-inits. This flag will be used in follow-on patches to ignore/drop fatal sigals to container-init from within the container but process the signals from an ancestor container. Based on discussions on earlier version of this ...

From: Sukadev Bhattiprolu <sukadev@linux.vnet.ibm.com> Date: Sat, 20 Dec 2008 13:25:24 -0800 Subject: [RFC][PATCH 5/6][v3] Protect cinit from unblocked SIG_DFL signals Drop early any SIG_DFL or SIG_IGN signals to container-init from within the same container. But queue SIGSTOP and SIGKILL to the container-init if they are from an acnestor container. Blocked, fatal signals (i.e when SIG_DFL is to terminate) from within the container can still terminate the container-init. That will be ...

This bug still occurs. So, it still needs to be on the regression list. I have not yet seen any replies to my bug report. François Valenduc --

No ... it's fixed and upstream. James --

not really a regression but a long-standing inconvenience/bug of the debug symbols of relocatable kernels. (ever since relocatable kernels were added in '06 or so.) Nevertheless we queued up a revert of the defconfig change for .29, to not expose it in the defconfig: f269b07: x86: revert CONFIG_RELOCATABLE=y defconfig change so i think it can be taken off the regressions list. Ingo --

hm, i think these were all fixed a long time ago, via: f6d87f4: genirq: keep affinities set from userspace across free/request_irq() 612e368: genirq: fix the affinity setting in setup_irq 6c2e940: x86: apic honour irq affinity which was set in early boot Kumar, could you please check v2.6.28-rc9 to see whether all issues are fixed? Ingo --

maybe you want to change the caps on KECHO in the changelog since it is no longer KECHO but kecho ? -mike --

What is wrong with the examples in the kernel tree itself? Are they not sufficient in some way? thanks, greg k-h --

This will incorrectly negate the already negative error code from input_register_device. Rabin --

Looks like the fan entries are being commanded pretty much full out.. (I'm sure those don't all correspond to physical fans, but likely different fan speeds.) Are you sure there's not a hardware problem (one or more fans not working, vents/heatsink clogged with dust)? Your system seems to be running very hot. --

This is horrible to read. + val = (1UL << UVH_IPI_INT_SEND_SHFT) | + (lapicid << UVH_IPI_INT_APIC_ID_SHFT) | + (vector << UVH_IPI_INT_VECTOR_SHFT); return uv_read_global_mmr64(pnode, UVH_EVENT_OCCURRED0) & Is this worth the trouble whether we allocate a couple of u64s per node or not ? Also isn't this kind of topology evaluation not done in x86 code u64 exp, lowest = ULLONG_MAX; int c, cpu = -1; Please move the expired check into uv_setup_intr() and ...

On Thu, 18 Dec 2008 23:33:09 -0500 (EST) Some of the partition formats do indeed go looking for the end of disk so it won't work in that case. --

[Empty message]

If we add dev_is_idecd() check here in patch #1 it won't be necessary to needlessly move the code around in this patch and it would also result in smaller resulting code (42 bytes saved on x86-32)... --

another thing. I turned off all the options that come ahead of the 'meat' of the trace data: # cat /debug/tracing/trace_options print-parent nosym-offset nosym-addr noverbose noraw nohex nobin noblock nostacktrace nosched-tree ftrace_printk noftrace_preempt nobranch annotate nouserstacktrace nosym-userobj printk-msg-only nofuncgraph-overrun nofuncgraph-cpu nofuncgraph-overhead nofuncgraph-proc but i still got the 'duration' field printed: # tracer: function_graph # # DURATION ...

On Wed, 17 Dec 2008 20:07:02 -0500 I can find no copies of them with Signed-off-by: lines so they appear to have escaped. If the authors of those changes would care to provided Signed-off-by: lines I'll chase this up further. --

This trivial patch adds support for i8k on the new Dell Vostro models. I tested it on my Vostro 1400, and it works. It does print a warning when loading the module: i8k: unable to get SMM BIOS version But I couldn't figure out how to fix that. The module seems to work fine, anyway... Signed-off-by: Federico Heinz <fheinz@vialibre.org.ar> --- drivers/char/i8k.c.orig 2007-07-08 20:32:17.000000000 -0300 +++ drivers/char/i8k.c 2007-09-27 03:06:08.000000000 -0300 @@ -439,6 +439,13 ...

I checked the two bugzillas (12149 & 12155) and both reporters have hpet=force on the command line. One of the reporters said: "If I de-select CONFIG_HPET_TIMER then the issue went away ..." It looks like this was not further investigated. Is this problem reproducible on other systems as well ? Thanks, tglx --

Deepak, Can you please upload the full trace somewhere ? Thanks, tglx --

ah, okay. Steve, any strong feelings against the patch? And we might just go for removing BUF_PAGE_SIZE itself instead. Ingo --

Hi, This time, the attached patch is against Linus' tree (linux/kernel/git/torvalds/linux-2.6.git). I'd be glad if Andrew would commit it so that you can pull it over to stable. Thanks in advance. Bye. -- Dipl.-Inform. (FH) Reinhard Nissl

On Sat, 13 Dec 2008 21:21:33 +0100 Applied, thanks. -- -- Pierre Ossman WARNING: This correspondence is being monitored by the Swedish government. Make sure your server uses encryption for SMTP traffic and consider using PGP for end-to-end encryption.

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEABECAAYFAklOvywACgkQdSjSd0sB4dJ9vACgvZw7tHsVOald55Y5NDYyoHy1 SHIAn18ZDBUq5CUl1ZtxtV7IC2BUBdeo =UtKp -----END PGP SIGNATURE-----

It seems that the bridge does support MSI. It looks like my video device is using MSI. Regards, Manu pci 0000:01:00.0: Boot video device PCI: Setting latency timer of device 0000:00:01.0 to 64 assign_interrupt_mode Found MSI capability Allocate Port Service[0000:00:01.0:pcie00] ...

Does: http://lkml.org/lkml/2008/12/16/40 help any? --

On Sun, 07 Dec 2008 13:51:39 -0800 Isn't it more likely that it needs 0x3 for any commands that ends an Perhaps a warning should be printed though, as there could be some You can't go fiddling with the voltage and removing the MMIO until you've made sure that there is no more activity on the slot. Fix the above issues and you can let it go via Russell with a: Acked-by: Pierre Ossman <drzeus@drzeus.cx> Rgds -- -- Pierre Ossman Linux kernel, MMC maintainer ...

On Tue, 2 Dec 2008 22:16:50 +0530 The ops are used fairly rarely and so far not in any hot-paths, so there would not be much gain in doing that. Rgds -- -- Pierre Ossman WARNING: This correspondence is being monitored by the Swedish government. Make sure your server uses encryption for SMTP traffic and consider using PGP for end-to-end encryption.

On Tue, 02 Dec 2008 15:40:25 +0000 I'm still waiting for a proper description of things here. Looking at the code, it looks like you have multiple clock sources and selecting the best one dynamically. That's probably a nice feature, but it should be possible to solve whilst still keeping calls going only from sdhci to sdhci-s3c. E.g. we could add a caps field (to keep quirks just for bugs) which states "has multiple clock sources". Before the core changes the clock, it calls ...

On Tue, 02 Dec 2008 15:40:23 +0000 You should probably put it under MMC_RICOH_MMC as that will become a I'm still waiting for a proper reason to allow this hook. Since you've added this, I assume you have at least one implementation of cfg_card. Care to include that so that I can see what it is you're trying to do? -- -- Pierre Ossman WARNING: This correspondence is being monitored by the Swedish government. Make sure your server uses encryption for SMTP traffic and consider ...

hm, that warning seems to show an ACPI bug (Len Cc:-ed): we preempt in an atomic section - right during executing an AML scriptlet. Executing ACPI AMLs is a rather fragile moment of the kernel: they are used by the BIOS to indirectly instruct the kernel to tweak lowlevel chipset registers and other platform details. The kernel executes AMLs 'blindly' - they tweak details that Linux typically has no knowledge about via any driver - so these things must absolutely run atomic, and ...

I know 2.6.23 has the same problem with resources not being assigned correctly to BARs as 2.6.27. It doesn't look like there are any patches in 2.6.24 that would have fixed it. --

On Thu, 04 Dec 2008 15:35:43 +0200 What confused me was that you sait "it is not in the standards", but perhaps you were just referring to the read case? In the write case the specs are clear that errors will be done during execution, which can be Queued. Thanks for all the work. :) Rgds -- -- Pierre Ossman WARNING: This correspondence is being monitored by the Swedish government. Make sure your server uses encryption for SMTP traffic and consider using PGP for end-to-end ...