Use bitmap_weight to count the total number of bits set in bitmap.
Signed-off-by: Joe Perches
---
sound/usb/endpoint.c |7 +--
1 files changed, 1 insertions(+), 6 deletions(-)
diff --git a/sound/usb/endpoint.c b/sound/usb/endpoint.c
index 34de6f2..51a9aa3 100644
---
On Sat, Nov 17, 2012 at 05:07:39PM +1300, Tony Prisk wrote:
> Hi Thierry,
>
> Looking a little feedback regarding a problem introduced with the pwm
> patch I sent converting the vt8500 pwm driver to devicetree.
>
> One of the recommendations you made was to enable/disable the pwm clock
> in
On Fri, Nov 16, 2012 at 03:56:03PM -0800, Andrew Morton wrote:
>
> This is a lousy output format. It's sort-of like a sensible set of
> name-value tuples: "name:value name:value name:value" but
>
> a) it has lots of random pointless whitespace after the colons and
>
> b) several of the labels
Modify qt_status_change_check() and delete qt_status_change().
Signed-off-by: YAMANE Toshiaki
---
drivers/staging/serqt_usb2/serqt_usb2.c | 53 +--
1 file changed, 22 insertions(+), 31 deletions(-)
diff --git a/drivers/staging/serqt_usb2/serqt_usb2.c
On Fri, Nov 16, 2012 at 10:28 AM, Mika Westerberg
wrote:
> ...
> From: Mika Westerberg
> Date: Mon, 10 Sep 2012 12:12:32 +0300
> Subject: [PATCH] i2c / ACPI: add ACPI enumeration support
>
> ACPI 5 introduced I2cSerialBus resource that makes it possible to enumerate
> and configure the I2C slave
On Sat, Nov 17, 2012 at 2:09 AM, Stephen Warren wrote:
> Acked-by: Stephen Warren
Thanks!
>> +POWER SEQUENCES
>> +M: Alexandre Courbot
>> +S: Maintained
>
> Given you're presumably working on this on NVIDIA's time, perhaps make
> that "Supported" not "Maintained"?
Absolutely.
Alex.
--
I'm working on an idea I had for improving the security of processes
in Linux. What I'm trying to do is a little complex, and I'm new to
Kernel development, so I figured it might be a good idea to reach out
to the Kernel community before I got too deep into the development.
Basically, I was hoping
On 11/09/2012 10:36 AM, Feng Tang wrote:
On Fri, Nov 09, 2012 at 10:30:43PM +0800, Moore, Robert wrote:
The ACPI Global Lock is in fact intended to provide exclusion between the BIOS
and the OS.
Bob
Thanks for the info.
And per my check, most of ACPI FW don't implement this lock, say
after
Node is selected on behalf of given task, but no reason to punish
the currently running tasks on other nodes. That punishment maybe benifit,
who knows. Better if they are treated not in random way.
Signed-off-by: Hillf Danton
---
--- a/kernel/sched/fair.c Sat Nov 17 12:29:08 2012
+++
No point to migrate task from node A to node A.
Signed-off-by: Hillf Danton
---
--- a/kernel/sched/fair.c Sat Nov 17 12:25:44 2012
+++ b/kernel/sched/fair.c Sat Nov 17 12:25:54 2012
@@ -891,6 +891,8 @@ static void task_numa_find_placement(str
/* Examine a task on every other
Checking ->mm is not needed, but too late if necessary.
Signed-off-by: Hillf Danton
---
--- a/kernel/sched/fair.c Sat Nov 17 12:12:08 2012
+++ b/kernel/sched/fair.c Sat Nov 17 12:14:26 2012
@@ -1125,7 +1125,7 @@ static void reset_ptenuma_scan(struct ta
On 11/16/2012 06:37 PM, Chris Ball wrote:
> Hi Trey, thanks for the analysis,
>
> On Fri, Nov 16 2012, Trey Ramsay wrote:
>> Good question. In regards to the original problem were it was hung in
>> mmc_blk_err_check, the new code path will timeout after 10 minutes, log
>> an error, issue a
Simply use @pages as we handle both pte and pmd numa faults.
Signed-off-by: Hillf Danton
---
--- a/kernel/sched/fair.c Sat Nov 17 11:40:36 2012
+++ b/kernel/sched/fair.c Sat Nov 17 12:05:06 2012
@@ -1112,10 +1112,10 @@ void task_numa_fault(int node, int pages
}
/*
Hi,
I want to use print some trace messages to the console in the kernel
setup/init stages. But I don't know what is the earliest time when safe
to do that. Sould be somewhere after decompress_kernel() invocation?
And, when should I use putstr() and when to use printk()? Thans.
--
-woody
I
If you were going to shoot me for not sending these earlier, you would be
right. -rc6 beat me by ~2 hours it seems, and they really should have
gone out to libata-dev.git and you long before that.
These have been in libata-dev.git for a day or so (unfortunately
linux-next is on vacation). The
s/ptep/pmdp/
Also a cleanup packed: use haddr directly.
Btw, will spin if you no longer need the debug trap.
Signed-off-by: Hillf Danton
---
--- a/mm/huge_memory.c Sat Nov 17 11:37:36 2012
+++ b/mm/huge_memory.c Sat Nov 17 11:54:18 2012
@@ -1055,9 +1055,9 @@ clear_pmdnuma:
Chris Friesen, on 11/15/2012 05:35 PM wrote:
The easiest way to implement this fsync would involve three things:
1. Schedule writes for all dirty pages in the fs cache that belong to
the affected file, wait for the device to report success, issue a cache
flush to the device (or request ordering
David Lang, on 11/15/2012 07:07 AM wrote:
There's no such thing as "barrier". It is fully artificial abstraction. After
all, at the bottom of your stack, you will have to translate it either to cache
flush, or commands order enforcement, or both.
When people talk about barriers, they are
杨苏立 Yang Su Li, on 11/15/2012 11:14 AM wrote:
1. fsync actually does two things at the same time: ordering writes (in a
barrier-like manner), and forcing cached writes to disk. This makes it very
difficult to implement fsync efficiently.
Exactly!
However, logically they are two distinctive
Further offtopic..
On Fri, 16 Nov 2012, Jaegeuk Hanse wrote:
> Some questions about your shmem/tmpfs: misc and fallocate patchset.
>
> - Since shmem_setattr can truncate tmpfs files, why need add another similar
> codes in function shmem_fallocate? What's the trick?
I don't know if I understand
Hello kernel folks,
I have an old 2.0 USB card reader, Linux detects the device but is not able to
mount the storage device.
I tried it in both a KVM Windows VM and in Linux to mount the storage but
device hangs, if I take out card, it detects all 6 device storage capabilities,
then it
On 11/14/2012 05:11 AM, Jonas Gorski wrote:
> On 13 November 2012 06:02, Stephen Warren wrote:
>> On 11/11/2012 05:50 AM, Jonas Gorski wrote:
>>> Add definitions for the clocks found and used in all supported SoCs.
>>
>>> diff --git a/arch/mips/bcm63xx/dts/bcm6328.dtsi
>>>
On 11/14/2012 05:09 AM, Jonas Gorski wrote:
> On 13 November 2012 06:00, Stephen Warren wrote:
>> On 11/11/2012 05:50 AM, Jonas Gorski wrote:
>>> Register IRQ domains through Device Tree for the internal and external
>>> interrupt controllers. Register the same IRQ ranges as previously to
>>>
Hi Thierry,
Looking a little feedback regarding a problem introduced with the pwm
patch I sent converting the vt8500 pwm driver to devicetree.
One of the recommendations you made was to enable/disable the pwm clock
in pwm_enable/pwm_disable, rather than at driver probe, to reduce power
usage.
I'm announcing the release of the 3.2.34 kernel.
All users of the 3.2 kernel series should upgrade.
The updated 3.2.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.2.y
and can be browsed at the normal kernel.org git web browser:
Hi Mark,
On Fri, Nov 16, 2012 at 7:35 PM, Mark Rutland wrote:
> Given there are several ARM platforms that may have an interest in this,
> please
> consider posting this to the ARM mailing list:
> linux-arm-ker...@lists.infradead.org.
That's right. New revision on the way.
>> +Similarly, each
rmi_bus.c implements the basic functionality of the RMI bus. This file is
greatly simplified compared to the previous patch - we've switched from
"do it yourself" device/driver binding to using device_type to distinguish
between the two kinds of devices on the bus (sensor devices and function
RMI Function 01 implements basic device control and power management
behaviors for the RMI4 sensor.
rmi_f01.h exports definitions that we expect to be used by other functionality
in the future (such as firmware reflash).
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
rmi_i2c.c abstracts an RMI4 device on some arbitrary I2C bus as a logical
device in the RMI bus. It handles reads/writes from/to the RMI4 devices,
and manages the page select register setting (since the meaning of page
select is dependent on the physical layer used to communicate with the RMi4
Infrastructure files for configuration and building.
Signed-off-by: Christopher Heiny
Cc: Dmitry Torokhov
Cc: Linus Walleij
Cc: Naveen Kumar Gaddipati
Cc: Joeri de Gram
---
drivers/input/Kconfig |2 +
drivers/input/Makefile |3 ++
drivers/input/rmi4/Kconfig | 76
rmi.h provides public definitions required by the RMI bus implementation and
modules that interact with it.
debugfs and sysfs attributes are documented in files in
Documentation/ABI/testing. There's two files, one for debugfs and one for
sysfs.
Signed-off-by: Christopher Heiny
Cc: Dmitry
This patch implements a driver supporting Synaptics ClearPad and other
touchscreen sensors that use the RMI4 protocol, as defined here:
http://www.synaptics.com/sites/default/files/511-000136-01-Rev-E-RMI4%20Intrfacing%20Guide.pdf
as well as successor documents that haven't made their way
Now we pass around use_gbpages and use_pse for calculating page table size,
Later we will need to call init_memory_mapping for every ram range one by one,
that mean those calculation will be done several times.
Those information are the same for all ram range and could be stored in
page_size_mask
We should not do that in every calling of init_memory_mapping.
At the same time need to move down early_memtest, and could remove after_bootmem
checking.
-v2: fix one early_memtest with 32bit by passing max_pfn_mapped instead.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 66
After
| commit 8548c84da2f47e71bbbe300f55edb768492575f7
| Author: Takashi Iwai
| Date: Sun Oct 23 23:19:12 2011 +0200
|
|x86: Fix S4 regression
|
|Commit 4b239f458 ("x86-64, mm: Put early page table high") causes a S4
|regression since 2.6.39, namely the machine reboots
So make init_memory_mapping smaller and readable.
-v2: use 0 instead of nr_range as input parameter found by Yasuaki Ishimatsu.
Suggested-by: Ingo Molnar
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
Cc: Yasuaki Ishimatsu
---
arch/x86/mm/init.c | 41
It should take physical address range that will need to be mapped.
find_early_table_space should take range that pgt buff should be in.
Separating page table size calculating and finding early page table to
reduce confusing.
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
From: Jacob Shin
There could be cases where user supplied memmap=exactmap memory
mappings do not mark the region where the kernel .text .data and
.bss reside as E820_RAM, as reported here:
https://lkml.org/lkml/2012/8/14/86
Handle it by complaining, and adding the range back into the e820.
We are going to map ram only, so under max_low_pfn_mapped,
between 4g and max_pfn_mapped does not mean mapped at all.
Use pfn_range_is_mapped() directly.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/pageattr.c | 16 +++-
1 files changed, 3 insertions(+), 13 deletions(-)
diff --git
We are going to map ram only, so under max_low_pfn_mapped,
between 4g and max_pfn_mapped does not mean mapped at all.
Use pfn_range_is_mapped() directly.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/amd_gart_64.c |5 ++---
1 files changed, 2 insertions(+), 3 deletions(-)
diff --git
instead of under 4g.
For 64bit, we can use any mapped mem instead of low mem.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c |7 +++
1 files changed, 3 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 68dffec..94f922a 100644
---
We could map small range in the middle of big range at first, so should use
big page size at first to avoid using small page size to break down page table.
Only can set big page bit when that range has ram area around it.
-v2: fix 32bit boundary checking. We can not count ram above max_low_pfn
It will need to call split_mem_range().
Move it down after that to avoid extra declaration.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 117 ++--
1 files changed, 59 insertions(+), 58 deletions(-)
diff --git a/arch/x86/mm/init.c
Now init_memory_mapping is called two times, later will be called for every
ram ranges.
Could put all related init_mem calling together and out of setup.c.
Actually, it reverts commit 1e7
x86: Exclude E820_RESERVED regions and memory holes above 4 GB from direct
mapping.
will address
From: Jacob Shin
Update code that previously assumed pfns [ 0 - max_low_pfn_mapped ) and
[ 4GB - max_pfn_mapped ) were always direct mapped, to now look up
pfn_mapped ranges instead.
-v2: change applying sequence to keep git bisecting working.
so add dummy pfn_range_is_mapped(). - Yinghai
From: Jacob Shin
Currently direct mappings are created for [ 0 to max_low_pfn<
Signed-off-by: Yinghai Lu
Reviewed-by: Pekka Enberg
---
arch/x86/include/asm/page_types.h |8 +--
arch/x86/kernel/setup.c |8 ++-
arch/x86/mm/init.c| 120
Get pgt_buf early from BRK, and use it to map PMD_SIZE from top at first.
Then use mapped pages to map more ranges below, and keep looping until
all pages get mapped.
alloc_low_page will use page from BRK at first, after that buffer is used
up, will use memblock to find and reserve pages for page
Now all page table buf are pre-mapped, and could use virtual address directly.
So don't need to remember physical address anymore.
Remove that phys pointer in alloc_low_page(), and that will allow us to merge
alloc_low_page between 64bit and 32bit.
Signed-off-by: Yinghai Lu
Acked-by: Stefano
Also change it to static.
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/page_types.h |1 -
arch/x86/kernel/setup.c |1 -
arch/x86/mm/init.c|2 ++
3 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/include/asm/page_types.h
We try to put page table high to make room for kdump, and at that time
those ranges are not mapped yet, and have to use ioremap to access it.
Now after patch that pre-map page table top down.
x86, mm: setup page table in top-down
We do not need that workaround anymore.
Just use __va to
Will replace that with top-down page table initialization.
New API need to take range: init_range_memory_mapping()
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 41 +++--
1 files changed, 19 insertions(+), 22 deletions(-)
diff --git
Page table area are pre-mapped now after
x86, mm: setup page table in top-down
x86, mm: Remove early_memremap workaround for page table accessing on
64bit
mapping_pagetable_reserve is not used anymore, so remove it.
Also remove operation in mask_rw_pte(), as modified
On 32bit, before patcheset that only set page table for ram, we only
call that one time.
Now, we are calling that during every init_memory_mapping if we have holes
under max_low_pfn.
We should only call it one time after all ranges under max_low_page get
mapped just like we did before.
Also
We are going to use buffer in BRK to map small range just under memory top,
and use those new mapped ram to map ram range under it.
The ram range that will be mapped at first could be only page aligned,
but ranges around it are ram too, we could use bigger page to map it to
avoid small page size.
memblock_x86_fill() could double memory array.
If we set memblock.current_limit to 512M, so memory array could be around 512M.
So kdump will not get big range (like 512M) under 1024M.
Try to put it down under 1M, it would use about 4k or so, and that is limited.
Signed-off-by: Yinghai Lu
---
We are going to map ram only, so under max_low_pfn_mapped,
between 4g and max_pfn_mapped does not mean mapped at all.
Use pfn_range_is_mapped() to find out if range is mapped for initrd.
That could happen bootloader put initrd in range but user could
use memmap to carve some of range out.
Also
32bit kmap mapping needs pages to be used for low to high.
At this point those pages are still from pgt_buf_* from BRK, so it is
ok now.
But we want to move early_ioremap_page_table_range_init() out of
init_memory_mapping() and only call it one time later, that will
make
Put it in mm/init.c, and call it from probe_page_mask().
init_mem_mapping is calling probe_page_mask at first.
So calling sequence is not changed.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c | 15 +--
arch/x86/mm/init.c | 12
2 files changed, 13
They are almost same except 64 bit need to handle after_bootmem case.
Add mm_internal.h to make that alloc_low_page() only to be accessible
from arch/x86/mm/init*.c
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c| 34 ++
arch/x86/mm/init_32.c |
From: Stefano Stabellini
Add link for more information
279b706 x86,xen: introduce x86_init.mapping.pagetable_reserve
-v2: updated to commets from hpa to include commit name.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c |9 +
1 files changed, 9 insertions(+), 0
They are only for mm/init*.c.
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/init.h | 16 +++-
arch/x86/mm/mm_internal.h |7 +++
2 files changed, 10 insertions(+), 13 deletions(-)
diff --git a/arch/x86/include/asm/init.h b/arch/x86/include/asm/init.h
index
after_bootmem has different meaning in 32bit and 64bit.
32bit: after bootmem is ready
64bit: after bootmem is distroyed
Let's merget them make 32bit the same as 64bit.
for 32bit, it is mixing alloc_bootmem_pages, and alloc_low_page under
after_bootmem is set or not set.
to replace own inline version for shifting.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 44 ++--
1 files changed, 22 insertions(+), 22 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 0e625e6..1cca052 100644
---
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init_32.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c
index 0ae1ba8..322ee56 100644
--- a/arch/x86/mm/init_32.c
+++ b/arch/x86/mm/init_32.c
@@ -575,7 +575,7 @@
During test patch that adjust page_size_mask to map small range ram with
big page size, found page table is setup wrongly for 32bit. And
native_pagetable_init wrong clear pte for pmd with large page support.
1. add more comments about why we are expecting pte.
2. add BUG checking, so next time
After we add code use buffer in BRK to pre-map buf for page table in
following patch:
x86, mm: setup page table in top-down
it should be safe to remove early_memmap for page table accessing.
Instead we get panic with that.
It turns out that we clear the initial page table wrongly for next
Now NO_BOOTMEM version free_all_bootmem_node() does not really
do free_bootmem at all, and it only call register_page_bootmem_info_node
instead.
That is confusing, try to kill that free_all_bootmem_node().
Before that, this patch will remove numa_free_all_bootmem().
That function could be
Now NO_BOOTMEM version free_all_bootmem_node() does not really
do free_bootmem at all, and it only call
register_page_bootmem_info_node instead.
That is confusing, try to kill that free_all_bootmem_node().
Before that, this patch will remove calling of free_all_bootmem_node()
We add
it is only used in arch/x86/mm/init*.c
Signed-off-by: Yinghai Lu
---
arch/x86/mm/mm_internal.h |2 ++
include/linux/mm.h|1 -
2 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/arch/x86/mm/mm_internal.h b/arch/x86/mm/mm_internal.h
index dc79ac1..6b563a1 100644
---
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/numa.h|2 --
arch/x86/include/asm/numa_64.h |4
arch/x86/kernel/acpi/boot.c|1 -
arch/x86/kernel/cpu/amd.c |1 -
arch/x86/kernel/cpu/intel.c|1 -
arch/x86/kernel/setup.c|3 ---
6 files
Current "memmap=" only can take one entry every time.
when we have more entries, we have to use memmap= for each of them.
For pxe booting, we have command line length limitation, those extra
"memmap=" would waste too much space.
This patch make memmap= could take several entries one time,
and
Now NO_BOOTMEM version free_all_bootmem_node() does not really
do free_bootmem at all, and it only call register_page_bootmem_info_node
for online nodes instead.
That is confusing.
We can kill that free_all_bootmem_node(), after we kill two callings
in x86 and sparc.
Signed-off-by: Yinghai Lu
could save some bit shifting operations.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 29 ++---
1 files changed, 14 insertions(+), 15 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 1cca052..4bf1c53 100644
--- a/arch/x86/mm/init.c
+++
instead of shifting end to get that.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 20 +++-
1 files changed, 11 insertions(+), 9 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 4bf1c53..f410dc6 100644
--- a/arch/x86/mm/init.c
+++
save some lines, and make code more readable.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 21 +
1 files changed, 5 insertions(+), 16 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 2a27e5a..6f85de8 100644
--- a/arch/x86/mm/init.c
+++
to replace own inline version for those roundup and rounddown.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 30 --
1 files changed, 12 insertions(+), 18 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index 8168bf8..0e625e6 100644
---
call split_mem_range inside the function.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c | 12 +---
1 files changed, 9 insertions(+), 3 deletions(-)
diff --git a/arch/x86/mm/init.c b/arch/x86/mm/init.c
index dbef4ff..51f919f 100644
--- a/arch/x86/mm/init.c
+++ b/arch/x86/mm/init.c
Also change them to static.
Signed-off-by: Yinghai Lu
---
arch/x86/include/asm/init.h |4
arch/x86/mm/init.c |6 +++---
2 files changed, 3 insertions(+), 7 deletions(-)
diff --git a/arch/x86/include/asm/init.h b/arch/x86/include/asm/init.h
index 4f13998..626ea8d 100644
rebase patchset together tip/x86/mm2 on top of linus v3.7-rc4
so this one include patchset : x86, mm: init_memory_mapping cleanup
in tip/x86/mm2
---
Current kernel init memory mapping between [0, TOML) and [4G, TOMH)
Some AMD systems have mem hole between 4G and TOMH, around 1T.
According to HPA,
cs->is_local will be used to indicate whether the cgroup has its own
configuration or inherited from the parent. It's set when classid is
configured by writing a positive value to cgroup file
"net_cls.classid" and cleared when a negative value is written.
is_local is visible to userland via
Hello, guys.
This patchset implements proper hierarchy support for netcls_cgroup.
Pretty simliar to the netprio one[3]. Simpler as each cgroup has
single config value instead of array of them.
This patchset contains the following three patches.
0001-netcls_cgroup-introduce-netcls_mutex.patch
netcls_cgroup implemented rather weird hierarchy behavior. A new
cgroup would inherit configuration from its parent but once created it
operates independently from its parent - updates to a parent doesn't
affect its children.
Proper hierarchy behavior can easily be implemented using cgroup
Introduce netcls_mutex to synchronize modifications to
cgroup_cls_state. New cgrp now inherits classid from ->css_online()
and write_classid() updates classid while holdin netcls_mutex.
As write_classid() doesn't propagate new configuration downwards, this
currently doesn't make any
On 11/15/2012 8:10 AM, Grant Likely wrote:
On Mon, 12 Nov 2012 18:48:43 -0800, Stepan Moskovchenko
wrote:
On 11/11/2012 5:45 PM, Stepan Moskovchenko wrote:
On Sun, Nov 11, 2012 at 2:32 AM, Rob Herring
wrote:
On 11/09/2012 06:48 PM, Stepan Moskovchenko wrote:
Use the cell-index property
On 11/16/2012 06:53 PM, Anton Vorontsov wrote:
On Fri, Nov 09, 2012 at 05:26:53PM -0800, Kees Cook wrote:
[]
@@ -171,7 +171,13 @@ static size_t ramoops_write_kmsg_hdr(struct
persistent_ram_zone *prz)
struct timeval timestamp;
size_t len;
- do_gettimeofday();
+
On Fri, Nov 09, 2012 at 05:26:53PM -0800, Kees Cook wrote:
[]
> >> @@ -171,7 +171,13 @@ static size_t ramoops_write_kmsg_hdr(struct
> >> persistent_ram_zone *prz)
> >> struct timeval timestamp;
> >> size_t len;
> >>
> >> - do_gettimeofday();
> >> + /* Handle dumping
On Mon, Oct 22, 2012 at 11:53:33AM -0700, Kees Cook wrote:
> On Wed, Oct 17, 2012 at 12:39 AM, Hannes Reinecke wrote:
> > The compiler complained about missing section annotations.
> > Fix it.
> >
> > Signed-off-by: Hannes Reinecke
> > Cc: Anton Vorontsov
> > Cc: Colin Cross
> > Cc: Kees Cook
On Sat, Sep 29, 2012 at 10:13:46AM +0300, Dan Carpenter wrote:
> psy->properties is an enum (32 bit type) so adding sizeof() puts us
> four times further along than we intended. It should be cast to a char
> pointer before doing the math.
>
> Signed-off-by: Dan Carpenter
> ---
> Casting to void
On Fri, 2012-11-16 at 17:34 +, Al Viro wrote:
> On Fri, Nov 16, 2012 at 08:43:28AM -0800, Linus Torvalds wrote:
> > On Fri, Nov 16, 2012 at 8:36 AM, Ian Kent wrote:
> > >
> > > Sure, are you recommending I alter the fs/libfs.c functions to add a
> > > function that doesn't have the outer
A virtual ethernet device that uses the NTB transport API to
send/receive data.
Signed-off-by: Jon Mason
Reviewed-by: Nicholas Bellinger
---
MAINTAINERS |1 +
drivers/net/Kconfig |4 +
drivers/net/Makefile |1 +
drivers/net/ntb_netdev.c | 419
I am submitting version 6 of the PCI-Express Non-Transparent Bridge
patches for inclusion in 3.8 via Greg KH's char-misc-next tree. All
outstanding issues have been addressed.
Version 6 corrects Greg KH's issues, most notably the improper usage of
the Linux device model.
Slightly less than a week, but since I'm leaving for vacation
tomorrow, here it is.
Things have continued to be pretty calm. We have a few more commits
here than there were in -rc5, but not enough to make me worry, and
most of the changes really tend to be tiny. And the few commits that
aren't
The LEN variable is unsigned, therefore checking whether it is less than 0 is
useless.
Signed-off-by: Cyril Roelandt
---
drivers/acpi/proc.c |2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/acpi/proc.c b/drivers/acpi/proc.c
index 27adb09..37871a7 100644
--- a/drivers/acpi/proc.c
On Sat, 2012-11-17 at 05:19 +0900, YAMANE Toshiaki wrote:
> Modify qt_status_change_check() and delete qt_status_change().
>
> Signed-off-by: YAMANE Toshiaki
> ---
> drivers/staging/serqt_usb2/serqt_usb2.c | 53
> +--
> 1 file changed, 22 insertions(+), 31
On Fri, Nov 16, 2012 at 01:57:09PM -0800, David Rientjes wrote:
> > > I'm wondering if we should have more than three different levels.
> > >
> >
> > In the case I outlined below, for backwards compatibility. What I
> > actually mean is that memcg *currently* allows arbitrary notifications.
> >
> pinctrl for Dove will not be enabled before DT clock support for Dove,
> which will hopefully make it into 3.8. If you agree, I will test and push it
> with the related patches for enabling pinctrl.
Ok. Thanks.
Axel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
* oleg.matcovs...@ti.com [121115 13:42]:
> From: Oleg Matcovschi
>
> OMAP_MODE_GPIO() macro verified only OMAP_MUX_MODE4.
Indeed, that needs to be fixed.
> It is not correct for following platforms:
> 2430 - gpio mux mode 3
> 44xx - gpio mux mode 3
Looks like these are set properly
Commit-ID: afd51a0e32cd79261f0e823400886ed322a355ac
Gitweb: http://git.kernel.org/tip/afd51a0e32cd79261f0e823400886ed322a355ac
Author: Alexander Duyck
AuthorDate: Fri, 16 Nov 2012 13:57:43 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 16 Nov 2012 16:42:10 -0800
x86/acpi: Use
Commit-ID: 217f155e9fc68bf2a6c58a7b47e0d1ce68d78818
Gitweb: http://git.kernel.org/tip/217f155e9fc68bf2a6c58a7b47e0d1ce68d78818
Author: Alexander Duyck
AuthorDate: Fri, 16 Nov 2012 13:57:32 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 16 Nov 2012 16:42:09 -0800
x86/ftrace: Use
Commit-ID: fc8d782677f163dee76427fdd8a92bebd2b50b23
Gitweb: http://git.kernel.org/tip/fc8d782677f163dee76427fdd8a92bebd2b50b23
Author: Alexander Duyck
AuthorDate: Fri, 16 Nov 2012 13:57:13 -0800
Committer: H. Peter Anvin
CommitDate: Fri, 16 Nov 2012 16:42:09 -0800
x86: Use __pa_symbol
1 - 100 of 1400 matches
Mail list logo
