This patch is to implement SSP SPI controller driver, which has been applied and
validated on intel Moorestown & Medfield platform. The patch are originated by
Ken Mills and Sylvain Centelles
,
migrating to lateset Linux mainline SPI framework by Channing
and Chen Jun according to their
On Mon, 17 Dec 2012, Mel Gorman wrote:
> Michal Hocko reported that the following build error occurs if
> CONFIG_NUMA_BALANCING is set without THP support
>
> kernel/sched/fair.c: In function â??task_numa_workâ??:
> kernel/sched/fair.c:932:55: error: call to â??__build_bug_failedâ?? declared
>
container_of() never returns NULL, thus remove the NULL checking for it.
Also rename get_max77686_clk() to to_max77686_clk() for better readability.
Signed-off-by: Axel Lin
---
drivers/clk/clk-max77686.c | 30 --
1 file changed, 8 insertions(+), 22 deletions(-)
This makes it possible to release mmu_lock and reschedule conditionally
in a later patch. Although this may increase the time needed to protect
the whole slot when we start dirty logging, the kernel should not allow
the userspace to trigger something that will hold a spinlock for such a
long time
No reason to make callers take mmu_lock since we do not need to protect
kvm_mmu_change_mmu_pages() and kvm_mmu_slot_remove_write_access()
together by mmu_lock in kvm_arch_commit_memory_region(): the former
calls kvm_mmu_commit_zap_page() and flushes TLBs by itself.
Note: we do not need to protect
Not needed any more.
Signed-off-by: Takuya Yoshikawa
---
Documentation/virtual/kvm/mmu.txt |7 ---
arch/x86/include/asm/kvm_host.h |5 -
arch/x86/kvm/mmu.c| 10 --
3 files changed, 0 insertions(+), 22 deletions(-)
diff --git
If the userspace starts dirty logging for a large slot, say 64GB of
memory, kvm_mmu_slot_remove_write_access() needs to hold mmu_lock for
a long time such as tens of milliseconds. This patch controls the lock
hold time by asking the scheduler if we need to reschedule for others.
One penalty for
Better to place mmu_lock handling and TLB flushing code together since
this is a self-contained function.
Signed-off-by: Takuya Yoshikawa
---
arch/x86/kvm/mmu.c |3 +++
arch/x86/kvm/x86.c |5 +
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kvm/mmu.c
No longer need to care about the mapping level in this function.
Signed-off-by: Takuya Yoshikawa
---
arch/x86/kvm/mmu.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 01d7c2a..bee3509 100644
--- a/arch/x86/kvm/mmu.c
ebied...@xmission.com (Eric W. Biederman) writes:
> Linus,
>
> Please pull the for-linus git tree from:
>
>git://git.kernel.org:/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
> for-linus
>
>HEAD: 5155040ed349950e16c093ba8e65ad534994df2a userns: Fix typo in
> description of the
On Tue, Dec 18, 2012 at 10:19:21AM +0800, Chao Xie wrote:
> On Tue, Dec 18, 2012 at 4:19 AM, Sascha Hauer wrote:
> > On Thu, Dec 06, 2012 at 10:52:03AM +0800, Chao Xie wrote:
> >> hi
> >> When develop the clk drivers for SOCs based on common clock framework.
> >> I met a issue.
> >> For example
devm_kzalloc returns NULL on failure.
Signed-off-by: Axel Lin
---
drivers/clk/clk-max77686.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/clk/clk-max77686.c b/drivers/clk/clk-max77686.c
index d098f72..8944214 100644
--- a/drivers/clk/clk-max77686.c
+++
On Tue, Dec 18, 2012 at 10:12:03AM +0900, Namhyung Kim wrote:
> Hi Jiri,
>
> On Mon, 17 Dec 2012 14:37:04 +0100, Jiri Olsa wrote:
> > Adding support to parse non architectural event aliases
> > for given cpu. These aliases will be provided as 'events'
> > directory like architectural ones
This is needed to make kvm_mmu_slot_remove_write_access() rmap based:
otherwise we may end up using invalid rmap's.
Signed-off-by: Takuya Yoshikawa
---
arch/x86/kvm/x86.c |9 -
virt/kvm/kvm_main.c |1 -
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git
This patch set makes kvm_mmu_slot_remove_write_access() rmap based and
adds conditional rescheduling to it.
The motivation for this change is of course to reduce the mmu_lock hold
time when we start dirty logging for a large memory slot. You may not
see the problem if you just give 8GB or less
We need to set trampoline code to EXEC early before we do smp
AP bootings.
Found the problem after switching to #PF handler set page table.
Change to use early_initcall instead.
Signed-off-by: Yinghai Lu
---
arch/x86/realmode/init.c |3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
with #PF handler way to set early page table, level3_ident will go away.
So just use entry in init_level4_pgt to set them
Signed-off-by: Yinghai Lu
---
arch/x86/realmode/init.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/realmode/init.c
There several places to find ramdisk information early for reserving
and relocating.
Use functions to make code more readable and consistent.
Later will add ext_ramdisk_image/size in those functions to support
loading ramdisk above 4g.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c |
cmdline.c::__cmdline_find_option... are shared between
16-bit setup code and 32/64 bit decompressor code.
for 32/64 only path via kexec, we should not check if ptr less 1M.
as those cmdline could be put above 1M, or even 4G.
Move out accessible checking out of __cmdline_find_option()
So
They are the same, could move them out from head32/64.c to setup.c.
We are using memblock, and it could handle overlapping properly, so
we don't need to reserve some at first to hold the location, and just
need to make sure we reserve them before we are using memblock to find
free mem to use.
boot/compressed/misc.c is used for bzImage in 64bit and 32bit, and
cmd_line_ptr could point to buffer that is above 4g, cmd_line_ptr
should be 64 bit otherwise high 32 bit will be capped out.
So need to change data type to unsigned long, that will be 64bit get correct
address of command line
later will check ext_cmd_line_ptr at the same time.
Signed-off-by: Yinghai Lu
---
arch/x86/boot/compressed/cmdline.c | 10 --
arch/x86/kernel/head64.c | 13 +++--
2 files changed, 19 insertions(+), 4 deletions(-)
diff --git a/arch/x86/boot/compressed/cmdline.c
Now we have limit kdump reseved under 896M, because kexec has the limitation.
and also bzImage need to stay under 4g.
To make kexec/kdump could use range above 4g, we need to make bzImage and
ramdisk could be loaded above 4g.
During booting bzImage will be unpacked on same postion and stay high.
During debug load kernel above 4G, found one page if is not used in BRK
and it should be with early page allocation.
Fix that checking and also add print out for every allocation from BRK
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init.c |4 +++-
1 file changed, 3 insertions(+), 1
After we switch to use #PF handler help to set page table, init_level4_pgt
will have entries set after init_mem_mapping.
We need to move coping init_level4_pgt to trampoline_pgd after than.
So separate reserve_real_mode out
Move the setup after init_mem_mapping()
Signed-off-by: Yinghai Lu
---
From: "H. Peter Anvin"
two use cases:
1. We will support load and run kernel above 4G, and zero_page, ramdisk
will be above 4G, too
2. need to access ramdisk early to get microcode to update that as
early possible.
We could use early_iomap to access them, but it will make code to
messy
Now 64bit kernel supports more than 1T ram and kexec tools
could find buffer above 1T, remove that obsolete limitation.
and use MAXMEM instead.
Tested on system more than 1024G ram.
Signed-off-by: Yinghai Lu
Cc: "Eric W. Biederman"
---
arch/x86/include/asm/kexec.h |6 +++---
1 file
When first kernel is booted with memmap= or mem= to limit max_pfn.
kexec can load second kernel above that max_pfn.
We need to set ident mapping for whole image in this case not just
for first 2M.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/machine_kexec_64.c | 43
We should not set mapping for all under max_pfn.
That causes same problem that is fixed by
x86, mm: Only direct map addresses that are marked as E820_RAM
This patch expose pfn_mapped array, and only set ident mapping for range
in that array.
This patch rely on new ident_mapping_init
Now ident_mapping_init is checking if pgd/pud is present for every 2M,
so several 2Ms are in same PUD, it will keep checking if pud is there.
init_level4_page does not check existing pgd/pud.
We will need to use ident_mapping_init with pfn_mapped array to
map ram only, and two entries in
Now 64bit entry is fixed on 0x200, can not be changed anymore.
Update the comments to reflect that.
Also put info about it in boot.txt
Signed-off-by: Yinghai Lu
---
Documentation/x86/boot.txt | 38
arch/x86/boot/compressed/head_64.S | 22
Normal boot path on system with iommu support:
swiotlb buffer will be allocated early at first and then try to initialize
iommu, if iommu for intel or amd could setup properly, swiotlb buffer
will be freed.
The early allocating is with bootmem, and could panic when we try to use
kdump with buffer
VM don't need to swap out volatile pages. Instead, it just discards
pages and set true to the vma's purge state so if user try to access
purged vma without calling mnovolatile, it will encounter SIGBUS.
Reclaimer reclaims volatile page when it reaches tail of LRU regardless
of the recent
That is for bootloader.
setup_data is in setup_header, and all bootloader is copying that
for bzImage. So for old bootloader should keep that as 0.
kexec till now for elf image, will set setup_data to 0.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c |6 --
1 file changed, 6
So use could disable swiotlb from command line, even swiotlb support
is compiled in. Just like we have intel_iommu=on and intel_iommu=off.
Signed-off-by: Yinghai Lu
---
Documentation/kernel-parameters.txt |7 +++
arch/x86/kernel/pci-swiotlb.c | 10 +-
Now kexeced kernel/ramdisk could be above 4g, so remove 896 limit for
64bit.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/setup.c |4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 15ce495..2631008 100644
---
We are short of space before 0x200 that is entry for startup_64.
According to hpa, we can not change startup_64 to other offset and
that become ABI now.
We could move function verify_cpu and no_longmode down, because one is
used via call and another will not return.
So could avoid extra code of
ext_ramdisk_image/size will record high 32bits for ramdisk info.
xloadflags bit0 will be set if relocatable with 64bit.
Let get_ramdisk_image/size to use ext_ramdisk_image/size to get
right positon for ramdisk.
bootloader will fill value to ext_ramdisk_image/size when it load
ramdisk above 4G.
During kdump kernel's booting stage, it need to find low ram for
swiotlb buffer when system does not support intel iommu/dmar remapping.
kexed-tools is appending memmap=exactmap and range from /proc/iomem
with "Crash kernel", and that range is above 4G for 64bit after boot
protocol 2.12.
We need
They are the same, could move them out from head32/64.c to setup.c.
We are using memblock, and it could handle overlapping properly, so
we don't need to reserve some at first to hold the location, and just
need to make sure we reserve them before we are using memblock to find
free mem to use.
We don't need to panic in some case, like for swiotlb preallocating.
Signed-off-by: Yinghai Lu
---
include/linux/bootmem.h |5 +
mm/bootmem.c|8
mm/nobootmem.c |8
3 files changed, 21 insertions(+)
diff --git a/include/linux/bootmem.h
On Tuesday, December 18, 2012 12:51 AM, Joe Perches wrote
> On Mon, 2012-12-17 at 17:22 +0900, Jingoo Han wrote:
> > Add the lms501kf03 LCD panel driver. The lms501kf03 LCD panel (800
> > x 480) driver uses 3-wired SPI inteface.
>
> A trivial note:
>
> > diff --git
commit 08da5a2ca
x86_64: Early segment setup for VT
add lldt/ltr to clean more segments.
Those code are put in code64, and it is using gdt that is only
loaded from code32 path.
That breaks booting with 64bit bootloader that does not go through
code32 path. It get at startup_64 directly,
Just like PUD_SIZE, and PMD_SIZE next calculation, aka
round down and add size.
also remove not need next checking, just pass end instead.
later phys_pud_init uses PTRS_PER_PUD checking to exit early
if end is too big.
Signed-off-by: Yinghai Lu
---
arch/x86/mm/init_64.c |6 ++
1 file
We are not having max_pfn_mapped set correctly until init_memory_mapping.
so don't print it initial value for 64bit
Also need to use KERNEL_IMAGE_SIZE directly for highmap cleanup.
Signed-off-by: Yinghai Lu
---
arch/x86/kernel/head64.c |3 ---
arch/x86/kernel/setup.c |2 ++
As pointer to PHY structure can be stored in struct usb_hcd
making use of it, to call PHY APIs.
Call to usb_phy_shutdown() is moved up in tegra_ehci_remove(),
so that to avoid dereferencing of hcd after its freed up.
Signed-off-by: Venu Byravarasu
---
This patch depends on patch
On Tuesday 18 December 2012 11:54 AM, Laxman Dewangan wrote:
On Tuesday 18 December 2012 11:44 AM, Prashant Gaikwad wrote:
On Tuesday 18 December 2012 03:13 AM, Stephen Warren wrote:
On 12/17/2012 05:08 AM, Laxman Dewangan wrote:
Tegra20 uart clock source have the 15.1 clock divider in place
On Tuesday 18 December 2012 03:14 AM, Stephen Warren wrote:
On 12/17/2012 05:08 AM, Laxman Dewangan wrote:
Add connection name "uart-clk" for the uart clock information.
Does the UART receive more than one clock, so that it actually cares
what the clock connection name is? If not, can we just
Nvidia's Tegra has multiple uart controller which supports:
- APB dma based controller fifo read/write.
- End Of Data interrupt in incoming data to know whether end
of frame achieve or not.
- Hw controlled RTS and CTS flow control to reduce SW overhead.
Add serial driver to use all above
On Tuesday 18 December 2012 11:48 AM, Prashant Gaikwad wrote:
On Tuesday 18 December 2012 03:17 AM, Stephen Warren wrote:
On 12/17/2012 05:08 AM, Laxman Dewangan wrote:
Add OF_DEV_AUXDATA for high speed uart controller driver for
Tegra20/Tegra30 board dt files.
Set the parent clock of uart
On 12/18/2012 06:55 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 20:47 Mon 17 Dec , Wolfgang Grandegger wrote:
>> On 12/17/2012 07:02 PM, Roland Stigge wrote:
>>> On 12/17/2012 06:37 PM, Wolfgang Grandegger wrote:
/* Do synchronous data output with a single write access */
This patch adds new system call m[no]volatile. If some user asks
is_volatile system call, it could, too.
The reason why I introduced new system call instead of madvise is
m[no]volatile vma handling is totally different with madvise's vma
handling.
1) The m[no]volatile should be successful
This patch add pgvolatile vmstat so admin can see how many of volatile
pages are discarded by VM until now. It could be a good indicator of
patch effect during test but still not sure we need it in real practice.
Will rethink it.
Cc: Michael Kerrisk
Cc: Arun Sharma
Cc: san...@google.com
Cc:
This is still RFC because we need more input from user-space
people and discussion about interface/reclaim policy of volatile
pages and I want to expand this concept to tmpfs volatile range
if it is possbile without big performance drop of anonymous volatile
rnage (Let's define our term. anon
Hi Linus,
The following changes since commit fa4c95bfdb85d568ae327d57aa33a4f55bab79c4:
Merge branch 'for_linus' of
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs (2012-12-17
08:27:59 -0800)
are available in the git repository at:
On 12/17/2012 10:33 PM, Roland Stigge wrote:
> On 17/12/12 20:47, Wolfgang Grandegger wrote:
>> On 12/17/2012 07:02 PM, Roland Stigge wrote:
>>> On 12/17/2012 06:37 PM, Wolfgang Grandegger wrote:
/* Do synchronous data output with a single write access */
__raw_writel(~mask, pio +
On 22:14 Mon 17 Dec , Olof Johansson wrote:
> On Mon, Dec 17, 2012 at 10:00 PM, Jean-Christophe PLAGNIOL-VILLARD
> wrote:
> > On 17:56 Mon 17 Dec , Olof Johansson wrote:
> >> On Mon, Dec 17, 2012 at 11:55 AM, Dongjin Kim wrote:
> >> > Add initial dtb file for Hardkernel's ODROID-X board
Using devm_kzalloc for allocating memory needed for PHY
pointer and hence removing kfree calls to PHY pointer.
Signed-off-by: Venu Byravarasu
---
drivers/usb/phy/tegra_usb_phy.c |4 +---
1 files changed, 1 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/phy/tegra_usb_phy.c
On 20:47 Mon 17 Dec , Wolfgang Grandegger wrote:
> On 12/17/2012 07:02 PM, Roland Stigge wrote:
> > On 12/17/2012 06:37 PM, Wolfgang Grandegger wrote:
> >>/* Do synchronous data output with a single write access */
> >>__raw_writel(~mask, pio + PIO_OWDR);
> >>__raw_writel(mask, pio
On 17.12.2012 22:55, Stephen Warren wrote:
> On 12/16/2012 09:37 AM, Terje Bergström wrote:
> ...
>> ... Sure we could tell DC to ask its parent
>> (host1x), and call host1x driver with platform_device pointer found that
>> way, and host1x would return a pointer to tegradrm's data. Hanging the
>>
Currently these DBG statements are emitted at KERN_DEFAULT.
Change the macro to emit at KERN_DEBUG.
This can help avoid unexpected message interleaving.
Signed-off-by: Joe Perches
---
Another way to fix this message interleaving...
drivers/acpi/glue.c |9 +++--
1 files changed, 7
On Tuesday 18 December 2012 11:44 AM, Prashant Gaikwad wrote:
On Tuesday 18 December 2012 03:13 AM, Stephen Warren wrote:
On 12/17/2012 05:08 AM, Laxman Dewangan wrote:
Tegra20 uart clock source have the 15.1 clock divider in place of
That says Tegra20, but ...
7.1. Add support for 15.1
On Mon, 2012-12-17 at 13:02 -0800, Stephen Boyd wrote:
> Reduce lines of code and simplify this driver by using the
> generic clock binding parsing function.
>
> Signed-off-by: Stephen Boyd
> Cc: Tony Prisk
> ---
> drivers/clk/clk-vt8500.c | 39 +++
> 1 file
On Tuesday 18 December 2012 03:17 AM, Stephen Warren wrote:
On 12/17/2012 05:08 AM, Laxman Dewangan wrote:
Add OF_DEV_AUXDATA for high speed uart controller driver for
Tegra20/Tegra30 board dt files.
Set the parent clock of uart controller to PLLP.
diff --git
On Tuesday 18 December 2012 03:13 AM, Stephen Warren wrote:
On 12/17/2012 05:08 AM, Laxman Dewangan wrote:
Tegra20 uart clock source have the 15.1 clock divider in place of
That says Tegra20, but ...
7.1. Add support for 15.1 clock divider and change the uart clock divider
flag to DIV_U151.
On Mon, Dec 17, 2012 at 10:00 PM, Jean-Christophe PLAGNIOL-VILLARD
wrote:
> On 17:56 Mon 17 Dec , Olof Johansson wrote:
>> On Mon, Dec 17, 2012 at 11:55 AM, Dongjin Kim wrote:
>> > Add initial dtb file for Hardkernel's ODROID-X board based on EXYNOS4412
>> > SoC.
>> >
>> > Signed-off-by:
Hi Fabio!
> On Mon, Dec 17, 2012 at 09:20:57PM +0100, "Bernd Krumböck" wrote:
>> > If you think it's useful for USB controller, just tell me or modify
>> the
>> > driver by yourself! As you see the patch is really easy.
>>
>> At least it is useful for the usb_8dev driver. I'll write a patch.
>>
On 17:56 Mon 17 Dec , Olof Johansson wrote:
> On Mon, Dec 17, 2012 at 11:55 AM, Dongjin Kim wrote:
> > Add initial dtb file for Hardkernel's ODROID-X board based on EXYNOS4412
> > SoC.
> >
> > Signed-off-by: Dongjin Kim
> > ---
> > arch/arm/boot/dts/Makefile |1 +
> >
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 | 10 +++
drivers/usb/phy/samsung-usbphy.c | 80 ++--
2 files
Based on patches for samsung-usbphy driver available at:
https://patchwork.kernel.org/patch/1794651/
In this patch we are adding support to parse device tree data for
samsung-usbphy driver and further setting pmu_isolation to
enable/disable phy as and when needed.
This further chucks out the need
On Fri, Dec 14, 2012 at 09:02:41PM +0100, Oleg Nesterov wrote:
> On 12/03, Suzuki K. Poulose wrote:
> >
> > Replace the ptrace helpers with the powerpc generic routines to
> > enable/disable single step. We save/restore the MSR (and DCBR for BookE)
> > across for the operation. We don't have to
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux.git
tags/virtio-next-for-linus
for you to fetch changes up to 1b6370463e88b0c1c317de16d7b962acc1dab4f2:
virtio_console: Add support for remoteproc serial (2012-12-18 15:20:44 +1030)
On 18 December 2012 06:59, Jingoo Han wrote:
> On Monday, Monday, December 17, 2012 7:01 PM, Sachin Kamat wrote
>>
>> Hi Jingoo,
>>
>> I had already submitted a patch for adding support for this driver [1]
>> and you had also provided your review comments on them ([2] and [3]).
>> There were
On Tuesday, December 18, 2012 2:00 PM, Sachin Kamat wrote
> On 18 December 2012 06:59, Jingoo Han wrote:
> > On Monday, Monday, December 17, 2012 7:01 PM, Sachin Kamat wrote
> >>
> >> Hi Jingoo,
> >>
> >> I had already submitted a patch for adding support for this driver [1]
> >> and you had also
When debug kernel, the the below information is found:
intel_idle: unaware of model 0x1a MWAIT 4 please contact lenb@kernel.orgACPI:
Device input0 -> No ACPI support
so this patch separates it.
Signed-off-by: Youquan Song
---
drivers/idle/intel_idle.c |2 +-
1 files changed, 1
Hey Jens,
Please git pull the following branch:
git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
stable/for-jens-3.8
which has a bug-fix to the xen-blkfront and xen-blkback driver
when using the persistent mode. An issue was discovered where LVM
disks could not be read correctly
Run in perf utility at Ivybridge EP server, encouter "not supported" event
L1-dcache-loads
L1-dcache-load-misses
L1-dcache-stores
L1-dcache-store-misses
L1-dcache-prefetches
L1-dcache-prefetch-misses
This patch add the support for this processor.
On 12/15/2012 01:32 AM, Oleg Nesterov wrote:
On 12/03, Suzuki K. Poulose wrote:
Replace the ptrace helpers with the powerpc generic routines to
enable/disable single step. We save/restore the MSR (and DCBR for BookE)
across for the operation. We don't have to disable the single step,
as
Thank you for reviewing my patch.
I will update it in accordance with your comment.
Seiji
> -Original Message-
> From: Steven Rostedt [mailto:rost...@goodmis.org]
> Sent: Monday, December 17, 2012 10:02 PM
> To: Seiji Aguchi
> Cc: x...@kernel.org; linux-kernel@vger.kernel.org; H. Peter
If menuconfig have Save/Load button like alternative
.config editors, xconfig, nconfig, etc.We will have
a obvious benefit when use menuconfig just like
when we use others, we can Save/Load our .config quickly
and conveniently.
This patch add the Save/Load button for menuconfig.
[remove trailing
Hello Omar Ramirez Luna:
excuse me to bother you (maybe you are busy in these days).
please help checking this suggestion when you have free time.
my suggestion may be not valid (I already have at least 9 fault which
I made)
for example of my fault:
A) net/atm: "%pM means format
Blacklist x2apic when Nivida graphics enabled on Lenovo ThinkPad T420.
Also set blacklist x2apic for Lenovo ThinkPad W520 and L520.
Thre are 3 bug reports:
https://bugzilla.kernel.org/show_bug.cgi?id=43054
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/776999
From: Jason Wang
Date: Tue, 18 Dec 2012 11:00:27 +0800
> Make tun_enable_queue() static to fix the sparse warning:
>
> drivers/net/tun.c:399:19: sparse: symbol 'tun_enable_queue' was not declared.
> Should it be static?
>
> Reported-by: Fengguang Wu
> Signed-off-by: Jason Wang
Applied,
USB register base address and sizes defined in iomap.h
are not used in any files other than board-dt-tegra20.c.
Hence removed those defines from header file and using
the absolute values in board files.
Signed-off-by: Venu Byravarasu
---
arch/arm/mach-tegra/board-dt-tegra20.c |6 +++---
On Fri, 14 Dec 2012, Konstantin Khlebnikov wrote:
> This bio pool guarantees reclaiming progress for anonymous pages.
> All avaliable bio in fs_bio_set may be borrowed by writeback which may
> never ends, because disk too slow or broken. I have seen this situation in
> real life in system where
Most SIP devices use a source port of 5060/udp on SIP requests, so the
response automatically comes back to port 5060:
phone_ip:5060 -> proxy_ip:5060 REGISTER
proxy_ip:5060 -> phone_ip:5060 100 Trying
The newer Cisco IP phones, however, use a randomly chosen high source
port for the
Hi Linus,
Not much for md this time round.
Thanks,
NeilBrown
The following changes since commit 874807a83139abc094f939e93623c5623573d543:
md/raid1{,0}: fix deadlock in bitmap_unplug. (2012-11-27 12:14:40 +1100)
are available in the git repository at:
git://neil.brown.name/md/
On Tue, Dec 18, 2012 at 12:09 PM, Kees Cook wrote:
>
> Do you mean a printk should be emitted on this error path? I can add that if
> so.
dev_err() should be better. With that, please feel free to add
Acked-by: Ming Lei
Thanks,
--
Ming Lei
--
To unsubscribe from this list: send the
On Tuesday, December 18, 2012 1:51 AM, devendra.aaru wrote
> Hello,
>
> > +static int lms501kf03_spi_write(struct lms501kf03 *lcd, unsigned char
> > address,
> > + unsigned char command)
> > +{
> > + int ret;
> > +
> > + ret =
On Fri, 14 Dec 2012, Konstantin Khlebnikov wrote:
> Content of non-uptodate pages completely random, we cannot expose them into
> userspace. This leads to information leak and will crash userspace for sure.
Good find, yes, it's very wrong as is. But, sorry, I don't like your fix
- better than
(At least I think that's where 'cpu_list_show' comes from...
those preprocessor tricks confuse ctags)
Just started seeing this today..
(fwiw, cpu is a Phenom(tm) 9750)
Dave
WARNING: at kernel/mutex.c:198 mutex_lock_nested+0x39c/0x3b0()
Hardware name: GA-MA78GM-S2H
Modules linked in:
On Mon, Dec 17, 2012 at 6:15 PM, Ming Lei wrote:
> On Tue, Dec 18, 2012 at 9:37 AM, Kees Cook wrote:
>> On Mon, Dec 17, 2012 at 5:30 PM, Ming Lei wrote:
>>> On Sat, Dec 15, 2012 at 6:51 AM, Kees Cook wrote:
Some devices have configurable firmware locations. If these configuration
regulator_get_voltage() may return negative error code.
Add error checking to avoid setting error code to voltage_uv.
Signed-off-by: Axel Lin
---
Sorry. Just found I made the same mistake again.
Here is v2, should check if ret is negative value.
drivers/iio/dac/ad5446.c |6 +-
1 file
On Mon, 17 Dec 2012, Sasha Levin wrote:
> Switch ksm to use the new hashtable implementation. This reduces the amount of
> generic unrelated code in the ksm module.
>
> This patch depends on d9b482c ("hashtable: introduce a small and naive
> hashtable") which was merged in v3.6.
>
>
Make tun_enable_queue() static to fix the sparse warning:
drivers/net/tun.c:399:19: sparse: symbol 'tun_enable_queue' was not declared.
Should it be static?
Reported-by: Fengguang Wu
Signed-off-by: Jason Wang
---
drivers/net/tun.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
On Tue, 2012-12-18 at 01:34 +, Seiji Aguchi wrote:
> Change log
>
> v5 -> v6
> - Rebased to 3.7
>
> v4 -> v5
> - Rebased to 3.6.0
>
> - Introduce a logic switching IDT at enabling/disabling TP time
>so that a time penalty makes a zero when tracepoints are disabled.
>This IDT
Hi all,
Changes since 20121217:
Lots of conflicts are migrating between trees.
The btrfs tree lost its build failure.
The akpm tree gained a build failure for which I applied a patch.
I have created today's linux
From: fangxiaozhi
1. Optimize the match rules with new macro for Huawei USB storage devices,
to avoid to load USB storage driver for the modem interface
with Huawei devices.
2. Add to support new switch command for new Huawei USB dongles.
Signed-off-by: fangxiaozhi
On Mon, Dec 17, 2012 at 11:22:02AM -0700, Jason Gunthorpe wrote:
> On Tue, Dec 18, 2012 at 12:14:33AM +0800, Feng Tang wrote:
>
> > > Sure, but my view on this is that it has nothing to do with
> > > read_persistent_clock. If the RTC driver can run with IRQs off is a
> > > property of the RTC
On Mon, Dec 17, 2012 at 5:57 PM, Al Viro wrote:
> On Mon, Dec 17, 2012 at 05:10:21PM -0800, Andy Lutomirski wrote:
>> I want to change inode->i_flags access to be atomic -- there are some
>> locking oddities right now, I think, and I want to use a new inode
>> flag to signal mtime updates from
1 - 100 of 1206 matches
Mail list logo
