Hi Stephen,
On Sat, Nov 3, 2012 at 12:19 AM, Stephen Rothwell wrote:
> On Fri, 2 Nov 2012 19:44:48 +0100 Geert Uytterhoeven
> wrote:
>> http://kisskb.ellerman.id.au/kisskb/buildresult/7458505/
>>
>> ccache: FATAL: Could not create
>>
On Wed, 14 Nov 2012, Ingo Molnar wrote:
> * Andrew Morton wrote:
> > On Wed, 14 Nov 2012 07:47:26 +0100 Ingo Molnar wrote:
> > > * Andrew Morton wrote:
> > > > On Wed, 14 Nov 2012 16:30:42 +1100 Stephen Rothwell
> > > > wrote:
> > > >
> > > > > News: next-20121115 (i.e. tomorrow) will be the
On 11/13/2012 04:30 PM, Michal Hocko wrote:
> Hi all,
> this patch set tries to make mem_cgroup_iter saner in the way how it
> walks hierarchies. css->id based traversal is far from being ideal as it
> is not deterministic because it depends on the creation ordering.
>
> Diffstat looks promising
On 11/13/2012 09:27 PM, Tejun Heo wrote:
> From bbf2566f9f4fc79ff3320e83cafb69533efc9ea0 Mon Sep 17 00:00:00 2001
> From: Tejun Heo
> Date: Tue, 13 Nov 2012 12:21:50 -0800
>
> Currently CGRP_CPUSET_CLONE_CHILDREN triggers ->post_clone(). Now
> that clone_children is cpuset specific, there's no
Thank you for commenting on my patch set.
(2012/11/14 11:31), Steven Rostedt wrote:
On Tue, 2012-11-13 at 18:03 -0800, David Sharp wrote:
On Tue, Nov 13, 2012 at 6:00 PM, Steven Rostedt wrote:
On Wed, 2012-11-14 at 10:36 +0900, Yoshihiro YUNOMAE wrote:
To merge the data like previous
On Tue, Nov 13, 2012 at 12:03:10AM -0800, Joe Perches wrote:
> On Tue, 2012-11-13 at 10:44 +0300, Dan Carpenter wrote:
> > I don't think this works as intended. '|' higher precedence than ?: so
> > the bitwize OR "0 | (val & STR_MOST)" is a no-op.
> >
> > I have re-written it to be more clear.
>
Hi Bryan,
On Tue, Nov 13, 2012 at 04:33:14PM -0800, Bryan Wu wrote:
> > +void led_trigger_rename_static(const char *name, struct led_trigger *trig)
> > +{
> > + /* new name must be on a temporary string to prevent races */
> > + BUG_ON(name == trig->name);
> > +
> > +
On 09.11.2012 15:20, Thierry Reding wrote:
> This commit adds the host1x node along with its children to the Tegra20
> DTSI. Furthermore the OF auxiliary data table is updated to have proper
> names assigned to the platform devices instantiated from the device
> tree. Moreover, the clocks required
2012/11/14 Mark Brown :
> On Wed, Nov 14, 2012 at 03:11:37PM +0800, Kevin Liu wrote:
>
>> - ret = regulator_set_voltage(host->vqmmc, 330, 330);
>> + ret = regulator_set_voltage(host->vqmmc, 270, 360);
>
> Should this be regulator_set_voltage_tol()?
On Wed 14-11-12 09:55:08, Li Zefan wrote:
> On 2012/11/13 23:30, Michal Hocko wrote:
> > Hi all,
> > this patch set tries to make mem_cgroup_iter saner in the way how it
> > walks hierarchies. css->id based traversal is far from being ideal as it
> > is not deterministic because it depends on the
This driver allows clk_get() failure, and still work without it.
This patch adds !IS_ERR(plgpio->clk) checking in plgpio_request() error path
so we only call clk_disable_unprepare() if clk_prepare_enable() is called.
Signed-off-by: Axel Lin
---
drivers/pinctrl/spear/pinctrl-plgpio.c |3 ++-
On Wed 14-11-12 17:17:51, Glauber Costa wrote:
[...]
> Why can't we reuse the scheduler iterator and move it to kernel/cgroup.c?
I do not care much about the internal implementation of the core
iterators. Those implemented by Tejun make sense to me. I just want to
get rid of css->id based ones.
On Wed, Nov 14, 2012 at 04:36:28PM +0800, Kevin Liu wrote:
> 2012/11/14 Mark Brown :
> > Should this be regulator_set_voltage_tol()? Otherwise it'd be good to
> > explain where the numbers come from.
> In SD physical layer spec 3.01 chapter 6.6.1, the threshold level for
> voltage range is
On Tue, Nov 13, 2012 at 08:36:00PM +0800, Shan Wei wrote:
> Steffen Klassert said, at 2012/11/13 18:48:
> >
> > Ok, so please add a commit message to describe your changes.
> >
> > Thanks.
> >
>
> [PATCH v5] net: xfrm: use __this_cpu_read per-cpu helper
>
> this_cpu_ptr/this_cpu_read is
Commit-ID: 411279658adf6a4f5bb25ec032a39ae905bcf234
Gitweb: http://git.kernel.org/tip/411279658adf6a4f5bb25ec032a39ae905bcf234
Author: Namhyung Kim
AuthorDate: Fri, 9 Nov 2012 14:58:49 +0900
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 9 Nov 2012 16:50:18 -0300
perf annotate:
Add a basic balloon driver to take advantage of the dynamic memory
management functionality supported on Windows hosts. Windows requires
the guests to support both memory hot add as well as ballooning. In this patch
we are adding the basic balloon driver. Memory hot add will be added in a
Add the basic balloon driver. Windows hosts dynamically manage the guest
memory allocation via a combination memory hot add and ballooning. Memory
hot add is used to grow the guest memory upto the maximum memory that can be
allocatted to the guest. Ballooning is used to both shrink as well as
Hi,
I'm trying to get Linux + KMS Framebuffer up and running on a board that has
this hardware configuration:
- CPU: Intel Atom N2600
- Chipset: Intel NM10
- Integrated graphics system: Intel GMA 3600
- LCD Panel with LVDS controller (LCD resolution is 800x480, 18 bpp, 60Hz)
I have
On Wed, Nov 14, 2012 at 10:35:31AM +0200, Terje Bergström wrote:
> On 09.11.2012 15:20, Thierry Reding wrote:
> > This commit adds the host1x node along with its children to the Tegra20
> > DTSI. Furthermore the OF auxiliary data table is updated to have proper
> > names assigned to the platform
What do you guys think about this mprotect() optimization?
Thanks,
Ingo
--
Ingo Molnar (1):
mm: Optimize the TLB flush of sys_mprotect() and change_protection()
users
Peter Zijlstra (1):
sched, numa, mm: Count WS scanning against present PTEs, not virtual
memory ranges
From: Peter Zijlstra
By accounting against the present PTEs, scanning speed reflects the
actual present (mapped) memory.
For this we modify mm/mprotect.c::change_protection() to return the
number of ptes modified. (No change in functionality.)
Suggested-by: Ingo Molnar
Signed-off-by: Peter
Reuse the NUMA code's 'modified page protections' count that
change_protection() computes and skip the TLB flush if there's
no changes to a range that sys_mprotect() modifies.
Given that mprotect() already optimizes the same-flags case
I expected this optimization to dominantly trigger on
This commit adds System MMU nodes to DT of Exynos SoCs.
Signed-off-by: KyongHo Cho
---
.../devicetree/bindings/arm/samsung/system-mmu.txt | 42 ++
arch/arm/boot/dts/exynos4210.dtsi | 96 ++
arch/arm/boot/dts/exynos4x12.dtsi | 124
On Tue 13-11-12 08:14:42, Tejun Heo wrote:
> On Tue, Nov 13, 2012 at 04:30:36PM +0100, Michal Hocko wrote:
> > @@ -1063,8 +1063,8 @@ struct mem_cgroup *mem_cgroup_iter(struct mem_cgroup
> > *root,
> >struct mem_cgroup *prev,
> >
The current exynos-iommu(System MMU) driver does not work autonomously
since it is lack of support for power management of peripheral blocks.
For example, MFC device driver must ensure that its System MMU is disabled
before MFC block is power-down not to invalidate IOTLB in the System MMU
when I/O
Touching some System MMU needs its master devices' clock to be enabled
before. This commit adds clk_ops.set_parent of gating clocks of System
MMU to ensure gating clocks of System MMU's mater devices are enabled
when enabling gating clocks of System MMU.
Signed-off-by: KyongHo Cho
---
This commit enhances power management of System MMU and its client
devices with the following changes:
- Each System MMU device becomes the parent device of its client
device while probe(). Thus, exynos-iommu driver must be initialized
before client devices.
- System MMU driver does not
This removes System MMU initialization from arch/arm/mach-exynos/
to move them to DT and the exynos-iommu driver except gating clock
definitions.
Signed-off-by: KyongHo Cho
---
arch/arm/mach-exynos/Kconfig | 5 -
arch/arm/mach-exynos/Makefile | 1 -
On 11/09/2012 01:10 PM, Akinobu Mita wrote:
It is unnecessary to disable preemption explicitly while calling
copy_highpage(). Because copy_highpage() will do it again through
kmap_atomic/kunmap_atomic.
Signed-off-by: Akinobu Mita
Cc: dri-de...@lists.freedesktop.org
Cc: David Airlie
---
2012/11/14 Mark Brown :
> On Wed, Nov 14, 2012 at 04:36:28PM +0800, Kevin Liu wrote:
>> 2012/11/14 Mark Brown :
>
>> > Should this be regulator_set_voltage_tol()? Otherwise it'd be good to
>> > explain where the numbers come from.
>
>> In SD physical layer spec 3.01 chapter 6.6.1, the threshold
On Tuesday 13 November 2012 22:34:21 Alan Cox wrote:
> On Tue, 13 Nov 2012 23:08:07 +0100
>
> Dimitar Popov wrote:
> > Hi all,
> >
> > I have an old computer with motherboard ASUS SK8N with AMD Opteron 148 and
> > 4 GiB of DDR400. There is an onboard SATA Promise RAID controller working
> > in
On Tue, 13 Nov 2012, Jens Axboe wrote:
> Date: Tue, 13 Nov 2012 09:42:58 -0700
> From: Jens Axboe
> To: Lukas Czerner
> Cc: linux-kernel@vger.kernel.org, linux-fsde...@vger.kernel.org,
> jmo...@redhat.com, a...@linux-foundation.org
> Subject: Re: [PATCH v3] loop: Limit the number of
On 14 November 2012 14:07, Axel Lin wrote:
> This driver allows clk_get() failure, and still work without it.
> This patch adds !IS_ERR(plgpio->clk) checking in plgpio_request() error path
> so we only call clk_disable_unprepare() if clk_prepare_enable() is called.
>
> Signed-off-by: Axel Lin
Am 14.11.2012 03:47, schrieb Alexander Holler:
Hello,
Am 13.11.2012 22:42, schrieb Jean Delvare:
Plus you don't address the main issues. Your syntax gives you no way to
support two i2c-tiny-usb adapters with different chips at a specific
address. The sysfs interface supports such a setup.
On 11/14/2012 03:22 AM, Julius Werner wrote:
> Many cpuidle drivers measure their time spent in an idle state by
> reading the wallclock time before and after idling and calculating the
> difference. This leads to erroneous results when the wallclock time gets
> updated by another processor in the
On Nov 14, 2012, at 8:57 AM, Kevin Liu wrote:
> 2012/11/14 Mark Brown :
>> On Wed, Nov 14, 2012 at 04:36:28PM +0800, Kevin Liu wrote:
>>> 2012/11/14 Mark Brown :
>>
Should this be regulator_set_voltage_tol()? Otherwise it'd be good to
explain where the numbers come from.
>>
>>> In
SPEAr SoC's don't do anything in clk_prepare() of plgpio driver, so there is no
need to call this routine multiple times. Just call it once at probe.
Signed-off-by: Viresh Kumar
---
Hi Linus,
This patch is rebased over https://lkml.org/lkml/2012/11/14/220
On Wednesday, November 14, 2012 02:23:51 AM Moore, Robert wrote:
> Rafael,
>
> I sounds like with a few changes, we can enhance this mechanism to
> be more useful to you and others. Some comments below. I need to look
> at the code in question a bit more, but I see no insurmountable issues.
To lock the entire system from parallel oom killing, it's possible to
pass in a zonelist with all zones rather than using
for_each_populated_zone() for the iteration. This obsoletes
try_set_system_oom() and clear_system_oom() so that they can be removed.
Cc: KAMEZAWA Hiroyuki
Cc: KOSAKI
out_of_memory() is a globally defined function to call the oom killer.
x86, sh, and powerpc all use a function of the same name within file
scope in their respective fault.c unnecessarily. Inline the functions
into the pagefault handlers to clean the code up.
Cc: Ingo Molnar
Cc: "H. Peter
With hotpluggable and memoryless nodes, it's possible that node 0 will
not be online, so use the first online node's zonelist rather than
hardcoding node 0 to pass a zonelist with all zones to the oom killer.
Cc: Greg Kroah-Hartman
Signed-off-by: David Rientjes
---
drivers/tty/sysrq.c |3
于 2012年11月14日 05:22, Marcelo Tosatti 写道:
> On Thu, Nov 01, 2012 at 01:55:04PM +0800, zhangyanfei wrote:
>> 于 2012年10月31日 17:01, Hatayama, Daisuke 写道:
>>>
>>>
-Original Message-
From: kexec-boun...@lists.infradead.org
[mailto:kexec-boun...@lists.infradead.org] On Behalf Of
Inspect the return value of get_user() and return -EFAULT on error.
Signed-off-by: Kumar Amit Mehta
---
drivers/staging/dgrp/dgrp_tty.c |9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/dgrp/dgrp_tty.c b/drivers/staging/dgrp/dgrp_tty.c
index
out_of_memory() will already cause current to schedule if it has not been
killed, so doing it again in pagefault_out_of_memory() is redundant.
Remove it.
Cc: KAMEZAWA Hiroyuki
Cc: KOSAKI Motohiro
Cc: Michal Hocko
Signed-off-by: David Rientjes
---
mm/oom_kill.c |1 -
1 files changed, 0
From: Peter Zijlstra
This will be used by three kinds of purposes:
- to optimize mprotect()
- to speed up working set scanning for working set areas that
have not been touched
- to more accurately scan per real working set
No change in functionality from this patch.
Suggested-by: Ingo
Ok, people suggested to split out the change_protection() modification
into a third patch.
This series implements an mprotect() optimization that also
helps improve the quality of working set scanning:
- working set scanning gets faster
- we can scan with a touched-page rate, instead of
Reuse the NUMA code's 'modified page protections' count that
change_protection() computes and skip the TLB flush if there's
no changes to a range that sys_mprotect() modifies.
Given that mprotect() already optimizes the same-flags case
I expected this optimization to dominantly trigger on
From: Peter Zijlstra
By accounting against the present PTEs, scanning speed reflects the
actual present (mapped) memory.
Suggested-by: Ingo Molnar
Signed-off-by: Peter Zijlstra
Cc: Linus Torvalds
Cc: Andrew Morton
Cc: Peter Zijlstra
Cc: Andrea Arcangeli
Cc: Rik van Riel
Cc: Mel Gorman
On Tuesday 13 November 2012 19:28:46 Cyrill Gorcunov wrote:
> On Tue, Nov 13, 2012 at 03:02:22PM +, Tvrtko Ursulin wrote:
> > Perhaps there could be a different way, where you could use additional
> > space only when it is actually used at runtime. But as I said, I am not
> > following
On Mon, 12 Nov 2012, Per Forlin wrote:
> Add support to extract device name from device tree blob.
> If the property "dev-name" is set in the DTS this name will
> be used when creating the device.
> The auxdata_lookup has precedence and will override
> the "dev-name" property.
>
> Adding support
On Wednesday, November 14, 2012 10:18:46 AM Rafael J. Wysocki wrote:
> On Wednesday, November 14, 2012 02:23:51 AM Moore, Robert wrote:
> > Rafael,
> >
> > I sounds like with a few changes, we can enhance this mechanism to
> > be more useful to you and others. Some comments below. I need to look
Currently, kdump just makes all the logical processors leave VMX operation by
executing VMXOFF instruction, so any VMCSs active on the logical processors may
be corrupted. But, sometimes, we need the VMCSs to debug guest images contained
in the host vmcore. To prevent the corruption, we should
crash_clear_loaded_vmcss is added to VMCLEAR vmcss loaded on all
cpus. And when loading kvm_intel module, the function pointer will be
made valid.
The percpu variable vmclear_skipped is added to flag the case that
if loaded_vmcss_on_cpu list is being modified while the machine crashes
and doing
Signed-off-by: Zhang Yanfei
---
arch/x86/kvm/vmx.c | 32
1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index 4ff0ab9..029ec7b 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -41,6 +41,7 @@
On Wed, Nov 14, 2012 at 09:20:51AM +, Tvrtko Ursulin wrote:
> On Tuesday 13 November 2012 19:28:46 Cyrill Gorcunov wrote:
> > On Tue, Nov 13, 2012 at 03:02:22PM +, Tvrtko Ursulin wrote:
> > > Perhaps there could be a different way, where you could use additional
> > > space only when it is
When regulator_register fails and exits through the scrub path the
regulator_put function was called whilst holding the
regulator_list_mutex, causing deadlock.
This patch adds a private version of the regulator_put function which
can be safely called whilst holding the mutex, replacing the
On Wed, 14 Nov 2012 00:38:52 +0100, Alexander Holler wrote:
> Am 13.11.2012 22:42, schrieb Jean Delvare:
> > Question is, what will you do the day someone wants to instantiate a
> > device for which the default probing mechanism doesn't work?
>
> Do you solve all problems you and others might
The flogr instruction scans a bitmap starting from the leftmost bit.
Implement support for these bitops. This could be useful to scan
bitmaps like an interrupt vector set by the hardware starting
at the leftmost bit.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/bitops.h | 81
Signed-off-by: Jan Glauber
---
drivers/gpu/vga/Kconfig | 2 +-
include/video/vga.h | 2 ++
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/vga/Kconfig b/drivers/gpu/vga/Kconfig
index f348388..29437ea 100644
--- a/drivers/gpu/vga/Kconfig
+++ b/drivers/gpu/vga/Kconfig
Signed-off-by: Jan Glauber
---
arch/s390/Kconfig | 56 +--
1 file changed, 50 insertions(+), 6 deletions(-)
diff --git a/arch/s390/Kconfig b/arch/s390/Kconfig
index 5dba755..e3dd4aec 100644
--- a/arch/s390/Kconfig
+++ b/arch/s390/Kconfig
@@
CLP instructions are used to query the firmware about detected PCI
functions, the attributes of those functions and to enable or disable
a PCI function. The CLP interface is the equivalent to a PCI bus scan.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/clp.h | 28
Add some s390 specific sysfs attributes to the PCI device directory.
The following attributes are introduced:
- function_id (PCI function ID)
- function_handle (PCI function handle)
- pchid (PCI channel ID)
- pfgid (PCI function group ID aka PCI root complex)
Signed-off-by: Jan Glauber
---
Add SCLP PCI configure/deconfigure and implement a PCI hotplug
controller (s390_pci_hpc). The hotplug controller creates a slot
for every PCI function in stand-by or configured state. The PCI
functions are named after the PCI function ID (fid). By writing to
the power attribute in
Add CHSC store-event-information support for PCI (notfication type 2)
and report error and availability events to the PCI architecture layer.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/pci.h | 4 ++
arch/s390/pci/Makefile | 3 +-
arch/s390/pci/pci_event.c | 93
Support PCI adapter interrupts using the Single-IRQ-mode. Single-IRQ-mode
disables an adapter IRQ automatically after delivering it until the SIC
instruction enables it again. This is used to reduce the number of IRQs
for streaming workloads.
Up to 64 MSI handlers can be registered per PCI
Add DMA IOMMU support using 4K page table entries. Implement dma_map_ops.
Signed-off-by: Jan Glauber
---
arch/s390/include/asm/dma-mapping.h | 76 ++
arch/s390/include/asm/dma.h | 19 +-
arch/s390/include/asm/pci.h | 21 ++
arch/s390/include/asm/pci_dma.h | 196
On Tue, 6 Nov 2012, Shaohua Li wrote:
> On Wed, Oct 24, 2012 at 09:13:56AM +0800, Shaohua Li wrote:
> > On Tue, Oct 23, 2012 at 09:41:00AM -0400, Rik van Riel wrote:
> > > On 10/23/2012 01:51 AM, Shaohua Li wrote:
> > >
> > > >I have no strong point against the global state method. But I'd agree
On Wednesday, November 14, 2012 09:08:28 AM Huang Ying wrote:
> On Tue, 2012-11-13 at 11:10 -0500, Alan Stern wrote:
> > On Tue, 13 Nov 2012, Huang Ying wrote:
> >
> > > > This is not quite right. Consider a device that is in runtime suspend
> > > > when a system sleep starts. When the system
Hi,
this patchset based on 3.7-rc4 aims at adding PCI(e) support to the
System z (s390) architecture. PCI is currently not available on s390,
so this is early prototype code.
I'm posting in the hope to get some feedback and direction on the more humble
aspects of it.
Patches 01-05 are only
Add PCI support for s390, (only 64 bit mode is supported by hardware):
- PCI facility tests
- PCI instructions: pcilg, pcistg, pcistb, stpcifc, mpcifc, rpcit
- map readb/w/l/q and writeb/w/l/q to pcilg and pcistg instructions
- pci_iomap implementation
- memcpy_fromio/toio
- pci_root_ops using
On Tue, Nov 13, 2012 at 09:51:39PM +0100, Rafael J. Wysocki wrote:
> Updated series, taking the Mika's feedback into account, follows. There are
> bug fixes in [1/3], [2/3] is unchanged and the new [3/3] is a replacement,
> done
> in a different way because of some ACPICA limitations I didn't
On Wednesday 14 November 2012 13:38:49 Cyrill Gorcunov wrote:
> On Wed, Nov 14, 2012 at 09:20:51AM +, Tvrtko Ursulin wrote:
> > On Tuesday 13 November 2012 19:28:46 Cyrill Gorcunov wrote:
> > > On Tue, Nov 13, 2012 at 03:02:22PM +, Tvrtko Ursulin wrote:
> > > > Perhaps there could be a
Hi Omar,
On Wed, Nov 14, 2012 at 4:34 AM, Omar Ramirez Luna wrote:
> Use runtime PM functionality interfaced with hwmod enable/idle
> functions, to replace direct clock operations and sysconfig
> handling.
>
> Dues to reset sequence, pm_runtime_put_sync must be used, to avoid
> possible
On Wed, Nov 14, 2012 at 09:50:55AM +, Tvrtko Ursulin wrote:
> > > You could not use a pointer and then allocate your buffers on the check
> > > point operation, freeing on restore?
> >
> > The problem is not allocating the memory itself but rather the time when the
> > information needed (ie
On Thursday, November 08, 2012 12:07:54 PM Alan Stern wrote:
> On Thu, 8 Nov 2012, Rafael J. Wysocki wrote:
[...]
I'd like to revisit this for a while if you don't mind.
> Your revised patch does do the job, except for a few problems.
> Namely, while local_pci_probe() and pci_device_remove()
On Wed, Nov 14, 2012 at 09:39:31AM +, Charles Keepax wrote:
> When regulator_register fails and exits through the scrub path the
> regulator_put function was called whilst holding the
> regulator_list_mutex, causing deadlock.
Applied, thanks.
> Cc: Laxman Dewangan
Please avoid doing this.
On Tue, Nov 13, 2012 at 03:41:02PM -0800, David Rientjes wrote:
> On Tue, 13 Nov 2012, Andy Lutomirski wrote:
>
> > It just happened again.
> >
> > $ grep -E "compact_|thp_" /proc/vmstat
> > compact_blocks_moved 8332448774
> > compact_pages_moved 21831286
> > compact_pagemigrate_failed 211260
>
On Wednesday, November 14, 2012 11:52:32 AM Mika Westerberg wrote:
> On Tue, Nov 13, 2012 at 09:51:39PM +0100, Rafael J. Wysocki wrote:
> > Updated series, taking the Mika's feedback into account, follows. There are
> > bug fixes in [1/3], [2/3] is unchanged and the new [3/3] is a replacement,
>
On Wed, 14 Nov 2012, Dave Jones wrote:
> On Tue, Nov 13, 2012 at 07:50:25PM -0800, Hugh Dickins wrote:
>
> > Originally I was waiting to hear further from Dave; but his test
> > machine was giving trouble, and it occurred to me that, never mind
> > whether he says he has hit it again, or he
On 14/11/12 07:47, Mark Brown wrote:
If consumers wish to set voltages based on a tolerance it stands to reason
that they will also want to query for support in the same manner.
Signed-off-by: Mark Brown
Acked-by: Liam Girdwood
--
To unsubscribe from this list: send the line "unsubscribe
On Wednesday 14 November 2012 13:58:12 Cyrill Gorcunov wrote:
> On Wed, Nov 14, 2012 at 09:50:55AM +, Tvrtko Ursulin wrote:
> > > > You could not use a pointer and then allocate your buffers on the
> > > > check
> > > > point operation, freeing on restore?
> > >
> > > The problem is not
Hi all,
Our QA noticed a regression in one of our i915/GEM testcases in 3.7:
https://bugs.freedesktop.org/show_bug.cgi?id=56859
Direct link to dmesg of the machine:
https://bugs.freedesktop.org/attachment.cgi?id=70052 Note that the
machine is 32bit, which seems to be important since Chris
On Wed 14-11-12 09:20:03, KAMEZAWA Hiroyuki wrote:
> (2012/11/14 0:30), Michal Hocko wrote:
[...]
> > @@ -1096,30 +1096,64 @@ struct mem_cgroup *mem_cgroup_iter(struct
> > mem_cgroup *root,
> > mz = mem_cgroup_zoneinfo(root, nid, zid);
> > iter =
On 11/14/2012 10:46 AM, Cyrill Gorcunov wrote:
> On Tue, Nov 13, 2012 at 02:38:08PM -0800, Andrew Morton wrote:
>> On Tue, 13 Nov 2012 12:00:32 +0400
>> Cyrill Gorcunov wrote:
>>
Dumb question: do we really need inotify_inode_mark.fhandle at all?
What prevents us from assembling this
On Wed, Nov 14, 2012 at 02:10:50PM +0400, Pavel Emelyanov wrote:
> >>
> >> How can the c/r restore code reestablish the inode data if the dentry
> >> isn't there any more?
> >
> > By "deleted" I meant deleted from dcache, thus when we call for
> > open_by_handle_at with fhandle, the kernel
On 11/14/2012 02:08 PM, Tvrtko Ursulin wrote:
> On Wednesday 14 November 2012 13:58:12 Cyrill Gorcunov wrote:
>> On Wed, Nov 14, 2012 at 09:50:55AM +, Tvrtko Ursulin wrote:
> You could not use a pointer and then allocate your buffers on the
> check
> point operation, freeing on
On 14.11.2012 10:49, Thierry Reding wrote:
> Can you find out how the host1x clock is setup without this change? I
> was told that freezes can occur when you try to access the registers
> without the host1x clock being enabled. However, the host1x driver
> should take care to properly setup the
On Wed, Nov 07, 2012 at 11:19:28AM -0800, Sukadev Bhattiprolu wrote:
SNIP
> +struct perf_pmu_events_attr {
> + struct device_attribute attr;
> + u64 id;
> +};
> +
> +extern ssize_t power_events_sysfs_show(struct device *dev,
> + struct device_attribute *attr,
On Wed, Nov 07, 2012 at 11:19:52AM -0800, Sukadev Bhattiprolu wrote:
>
> From bafc551c31ce23c1cba0b75d23de6c46aba90f26 Mon Sep 17 00:00:00 2001
> From: Sukadev Bhattiprolu
> Date: Tue, 6 Nov 2012 16:30:28 -0800
> Subject: [PATCH 4/4] perf: Create a sysfs entry for Power event format
>
> Create
The following warnings fixed.
- WARNING: braces {} are not necessary for any arm of this statement
- WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_connector.c |8 +++-
1 file changed, 3 insertions(+), 5
The following error fixed.
- ERROR: do not initialise statics to 0 or NULL
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_crtc.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/omapdrm/omap_crtc.c
b/drivers/staging/omapdrm/omap_crtc.c
The following warning fixed.
- WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_crtc.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_crtc.c
The following warnings fixed.
- WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_drv.c | 36 ++--
1 file changed, 14 insertions(+), 22 deletions(-)
diff --git
The following errors fixed.
- ERROR: "foo * bar" should be "foo *bar"
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_drv.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_drv.h
b/drivers/staging/omapdrm/omap_drv.h
index
The following warnings fixed.
- WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_drv.h |8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_drv.h
The following warnings fixed.
- WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_encoder.c |7 +++
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_encoder.c
The following warnings fixed.
- WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_fb.c | 11 +--
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_fb.c
The following error fixed.
- ERROR: "foo ** bar" should be "foo **bar"
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_gem.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/omapdrm/omap_gem.c
b/drivers/staging/omapdrm/omap_gem.c
index
The following warnings fixed.
- WARNING: braces {} are not necessary for single statement blocks
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_gem.c | 38 ++--
1 file changed, 15 insertions(+), 23 deletions(-)
diff --git
The following errors fixed.
- ERROR: space prohibited after that '!' (ctx:BxW)
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/omapdrm/omap_gem.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/omapdrm/omap_gem.c
1 - 100 of 1642 matches
Mail list logo
