---
From: Borislav Petkov <[EMAIL PROTECTED]>
Update the rest of Documentation/filesystems/vfs.txt
Signed-off-by: Borislav Petkov <[EMAIL PROTECTED]>
--
Index: linux-2.6.22-rc6/Documentation/filesystems/vfs.txt
===
--- linux-2.6.22
On Sat, 30 Jun 2007 19:13:40 +0200 Rodolfo Giometti <[EMAIL PROTECTED]> wrote:
>
> Maybe I can define a special struct for exchanging time data as:
>
>struct pps_timedata_s {
> long sec;
> long nsec;
>}
>
> and managing time data conversions at userland...
>
> What do you thi
On Sat, 2007-06-30 at 15:04 +0100, Hugh Dickins wrote:
> > Oh yes, the dirty handling is tricky. I had to fix a really nasty bug
> > with it lately. As for page_mkclean_one the difference is that it
> > doesn't claim a page is dirty if only the write protect bit has not been
> > set. If we manage t
Bjorn Helgaas wrote:
[...]
>
> I suspect that things will mostly work if you load the drivers in
> the (smsc-ircc2, wlags49_h1_cs) order.
yes
> Then smsc-ircc2 has a chance
> to reserve the resources before yenta and wlags49 get involved. But
> of course, we can't rely on that workaround.
>
On Fri, 2007-06-29 at 13:57 -0700, Andrew Morton wrote:
> On Fri, 29 Jun 2007 11:50:04 -0400
> Mingming Caoc <[EMAIL PROTECTED]> wrote:
>
> > I think the ext4 patch queue is in good shape now.
>
> Which ext4 patches are you intending to merge into 2.6.23?
>
> Please send all those out to lkml fo
Add a mount option to turn off extents.
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
---
Index: linux-2.6.22-rc4/fs/ext4/super.c
===
--- linux-2.6.22-rc4.orig/fs/ext4/super.c 2007-06-11 17:02:18.0
-0700
+++ linux-2.6
Turn on extents feature by default in ext4 filesystem. User could use
-o noextents to turn it off.
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc4/fs/ext4/super.c
===
--- linux-2.6.22-rc4.orig/fs/ext4/super.c
Propagate flags such as S_APPEND, S_IMMUTABLE, etc. from i_flags into
ext4-specific i_flags. Hence, when someone sets these flags via a different
interface than ioctl, they are stored correctly.
Signed-off-by: Jan Kara <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Index: lin
with the patch all headers are checked. the code should become
more resistant to on-disk corruptions. needless BUG_ON() have
been removed. please, review for inclusion.
Signed-off-by: Alex Tomas <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc4/fs/ext4/ex
Set the journals JBD2_FEATURE_INCOMPAT_64BIT on devices with more
than 32bit block sizes during mount time. This ensure proper record
lenth when writing to the journal.
Signed-off-by: Jose R. Santos <[EMAIL PROTECTED]>
Signed-off-by: Andreas Dilger <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao
When the JBD code was forked to create the new JBD2 code base, the
references to CONFIG_JBD_DEBUG where never changed to
CONFIG_JBD2_DEBUG. This patch fixes that.
Signed-off-by: Jose R. Santos <[EMAIL PROTECTED]>
---
Index: linux-2.6.22-rc4/fs/jbd2/journal.c
==
> On Jun 07, 2007 23:45 -0500, Jose R. Santos wrote:
> > The jbd2-debug file used to be located in /proc/sys/fs/jbd2-debug, but
> > create_proc_entry() does not do lookups on file names with more that one
> > directory deep. This causes the entry creation to fail and hence, no proc
> > file is cr
This patch is a spinoff of the old nanosecond patches.
It includes some cleanups and addition of a creation timestamp. The
EXT3_FEATURE_RO_COMPAT_EXTRA_ISIZE flag has also been added along with
s_{min, want}_extra_isize fields in struct ext3_super_block.
Signed-off-by: Andreas Dilger <[EMAIL PROT
This patch converts the 32-bit i_version in the generic inode to a 64-bit
i_version field.
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Signed-off-by: Jean Noel Cordenner <[EMAIL PROTECTED]>
Signed-off-by: Kalpak Shah <[EMAIL PROTECTED]>
Index: linux-2.6.21/include/linux/fs.h
=
This patch adds a 32-bit i_version_hi field to ext4_inode, which can be used
for 64-bit inode versions. This field will store the higher 32 bits of the
version, while Jean Noel's patch has added support to store the lower 32-bits
in osd1.linux1.l_i_version.
Signed-off-by: Mingming Cao <[EMAIL P
This patch adds 64-bit inode version support to ext4. The lower 32 bits
are stored in the osd1.linux1.l_i_version field while the high 32 bits
are stored in the i_version_hi field newly created in the ext4_inode.
Signed-off-by: Kalpak Shah <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao <[EMAIL PR
This patch is on top of i_version_update_vfs.
The i_version field of the inode is set on inode creation and incremented when
the inode is being modified.
Signed-off-by: Jean Noel Cordenner <[EMAIL PROTECTED]>
Signed-off-by: Mingming Cao <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc4/fs/ext4/ialloc.c
Add a "noversion" mount option to disable inode version updates.
Signed-off-by: Andreas Dilger <[EMAIL PROTECTED]>
Signed-off-by: Kalpak Shah <[EMAIL PROTECTED]>
Index: linux-2.6.21/fs/ext4/super.c
===
--- linux-2.6.21.orig/fs/ext4/s
This patch is on top of the nanosecond timestamp and i_version_hi
patches.
We need to make sure that existing filesystems can also avail the new
fields that have been added to the inode. We use s_want_extra_isize and
s_min_extra_isize to decide by how much we should expand the inode. If
EXT4_FEAT
Having recently upgraded our Asterisk server, I figured it would be a
good time to try a NO_HZ kernel. Everything was running well, until...
it decided to panic.
All I have is a fuzzy picture of the console to work from. The panic
was a fatal exception in interrupt, with EIP within run_posix_cp
[PATCH] jbd2 stats through procfs
The patch below updates the jbd stats patch to 2.6.20/jbd2.
The initial patch was posted by Alex Tomas in December 2005
(http://marc.info/?l=linux-ext4&m=113538565128617&w=2).
It provides statistics via procfs such as transaction lifetime and size.
[ This probabl
>From [EMAIL PROTECTED] Thu May 17 17:21:08 2007
Hi,
I have rebased this patch to 2.6.22-rc1 so that it can be added to the
ext4 patch queue. It has been tested by creating more than 65000 subdirs
and then deleting them and checking the nlinks. The e2fsprogs part of
this patch was sent earlier by
Journal checksum feature has been added to detect corruption of journal.
Signed-off-by: Andreas Dilger <[EMAIL PROTECTED]>
Signed-off-by: Girish Shilamkar <[EMAIL PROTECTED]>
Signed-off-by: Dave Kleikamp <[EMAIL PROTECTED]>
diff -Nurp linux024/fs/ext4/super.c linux/fs/ext4/super.c
--- linux024/fs
Use zero_user_page() in ext4 where possible.
Signed-off-by: Eric Sandeen <[EMAIL PROTECTED]>
Index: linux-2.6.22-rc4-mm2/fs/ext4/inode.c
===
--- linux-2.6.22-rc4-mm2.orig/fs/ext4/inode.c
+++ linux-2.6.22-rc4-mm2/fs/ext4/inode.c
@@ -
Subject: is_power_of_2: ext4/super.c
From: vignesh babu <[EMAIL PROTECTED]>
Replace (n & (n-1)) in the context of power of 2 checks with is_power_of_2()
Signed-off-by: vignesh babu <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Dave Kle
Subject: ext4: remove extra IS_RDONLY() check
From: Dave Hansen <[EMAIL PROTECTED]>
ext4_change_inode_journal_flag() is only called from one location:
ext4_ioctl(EXT3_IOC_SETFLAGS). That ioctl case already has a IS_RDONLY()
call in it so this one is superfluous.
Signed-off-by: Dave Hansen <[EMAI
From: Dmitry Monakhov <[EMAIL PROTECTED]>
Subject: ext4: extent compilation fixes
Fix compilation with EXT_DEBUG, also fix leXX_to_cpu convertions.
Signed-off-by: Dmitry Monakhov <[EMAIL PROTECTED]>
Acked-by: Alex Tomas <[EMAIL PROTECTED]>
Signed-off-by: Dave Kleikamp <[EMAIL PROTECTED]>
---
fs/
From: Dmitry Monakhov <[EMAIL PROTECTED]>
Subject: ext4: extent macros cleanup
- Replace math equation to it's macro equivalent
- make ext4_ext_grow_indepth() indexes/leaf correct
Signed-off-by: Dmitry Monakhov <[EMAIL PROTECTED]>
Acked-by: Alex Tomas <[EMAIL PROTECTED]>
Signed-off-by: Dave Kleik
* Willy Tarreau <[EMAIL PROTECTED]> wrote:
> Ingo,
>
> I've accidentally discovered a problem with -v18.
>
> Some time ago, I wrote a small program to prevent my laptop from
> entering low-power mode, and noticed that after upgrading my laptop's
> kernel from 2.4.20.9+cfs-v6 to 2.4.20.14+cfs-
Willy,
could you check whether your current v18 CFS tree has the fix below
included? I discovered it right after having released v18 so i updated
the v18 files in place - but maybe you downloaded an early version? I
thought it's relatively harmless, that it would only affect SCHED_IDLE
tasks,
On Jun 28, 2007, Alexandre Oliva <[EMAIL PROTECTED]> wrote:
> On Jun 28, 2007, Alexandre Oliva <[EMAIL PROTECTED]> wrote:
>> So, let's narrow the scenario to: tivoized machine downloads binary
>> from protected site, refrains from downloading sources that it could
>> download, user can still acces
On Sun, 1 Jul 2007, Martin Schwidefsky wrote:
> >
> > Expect you're right, but I _really_ don't want to comment, when I don't
> > understand that "|| pte_write" in the first place, and don't know the
> > consequence of pte_dirty && !pte_write or !pte_dirty && pte_write there.
>
> The pte_write()
Hi Ingo,
On Sun, Jul 01, 2007 at 10:45:01AM +0200, Ingo Molnar wrote:
> could you check whether your current v18 CFS tree has the fix below
> included? I discovered it right after having released v18 so i updated
> the v18 files in place - but maybe you downloaded an early version? I
> thought
On Sun, 01 Jul 2007 03:38:10 -0400
Mingming Cao <[EMAIL PROTECTED]> wrote:
> [PATCH] jbd2 stats through procfs
>
> The patch below updates the jbd stats patch to 2.6.20/jbd2.
> The initial patch was posted by Alex Tomas in December 2005
> (http://marc.info/?l=linux-ext4&m=113538565128617&w=2).
>
Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> On Jun 28 2007 12:57, Jan-Benedict Glaw wrote:
>>> > It's not an accusation -- it's merely an observation. You may not have
>>> > noticed that your mailer was misbehaving; now you _do_ know, and if you
>>> > care about RFC compliance you might want to fi
On Saturday, 30 June 2007 23:34, Andrey Borzenkov wrote:
> On Sunday 01 July 2007, Rafael J. Wysocki wrote:
> > On Saturday, 30 June 2007 06:59, Andrey Borzenkov wrote:
> > > Since 2.6.18 I do not have suspend to RAM; now I am starting to lose
> > > suspend to disk :)
> > >
> > > Environment - vani
On Sunday 01 July 2007 01:17:34 Lennert Buytenhek wrote:
> More or less. You can't add the resistances like that, since the
> bus isolation chip buffers the IDSEL signal, but it is correct that
> if the host's IDSEL resistor is larger than a certain value, the
> combination of the resistive coupli
> page_mkclean_one is used to clear the dirty bit and to set the write
> protect bit of a pte. In additions it returns true if the pte either
> has been dirty or if it has been writable. As far as I can see the
> function should return true only if the pte has been dirty, or page
> writeback will n
Hi!
> > ACPI Error (event-0305): No installed handler for fixed event [0002
> > 20070125]
> >
> > And SysRq was functioning.
>
> That probably means that there's a deadlock somewhere in there.
>
> > Unfortunately I do not have serial console so I
> > copy manually stacks from several las
On Friday 29 June 2007, Miklos Szeredi wrote:
> > > > Not as if it would be hard to add ioctl support to fuse. What fuse
> > > > can't handle is the data argument of ioctl(), so the most it could do
> > > > is give the filesystem a pid (tid) and a virtual address. The
> > > > userspace fs could t
On Sat, 2007-06-30 at 19:13 +0200, Rodolfo Giometti wrote:
> Maybe I can define a special struct for exchanging time data as:
>
>struct pps_timedata_s {
> long sec;
> long nsec;
>}
Seems reasonable enough in principle -- but whatever you do, don't use
"long" for it. That woul
> > Well, had a look at what FUSD does. It assumes that the ioctl
> > argument is stuctured according to the command. If all OSS ioctls are
> > like that, then fine, fuse can support it properly.
> >
> > The drawback of this is that ioctls which aren't structured properly
> > could cause weird fa
Here's a bit of email I exchanged with Davide Libenzi on epoll (7) man
page. There is an error in answer 9:
Davide Libenzi wrote:
> On Mon, 25 Jun 2007, Heikki Orsila wrote:
>> >From epoll man page:
>>
>>Q9 Do I need to continuously read/write an fd until EAGAIN when
>>
I'm resubmitting this as I didn't get any replies, this time CCeing
proper people, sorry..
Kernel locking/synchronization primitives are better than volatile types
from code readability point of view also.
This patch is against 2.6.22-rc6.
Signed-off-by: Heikki Orsila <[EMAIL PROTECTED]>
diff
On 6/30/07, Stephen Hemminger <[EMAIL PROTECTED]> wrote:
This is a non-standard formatting for comments, please follow
Coding style:
Thanks, I have updated the patch.
When the interface is down (or driver removed), the BroadCom 44xx card
remains powered on,
and both its MAC and PHY is using u
prompted by the earlier post on "volatile"s, is there a reason that
most atomic_t typedefs use volatile int's, while the rest don't?
$ grep "typedef.*struct" $(find . -name atomic.h)
./include/asm-v850/atomic.h:typedef struct { int counter; } atomic_t;
./include/asm-mips/atomic.h:typedef struc
On Sunday 01 July 2007 14:49:23 Török Edvin wrote:
> On 6/30/07, Stephen Hemminger <[EMAIL PROTECTED]> wrote:
> >
> > This is a non-standard formatting for comments, please follow
> > Coding style:
>
> Thanks, I have updated the patch.
>
> When the interface is down (or driver removed), the Broad
On 6/30/07, Matthew Garrett <[EMAIL PROTECTED]> wrote:
On Sat, Jun 30, 2007 at 07:44:59AM -0700, Arjan van de Ven wrote:
> Matthew Garrett wrote:
> >Do you still get link beat detection when the phy is powered down?
No.
As for link detection on the switch connected to this card:
If I have WoL t
On 7/1/07, Michael Buesch <[EMAIL PROTECTED]> wrote:
>
> You patch is also damaged here.
> Check your MUA settings.
>
[Sorry about that, resending again]
When the interface is down (or driver removed), the BroadCom 44xx card remains
powered on,
and both its MAC and PHY is using up power.
Thi
On Sun, 2007-07-01 at 09:54 +0100, Hugh Dickins wrote:
> But I could easily be overlooking something: Peter will recall.
/me tries to get his brain up to speed after the OLS closing party :-)
I did both pte_dirty and pte_write because I was extra careful. One
_should_ imply the other, but since
Hi
I'm using vmware and bridged networking with interface eth1.
The brigde works only when eth1 has the physical connection enabled, so
i always need to have another pc running.
with tcpdump i can see packets coming from virtual machines, but none
sent back.
I wonder if it's possibile to have th
Andrew, can you apply the patch below for 2.6.22? It reverts
smsc-ircc2 to the old blind probing behavior. There's a lot of
infrastructure work I need to do before the PNP probe will be
reliable.
Thanks,
Bjorn
On Sunday 01 July 2007 01:08:16 am Andrey Borzenkov wrote:
> Bjorn Helgaas wrote:
>
Hi,
the tg3 module automatically removes any incoming vlantags from packets.
how can i stop this on 2.6.18?
is there some hidden echo foo > /sys/...
or modprobe options tg3 dontusetagbla?
Thanks
Daniel
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
On Thu, Jun 28, 2007 at 12:36:20PM +0200, Rodolfo Giometti wrote:
> attached you can find new version of my patch for PXA27x UDC driver
> support against kernel 2.6.22-rc3 (but it applies also ro rc6).
>
> I'd like to know what I have to do in order to prepare this patch for
> kernel inclusion. I
On Sun, Jul 01, 2007 at 12:23:16PM +0200, Michael Buesch wrote:
> > More or less. You can't add the resistances like that, since the
> > bus isolation chip buffers the IDSEL signal, but it is correct that
> > if the host's IDSEL resistor is larger than a certain value, the
> > combination of the
On Thu, Jun 28, 2007 at 12:36:20PM +0200, Rodolfo Giometti wrote:
> attached you can find new version of my patch for PXA27x UDC driver
> support against kernel 2.6.22-rc3 (but it applies also ro rc6).
>
> I'd like to know what I have to do in order to prepare this patch for
> kernel inclusion. It
Videopix Frame Grabber: vfc_debug() doesn't release the device lock
when copy_from_user() fails
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
---
diff --git a/drivers/sbus/char/vfc_dev.c b/drivers/sbus/char/vfc_dev.c
index 6afc7e5..1cbdabd 100644
--- a/drivers/sbus/char/vfc_dev.c
+++ b/dr
On Sunday 01 July 2007 17:00:06 Lennert Buytenhek wrote:
> On Sun, Jul 01, 2007 at 12:23:16PM +0200, Michael Buesch wrote:
>
> > > More or less. You can't add the resistances like that, since the
> > > bus isolation chip buffers the IDSEL signal, but it is correct that
> > > if the host's IDSEL r
Imho, the current naming of cancel_xxx workqueue functions is very confusing.
cancel_delayed_work()
cancel_rearming_delayed_work()
cancel_rearming_delayed_workqueue() // obsolete
cancel_work_sync()
This looks as if the first 2 functions differ in "type" of the
Change cancel_work_sync() and cancel_delayed_work_sync() to return a boolean
indicating whether the work was actually cancelled. A zero return value means
that the work was not pending/queued.
Without that kind of change it is not possible to avoid flush_workqueue()
sometimes, see the next patch a
I don't know how to test this patch, the ack/nack from maintainer is wanted.
flush_scheduled_work() is evil and should be avoided. Change tty_set_ldisc()
and release_dev() to use cancel_delayed_work_sync/cancel_work_sync.
I am not sure we really need to call do_tty_hangup() when cancel_work_sync(
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
> Adrian Bunk wrote:
>> <-- snip -->
>>
>> ...
>> RELOCS arch/i386/boot/compressed/vmlinux.relocs
>> WARNING: Absolute relocations present
>> Offset Info Type Sym.Value Sym.Name
>> c0101f80 020c6501 R_386_32 xen_irq_disab
On Sun, 1 Jul 2007 19:37:49 +0400
Oleg Nesterov <[EMAIL PROTECTED]> wrote:
> I don't know how to test this patch, the ack/nack from maintainer is wanted.
>
> flush_scheduled_work() is evil and should be avoided. Change tty_set_ldisc()
> and release_dev() to use cancel_delayed_work_sync/cancel_wor
i just noticed that, in the Kconfig files that support KPROBES, both
the "Instrumentation support" menu is still listed as EXPERIMENTAL,
while Kprobes support within is simultaneously dependent on that same
selection.
for one, that's kind of redundant and, for another, isn't kprobes
mature en
On Jun 30, 2007 11:21 +0100, Christoph Hellwig wrote:
> On Tue, Jun 26, 2007 at 04:02:47PM +0530, Amit K. Arora wrote:
> > Currently it is left on the file system implementation. In ext4, we do
> > not undo preallocation if some error (say, ENOSPC) is hit. Hence it may
> > end up with partial (pre
Sam Ravnborg wrote:
Grouping related things together is always a good approach. But the right
factor should be used for the grouping. For the ELF file is would from a usage
perspective be natural to have constants close to the definition that
they are used to describe. Having constants grouped wi
This patchset converts semaphores that are used as mutexes to the
mutex API in the following drivers:
Megaraid Mailbox
Philips webcam
SMSC LPC47M192
Virtual Video
VLSI 82C147 IrDA controller
--
Matthias Kaehlcke
Linux Application Developer
Barcelona
Insanity: doing the same thing
On 6/30/07, Davide Libenzi <[EMAIL PROTECTED]> wrote:
This is how all those overloaded syscalls looks like, BTW:
[...]
How would you do that with a single shared strcture, w/out adding in all
signal paths the knowledge of the structure?
You said it yourself: each individual wrapper would look l
The Megaraid Mailbox driver uses a semaphore as mutex. Use the mutex
API instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/scsi/megaraid/mega_common.h
b/drivers/scsi/megaraid/mega_common.h
index 26e1e6c..fef9ac9 100644
--- a/drivers/
The Philips webcam driver uses a semaphore as mutex. Use the mutex API
instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/media/video/pwc/pwc-if.c b/drivers/media/video/pwc/pwc-if.c
index 085332a..9c0e8d1 100644
--- a/drivers/media/vid
The SMSC LPC47M192 driver uses a semaphore as mutex. Use the mutex API
instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/hwmon/smsc47m192.c b/drivers/hwmon/smsc47m192.c
index a012f39..7c5cfa2 100644
--- a/drivers/hwmon/smsc47m192.c
++
The Virtual Video driver uses a semaphore as mutex. Use the mutex API
instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/media/video/vivi.c b/drivers/media/video/vivi.c
index f7e1d19..e86f4cd 100644
--- a/drivers/media/video/vivi.c
+++
Eric W. Biederman wrote:
Jeremy Fitzhardinge <[EMAIL PROTECTED]> writes:
Adrian Bunk wrote:
<-- snip -->
...
RELOCS arch/i386/boot/compressed/vmlinux.relocs
WARNING: Absolute relocations present
Offset Info Type Sym.Value Sym.Name
c0101f80 020c6501 R_386_32
The VLSI 82C147 IrDA controller driver uses a semaphore as mutex. Use
the mutex API instead of the (binary) semaphore.
Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
--
diff --git a/drivers/net/irda/vlsi_ir.c b/drivers/net/irda/vlsi_ir.c
index bf78ef1..0538ca9 100644
--- a/drivers/net/irda
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
BTW, avr32 also has some support for kprobes, but it's implemented
in a non-standard way so i thought i'd just ignore that here. if
someone thinks it should be added, i'm good with that, too.
i have *no* idea who should sign off on th
On 07/01, Alan Cox wrote:
>
> On Sun, 1 Jul 2007 19:37:49 +0400
> Oleg Nesterov <[EMAIL PROTECTED]> wrote:
>
> > I don't know how to test this patch, the ack/nack from maintainer is wanted.
> >
> > flush_scheduled_work() is evil and should be avoided. Change tty_set_ldisc()
> > and release_dev()
The blink driver wakes up every jiffies which wastes power unnecessarily.
Using a notifier gives same effect. Also add ability to unload module.
Signed-off-by: Stephen Hemminger <[EMAIL PROTECTED]>
--- a/drivers/misc/blink.c 2007-06-29 22:56:20.0 -0400
+++ b/drivers/misc/blink.c
Signed-off-by: Robert P. J. Day <[EMAIL PROTECTED]>
---
diff --git a/arch/sparc64/Kconfig b/arch/sparc64/Kconfig
index 89a1b46..6b04c86 100644
--- a/arch/sparc64/Kconfig
+++ b/arch/sparc64/Kconfig
@@ -446,6 +446,7 @@ config KPROBES
execute a callback function. register_kprobe() establ
Are you able (as a matter of some urgency) to run a git bisection
search to identify the offending commit?
For some reason I am no longer able to reproduce the problem. I've
tried several versions including the one I reported and I just can't
reproduce the problem. I accidentally overwrote the o
Jesper Juhl wrote:
(originally from 28 May 2007, resending due to no response to this
final version and not seeing the patch picked up anywhere)
The UMSDOS filesystem was removed back in 2.6.11, but some tiny bits
stuck around. This patch removes the few remaining leftovers.
The only things l
On Sun, 1 Jul 2007, Heikki Orsila wrote:
> So, the Q9 should be changed:
>
> Q9Do I need to continuously read/write an fd until EAGAIN when
> using the EPOLLET flag ( Edge Triggered behaviour ) ?
>
> A9As a general rule, yes. However, there are exceptions.
> With some type
On Sun, 1 Jul 2007, Ulrich Drepper wrote:
> On 6/30/07, Davide Libenzi <[EMAIL PROTECTED]> wrote:
> > This is how all those overloaded syscalls looks like, BTW:
> > [...]
> > How would you do that with a single shared strcture, w/out adding in all
> > signal paths the knowledge of the structure?
>
Hi Matthias:
* Matthias Kaehlcke <[EMAIL PROTECTED]> [2007-07-01 18:32:24 +0200]:
> The SMSC LPC47M192 driver uses a semaphore as mutex. Use the mutex API
> instead of the (binary) semaphore.
>
> Signed-off-by: Matthias Kaehlcke <[EMAIL PROTECTED]>
Already in my testing tree[1] and therefore in
On 7/1/07, Dan <[EMAIL PROTECTED]> wrote:
> Are you able (as a matter of some urgency) to run a git bisection
> search to identify the offending commit?
For some reason I am no longer able to reproduce the problem. I've
tried several versions including the one I reported and I just can't
reprodu
Jarek Poplawski wrote:
>
>#1
>Until kernel ver. 2.6.21 (including) cancel_rearming_delayed_work()
>required a work function should always (unconditionally) rearm with
>delay > 0 - otherwise it would endlessly loop. This patch replaces
>this function with cancel_delayed_work(). L
On Sunday 01 July 2007, Russell King - ARM Linux wrote:
> >
> > +#ifdef CONFIG_USB_GADGET_PXA27X
> > +#define DEV_CONFIG_SUBSET
> > +#endif
> > +
>
> Bad - can we not make this runtime dependent?
The #define controls which descriptors are statically linked
into every object. I suppose someone
On Sun, 1 Jul 2007, Stephen Hemminger wrote:
>
> The blink driver wakes up every jiffies which wastes power unnecessarily.
> Using a notifier gives same effect. Also add ability to unload module.
I really get the feeling this thing should be removed entirely. Wasting
power is the _least_ of its
please submit the patch via email as per
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
to
Andrew Morton <[EMAIL PROTECTED]>
[EMAIL PROTECTED]
linux-kernel@vger.kernel.org
thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
> Thomas, any chance you could try the patch below? It is very, very stupid,
> it was done without any understanding of this code, and of course it is
> completely untested. I doubt very much it is correct, and even if it is
> correct it is definitely not good. It would be great if Dmitry can take
On Sun, Jul 01, 2007 at 05:13:25PM +1000, Stephen Rothwell wrote:
> On Sat, 30 Jun 2007 19:13:40 +0200 Rodolfo Giometti <[EMAIL PROTECTED]> wrote:
> >
> > Maybe I can define a special struct for exchanging time data as:
> >
> >struct pps_timedata_s {
> > long sec;
> > long nsec;
>
On Sun, Jul 01, 2007 at 01:03:11PM +0100, David Woodhouse wrote:
>
> Seems reasonable enough in principle -- but whatever you do, don't use
> "long" for it. That would definitely need different behaviour for 32-bit
> vs. 64-bit. Use explicitly sized types such as uint32_t or uint64_t.
Which is th
On 07/01, Thomas Sattler wrote:
>
> > Thomas, any chance you could try the patch below? It is very, very stupid,
> > it was done without any understanding of this code, and of course it is
> > completely untested. I doubt very much it is correct, and even if it is
> > correct it is definitely not g
On Sun, 2007-07-01 at 09:54 +0100, Hugh Dickins wrote:
> On Sun, 1 Jul 2007, Martin Schwidefsky wrote:
> > >
> > > Expect you're right, but I _really_ don't want to comment, when I don't
> > > understand that "|| pte_write" in the first place, and don't know the
> > > consequence of pte_dirty && !
This patch contains the following cleanups:
- make the needlessly global variable rt_trace_on static
- remove the unused global function deadlock_trace_off()
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch has been sent on:
- 4 Apr 2007
--- linux-2.6.21-rc5-mm3/kernel/rtmutex-debu
This patch makes some needlessly global functions static.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch has been sent on:
- 4 Apr 2007
kernel/relay.c | 13 ++---
1 file changed, 6 insertions(+), 7 deletions(-)
--- linux-2.6.21-rc5-mm3/kernel/relay.c.old 2007-04-0
This patch contains the overdue removal of X86_SPEEDSTEP_CENTRINO_ACPI.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Acked-by: Venkatesh Pallipadi <[EMAIL PROTECTED]>
Acked-by: Dave Jones <[EMAIL PROTECTED]>
---
This patch has been sent on:
- 6 Apr 2007
Documentation/feature-removal-schedule
This patch removes dead code introduced by
commit 90a42210f275e1f828eb6c08bf8252c2d6a774e0 and spotted
by the Coverity checker.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
drivers/net/wireless/libertas/wext.c |3 ---
1 file changed, 3 deletions(-)
--- linux-2.6.22-rc6-mm1/drivers/ne
e1000_{read,write}_pci_cfg() are no longer used.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch has been sent on:
- 5 Jun 2007
drivers/net/e1000/e1000_hw.h |2 --
drivers/net/e1000/e1000_main.c |4
2 files changed, 4 insertions(+), 2 deletions(-)
--- linux-2.6.22
The CONFIG_MTD_PMC551_APERTURE_SIZE option seems to never have existed,
so there's no reason for carrying an #ifdef for it.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
This patch has been sent on:
- 3 Jun 2007
--- linux-2.6.22-rc3-mm1/drivers/mtd/devices/pmc551.c.old 2007-06-03
1
congestion_wait_interruptible() is no longer used.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
Acked-by: Trond Myklebust <[EMAIL PROTECTED]>
---
This patch has been sent on:
- 12 Jun 2007
include/linux/backing-dev.h |1 -
mm/backing-dev.c|2 ++
2 files changed, 2 inserti
1 - 100 of 157 matches
Mail list logo
