On Fri, 2012-09-14 at 21:21 -0600, Jim Cromie wrote:
> Replace printks with pr_s, add pr_fmt()s to replace NAMEs
Hi Jim.
When you do these, please maximally fill to 80 columns the printk
arguments and coalesce formats without regard to 80 columns.
> diff --git a/drivers/i2c/busses/scx200_acb.c
On Fri, Sep 14, 2012 at 03:38:01PM -0700, Stephen Boyd wrote:
> On 09/14/12 14:34, Arnd Bergmann wrote:
> > ARM is moving to stricter checks on readl/write functions,
> > so we need to use the correct types everywhere.
> >
> > Cc: David Brown
> > Cc: Daniel Walker
> > Cc: Bryan Huntsman
> >
On Fri, Sep 14, 2012 at 8:05 PM, Jiang Liu wrote:
> From: Yijing Wang
>
> Changeset 2ed168eeb3edec029aa0eca5cb981d6376f931f9 "PCI: Fold stop and
> remove helpers into their callers" has changed the behavior when
> removing a PCI device.
>
> Previously, for a PCI bridge device with secondary bus,
On Fri, 2012-09-14 at 21:15 -0700, Linus Torvalds wrote:
> We don't do random crazy "use another scheduler" to hide problems with
> the default one.
I was proposing a diagnostic.
>
> And since you are the author of the regressing patch, and don't seem
> to treat the regression as something
From: Greg Kroah-Hartman
As discussed at the kernel summit this year, CONFIG_EXPERIMENTAL means
nothing, so let's get rid of it.
Cc: Kees Cook
Cc: Felipe Balbi
Cc: David Herrmann
Cc: Hauke Mehrtens
Cc: Alan Stern
Cc: Neil Zhang
Cc: Randy Dunlap
Cc: Fabio Estevam
Signed-off-by: Greg
Hi Larry, hi all,
On Fr, 14 Sep 2012, wrote:
> I am running on top of default kernel git, will try wireless-testing, too.
I tried now with wireless-testing from yesterday, and had the same problem.
Actually, I got even *better* results:
64 bytes from 192.168.0.1: icmp_req=75 ttl=255 time=137856
On Fri, 2012-09-14 at 23:27 +0200, Borislav Petkov wrote:
> (Adding everybody to CC and leaving the below for reference.)
>
> Guys,
>
> as Nikolay says below, we have a regression in 3.6 with pgbench's
> benchmark in postgresql.
>
> I was able to reproduce it on another box here and did a
From: Russell King - ARM Linux
Date: Sat, 15 Sep 2012 00:56:07 +0100
> On Fri, Sep 14, 2012 at 11:34:52PM +0200, Arnd Bergmann wrote:
>> ARM is moving to stricter checks on readl/write functions,
>> so we need to use the correct types everywhere.
>
> Same comment as for eesox. const void
On Fri, 2012-09-14 at 23:59 +0200, Peter Zijlstra wrote:
> On Fri, 2012-09-14 at 23:56 +0200, Peter Zijlstra wrote:
> > On Fri, 2012-09-14 at 14:44 -0700, Linus Torvalds wrote:
> > > On Fri, Sep 14, 2012 at 2:40 PM, Peter Zijlstra
> > > wrote:
> > > >
> > > > The problem the patch is trying to
I'm announcing the release of the 3.5.4 kernel.
All users of the 3.5 kernel series must upgrade.
The updated 3.5.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.5.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 3.4.11 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index d863aa0..4bd7aed 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 0
-SUBLEVEL = 42
+SUBLEVEL = 43
EXTRAVERSION =
NAME = Sneaky Weasel
diff --git a/arch/alpha/include/asm/socket.h b/arch/alpha/include/asm/socket.h
index
I'm announcing the release of the 3.0.43 kernel.
All users of the 3.0 kernel series must upgrade.
The updated 3.0.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.0.y
and can be browsed at the normal kernel.org git web browser:
On Fri, 2012-09-14 at 14:42 -0700, Linus Torvalds wrote:
> On Fri, Sep 14, 2012 at 2:27 PM, Borislav Petkov wrote:
> >
> > as Nikolay says below, we have a regression in 3.6 with pgbench's
> > benchmark in postgresql.
> >
> > I was able to reproduce it on another box here and did a bisection
Replace printks with pr_s, add pr_fmt()s to replace NAMEs
Signed-off-by: Jim Cromie
---
drivers/i2c/busses/scx200_acb.c | 18 ++
drivers/i2c/busses/scx200_i2c.c | 12 +++-
2 files changed, 17 insertions(+), 13 deletions(-)
diff --git a/drivers/i2c/busses/scx200_acb.c
Currently the pci_slot driver doesn't update PCI slot information
when PCI device hotplug event happens, which may cause memory leak
and returning stale information to user.
So hook the BUS_NOTIFY_ADD_DEVICE/BUS_NOTIFY_DEL_DEVICE events to
update PCI slot information when PCI hotplug event
Currently the acpiphp driver fails to update hotplug slot information under
several conditions, such as:
1) The bridge device is removed through /sys/bus/pci/devices/.../remove
2) The bridge device is added/removed by PCI hotplug driver other than the
acpiphp driver itself. For example, if an
From: Yijing Wang
The AER driver only configures downstream PCIe devices at driver
binding time and all hot-added PCIe devices won't be managed by
the AER driver. So hook PCIe device hotplug events to setup AER
configuration for hot-added PCIe devices.
Signed-off-by: Yijing Wang
Serialize access to the bridge_list in the acpiphp driver.
Signed-off-by: Jiang Liu
Signed-off-by: Yijing Wang
---
drivers/pci/hotplug/acpiphp_glue.c | 11 +++
1 file changed, 11 insertions(+)
diff --git a/drivers/pci/hotplug/acpiphp_glue.c
b/drivers/pci/hotplug/acpiphp_glue.c
On Sat, Sep 15, 2012 at 01:22:20AM +0100, Ben Hutchings wrote:
> On Wed, 2012-09-12 at 16:39 -0700, Greg Kroah-Hartman wrote:
> > From: Greg KH
> >
> > 3.0-stable review patch. If anyone has any objections, please let me know.
> >
> > --
> >
> > From: Alex Deucher
> >
> >
From: Jiang Liu
Currently pci_bind.c is used to maintain binding relationship between
ACPI and PCI devices. But it's broken when handling PCI hotplug events.
For the acpiphp driver, it's designed to update the binding relationship
when PCI hotplug event happens, but the implementation is
From: Yijing Wang
Changeset 2ed168eeb3edec029aa0eca5cb981d6376f931f9 "PCI: Fold stop and
remove helpers into their callers" has changed the behavior when
removing a PCI device.
Previously, for a PCI bridge device with secondary bus, dev->subordinate
is valid when calling PCI bus notification
From: Jiang Liu
Now ACPI devices are created before/destroyed after corresponding PCI
devices, and acpi_platform_notify/acpi_platform_notify_remove will
update PCI<->ACPI binding relationship when creating/destroying PCI
devices, there's no need to invoke bind/unbind callbacks from ACPI
device
When handling BUS_NOTIFY_ADD_DEVICE event for a PCI bridge device,
the notification handler can't hold reference count to the new PCI bus
because the device object for the new bus (pci_dev->subordinate->dev)
hasn't been initialized yet.
Split the registration of PCI bus device into two stages as
According to device model documentation, the way to create/destroy PCI
devices should be symmetric.
/**
* device_del - delete device from system.
* @dev: device.
*
* This is the first part of the device unregistration
* sequence. This removes the device from the lists we control
* from
Several PCI related drivers, such as pci_bind, pci_slot, acpiphp and
aerdrv, don't handle PCI device hotplug events, which may cause stale
state and even system crashes.
This patch set registers bus notification callbacks to update driver
states when PCI device hotplug happens.
V1->V2:
Hi,
* On Mon, Sep 10, 2012 at 09:41:49AM -0400, Paul Gortmaker
wrote:
On 12-09-09 03:25 PM, raghu.prabh...@gmail.com wrote:
From: Raghavendra D Prabhu
Errors like "do_IRQ: 0.84 No Irq handler for vector (irq -1)" have been reported
earlier filling up the console/logs. So this adds a
於 四，2012-09-13 於 21:41 -0700，H. Peter Anvin 提到：
> On 09/13/2012 08:45 PM, joeyli wrote:
> > Hi Peter,
> >
> > 於 四，2012-09-13 於 09:52 -0400，Peter Jones 提到：
> >> On Thu, 2012-09-13 at 16:10 +0800, joeyli wrote:
> >>
> >>> Do we have plan to create a new kobject add to /sys/firmware/efi for
> >>>
於 二，2012-09-11 於 15:23 +0800，lee joey 提到：
> From: Matthew Garrett
>
> The existing EFI variables code only supports variables of up to 1024
> bytes. This limitation existed in version 0.99 of the EFI
> specification,
> but was removed before any full releases. Since variables can now be
> larger
On Fri, Sep 14, 2012 at 07:17:12PM -0700, Jacob Sowles wrote:
> The first instance of my code calls debugfs_create_file and stores a
> pointer to the dentry of that directory. But when the second instance
> calls debugfs_create_file, the function returns NULL because that
> directory already
On 09/02/2012 09:59 PM, Rik van Riel wrote:
On 09/02/2012 06:12 AM, Gleb Natapov wrote:
On Thu, Aug 30, 2012 at 12:51:01AM +0530, Raghavendra K T wrote:
The idea of starting from next vcpu (source of yield_to + 1) seem to
work
well for overcomitted guest rather than using last boosted vcpu. We
Quoting Aristeu Rozanski (a...@ruivo.org):
> Tejun,
> On Thu, Sep 13, 2012 at 01:58:27PM -0700, Tejun Heo wrote:
> > memcg can be handled by memcg people and I can handle cgroup_freezer
> > and others with help from the authors. The problematic one is
> > blkio. If anyone is interested in
On Wed, 2012-09-12 at 16:36 -0700, Greg Kroah-Hartman wrote:
> From: Greg KH
>
> 3.4-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Alex Deucher
>
> commit 4f81f986761a7663db7d24d24cd6ae68008f1fc2 upstream.
>
> We need it in the
debugfs_create_dir, rather. Not debugfs_create_file.
On Fri, Sep 14, 2012 at 7:17 PM, Jacob Sowles wrote:
> The first instance of my code calls debugfs_create_file and stores a
> pointer to the dentry of that directory. But when the second instance
> calls debugfs_create_file, the function
The first instance of my code calls debugfs_create_file and stores a
pointer to the dentry of that directory. But when the second instance
calls debugfs_create_file, the function returns NULL because that
directory already exists, so it doesn't return the dentry that I need.
On Fri, Sep 14, 2012
On Fri, Sep 14, 2012 at 07:07:43PM -0700, Jacob Sowles wrote:
> Multiple instances of my code can be run simultaneously, and all
> instances use the same debugfs directory, so I need the path to the
> debugfs root directory so that I can use filp_open to get the dentry
> for that directory.
Multiple instances of my code can be run simultaneously, and all
instances use the same debugfs directory, so I need the path to the
debugfs root directory so that I can use filp_open to get the dentry
for that directory.
Jacob
On Fri, Sep 14, 2012 at 6:57 PM, Al Viro wrote:
> On Fri, Sep 14,
On Fri, Sep 14, 2012 at 06:49:01PM -0700, Jacob Sowles wrote:
> Is there an easy way to get the path to where debugfs is mounted? I
> found a function called debugfs_find_mountpoint(), which is exactly
> what I want, but it’s not exported, so I can’t use it. The only
> exported debugfs functions
Is there an easy way to get the path to where debugfs is mounted? I
found a function called debugfs_find_mountpoint(), which is exactly
what I want, but it’s not exported, so I can’t use it. The only
exported debugfs functions that I could find are the ones that create,
remove, etc.
Jacob
--
To
On Tue, 11 Sep 2012, Laura Abbott wrote:
> When a buffer is added to the LRU list, a reference is taken which is
> not dropped until the buffer is evicted from the LRU list. This is the
> correct behavior, however this LRU reference will prevent the buffer
> from being dropped. This means that the
On 2012-08-10 21:09 Jens Axboe Wrote:
>On 08/10/2012 01:46 PM, Jianpeng Ma wrote:
>> If process handled two or more devices,there will not be trace some
>> devices plug-operation.
>>
>> Signed-off-by: Jianpeng Ma
>> ---
>> block/blk-core.c | 16 +++-
>> 1 file changed, 15
On 09/14/2012 06:05 PM, John Stultz wrote:
Just wanted to send this out for initial review and comments.
Gah. And I forgot to add the [RFC] header to my mails to make this
clear. Hopefully this doesn't confuse anyone.
These are not yet ready for submission! Just wanting feedback on the
CLOCK_TICK_RATE is used to accurately caclulate exactly how
a tick will be at a given HZ.
This is useful, because while we'd expect NSEC_PER_SEC/HZ,
the underlying hardware will have some granularity limit,
so we won't be able to have exactly HZ ticks per second.
This slight error can cause
This isn't really something I want to submit, but shows what is
required to retain the refined jiffies clock calculation.
Instead of submitting this, which adds code that really
doesn't matter in most cases, I instead propose to not
submit this patch, and should anyone notice time quality
No one is using TICK_USEC_TO_NSEC, so kill it.
Cc: Catalin Marinas
Cc: Arnd Bergmann
Cc: Richard Cochran
Cc: Prarit Bhargava
Cc: Thomas Gleixner
Signed-off-by: John Stultz
---
include/linux/jiffies.h |6 --
1 file changed, 6 deletions(-)
diff --git a/include/linux/jiffies.h
Just wanted to send this out for initial review and comments.
During Linux Plumbers, Thomas mentioned that Arnd was still
wanting to kill off the derived values from the compile time
constant CLOCK_TICK_RATE, as it is a problem for unified zImage
on ARM.
One issue holding this back is that
Found one system one root bus hot remove get panic.
Panic happens when try to release hostbridge resource.
It turns out that resource get reject during put into resource tree
because of conflicts.
Also that resource parent pointer have random value.
That invalid value cause it pass through check
Should use struct pci_bus_resource instead of struct pci_host_bridge_window
Signed-off-by: Yinghai Lu
---
drivers/pci/bus.c |6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
Index: linux-2.6/drivers/pci/bus.c
===
---
when __ARCH_HAS_VGA_DEFAULT_DEVICE is not defined, aka EFIFB is not used,
for static path, vga_default setting is through vga_arbiter_add_pci_device.
and for x86 pci_fixup_video, will skip that.
because subsys_initcall(vga_arb_device_init) come first to call
vga_arbiter_add_pci_device.
for
On Wed, 2012-09-12 at 16:39 -0700, Greg Kroah-Hartman wrote:
> From: Greg KH
>
> 3.0-stable review patch. If anyone has any objections, please let me know.
>
> --
>
> From: Alex Deucher
>
> commit 4f81f986761a7663db7d24d24cd6ae68008f1fc2 upstream.
>
> We need it in the
> > The LP8788 has 13 ADC input selection.
> >
> > ADC selection:
> > Battery voltage, general ADC1 and so on.
> >
> > ADC result:
> > Result = MAX_VALUE * (raw + 0.5) / 4095 except ADC is the charger
> voltage
> > If the ADC input is the charger voltage,
> > Result = MAX_VALUE * (raw + 0.5) /
rval_tree.c:110
>> anon_vma_interval_tree_verify+0x81/0xa0()
>> [ 24.981765] Pid: 5928, comm: trinity-child37 Tainted: GW
>> 3.6.0-rc5-next-20120914-sasha-3-g7deb7fa-dirty #333
>> [ 24.985501] Call Trace:
>> [ 24.986345] [] ?
>> anon_vma_inte
On Fri, Sep 14, 2012 at 11:34:52PM +0200, Arnd Bergmann wrote:
> ARM is moving to stricter checks on readl/write functions,
> so we need to use the correct types everywhere.
Same comment as for eesox. const void __iomem * is not a problem on
x86, so it should not be a problem on ARM.
--
To
On Fri, Sep 14, 2012 at 11:34:49PM +0200, Arnd Bergmann wrote:
> ARM is moving to stricter checks on readl/write functions,
> so we need to use the correct types everywhere.
>
> Cc: Alan Cox
> Cc: Greg Kroah-Hartman
> Signed-off-by: Arnd Bergmann
Acked-by: Greg Kroah-Hartman
--
To
On Fri, Sep 14, 2012 at 11:34:50PM +0200, Arnd Bergmann wrote:
> ARM is moving to stricter checks on readl/write functions,
> so we need to use the correct types everywhere.
There's nothing wrong with const iomem pointers. If you think
otherwise, patch x86 not to use const in its accessor
On Wed, Sep 12, 2012 at 06:31:53PM -0400, Mikulas Patocka wrote:
> This is the patch based on this tree.
I've pulled this into the dm tree for now.
Alasdair
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More
On Thu, Jul 19, 2012 at 2:15 PM, Tejun Heo wrote:
> Hello,
>
> kthread_worker was introduced together with concurrency managed
> workqueue to serve workqueue users which need a special dedicated
> worker - e.g. RT scheduling. This is minimal queue / flush / flush
> all iterface on top of kthread
xed after each such update).
>
> This patch exposes the following warning:
>
> [ 24.977502] [ cut here ]
> [ 24.979089] WARNING: at mm/interval_tree.c:110
> anon_vma_interval_tree_verify+0x81/0xa0()
> [ 24.981765] Pid: 5928, comm: trinity-child37 Taint
ed after each such update).
>
> This patch exposes the following warning:
>
> [ 24.977502] [ cut here ]
> [ 24.979089] WARNING: at mm/interval_tree.c:110
> anon_vma_interval_tree_verify+0x81/0xa0()
> [ 24.981765] Pid: 5928, comm: trinity-child37 Taint
On 09/14/12 14:34, Arnd Bergmann wrote:
> ARM is moving to stricter checks on readl/write functions,
> so we need to use the correct types everywhere.
>
> Cc: David Brown
> Cc: Daniel Walker
> Cc: Bryan Huntsman
> Signed-off-by: Arnd Bergmann
I was going to send this patch out today. Thanks.
While building an allyesconfig for UML I received this error message(s):
drivers/mtd/nand/docg4.c: In function 'probe_docg4':
drivers/mtd/nand/docg4.c:1272:2: error: implicit declaration of function
'ioremap' [-Werror=implicit-function-declaration]
drivers/mtd/nand/docg4.c:1272:10: warning:
On Fri, Sep 14, 2012 at 02:53:11PM -0600, Bjorn Helgaas wrote:
> +cc Greg KH
>
> On Fri, Sep 14, 2012 at 2:44 PM, Thierry Reding
> wrote:
> > In order to keep pci_fixup_irqs() around after init (e.g. for hotplug),
> > mark it __devinit instead of __init. This requires the same change for
> > the
On Fri, Sep 14, 2012 at 6:34 PM, Arnd Bergmann wrote:
> ARM is moving to stricter checks on readl/write functions,
> so we need to use the correct types everywhere.
>
> This found a bug in mach-armadillo5x0.c, where we attempt mmio
> on the MXC_CCM_RCSR address that is currently defined to 0xc
>
From: Markus Mayer
Date: Thu, 13 Sep 2012 14:46:28 -0700
Subject: [PATCH] Fix segfault in dtc when empty input file is given.
Prior to this change, an empty input file would cause a segfault, because
yylloc had never been initialized. There was never any characters for the
lexer to match, so
The current arch_timer only support accessing through CP15 interface.
Add support for ARM processors that only support IO mapped register
interface. The memory mapped timer interface works with SPI
interrupts instead of PPI.
Signed-off-by: Rohit Vaswani
---
On some hardware, the timer deasserts the interrupt when a
new TVAL is written only when the enable bit is cleared.
Hence explicitly disable the timer and then program the
TVAL followed by enabling the timer.
If this order is not followed, there are chances that
you would not receive any timer
On Fri, Sep 14, 2012 at 1:53 AM, Bryan Wu wrote:
> The API function led_set_brightness() and __led_set_brightness will
> call .brightness_set() function provided by led class drivers. So
> .brightness_set() function will run in atomic context, which requires
> led class drivers use workqueue in
On Fri, Sep 14, 2012 at 3:10 PM, Peter Zijlstra wrote:
>
> I'm not seeing how it could be. Only ever looking at 1 other cpu
> (regardless which one) cannot be the same as checking 'all' of them.
Oh, you're right, it has that cpu_idle() in the loop too. So yeah, you
can't make it be even remotely
On Fri, Sep 14, 2012 at 11:02 PM, Mark Langsdorf
wrote:
> Fix patch follows. Do I need to submit it as a separate patch or is this
> sufficient?
You appear to have submitted it as a separate patch just now ;p
Will queue and push to libata-dev.git#upstream (and thus linux-next)
Jeff
--
To
On 15/09/12 07:34, Arnd Bergmann wrote:
> ARM is moving to stricter checks on readl/write functions,
> so we need to use the correct types everywhere.
>
> Cc: Hartley Sweeten
> Cc: Ryan Mallon
> Signed-off-by: Arnd Bergmann
Hi Arnd,
Do you want me to queue both this and my patch to move
On Fri, Sep 14, 2012 at 03:01:44PM -0700, Linus Torvalds wrote:
> On Fri, Sep 14, 2012 at 2:56 PM, Peter Zijlstra
> wrote:
> >
> > Both things change semantics, not looking at the entire package is new
> > too.
>
> Well, the "idle_buddy" thing on its own could be considered to be
> purely a
] [ cut here ]
[ 24.979089] WARNING: at mm/interval_tree.c:110
anon_vma_interval_tree_verify+0x81/0xa0()
[ 24.981765] Pid: 5928, comm: trinity-child37 Tainted: G W
3.6.0-rc5-next-20120914-sasha-3-g7deb7fa-dirty #333
[ 24.985501] C
On Fri, 2012-09-14 at 15:01 -0700, Linus Torvalds wrote:
> Sure, it doesn't take tsk_cpus_allowed() into account while setting up
> the cache (since it's not dynamic enough), but *assuming* the common
> case is that people let threads be on any of the cores of a package,
> it should be possible to
3.5.3 and older works, 3.6-rc not -> shared directories sometimes work,
sometimes not,
/etc/init.d/samba restart did help atleast once with 3.6-rc5,
hope this helps
thanks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Hello,
On Fri, Sep 14, 2012 at 06:03:16PM -0400, Dhaval Giani wrote:
> >
> > * Sort & unique when listing tasks. Even the documentation says it
> > doesn't happen but we have a good hunk of code doing it in
> > cgroup.c. I'm gonna rip it out at some point. Again, if you
> > don't
>
> * Sort & unique when listing tasks. Even the documentation says it
> doesn't happen but we have a good hunk of code doing it in
> cgroup.c. I'm gonna rip it out at some point. Again, if you
> don't like it, scream.
>
I think some userspace tools do assume the uniq bit. So if
On Fri, 14 Sep 2012 23:22:47 +0200
Petr Holasek wrote:
> Introduces new sysfs boolean knob /sys/kernel/mm/ksm/merge_nodes
I wonder if merge_across_nodes would be a better name.
> which control merging pages across different numa nodes.
> When it is set to zero only pages from the same node are
On Fri, Sep 14, 2012 at 2:56 PM, Peter Zijlstra wrote:
>
> Both things change semantics, not looking at the entire package is new
> too.
Well, the "idle_buddy" thing on its own could be considered to be
purely a caching thing.
Sure, it doesn't take tsk_cpus_allowed() into account while setting
On 09/14/2012 12:04 PM, Randy Dunlap wrote:
> On 09/14/2012 12:38 AM, Stephen Rothwell wrote:
>
>> Hi all,
>>
>> Changes since 201209013:
>>
>
>
>
> on i386:
>
> CONFIG_SATA_HIGHBANK=m
> # CONFIG_SATA_AHCI_PLATFORM is not set
>
> ERROR: "ahci_sdev_attrs" [drivers/ata/sata_highbank.ko]
On Fri, 2012-09-14 at 23:56 +0200, Peter Zijlstra wrote:
> On Fri, 2012-09-14 at 14:44 -0700, Linus Torvalds wrote:
> > On Fri, Sep 14, 2012 at 2:40 PM, Peter Zijlstra
> > wrote:
> > >
> > > The problem the patch is trying to address is not having to scan an
> > > entire package for idle cores
Hello, Vivek, Peter.
On Fri, Sep 14, 2012 at 11:14:47AM -0400, Vivek Goyal wrote:
> We don't have to start with 0%. We can keep a pool with dynamic % and
> launch all the virtual machines from that single pool. So nobody starts
> with 0%. If we require certain % for a machine, only then we look
On Fri, 2012-09-14 at 14:44 -0700, Linus Torvalds wrote:
> On Fri, Sep 14, 2012 at 2:40 PM, Peter Zijlstra
> wrote:
> >
> > The problem the patch is trying to address is not having to scan an
> > entire package for idle cores on every wakeup now that packages are
> > getting stupid big.
>
> No,
On Fri, Sep 14, 2012 at 9:29 PM, Tejun Heo wrote:
> On Fri, Sep 14, 2012 at 09:58:30AM -0400, Vivek Goyal wrote:
>> I am little concerned about above and wondering how systemd and libvirt
>> will interact and behave out of the box.
>>
>> Currently systemd does not create its own hierarchy under
On Thu, Sep 06, 2012 at 03:35:02PM -0700, Kent Overstreet wrote:
> Previously, there was bio_clone() but it only allocated from the fs bio
> set; as a result various users were open coding it and using
> __bio_clone().
Explain in the header the reasoning behind the change to dm-crypt so that
it
On Fri, Sep 14, 2012 at 11:40:43PM +0200, Peter Zijlstra wrote:
> Hmm, cute. What kind of machine did you test it on? Nikolay's machines
> look to be smallish AMD X6 or ancient Intel c2d (the patch will indeed
> have absolutely no effect on a dual core).
Yep, I took an X6 too. So it's a
On Fri, Sep 14, 2012 at 2:40 PM, Peter Zijlstra wrote:
>
> The problem the patch is trying to address is not having to scan an
> entire package for idle cores on every wakeup now that packages are
> getting stupid big.
No, it does something *else* too. That whole "left-right" logic to
(according
On Fri, Sep 14, 2012 at 2:27 PM, Borislav Petkov wrote:
>
> as Nikolay says below, we have a regression in 3.6 with pgbench's
> benchmark in postgresql.
>
> I was able to reproduce it on another box here and did a bisection run.
> It pointed to the commit below.
Ok. I guess we should just revert
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-ebsa110/core.c |8
arch/arm/mach-ebsa110/core.h | 12 ++--
2 files changed, 10 insertions(+), 10 deletions(-)
diff
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Barry Song
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-prima2/include/mach/uncompress.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Roland Stigge
Cc: Wolfram Sang
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-lpc32xx/common.c|8
arch/arm/mach-lpc32xx/include/mach/hardware.h |2 +-
On Fri, 2012-09-14 at 23:27 +0200, Borislav Petkov wrote:
>
> I was able to reproduce it on another box here and did a bisection run.
> It pointed to the commit below.
>
> And yes, reverting that commit fixes the issue here.
Hmm, cute. What kind of machine did you test it on? Nikolay's machines
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Imre Kaloz
Cc: Krzysztof Halasa
Cc: Lennert Buytenhek
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-iop32x/glantank.c |2 +-
arch/arm/mach-ixp4xx/common.c
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Alessandro Rubini
Cc: Linus Walleij
Cc: STEricsson
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-nomadik/board-nhk8815.c |3 +--
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Rob Herring
Cc: Lennert Buytenhek
Signed-off-by: Arnd Bergmann
---
arch/arm/mach-iop13xx/include/mach/iop13xx.h | 20 +---
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Dmitry Torokhov
Cc: linux-in...@vger.kernel.org
Signed-off-by: Arnd Bergmann
---
drivers/input/mouse/rpcmouse.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
This patch has a few small conflicts with stuff in linux-next, which
we have to sort out in arm-soc.
Cc: Linus Walleij
Cc: Russell King
Signed-off-by: Arnd Bergmann
---
Hello, Vivek.
On Fri, Sep 14, 2012 at 10:25:39AM -0400, Vivek Goyal wrote:
> On Thu, Sep 13, 2012 at 01:58:27PM -0700, Tejun Heo wrote:
>
> [..]
> > * blkio is the most problematic. It has two sub-controllers - cfq
> > and blk-throttle. Both are utterly broken in terms of hierarchy
> >
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: Florian Tobias Schandinat
Cc: linux-fb...@vger.kernel.org
Signed-off-by: Arnd Bergmann
---
drivers/video/da8xx-fb.c |8
1 file changed, 4 insertions(+), 4 deletions(-)
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
This patch is a bit ugly for shmobile, which is the only platform
that just uses integer literals all over the place, but I can't
see a better way to do this.
Cc: Magnus Damm
Cc: Kuninori
ARM is moving to stricter checks on readl/write functions,
so we need to use the correct types everywhere.
Cc: net...@vger.kernel.org
Cc: "David S. Miller"
Signed-off-by: Arnd Bergmann
---
drivers/net/ethernet/seeq/ether3.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff
1 - 100 of 1246 matches
Mail list logo
