From: Hiroshi Shimamoto <[EMAIL PROTECTED]>
Now cpu/proc.c and cpu/proc_64.c are same.
So cpu/proc_64.c can be removed.
Signed-off-by: Hiroshi Shimamoto <[EMAIL PROTECTED]>
---
arch/x86/kernel/cpu/Makefile |5 +-
arch/x86/kernel/cpu/proc_64.c | 180
From: Hiroshi Shimamoto <[EMAIL PROTECTED]>
make cpu/proc.c and cpu/proc_64.c same.
Signed-off-by: Hiroshi Shimamoto <[EMAIL PROTECTED]>
---
arch/x86/kernel/cpu/proc.c| 36 ++
arch/x86/kernel/cpu/proc_64.c | 49 +++-
2
Jeff Chua wrote:
On Feb 20, 2008 2:19 PM, Jeff Chua
I'll try the "idle=poll" to see if that works and will try some printk
I don't know what exactly the i915_suspend() and i915_resume() are
supposed to do because it works better without them.
After inserting "return 0;" right at the top
From: Hiroshi Shimamoto <[EMAIL PROTECTED]>
Change /proc/cpuinfo. It will look like x86_64's.
'power management' line is added and power management information
will be printed at the line.
Signed-off-by: Hiroshi Shimamoto <[EMAIL PROTECTED]>
---
arch/x86/kernel/cpu/proc.c | 14 +-
From: Hiroshi Shimamoto <[EMAIL PROTECTED]>
clean up for unification.
Signed-off-by: Hiroshi Shimamoto <[EMAIL PROTECTED]>
---
arch/x86/kernel/cpu/proc.c| 120 +++-
arch/x86/kernel/cpu/proc_64.c | 63 -
2 files changed, 105
On Wed, 20 Feb 2008 19:16:15 +0100
Peter Zijlstra <[EMAIL PROTECTED]> wrote:
>
> On Tue, 2008-02-19 at 12:37 -0800, Arjan van de Ven wrote:
> > From: Soren Sandmann <[EMAIL PROTECTED]>
> > Subject: [PATCH] x86: add the debugfs interface for the sysprof tool
> >
> > The sysprof tool is a very
From: Hiroshi Shimamoto <[EMAIL PROTECTED]>
x86 /proc/cpuinfo code can be unified.
This is the first step of unification.
Signed-off-by: Hiroshi Shimamoto <[EMAIL PROTECTED]>
---
arch/x86/kernel/cpu/Makefile |1 +
arch/x86/kernel/cpu/proc_64.c | 126
On Thu, 21 Feb 2008, Jeff Chua wrote:
>
> > That said, before you do anything else, try if suspend-to-RAM works.
>
> Linus, guess I missed this part ... so before touch anything, I did
> tried suspend-to-ram, and it works on console and in X.
Ok, so this is with clean current -git, and
Kok, Auke wrote:
> Andrew Morton wrote:
>> On Sun, 17 Feb 2008 15:36:50 +0300 Andrey Borzenkov <[EMAIL PROTECTED]>
>> wrote:
>>
>>> ... and possibly reboot/poweroff (it flows by too fast to be legible).
>>>
>>> [ 8803.850634] ACPI: Preparing to enter system sleep state S3
>>> [ 8803.853141]
On Feb 21, 2008 1:50 AM, Jesse Barnes <[EMAIL PROTECTED]> wrote:
> > I would like to know what they're for.
> They're for saving and restoring GPU state across suspend/resume. They're
> particularly useful if your machine doesn't re-POST at resume time. In that
> case your GPU may be totally
On 2/20/2008 12:15 PM, Alan Stern wrote:
On Wed, 20 Feb 2008, Andrew Buehler wrote:
Hmm. One thing which just sprang to mind, in the stab-in-the-dark
category: in 2.6.24.2, launching the program on some machines gave
warnings along the lines of "this program is using a deprecated
ioctl,
On Feb 20 2008 18:19, Pavel Machek wrote:
>>
>> For ordinary desktop people, memory controller is what developers
>> know as MMU or sometimes even some other mysterious piece of silicon
>> inside the heavy box.
>
>Actually I'd guess 'memory controller' == 'DRAM controller' == part of
Am 20.02.2008 17:54 schrieb Andi Kleen:
mISDN has two problems, which are of course interrelated:
a) complete lack of documentation for the in-kernel driver interface
(equivalent of Documentation/isdn/INTERFACE)
Most subsystems in the kernel would disqualify under that rule
I beg to
Hi!
> >> I know this is a pedantic comment, but why the heck is it called such
> >> a generic term as "Memory Controller" which doesn't give any
> >> indication of what it does.
> >>
> >> Shouldn't it be something like "Memory Quota Controller", or "Memory
> >> Limits Controller"?
> >
> >It's
I wrote:
>>> Thomas Meyer wrote at LKML:
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
>
> There are junk interrupt events sent to ohci1394's IRQ handler.
PS, do you still have the log lines which come from ohci1394's
On Tue, 2008-02-19 at 12:37 -0800, Arjan van de Ven wrote:
> From: Soren Sandmann <[EMAIL PROTECTED]>
> Subject: [PATCH] x86: add the debugfs interface for the sysprof tool
>
> The sysprof tool is a very easy to use GUI tool to find out where
> userspace is spending CPU time. See
>
[David Howells - Wed, Feb 20, 2008 at 06:13:15PM +]
| Cyrill Gorcunov <[EMAIL PROTECTED]> wrote:
|
| > Sam, maybe we should just eliminate this section at least for FRV?
|
| You should have a patch in your inbox to do just that.
|
| David
|
Thanks David! I've got them all.
I think Sam
Thomas Meyer wrote:
> Stefan Richter schrieb:
>> Thomas Meyer wrote at LKML:
>>> With 2.6.25-rc2 my kernel log consists mainly of:
>>>
>>> "ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
There are junk interrupt events sent to ohci1394's IRQ handler.
...
>> Do you have any hardware
On Mon, 2008-02-18 at 11:00 +0100, Jan-Bernd Themann wrote:
> Dave Hansen <[EMAIL PROTECTED]> wrote on 15.02.2008 17:55:38:
>
> > I've been thinking about that, and I don't think you really *need* to
> > keep a comprehensive map like that.
> >
> > When the memory is in a particular
Cyrill Gorcunov <[EMAIL PROTECTED]> wrote:
> Sam, maybe we should just eliminate this section at least for FRV?
You should have a patch in your inbox to do just that.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
From: David Howells <[EMAIL PROTECTED]>
There is no .data.idt section for FRV, so drop it from the linker script.
Signed-off-by: David Howells <[EMAIL PROTECTED]>
---
arch/frv/kernel/vmlinux.lds.S |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git
From: David Howells <[EMAIL PROTECTED]>
Change the FRV timerfd syscalls to be the same as i386 timerfd syscalls.
Signed-off-by: David Howells <[EMAIL PROTECTED]>
---
arch/frv/kernel/entry.S |4 +++-
include/asm-frv/unistd.h |4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
From: David Howells <[EMAIL PROTECTED]>
Change the FRV timerfd syscalls to be the same as i386 timerfd syscalls.
Signed-off-by: David Howells <[EMAIL PROTECTED]>
---
arch/frv/kernel/entry.S |4 +++-
include/asm-frv/unistd.h |4 +++-
2 files changed, 6 insertions(+), 2 deletions(-)
From: David Howells <[EMAIL PROTECTED]>
There is no .data.idt section for FRV, so drop it from the linker script.
Signed-off-by: David Howells <[EMAIL PROTECTED]>
---
arch/frv/kernel/vmlinux.lds.S |3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git
On Feb 20 2008 09:44, David Rees wrote:
>On Wed, Feb 20, 2008 at 2:57 AM, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
>> But GNU tar does not handle acls and xattrs. So back to rsync/cp/mv.
>
>Huh? The version of tar on my Fedora 8 desktop (tar-1.17-7) does. Just
>add the --xattrs option (which
Arne,
On Wed, 20 Feb 2008, Arne Georg Gleditsch wrote:
> I'm looking at 2.6.25-rc2. vsyscall_sysctl_change contains code to NOP
> out the actual system call instructions of the vsyscall page when
> vsyscall64 is enabled. This seems to interact badly with the fallback
> code in do_vgettimeofday
Hisashi Hifumi <[EMAIL PROTECTED]> writes:
> Hi Andrew.
>
> DIO invalidates page cache through invalidate_inode_pages2_range().
> invalidate_inode_pages2_range() sets ret=-EIO when invalidate_complete_page2()
> fails, but this ret is cleared if do_launder_page() succeed on a page of next
>
On Feb 21, 2008 1:52 AM, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Ahh. You're using the BIOS to re-initialize your video, aren't you?
I don't know. Just pure simple "s2ram" without any options.
> Let's try to narrow it down to what the interaction is. Are you using
> something like
On Wed, Feb 20, 2008 at 06:47:58PM +0100, Milan Broz wrote:
>
> I just tested one affected configuration and problem was in missing
> "chainiv.ko" module on ramdisk.
Ah OK. We probably should merge chainiv into the blkcipher
module too since it's the default IV generator. I'll take
care of it.
t; > people who have to check the results and actually report things to lkml.
>
> I hope I have addressed this issue by tagging each tree with its date
> i.e. todays was next-20080220.
>
> > Also will you be producing any tarballs for these releases? If so I
> > wou
Hi!
On Wednesday 20 February 2008, you wrote:
> A spi transfer with zero length is not invalid. Such transfer can be
> used to achieve delay before first CLK edge after chipselect assertion.
How long will be that delay?
If they are really users of that kind of thing, this should be fixed by
On Feb 21, 2008 1:28 AM, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> That said, before you do anything else, try if suspend-to-RAM works.
Linus, guess I missed this part ... so before touch anything, I did
tried suspend-to-ram, and it works on console and in X.
And suspend-to-disk hangs, but I
Stefan Richter schrieb:
Thomas Meyer wrote at LKML:
Hi.
With 2.6.25-rc2 my kernel log consists mainly of:
"ohci1394: fw-host0: Unhandled interrupt(s) 0xfc7cfe0c
ohci1394: fw-host0: Unrecoverable error!
ohci1394: fw-host0: Async Rsp Tx Context died: ctrl[f0002a00]
cmdptr[f0002a00]
[David Howells - Wed, Feb 20, 2008 at 01:01:05PM +]
| Cyrill Gorcunov <[EMAIL PROTECTED]> wrote:
|
| > being see over vmlinux.lds for FRV architecture I found the string:
| >
| > . = ALIGN(4096);
| > .data.page_aligned : { *(.data.idt) }
| >
| > though the PAGE_SIZE is 16K. Can't
On Thu, 21 Feb 2008, Jeff Chua wrote:
>
> Works without those two functions.
Ahh. You're using the BIOS to re-initialize your video, aren't you?
If STR works without X, then you have something else resuming graphics,
and that may be what then interacts badly with the fact that the kernel
[Sam Ravnborg - Wed, Feb 20, 2008 at 02:14:42PM +0100]
| On Wed, Feb 20, 2008 at 01:01:05PM +, David Howells wrote:
| > Cyrill Gorcunov <[EMAIL PROTECTED]> wrote:
| >
| > > being see over vmlinux.lds for FRV architecture I found the string:
| > >
| > > . = ALIGN(4096);
| > >
On Wednesday, February 20, 2008 9:17 am Jeff Chua wrote:
> On Feb 20, 2008 2:19 PM, Jeff Chua
>
> > I'll try the "idle=poll" to see if that works and will try some printk
>
> I don't know what exactly the i915_suspend() and i915_resume() are
> supposed to do because it works better without them.
>
Quoting Casey Schaufler ([EMAIL PROTECTED]):
> From: Casey Schaufler <[EMAIL PROTECTED]>
>
> Update the Smack LSM to allow the registration of the capability
> "module" as a secondary LSM. Integrate the new hooks required for
> file based capabilities.
Hi Casey,
to help people keep their
Herbert Xu wrote:
> On Wed, Feb 20, 2008 at 12:23:21PM +0100, Milan Broz wrote:
>> It seems that some module dependency was lost,
>> dm-crypt with async crypto depends now on crypto_blkcipher module
>> for this configuration.
>>
>> Herbert, any following change required for dm-crypt or it is only
On Wed, Feb 20, 2008 at 2:57 AM, Jan Engelhardt <[EMAIL PROTECTED]> wrote:
> But GNU tar does not handle acls and xattrs. So back to rsync/cp/mv.
Huh? The version of tar on my Fedora 8 desktop (tar-1.17-7) does. Just
add the --xattrs option (which turns on --acls and --selinux).
-Dave
--
To
Quoting Andrew G. Morgan ([EMAIL PROTECTED]):
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Andrew
>
> Here is the patch to add per-process securebits again. This version
> includes Serge's argument type fix (thanks), but is otherwise unchanged
> from the one posted a couple of weeks back.
On Feb 21, 2008 1:28 AM, Linus Torvalds <[EMAIL PROTECTED]> wrote:
> Try suspend-and-resume without X.
Works without those two functions.
> Also, try it on one of the more modern laptops - even *with* X.
Again, still works. Tested on Lenovo X60s.
> Basically, the kernel wants to be able to do
Nesting min_t/max_t macros produces many shadowed variable warnings
due to use of __x. Add a clamp_t macro to linux/kernel.h and use
it in the FIT macro.
Signed-off-by: Harvey Harrison <[EMAIL PROTECTED]>
---
include/linux/kernel.h |9 +
include/linux/libata.h |2 +-
2 files
> diff --git a/drivers/regulator/Makefile b/drivers/regulator/Makefile
> new file mode 100644
> index 000..3f70871
> --- /dev/null
> +++ b/drivers/regulator/Makefile
> @@ -0,0 +1,9 @@
> +#
> +# Makefile for regulator drivers.
> +#
> +
> +obj-$(CONFIG_REGULATOR) += reg-core.o
> +
Replace this
>
Linus,
please do so.
It is too annoying to await next pull request from xfs.
Sam
On Wed, Feb 20, 2008 at 11:58:48AM -0500, Jeff Garzik wrote:
> In current upstream, fs/xfs/Makefile-linux-2.6 is zero bytes, which
> means 'make distclean' deletes, and git promptly (and properly)
sound/core/init.c: In function ‘snd_card_disconnect’:
sound/core/init.c:307: warning: the address of ‘snd_shutdown_f_ops’ will always
evaluate as ‘true’
Signed-off-by: Joshua Roys <[EMAIL PROTECTED]>
---
sound/core/init.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git
2008-02-20 18:22:50 +0100, Jörn Engel:
> On Wed, 20 February 2008 17:02:31 +, Stephane Chazelas wrote:
> >
> > sorry, I wasn't very clear.
> >
> > With "loop", you're doing an ioctl() to /dev/loop so that
> > /dev/loop become a block device associated with a given file.
> >
> > Applying
On Thu, 21 Feb 2008, Jeff Chua wrote:
>
> After inserting "return 0;" right at the top of those two functions, suspend
> (and power-off properly), and resume (without green screen) works just fine.
>
> I would like to know what they're for.
Try suspend-and-resume without X.
Also, try it on
On Wed, 20 Feb 2008 11:42:56 -0500 (EST)
Alan Stern <[EMAIL PROTECTED]> wrote:
> >
> > --- Comment #14 from [EMAIL PROTECTED] 2008-02-19 15:23 ---
> > Thanks a lot for the debugging work!
> >
> > First, the patch triggers, which means that the problem discovered by Alan
> > is
> >
Note: Tejun's change is a feature addition, but one that is IMO
important for debugging and serious-bug workarounds. It's
self-contained and should not affect anyone not using the new parm.
Please pull from 'upstream-linus' branch of
On Wed, Feb 20, 2008 at 12:23:21PM +0100, Milan Broz wrote:
>
> It seems that some module dependency was lost,
> dm-crypt with async crypto depends now on crypto_blkcipher module
> for this configuration.
>
> Herbert, any following change required for dm-crypt or it is only
> crypto subsystem
On Wed, 20 February 2008 17:02:31 +, Stephane Chazelas wrote:
>
> sorry, I wasn't very clear.
>
> With "loop", you're doing an ioctl() to /dev/loop so that
> /dev/loop become a block device associated with a given file.
>
> Applying that strictly to block2mtd wouldn't make sense.
>
> At
On Wed, 20 Feb 2008 16:07:03 +0200 Avi Kivity wrote:
> > Looks like KVM conflicts with CONFIG_VOYAGER...
> >
>
> Attached patch should fix.
>
> Subject: x86: disable KVM on Voyager
>
> Most classic Pentiums don't have hardware virtualization
> extension, and building kvm with voyager generates
On Feb 21, 2008 1:17 AM, Jeff Chua <[EMAIL PROTECTED]> wrote:
>
>
> On Feb 20, 2008 2:19 PM, Jeff Chua
> > I'll try the "idle=poll" to see if that works and will try some printk
Tried "idle=poll" but it has not effect.
Thanks,
Jeff.
--
To unsubscribe from this list: send the line "unsubscribe
On Feb 20, 2008 2:19 PM, Jeff Chua
I'll try the "idle=poll" to see if that works and will try some printk
I don't know what exactly the i915_suspend() and i915_resume() are
supposed to do because it works better without them.
After inserting "return 0;" right at the top of those two
Harvey Harrison wrote:
Avoid ~70 sparse warnings like:
drivers/ata/pata_ali.c:176:14: warning: symbol '__x' shadows an earlier one
drivers/ata/pata_ali.c:176:14: originally declared here
Due to nesting min_t macro inside max_t macro which both use a __x
identifier internally.
Signed-off-by:
On Wed, 20 Feb 2008, Andrew Buehler wrote:
> > What do you mean by "does not see the drive"?
>
> Its detect-hardware-and-report mode shows a HD size of 0 (which is what
> it has showed in cases where the kernel has not detected the drive), its
> detect-partitions-and-report mode shows no
On Wed, Feb 20, 2008 at 10:42:35AM -0500, Theodore Tso wrote:
> On Wed, Feb 20, 2008 at 04:38:52PM +0100, Stefan Richter wrote:
> > Two things may largely eliminate the need for parallel branches.
> >
> > 1. Do infrastructure changes and whole tree wide refactoring etc. in a
> > compatible manner
(depends on "[PATCH 1/2] lock_task_sighand: add rcu lock/unlock",
http://marc.info/?l=linux-kernel=120335433821564)
lock_task_sighand() was changed, and do_task_stat() doesn't need rcu_read_lock
any longer. sighand->siglock protects all "interesting" fields.
Except: it doesn't protect
Holger Macht wrote:
On Thu 14. Feb - 13:40:48, Holger Macht wrote:
If a device/bay is inside a docking station, we need to register for dock
events additionally to bay events. If a dock event occurs, the dock driver
will call the appropriate handler (ata_acpi_ap_notify() or
Harvey Harrison wrote:
Use ld_qdi and ld_winbond to avoid shadowing static int
variables qdi and winbond. The ld_ prefix refers to
legacy_data.
drivers/ata/pata_legacy.c:777:21: warning: symbol 'qdi' shadows an earlier one
drivers/ata/pata_legacy.c:128:12: originally declared here
This patch adds support to build the regulator core.
Signed-off-by: Liam Girdwood <[EMAIL PROTECTED]>
---
drivers/Kconfig|2 ++
drivers/Makefile |1 +
drivers/regulator/Kconfig | 32
drivers/regulator/Makefile |9 +
4
Added Liam Girdwood and Mark Brown as maintainers.
Signed-off-by: Liam Girdwood <[EMAIL PROTECTED]>
---
MAINTAINERS |9 +
1 files changed, 9 insertions(+), 0 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 082d1ee..1f7d3ce 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@
This patch provides the regulator framework core. The core also provides a
sysfs interface for userspace information.
Signed-off-by: Liam Girdwood <[EMAIL PROTECTED]>
---
drivers/regulator/reg-core.c | 1049 ++
1 files changed, 1049 insertions(+), 0
This interface allows regulator drivers to register their voltage and current
regulators with the core. It also has a notifier call chain for propagating
regulator events to clients.
Signed-off-by: Liam Girdwood <[EMAIL PROTECTED]>
---
include/linux/regulator/regulator-drv.h | 119
This interface configures a regulator for use within a specific device. It
allows for the creation of voltage and current domains (with constraints) for
each regulator. Regulator constraints help prevent device damage by providing
protection for over voltage or over current events caused by buggy
This framework provides voltage and current regulator control to allow
consumer drivers to control their supply voltages and current levels.
The framework is similar to the kernel clock interface in that client or
consumer drivers can get() and put() a regulator (like they can with clocks
atm).
Hi,
On Tue, 19 Feb 2008, john stultz wrote:
> To better keep with your analogy, you'd have to imagine a scale that
> only reads in X pound increments. As long as X is fairly small, it
> should measure everyone's weight fairly well. However, if X is large,
> like say 50kg, then it won't weigh a
Version 2 with thanks to Sam Ravnborg, Mariusz Kozlowski, David Brownell
and Laura Lawrence for their comments.
This patch series provides a generic framework to allow device drivers
to control voltage and current regulators on SoC based devices (e.g.
phones, gps, media players).
The intention
On 20-02-08 18:05, H. Peter Anvin wrote:
Rene Herman wrote:
_Something_ like this would seem to be the only remaining option. It
seems fairly unuseful to #ifdef around that switch statement for
kernels without support for the earlier families, but if you insist...
"Only remaining
Rene Herman wrote:
_Something_ like this would seem to be the only remaining option. It
seems fairly unuseful to #ifdef around that switch statement for kernels
without support for the earlier families, but if you insist...
"Only remaining option" other than the one we've had all along.
(I suspect that some of the existing CC:s can now be dropped, and others
might need to be added if indeed this is worth discussing on kernel
lists at all, but I don't know what the protocol on that is so I have
left all of them in for the moment.)
On 2/20/2008 10:50 AM, Alan Stern wrote:
On
On Wed, 20 Feb 2008 10:11:23 -0600
Kumar Gala <[EMAIL PROTECTED]> wrote:
>
> Is the functionality provided by drivers/char/gen_rtc.c completely
> handled by the rtc subsystem in drivers/rtc?
>
> I ask for two reasons:
> 1. should we make it mutually exclusive in Kconfig
> 2. I've enabled both
Greg KH wrote:
On Mon, Feb 18, 2008 at 08:34:42AM +0100, Jonas Bonn wrote:
And again, what does this buy us?
Clarity and simplicity, I hope... there are a bunch of definitions
scattered about the kernel that omit the __devinitdata modifier despite the
documentation stating that it should
On Tuesday 19 February 2008 05:00:43 pm Rene Herman wrote:
> On 19-02-08 23:49, Adrian Bunk wrote:
>
> > The Coverity checker spotted the following inconsequent NULL checking
> > introduced by commit 5d38998ed15b31f524bde9a193d60150af30d916:
> >
> > <-- snip -->
> >
> > ...
> > static int
2008/2/15, Zan Lynx <[EMAIL PROTECTED]>:
>
> On Fri, 2008-02-15 at 15:57 +0100, Prakash Punnoor wrote:
> > On the day of Friday 15 February 2008 Jan Engelhardt hast written:
> > > On Feb 14 2008 17:21, Lukas Hejtmanek wrote:
> > > >Hello,
> > > >
> > > >whom should I blame about disk schedulers?
>
2008-02-20 17:30:42 +0100, Jörn Engel:
> On Wed, 20 February 2008 14:43:39 +, Stephane Chazelas wrote:
> >
> > note that for "loop", you have /dev/loop0, /dev/loop1... which
> > makes it a pain to handle
> >
> > For block2mtd, you don't need several device files in /dev, you
> > only need
In current upstream, fs/xfs/Makefile-linux-2.6 is zero bytes, which
means 'make distclean' deletes, and git promptly (and properly) squawks
about a working tree/index difference.
Would somebody please delete this file?
Thanks,
Jeff
--
To unsubscribe from this list: send the line
> OK, I'll queue a patch and try to explain various terms used by resource
> management.
Don't make it too verbose or nobody will read it. It should
be more like a one paragraph abstract on a scientific paper
about the linux memory controller.
But I think it should include some variant of the
Quoting Nick Andrew ([EMAIL PROTECTED]):
> On Tue, Feb 19, 2008 at 06:04:57PM -0800, Paul Menage wrote:
> > On Feb 19, 2008 7:12 AM, Nick Andrew <[EMAIL PROTECTED]> wrote:
> > > config CGROUPS
> > > [...]
> > > + When enabled, a new filesystem type "cgroup" is available
> > > +
> I know this is a pedantic comment, but why the heck is it called such
> a generic term as "Memory Controller" which doesn't give any
> indication of what it does.
I don't think it's pedantic. I would agree with you in fact
that the Kconfig description is not very helpful, even with
my warning
Note: this is based off of Linus's latest commit
(5d9c4a7de64d398604a978d267a6987f1f4025b7), since all my previous
submissions are now upstream (thanks!).
Please pull from 'upstream-davem' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jgarzik/netdev-2.6.git
upstream-davem
to receive
On Wed, Feb 20, 2008 at 7:20 AM, Balbir Singh <[EMAIL PROTECTED]> wrote:
> John Stoffel wrote:
> > I know this is a pedantic comment, but why the heck is it called such
> > a generic term as "Memory Controller" which doesn't give any
> > indication of what it does.
> >
> > Shouldn't it be
2008-02-20 17:42:27 +0100, Jörn Engel:
> On Wed, 20 February 2008 14:36:46 +, Stephane Chazelas wrote:
> >
> > At the moment, when we bind a mtd device to a block device, we
> > don't increase the refcount. When a mtdblock on a block2mtd, the
> > refcount is not increased either (the
Quoting Nick Andrew ([EMAIL PROTECTED]):
> Rewrite the help descriptions for clarity, accuracy and consistency.
>
> Kernel config options affected:
>
> - NAMESPACES
> - UTS_NS
> - IPC_NS
> - USER_NS
> - PID_NS
>
> Signed-off-by: Nick Andrew <[EMAIL PROTECTED]>
> ---
> Here's try #2 at
> mISDN has two problems, which are of course interrelated:
>
> a) complete lack of documentation for the in-kernel driver interface
>(equivalent of Documentation/isdn/INTERFACE)
Most subsystems in the kernel would disqualify under that rule
Did you ever look for full documentation on how
Adrian Bunk wrote:
This patch fixes a check-after-use spotted by the Coverity checker.
Signed-off-by: Adrian Bunk <[EMAIL PROTECTED]>
---
6beeb3ac577d74d72b2f91bd654eecb904c3c17e diff --git
a/drivers/net/phy/mdio_bus.c b/drivers/net/phy/mdio_bus.c
index 6e9f619..963630c 100644
---
Harvey Harrison wrote:
The forward declarations were already marked static, make the definitions
be static as well. Fixes the sparse warnings as well.
drivers/net/tlan.c:1403:5: warning: symbol 'TLan_HandleInvalid' was not
declared. Should it be static?
drivers/net/tlan.c:1435:5: warning:
Leonardo Potenza wrote:
From: Leonardo Potenza <[EMAIL PROTECTED]>
Suppress the warning message about the 'netcard_portlist' defined but not used.
Signed-off-by: Leonardo Potenza <[EMAIL PROTECTED]>
---
When building cs89x0 as a module, the following warning message is generated:
Thomas Klein wrote:
This patch adds kdump support to the ehea driver. As the firmware doesn't free
resource handles automatically, the driver has to run an as simple as possible
free resource function in case of a crash shutdown. The function iterates over
two arrays freeing all resource handles
On Wed, 2008-02-20 at 08:30 -0800, Randy Dunlap wrote:
> On Wed, 20 Feb 2008 15:46:32 +0100 Peter Zijlstra wrote:
< grammar mistakes >
Thanks Randy!
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Nick wrote:
> Ok, I had just picked up on the "legacy" word in the option title
> and assumed that it meant deprecated.
Just because something's old (and some newer equivalent exists)
doesn't mean we're making funeral arrangements for it yet.
Paul "old man" Jackson
--
On Tue, 19 Feb 2008 [EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=10030
>
>
>
>
>
> --- Comment #14 from [EMAIL PROTECTED] 2008-02-19 15:23 ---
> Thanks a lot for the debugging work!
>
> First, the patch triggers, which means that the problem discovered by
On Wed, 20 February 2008 14:36:46 +, Stephane Chazelas wrote:
>
> At the moment, when we bind a mtd device to a block device, we
> don't increase the refcount. When a mtdblock on a block2mtd, the
> refcount is not increased either (the mtdblock's one is I
> guess).
That is a bug then.
Jörn
On Wed, 20 Feb 2008 15:46:32 +0100 Peter Zijlstra wrote:
> Signed-off-by: Peter Zijlstra <[EMAIL PROTECTED]>
> ---
> Documentation/filesystems/Locking | 19 +
> Documentation/filesystems/vfs.txt | 17
> include/linux/buffer_head.h |2 -
> include/linux/fs.h
On Wed, 2008-02-20 at 10:35 +0100, Jens Axboe wrote:
> When non-blocking is set, ideally we want to return 0 if there's no hope
> of anymore data and EAGAIN if trying later may yield some data. So how
> about this instead?
>
Thank you Jens and Johann.
-Patrick
--
To unsubscribe from this
> > *ping* - Any further activity on this one? I got bit by it as well on
> > the very first attempted boot of 25-rc2-mm1, the instant it tried to leave
> > single-user and go multi-user.
>
> Valdis, any chance you can try the
> "[PATCH] (for -mm only) put_pid: make sure we don't free the
On Wed, 20 February 2008 14:43:39 +, Stephane Chazelas wrote:
>
> note that for "loop", you have /dev/loop0, /dev/loop1... which
> makes it a pain to handle
>
> For block2mtd, you don't need several device files in /dev, you
> only need one to pass ioctls down to create mtd devices.
>
>
On Feb 20 2008 17:27, Patrick McHardy wrote:
>> Striking. How can this even happen? A callsite which calls
>>
>> dev_alloc_skb(n)
>>
>> is just equivalent to
>>
>> __dev_alloc_skb(n, GFP_ATOMIC);
>>
>> which means there's like 4 (or 8 if it's long) bytes more on the
>> stack. For a worst
(sorry, the previous message was not finished)
On 02/20, Oleg Nesterov wrote:
>
> (Change the subject, cc Alan)
>
> On 02/19, [EMAIL PROTECTED] wrote:
> >
> > On Sun, 17 Feb 2008 21:11:14 MST, Eric W. Biederman said:
> > > Oleg Nesterov <[EMAIL PROTECTED]> writes:
> > > > On 02/16, Oleg Nesterov
301 - 400 of 1316 matches
Mail list logo
