On Sat, Dec 22, 2012 at 11:23:25AM +0100, Stefan Hasko wrote:
> Fixed different size cast warnings in function setup_efi_pci
>
> Signed-off-by: Stefan Hasko
You might want to add the actual compiler warnings to the commit
message:
arch/x86/boot/compressed/eboot.c: In function ‘setup_efi_pci’:
a
On Wed, 2012-12-26 at 13:22 +0900, Namjae Jeon wrote:
> 2012/12/26, Joe Perches :
> > On Wed, 2012-12-26 at 11:10 +0900, Namjae Jeon wrote:
> >> 2012/12/26, Jaegeuk Kim :
> >> > Could you make them follow the file system convention?
> >> > Something like "F2FS: blah blah~".
> >> Yes, I agree.
> >>
On Sun, 2012-12-23 at 13:34 -0800, Christian Kujau wrote:
> On Sat, 22 Dec 2012 at 16:28, Maciej Rutecki wrote:
> > Got during suspend to disk:
>
> I got a similar message on a powerpc G4 system, right after bootup (no
> suspend involved):
>
> http://nerdbynature.de/bits/3.8.0-rc1/
>
> [
On Thu, 2012-12-20 at 19:32 +0100, Frederic Weisbecker wrote:
> If we want to stop the tick further idle, we need to be
> able to account the cputime without using the tick.
>
> Virtual based cputime accounting solves that problem by
> hooking into kernel/user boundaries.
>
> However implementing
max8997_set_voltage_ldobuck_time_sel() returns 0 for all LDOs.
Thus remove set_voltage_time_sel setting for max8997_ldo_ops.
max8997_set_voltage_ldobuck_time_sel() is only used for max8997_buck_ops now,
rename it to max8997_set_voltage_buck_time_sel().
Signed-off-by: Axel Lin
---
drivers/regula
Signed-off-by: Axel Lin
---
drivers/regulator/max8997.c | 76 ++-
1 file changed, 18 insertions(+), 58 deletions(-)
diff --git a/drivers/regulator/max8997.c b/drivers/regulator/max8997.c
index 57e8907..c30424a 100644
--- a/drivers/regulator/max8997.c
+++
Hi Tang,
2012/12/26 16:39, Tang Chen wrote:
> On 12/26/2012 02:53 PM, Yasuaki Ishimatsu wrote:
>> Hi Tang,
>>
>> I don't think it can work well.
>> The patch gets memory range of hotpluggable memory by
>> acpi_numa_memory_affinity_init(). But it too late.
>> For example, if we use log_buf_len boot
On Tue, 2012-12-25 at 22:32 -0800, David Rientjes wrote:
> This creates quite a few build failures on auto-latest:
>
> arch/x86/built-in.o: In function `hpet_setup_msi_irq':
> hpet.c:(.text+0x34638): undefined reference to `arch_setup_hpet_msi'
> hpet.c:(.text+0x34651): undefined reference to `dest
2012/12/26, Joe Perches :
> On Wed, 2012-12-26 at 13:22 +0900, Namjae Jeon wrote:
>> 2012/12/26, Joe Perches :
>> > On Wed, 2012-12-26 at 11:10 +0900, Namjae Jeon wrote:
>> >> 2012/12/26, Jaegeuk Kim :
>> >> > Could you make them follow the file system convention?
>> >> > Something like "F2FS: blah
The commit bf4d1b5ddb78f86078ac6ae0415802d5f0c68f92 introduces
a lock in the cpuidle_get_cpu_driver function. This function
is used in the idle_call function.
The problem is the contention with a large number of cpus because
they try to access the idle routine at the same time.
The lock could be
On 12/26/2012 03:06 PM, Wanlong Gao wrote:
> Add a cpu notifier to virtio-net, so that we can reset the
> virtqueue affinity if the cpu hotplug happens. It improve
> the performance through enabling or disabling the virtqueue
> affinity after doing cpu hotplug.
Hi Wanlong:
Thanks for looking at t
Hi Terje,
I applied your patches on top of upstream 1224 kernel. Then I read the
codes. So here is my review comments(I use "git diff" to print out,
check below). I admit it's easy for me to not need to find the
corresponding lines in your 8 patch mails, but I've no idea whether it
is ok for you.
On 12/26/2012 06:06 PM, Jason Wang wrote:
> On 12/26/2012 03:06 PM, Wanlong Gao wrote:
>> Add a cpu notifier to virtio-net, so that we can reset the
>> virtqueue affinity if the cpu hotplug happens. It improve
>> the performance through enabling or disabling the virtqueue
>> affinity after doing cp
On 2012/11/29 5:34, Tejun Heo wrote:
> cpuset_can_attach() prepare global variables cpus_attach and
> cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
> There is no reason to prepare in cpuset_can_attach(). The same
> information can be accessed from cpuset_attach().
>
> Move t
Hi folks,
I get a lot of strange messages in /var/log/kern.log:
:
Dec 26 08:01:58 dpcl082 kernel: <>[1862186]xc_c 000:00 RO oro ne
ig<>1862143]hb5110 ciae->-23862114]xc_c 000:00 RO oro ne ig<>1862186]hb5110
ciae->-231862075]xc_c 000:00 RO oro ne ig<>1862140]hb5110
ciae->-2<>[1872078]xc_c 000:0
Forgot to CC: possibly interested people, sorry.
-- Forwarded message --
From: Fabio Coatti
Date: 2012/12/24
Subject: usb issues with 3.6.X and 3.7.X
To: linux-kernel@vger.kernel.org
Hi all,
I'm experiencing some usb-related issues with recent kernels (3.6.7
and 3.7.1 at least.
On Wed, Dec 26, 2012 at 03:06:54PM +0800, Wanlong Gao wrote:
> Add a cpu notifier to virtio-net, so that we can reset the
> virtqueue affinity if the cpu hotplug happens. It improve
> the performance through enabling or disabling the virtqueue
> affinity after doing cpu hotplug.
>
> Cc: Rusty Russ
On Wed, 26 Dec 2012, David Woodhouse wrote:
> > arch/x86/built-in.o: In function `hpet_setup_msi_irq':
> > hpet.c:(.text+0x34638): undefined reference to `arch_setup_hpet_msi'
> > hpet.c:(.text+0x34651): undefined reference to `destroy_irq'
> > arch/x86/built-in.o: In function `hpet_msi_capability
On 2012/11/29 5:34, Tejun Heo wrote:
> Hello, guys.
>
> Depending on cgroup core locking - cgroup_mutex - is messy and makes
> cgroup prone to locking dependency problems. The current code already
> has lock dependency loop - memcg nests get_online_cpus() inside
> cgroup_mutex. cpuset the other
On Wed, Dec 26, 2012 at 7:22 PM, Zhouping Liu wrote:
> Hello everyone,
>
> The latest mainline(637704cbc95c) would trigger the following error when the
> system was under
> some pressure condition(in my testing, I used oom01 case inside LTP test
> suite to trigger the issue):
>
> [ 5462.920151]
(cc'ing Rusty, hi!)
Hello, Li.
On Wed, Dec 26, 2012 at 06:20:11PM +0800, Li Zefan wrote:
> On 2012/11/29 5:34, Tejun Heo wrote:
> > cpuset_can_attach() prepare global variables cpus_attach and
> > cpuset_attach_nodemask_{to|from} which are used by cpuset_attach().
> > There is no reason to prepar
Hi Doug,
On Fri, Dec 21, 2012 at 10:35 PM, Doug Anderson wrote:
> Vivek,
>
> Nothing really serious below and things look good to me, but figured
> I'd put a few nits in (sorry!).
>
>
> On Fri, Dec 21, 2012 at 12:16 AM, Vivek Gautam
> wrote:
>> diff --git a/Documentation/devicetree/bindings/us
On Wed, Dec 26, 2012 at 6:30 AM, Borislav Petkov wrote:
> Hi all,
>
> just saw this in dmesg while running -rc1 + tip/master:
>
>
> [ 6983.694615] =
> [ 6983.694617] [ INFO: possible recursive locking detected ]
> [ 6983.694620] 3.8.0-rc1+ #26 Not tainte
Changes form v3:
- Removing the hostphy_en_mas since this gets used in forthcoming patches
only when host phy support is added.
- Resolving few nits:
- using 'const' specifier for driver data structures.
- using ARRAY_SIZE() instead of giving magic number
for of_prope
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 31
drivers/usb/phy/samsung-usbphy.c | 145 +---
2 files c
batadv_iv_ogm_emit_send_time() attempts to calculates a random integer
in the range of 'orig_interval +- BATADV_JITTER' by the below lines.
msecs = atomic_read(&bat_priv->orig_interval) - BATADV_JITTER;
msecs += (random32() % 2 * BATADV_JITTER);
But it actually gets 'orig_interval
Maybe you got something wrong with USB 3.0 driver and its devices, U'd better
reach USB guys.
Ethan
在 2012-12-26，17:53，Harald Dunkel 写道：
> Hi folks,
>
> I get a lot of strange messages in /var/log/kern.log:
>
> :
> Dec 26 08:01:58 dpcl082 kernel: <>[1862186]xc_c 000:00 RO oro ne
> ig<>18621
On Wed, 2012-12-26 at 02:44 -0800, David Rientjes wrote:
> I'm sure it's a 32-bit issue, nothing has changed recently in auto-latest
> related to these subsystems and I'm sure it's just because my randconfig
> builds were exposed to this combination solely because of this patch.
Hm, that's an un
Hi,
The feature was added long time ago (commit 08a53cdc...) with the comment:
> A task may have at most one synchronous request allocated. So these requests
> need not be otherwise limited.
>
> However the number of background requests (release, forget, asynchronous
> reads, interrupted reques
There are two types of processing requests in FUSE: synchronous (via
fuse_request_send()) and asynchronous (via adding to fc->bg_queue).
Fortunately, the type of processing is always known in advance, at the time
of request allocation. This preparatory patch utilizes this fact making
fuse_get_req(
Miklos wrote:
> A task may have at most one synchronous request allocated. So these
> requests need not be otherwise limited.
The patch re-works fuse_get_req() to follow this idea.
Signed-off-by: Maxim Patlasov
---
fs/fuse/dev.c | 21 +
1 files changed, 13 insertions(+),
The patch solves thundering herd problem. So far as previous patches ensured
that only allocations for background may block, it's safe to wake up one
waiter. Whoever it is, it will wake up another one in request_end() afterwards.
Signed-off-by: Maxim Patlasov
---
fs/fuse/dev.c | 21 +++
[Sorry for the duplicate on linux-mm-cc, the first copy used a wrong
address for LKML]
Hello.
I have a single-core KVM virtual machine with 2 GB of RAM and
linux-3.7.1 inside, and I wanted to test the ZRAM module from staging
there. Here is how:
#!/bin/sh
modprobe zram
echo $((5*1024*1024*1024
On 12/26/2012 08:01 PM, Hillf Danton wrote:
On Wed, Dec 26, 2012 at 7:22 PM, Zhouping Liu wrote:
Hello everyone,
The latest mainline(637704cbc95c) would trigger the following error when the
system was under
some pressure condition(in my testing, I used oom01 case inside LTP test suite
to tri
Adds debug file "clk_summary" in /sys/kernel/debug/clk dir.
It helps to view all the clock registered in human-readable format.
For example:
clockenable_cnt prepare_cnt rate
-
i2s0_sync
Clock information is dumped in JSON format which is easy
for machines to parse.
Each clock is represented as an object which has same name as
clock and following properties
- enable_count
- prepare_count
- rate
Output is verified using online JSON editor.
Signed-off-by: P
Hi Sylwester,
On Wed, Dec 26, 2012 at 5:58 PM, Vivek Gautam wrote:
> Adding support to parse device node data in order to get
> required properties to set pmu isolation for usb-phy.
>
> Signed-off-by: Vivek Gautam
> ---
Hope these changes align with what architectural changes you had suggested
On Tue, Nov 27, 2012 at 04:29:11PM -0700, Stephen Warren wrote:
> From: Grant Likely
>
> The current rules have the .dtb files build in a different directory
> from the .dts files. The only reason for this is that it was what
> PowerPC has done historically. This patch changes ARM to use the gene
On Tue, Dec 25, 2012 at 05:58:03PM +0100, Oleg Nesterov wrote:
> On 12/25, Pavel Emelyanov wrote:
> >
> > On 12/25/2012 07:27 PM, Oleg Nesterov wrote:
> > >
> > > I guess that probably you actually need DUMP, not DEQUEUE. but the
> > > latter is not trivial. However, perhaps we can do this assuming
On 26.12.2012 12:22, Zhouping Liu wrote:
Hello everyone,
The latest mainline(637704cbc95c) would trigger the following error when the
system was under
some pressure condition(in my testing, I used oom01 case inside LTP test suite
to trigger the issue):
[ 5462.920151] BUG: unable to handle ker
Now that balance_pgdat() is slightly tidied up, thanks to more capable
pgdat_balanced(), it's become obvious that pgdat_balanced() is called
to check the status, then break the loop if pgdat is balanced, just to
be immediately called again. The second call is completely unnecessary,
of course.
The
There is a race in enqueueing thread to a pool and
waking up a thread.
lockd doesn't wake up on reception of lock granted callback
if svc_wake_up() is called before lockd's thread is added
to a pool.
Signed-off-by: Andriy Skulysh
---
include/linux/sunrpc/svc.h |1 +
net/sunrpc/svc_xprt.c
On Wed, Dec 26, 2012 at 9:24 PM, Zhouping Liu wrote:
> On 12/26/2012 08:01 PM, Hillf Danton wrote:
>>
>> On Wed, Dec 26, 2012 at 7:22 PM, Zhouping Liu wrote:
>>>
>>> Hello everyone,
>>>
>>> The latest mainline(637704cbc95c) would trigger the following error when
>>> the system was under
>>> some
Most of *_ops and other structures in vivi.c were already declared const
but some have not. Constify and code/data will take less space:
$ size drivers/media/platform/vivi.o
textdata bss dec hex filename
before: 12569 248 8 128253219 drivers/m
On Wed, 2012-12-26 at 15:06 +0800, Wanlong Gao wrote:
> Add a cpu notifier to virtio-net, so that we can reset the
> virtqueue affinity if the cpu hotplug happens. It improve
> the performance through enabling or disabling the virtqueue
> affinity after doing cpu hotplug.
>
> Cc: Rusty Russell
>
On 12/26, Andrew Vagin wrote:
>
> On Tue, Dec 25, 2012 at 05:58:03PM +0100, Oleg Nesterov wrote:
> > On 12/25, Pavel Emelyanov wrote:
> > >
> > > On 12/25/2012 07:27 PM, Oleg Nesterov wrote:
> > > >
> > > > I guess that probably you actually need DUMP, not DEQUEUE. but the
> > > > latter is not tri
On Tue, 25 Dec 2012, Larry Finger wrote:
> On 12/25/2012 10:26 AM, Alan Stern wrote:
> > On Mon, 24 Dec 2012, Larry Finger wrote:
> >
> >> The problem has been bisected to commit adfa79d entitled "USB: EHCI: make
> >> ehci-pci a separate driver". The symptom is that my NVIDIA controller again
> >>
On Wed, 26 Dec 2012, Fabio Coatti wrote:
> Hi all,
> I'm experiencing some usb-related issues with recent kernels (3.6.7
> and 3.7.1 at least.)
> Basically I have a V500 epson scanner that worked just fine with older
> kernels; since last time I used it I've changed several kernels and
> now the o
On Wed, Dec 26, 2012 at 6:10 AM, Namhyung Kim wrote:
> Hi Stefan,
>
> On Sun, 23 Dec 2012 22:18:32 +0100, Stefan Beller wrote:
>> Hi,
>>
>> I get segmentation faults when running one of these commands:
>> perf report -g --sort symbol_to
>> perf report -g --sort symbol_from
>> perf report -g --sort
Discourage use of glibc pthread_atfork() for call_rcu handlers due to
its inappropriate assumptions about single-threadedness while pthread
atfork handlers are executing. This results in hangs within the glibc
memory allocator.
Signed-off-by: Mathieu Desnoyers
---
diff --git a/README b/README
On Tue, Dec 25, 2012 at 09:09:05AM +0800, Yanmin Zhang wrote:
> On Mon, 2012-12-24 at 09:55 -0800, Greg KH wrote:
> > On Mon, Dec 24, 2012 at 01:01:55PM +0800, he, bo wrote:
> > > From: "he, bo"
> > >
> > > We often hit kernel panic issues on SMP machines because processes race
> > > on multiple
On Wed, Dec 26, 2012 at 02:48:24PM +0800, Li Zefan wrote:
> sock->sk_cgrp_prioidx won't be used at all if CONFIG_NETPRIO_CGROUP=n.
>
> Signed-off-by: Li Zefan
Acked-by: Neil Horman
> ---
> include/net/sock.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/net/
On Tue, Dec 25, 2012 at 9:41 PM, Cong Wang wrote:
> On Wed, Dec 26, 2012 at 12:08 AM, Sasha Levin wrote:
>> On Tue, Dec 18, 2012 at 10:20 AM, Josh Boyer wrote:
>>> On Wed, Nov 21, 2012 at 7:53 AM, Alan Cox wrote:
On Wed, 21 Nov 2012 07:45:45 -0500
Josh Boyer wrote:
> On Fri,
On 12/26/2012 10:45 AM, Alan Stern wrote:
I see. Do you happen to have CONFIG_USB_EHCI_HCD=y and
CONFIG_USB_EHCI_PCI=m in your .config? If you do, try changing
EHCI_PCI to y.
No, they are both "m". My configuration parameters with EHCI in them are
CONFIG_USB_ARCH_HAS_EHCI=y
CONFIG_USB_EHCI_
On Tue, Dec 25, 2012 at 3:42 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
> Subject: PCI / ACPI: Set root bridge ACPI handle in advance
>
> The ACPI handles of PCI root bridges need to be known to
> acpi_bind_one(), so that it can create the appropriate
> "firmware_node" and "physical_n
Handle HKEY event generated on AC power change. The current message
asks users to submit data related to this event which leads to
a lot of confusion and noise on the mailing list.
The following is a list of causes, affected models, and 'message-id'
from ibm-acpi-de...@lists.sourceforge.net :
AC
On 12/22/2012 12:21 AM, Simon Marchi wrote:
> Call tracehook functions for syscall tracing.
>
> The check for TIF_SYSCALL_TRACE was removed, because the same check is
> done right before in the assembly file.
>
> Signed-off-by: Simon Marchi
>
I've taken this one, and patch 3/3 in this series, int
This patch adds EHCI device node on device tree for Exynos4 and defines its
default platform data, s5p_usb_phy_init and s5p_usb_phy_exit, so that those
function can be called from the driver.
Signed-off-by: Dongjin Kim
---
arch/arm/boot/dts/exynos4.dtsi |7 +++
arch/arm/mach-exyn
This patch support to get interrupt resource from device tree as well as
platform device if ehci node is defined in device tree and it's irq is
described.
Signed-off-by: Dongjin Kim
---
drivers/usb/host/ehci-s5p.c |8 +++-
1 file changed, 7 insertions(+), 1 deletion(-)
diff --git a/driv
On Fri, 2012-12-21 at 22:50 -0500, Rik van Riel wrote:
> I will try to run this test on a really large SMP system
> in the lab during the break.
>
> Ideally, the auto-tuning will keep the delay value large
> enough that performance will stay flat even when there are
> 100 CPUs contending over the
On 12/26/2012 10:45 AM, Alan Stern wrote:
I see. Do you happen to have CONFIG_USB_EHCI_HCD=y and
CONFIG_USB_EHCI_PCI=m in your .config? If you do, try changing
EHCI_PCI to y.
One additional data point: When the EHCI and HCD parameters are set to y rather
than m as in the list that follows,
Hello.
On 12/26/2012 09:42 PM, Dongjin Kim wrote:
> This patch support to get interrupt resource from device tree as well as
> platform device if ehci node is defined in device tree and it's irq is
> described.
> Signed-off-by: Dongjin Kim
> ---
> drivers/usb/host/ehci-s5p.c |8 +++-
>
On Wed, 2012-12-26 at 11:10 -0800, Eric Dumazet wrote:
> +#define DELAY_HASH_SHIFT 4
> +DEFINE_PER_CPU(int [1 << DELAY_HASH_SHIFT], spinlock_delay) = {
> + MIN_SPINLOCK_DELAY, MIN_SPINLOCK_DELAY,
> + MIN_SPINLOCK_DELAY, MIN_SPINLOCK_DELAY,
> + MIN_SPINLOCK_DELAY, MIN_SPINLOCK_DELAY,
>
On Tue, Dec 18, 2012 at 9:45 PM, Doug Anderson wrote:
> Amit,
>
> On Tue, Dec 18, 2012 at 8:17 PM, amit daniel kachhap
> wrote:
>> On Tue, Dec 18, 2012 at 12:29 AM, Sonny Rao wrote:
>>> The cpu_thermal generic thermal management code has a bug where once
>>> max cpu frequency has been lowered in
On 12/26/2012 02:10 PM, Eric Dumazet wrote:
I did some tests with your patches with following configuration :
tc qdisc add dev eth0 root htb r2q 1000 default 3
(to force a contention on qdisc lock, even with a multi queue net
device)
and 24 concurrent "netperf -t UDP_STREAM -H other_machine --
On Tue, Dec 25, 2012 at 2:42 PM, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
> Subject: PCI / ACPI: Set root bridge ACPI handle in advance
>
> The ACPI handles of PCI root bridges need to be known to
> acpi_bind_one(), so that it can create the appropriate
> "firmware_node" and "physical_n
On Wed, Dec 26, 2012 at 1:04 PM, Yinghai Lu wrote:
> On Tue, Dec 25, 2012 at 2:42 PM, Rafael J. Wysocki wrote:
>> From: Rafael J. Wysocki
>> Subject: PCI / ACPI: Set root bridge ACPI handle in advance
>>
>> The ACPI handles of PCI root bridges need to be known to
>> acpi_bind_one(), so that it c
On Wed, Dec 26, 2012 at 12:10 PM, Bjorn Helgaas wrote:
> Do you have a reference for this? I think this might have been true
> in the past, but I don't think it's true for any version of gcc we
> support for building Linux.
http://lkml.indiana.edu/hypermail/linux/kernel/0804.3/3600.html
--
To un
If kzalloc() or csio_hw_check_fwconfig() fail we may leave the
csio_hw_flash_config() function without freeing allocated memory or
firmware. This should take care of the leaks.
Signed-off-by: Jesper Juhl
---
drivers/scsi/csiostor/csio_hw.c | 15 +--
1 files changed, 9 insertions(+)
On Wed, Dec 26, 2012 at 12:16 PM, Yinghai Lu wrote:
> On Wed, Dec 26, 2012 at 12:10 PM, Bjorn Helgaas wrote:
>> Do you have a reference for this? I think this might have been true
>> in the past, but I don't think it's true for any version of gcc we
>> support for building Linux.
>
> http://lkml
On 2012-12-25 10:27, majianpeng wrote:
> In commit 975927b942c932,it add blk_rq_pos to sort rq when flushing.
> Although this commit was used for the situation which blk_plug handled
> multi devices on the same time like md device.
> I think there must be some situations like this but only single
>
With 3.8-rc1, there are WARNINGS that the driver is not checking for
DMA mapping errors. The warnings start with
[ cut here ]
WARNING: at lib/dma-debug.c:933 check_unmap+0x480/0x950()
Hardware name: HP Pavilion dv2700 Notebook PC
forcedeth :00:0a.0: DMA-API: device driv
We fail to release 'urb' if '_rtl_prep_rx_urb()' fails in
_rtl_usb_receive().
This patch should take care of the leak.
Signed-off-by: Jesper Juhl
---
drivers/net/wireless/rtlwifi/usb.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
note: compile tested only.
diff --git a/drivers/n
On 12/26/2012 02:51 PM, Jesper Juhl wrote:
We fail to release 'urb' if '_rtl_prep_rx_urb()' fails in
_rtl_usb_receive().
This patch should take care of the leak.
Signed-off-by: Jesper Juhl
---
drivers/net/wireless/rtlwifi/usb.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
no
This patch adds the missing cpufreq_cpu_put function needed for
returning the cpufreq policy instance.
Signed-off-by: Amit Daniel Kachhap
---
drivers/cpufreq/exynos-cpufreq.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/cpufreq/exynos-cpufreq.c b/drivers/cpufr
'if ((!help) && (!cda[CTA_EXPECT_TIMEOUT]))' then we should remember
to free 'exp' that was allocated by 'nf_ct_expect_alloc()' by jumping
to the 'err_out' label rather than the 'out' label in
ctnetlink_create_expect().
This patch should get rid of the leak.
Signed-off-by: Jesper Juhl
---
net/ne
On Wed, Dec 26, 2012 at 10:49:40PM +0100, Jesper Juhl wrote:
> 'if ((!help) && (!cda[CTA_EXPECT_TIMEOUT]))' then we should remember
> to free 'exp' that was allocated by 'nf_ct_expect_alloc()' by jumping
> to the 'err_out' label rather than the 'out' label in
> ctnetlink_create_expect().
> This pat
From: Akinobu Mita
Date: Wed, 26 Dec 2012 21:32:10 +0900
> batadv_iv_ogm_emit_send_time() attempts to calculates a random integer
> in the range of 'orig_interval +- BATADV_JITTER' by the below lines.
>
> msecs = atomic_read(&bat_priv->orig_interval) - BATADV_JITTER;
> msecs += (
From: Neil Horman
Date: Wed, 26 Dec 2012 13:03:39 -0500
> On Wed, Dec 26, 2012 at 02:48:24PM +0800, Li Zefan wrote:
>> sock->sk_cgrp_prioidx won't be used at all if CONFIG_NETPRIO_CGROUP=n.
>>
>> Signed-off-by: Li Zefan
> Acked-by: Neil Horman
Applied, thanks.
--
To unsubscribe from this list
On Wed, 2012-12-26 at 14:00 -0800, David Rientjes wrote:
> Umm, you're saying that is legitimate for "make randconfig" done on a
> 32-bit machine to generate 64-bit configurations? The resulting kernel
> cannot be booted.
It has never been expected that a 'randconfig' kernel would actually
boo
On Wednesday, December 26, 2012 11:14:22 AM Bjorn Helgaas wrote:
> On Tue, Dec 25, 2012 at 3:42 PM, Rafael J. Wysocki wrote:
> > From: Rafael J. Wysocki
> > Subject: PCI / ACPI: Set root bridge ACPI handle in advance
> >
> > The ACPI handles of PCI root bridges need to be known to
> > acpi_bind_o
On Wed, 26 Dec 2012, David Rientjes wrote:
> On Wed, 26 Dec 2012, David Woodhouse wrote:
>
> > > I'm sure it's a 32-bit issue, nothing has changed recently in auto-latest
> > > related to these subsystems and I'm sure it's just because my randconfig
> > > builds were exposed to this combination
On Wednesday, December 26, 2012 12:41:05 PM Yinghai Lu wrote:
> On Wed, Dec 26, 2012 at 12:16 PM, Yinghai Lu wrote:
> > On Wed, Dec 26, 2012 at 12:10 PM, Bjorn Helgaas wrote:
> >> Do you have a reference for this? I think this might have been true
> >> in the past, but I don't think it's true fo
From: Rafael J. Wysocki
Subject: ACPI: Rework acpi_get_child() to be more efficient
Observe that acpi_get_child() doesn't need to use the helper
struct acpi_find_child structure and change it to work without it.
Also, using acpi_get_object_info() to get the output of _ADR for the
given device is
On Sat, Dec 22, 2012 at 12:01 PM, Lucas Kannebley Tavares
wrote:
> During the process of obtaining the speed cap for the device, it
> attempts go get the PCI Host bus. However on architectures such as PPC
> or IA64, those do not appear as devices.
>
> Signed-off-by: Lucas Kannebley Tavares
> ---
On Thu, Dec 27, 2012 at 8:40 AM, Bjorn Helgaas wrote:
> On Sat, Dec 22, 2012 at 12:01 PM, Lucas Kannebley Tavares
> wrote:
>> During the process of obtaining the speed cap for the device, it
>> attempts go get the PCI Host bus. However on architectures such as PPC
>> or IA64, those do not appear
On 12/26/2012 01:28 PM, Vivek Gautam wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam
---
.../devicetree/bindings/usb/samsung-usbphy.txt | 31
drivers/usb/phy/samsung-usbphy.c
Hi,
On 12/26/2012 02:56 PM, Vivek Gautam wrote:
On Wed, Dec 26, 2012 at 5:58 PM, Vivek Gautam wrote:
Adding support to parse device node data in order to get
required properties to set pmu isolation for usb-phy.
Signed-off-by: Vivek Gautam
---
Hope these changes align with what architectura
On Wed, 2012-12-26 at 14:00 -0800, David Rientjes wrote:
> I do quite a bit of automated config and boot tests to try out
> combinations that others may not have tested when developing their
> code; staging branches such as in tip are interesting to try because
> they haven't yet reached Linus and
On 12/26/2012 02:00 PM, David Rientjes wrote:
>
In the past, "make randconfig" would always generate a
kernel that _should_ boot on that machine unless there was an underlying
bug that should be fixed.
>
Not even remotely true. There are tons of options which may not be set
that your machine
From: Paolo valente
Date: Wed, 19 Dec 2012 18:31:06 +0100
> + /*
> + * The next assignment may let
> + * agg->initial_budget > agg->budgetmax
> + * hold, but this does not cause any harm
> + */
Please format comments in the networking:
/* Like
* this.
On Wed, Dec 19, 2012 at 08:04:11PM +0800, Hillf Danton wrote:
> >@@ -52,15 +46,6 @@ struct kioctx;
> > * not ask the method again -- ki_retry must ensure forward progress.
> > * aio_complete() must be called once and only once in the future, multiple
> > * calls may result in undefined behaviour
On Tue, 2012-12-25 at 22:32 -0800, David Rientjes wrote:
>
> This creates quite a few build failures on auto-latest:
>
> arch/x86/built-in.o: In function `hpet_setup_msi_irq':
> hpet.c:(.text+0x34638): undefined reference to `arch_setup_hpet_msi'
> hpet.c:(.text+0x34651): undefined reference to `
On Wed, Dec 26, 2012 at 2:36 PM, Rafael J. Wysocki wrote:
> On Wednesday, December 26, 2012 12:41:05 PM Yinghai Lu wrote:
>> On Wed, Dec 26, 2012 at 12:16 PM, Yinghai Lu wrote:
>> > On Wed, Dec 26, 2012 at 12:10 PM, Bjorn Helgaas
>> > wrote:
>> >> Do you have a reference for this? I think this
Mike,
Three bugfixes for 3.8.
#1 was a boo-boo on my part, function returned the wrong variables.
#2 is a truncation problem which results in a higher-than-requested clock rate.
#3 became apparent when the MMC driver started requesting rate=0 during init.
Tony Prisk (3):
clk: vt8500: Fix error
When a PLL frequency calculation is performed and a non-exact match
is found the wrong multiplier and divisors are returned.
Signed-off-by: Tony Prisk
---
drivers/clk/clk-vt8500.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/clk/clk-vt8500.c b/drivers/clk/
When calculating device clock divisor values in set_rate and
round_rate, we do a simple integer divide. If parent_rate / rate
has a fraction, this is dropped which results in the device clock
being set too high.
This patch corrects the problem by adding 1 to the calculated
divisor if the division
A request to vt8500_dclk_(round_rate/set_rate) with rate=0 results
in a division-by-0 in the kernel.
Signed-off-by: Tony Prisk
---
drivers/clk/clk-vt8500.c | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/drivers/clk/clk-vt8500.c b/drivers/clk/clk-vt8500.c
in
Control register bitfield for 12H/24H mode is handled incorrectly.
Setting CR_24H actually enables 12H mode. This patch renames the
define and changes the initialization code to correctly set
24H mode.
Signed-off-by: Tony Prisk
---
drivers/rtc/rtc-vt8500.c |4 ++--
1 file changed, 2 insertio
This patch adds support for .fb_check_var which is required when
X attempts to initialize the framebuffer. The only supported
resolution is the native resolution of the LCD panel, so we test
against the resolution supplied from the DT panel definition.
Signed-off-by: Tony Prisk
---
drivers/video
1 - 100 of 187 matches
Mail list logo
