Re: mount ramdisk rootfs /etc directory to jffs2 filesystem.

2010-01-25 Thread Chris Simmonds
Johnny Hung wrote: 2010/1/22 Marco Stornelli marco.storne...@gmail.com: 2010/1/22 Johnny Hung johnny.hack...@gmail.com: 2010/1/20 Marco Stornelli marco.storne...@gmail.com: 2010/1/20 Johnny Hung johnny.hack...@gmail.com: 2010/1/19 Matthias Kaehlcke matth...@kaehlcke.net: El Tue, Jan 19,

Re: Blacklisting in-kernel drivers

2010-01-25 Thread luca ellero
Peter Teoh wrote: similar from previous links posted, a lot of solutions are distro-specific, and varies from version to version: http://www.mail-archive.com/debian-bugs-d...@lists.debian.org/msg351306.html On Sun, Jan 24, 2010 at 12:26 PM, Peter Teoh htmldevelo...@gmail.com wrote:

accessing per-cpu variables from gdb

2010-01-25 Thread Joel Fernandes
I am having some trouble accessing 'current' to get the currently executing task in kgdb (x86_64). As current is a macro, I can't expand it in kgdb, so instead I'm trying to access the variable per_cpu__current_task inorder to get the task_struct for the currently executing task. But the memory

Re: sysfs_ops show vector: size of buffer not required?

2010-01-25 Thread Greg KH
On Sun, Jan 24, 2010 at 01:11:18PM +0530, Himanshu Chauhan wrote: Hi All, The sysfs_ops's show vector doesn't have a size of the buffer given to the vector, while store on the other hand has. What is the rationale behind it? If you need to check the size, you are doing something wrong.

Re: sysfs_ops show vector: size of buffer not required?

2010-01-25 Thread Himanshu Chauhan
On Mon, Jan 25, 2010 at 08:36:46PM -0800, Greg KH wrote: On Sun, Jan 24, 2010 at 01:11:18PM +0530, Himanshu Chauhan wrote: Hi All, The sysfs_ops's show vector doesn't have a size of the buffer given to the vector, while store on the other hand has. What is the rationale behind it?

Re: accessing per-cpu variables from gdb

2010-01-25 Thread Robin Randhawa
Hi Joel. On Tue, Jan 26, 2010 at 03:23:03AM +0530, Joel Fernandes wrote: I am having some trouble accessing 'current' to get the currently executing task in kgdb (x86_64). As current is a macro, I can't expand it in kgdb, so instead I'm trying to access the variable per_cpu__current_task

Small patches for Linux kernel

2010-01-25 Thread Himanshu Chauhan
Hi All, Where should I send small patches? Patches which address small compilation warnings etc. Linux kernel mailing list receives a lot of heavy weight patches and small patches get lost. Which is the best place to send, then? Is Kernel Janitor mailing list alive? Regards Himanshu -- To

Re: Small patches for Linux kernel

2010-01-25 Thread SandeepKsinha
On Tue, Jan 26, 2010 at 12:41 PM, Himanshu Chauhan hschau...@nulltrace.org wrote: Hi All, Where should I send small patches? Patches which address small compilation warnings etc. Linux kernel mailing list receives a lot of heavy weight patches and small patches get lost. Which is the best