[PATCH 1/1] e1000: prevent oops when adapter is being closed and reset simultaneously

2013-11-21 Thread yzhu1
Hi, maintainers This change is based on a similar change made to e1000e support in commit bb9e44d0d0f4 ("e1000e: prevent oops when adapter is being closed and reset simultaneously"). The same issue has also been observed on the older e1000 cards. Here, we have increased the RESET_COUNT value

[f2fs-dev] [PATCH] f2fs: readahead contiguous pages for restore_node_summary

2013-11-21 Thread Chao Yu
If cp has no CP_UMOUNT_FLAG, we will read all pages in whole node segment one by one, it makes low performance. So let's merge contiguous pages and readahead for better performance. Signed-off-by: Chao Yu --- fs/f2fs/node.c | 89 +++- 1

[PATCH] net: sctp: set chunk->tsn_gap_acked at the end of cycle

2013-11-21 Thread Chang Xiangzhong
tsn_gap_acked is an important state flag in chunk, which indicates if the chunk has been acked in gap reports before. SFR-CACC algorithm depends on this variable. So set this at the end of each iteration, otherwise the SFR-CACC algorithm would never be toggled. Signed-off-by: Chang Xiangzhong

Re: [PATCH V2] Cpufreq: Make governor data on nonboot cpus across system suspend/resume

2013-11-21 Thread viresh kumar
On Sunday 17 November 2013 09:43 AM, viresh kumar wrote: > On 16 November 2013 21:06, Lan Tianyu wrote: > But I don't really like the solution here. You are handling frozen for EXIT in > cpufreq-core and for INIT in governor. That doesn't look like the right > approach. There are out of tree

Personal email(22 November 2013)

2013-11-21 Thread Mrs Nicole Marois
CONTACT US IMMEDIATELY FOR YOUR PAYMENT. Dear Beloved Friend, I am Mrs Nicole Marois Benoite, and i have been suffering from ovarian cancer disease and the doctor says that i have just few days to leave. I am from (Paris) France but based in Africa Burkina Faso since eleven years ago as a

Re: [PATCH linux-next] hisax: disable build for big-endian arm

2013-11-21 Thread Karsten Keil
l >> --- >> >> Hi, >> >> This can be seen on e.g. linux next-20131121 with arm allyesconfig. >> >> Best regards, >> >> V. >> >> drivers/isdn/hisax/Kconfig | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> &

Re: [PATCH 6/7] Squashfs: Directly decompress into the page cache for file data

2013-11-21 Thread Roman Peniaev
Hello, Phillip. one remark below: > > +static int squashfs_read_cache(struct page *target_page, u64 block, int bsize, > + int pages, struct page **page) > +{ > + struct inode *i = target_page->mapping->host; > + struct squashfs_cache_entry *buffer = squashfs_get_datablock(i- >i_sb,

Re: 3.12: kernel panic when resuming from suspend to RAM (x86_64)

2013-11-21 Thread Francis Moreau
Le 21/11/2013 12:17, Jingoo Han a écrit : [...] >> >>> Also I took a look at the changes between v3.11 and v3.12 in this area >>> and those changes match the issue I'm facing: >>> >>> $ git log --oneline v3.11..v3.12 -- drivers/mfd/rtsx_pcr.c >>> 09fd867 mfd: rtsx: Copyright modifications >>>

Re: [PATCHv5 2/9] driver/core: populate devices in order for IOMMUs

2013-11-21 Thread Grant Likely
On Thu, 21 Nov 2013 12:04:18 -0700, Stephen Warren wrote: > On 11/21/2013 06:15 AM, Grant Likely wrote: > > On Tue, 19 Nov 2013 11:33:06 +0200, Hiroshi Doyu wrote: > >> IOMMU devices on the bus need to be poplulated first, then iommu > >> master devices are done later. > >> > >> With

[PATCH V3] Cpufreq: Make governor data on nonboot cpus across system suspend/resume

2013-11-21 Thread Lan Tianyu
Currently, governor of nonboot cpus will be put to EXIT when system suspend. Since all these cpus will be unplugged and the governor usage_count decreases to zero. The governor data and its sysfs interfaces will be freed or released. This makes user config of these governors loss during suspend

Re: [PATCH] mm/zswap: change params from hidden to ro

2013-11-21 Thread Vladimir Murzin
On Wed, Nov 20, 2013 at 12:52:47PM -0500, Dan Streetman wrote: > On Wed, Nov 20, 2013 at 12:33 PM, Vladimir Murzin wrote: > > Hi Dan! > > > > On Wed, Nov 20, 2013 at 11:38:42AM -0500, Dan Streetman wrote: > >> The "compressor" and "enabled" params are currently hidden, > >> this changes them to

Re: Some kernel module options not showing up in modinfo

2013-11-21 Thread Raphael Hertzog
Hi, On Fri, 22 Nov 2013, Rusty Russell wrote: > Raphael Hertzog writes: > > Hello, > > > > I noticed that some options are not visible in the modinfo output. For > > instance "modinfo lockd" reports this on my Debian sid system: [...] > > Multiple other options are defined by way of

Re: [PATCH 1/2] i2c: exynos5: add support for HSI2C on Exynos5260 SoC

2013-11-21 Thread Naveen Krishna Ch
Hello Yuvaraj, On 22 November 2013 12:16, Yuvaraj Cd wrote: > On Fri, Nov 22, 2013 at 11:42 AM, Naveen Krishna Chatradhi > wrote: >> This patch adds new compatible to support HSI2C module on Exynos5260 >> HSI2C module on Exynos5260 needs to be reset during during initialization. >> >>

Re: [PATCH linux-next] hisax: disable build for big-endian arm

2013-11-21 Thread Takashi Iwai
At Fri, 22 Nov 2013 00:49:54 +0100, Vincent Stehlé wrote: > > Teles PCI and HFC PCI-bus refuse to build on big-endian ARM; disable them in > Kconfig. > > Signed-off-by: Vincent Stehlé > Cc: Karsten Keil > --- > > Hi, > > This can be seen on e.g. linux ne

Re: user defined OOM policies

2013-11-21 Thread Vladimir Murzin
On Wed, Nov 20, 2013 at 06:33:57PM +0100, Michal Hocko wrote: > On Wed 20-11-13 18:21:23, Vladimir Murzin wrote: > > On Tue, Nov 19, 2013 at 02:40:07PM +0100, Michal Hocko wrote: > > Hi Michal > > > On Tue 19-11-13 14:14:00, Michal Hocko wrote: > > > [...] > > > > We have basically ended up with 3

RE: [PATCHv6 0/4] Add Freescale FTM PWM driver.

2013-11-21 Thread Li Xiubo
Hi Thierry, Could you help review this series of patches please ? And could it be merged into the PWM next tree? Thanks very much. -- > Subject: [PATCHv6 0/4] Add Freescale FTM PWM driver. > > Hello Thierry, > > The series of patches for this version has been reviewed and acked > already.

Re: [PATCH 0/3] makedumpfile: hugepage filtering for vmcore dump

2013-11-21 Thread HATAYAMA Daisuke
(2013/11/07 9:54), HATAYAMA Daisuke wrote: (2013/11/06 11:21), Atsushi Kumagai wrote: (2013/11/06 5:27), Vivek Goyal wrote: On Tue, Nov 05, 2013 at 09:45:32PM +0800, Jingbai Ma wrote: This patch set intend to exclude unnecessary hugepages from vmcore dump file. This patch requires the kernel

[PATCH] rtc: ds1511: add device-tree bindings

2013-11-21 Thread Marcus Folkesson
Compatible with ds1500, ds1501 and ds1511 Signed-off-by: Marcus Folkesson --- .../devicetree/bindings/rtc/maxim-ds1511.txt | 18 + drivers/rtc/rtc-ds1511.c | 85 +--- 2 files changed, 90 insertions(+), 13 deletions(-) create mode 100644

[PATCH RESEND] rtc: ds1511: add device-tree bindings

2013-11-21 Thread Marcus Folkesson
Resending patch. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/

Re: [PATCH] cpufreq: Make sure CPU is running on a freq from freq-table

2013-11-21 Thread viresh kumar
On Friday 22 November 2013 03:13 AM, Rafael J. Wysocki wrote: > On Thursday, November 21, 2013 09:56:32 AM Dirk Brandewie wrote: >> The scaling driver for the CPU has already loaded and its .init procedure >> has >> been called so .target better be callable. Yeah.. >> Since the scaling driver

Re: [PATCH] cpufreq: Make sure CPU is running on a freq from freq-table

2013-11-21 Thread viresh kumar
On Thursday 21 November 2013 12:39 PM, Viresh Kumar wrote: > Sometimes boot loaders set CPU frequency to a value outside of frequency table > present with cpufreq core. In such cases CPU might be unstable if it has to > run > on that frequency for long duration of time and so its better to set it

Re: [PATCH 6/7] sched: Clean up preempt_enable_no_resched() abuse

2013-11-21 Thread Eliezer Tamir
On 21/11/2013 15:39, Peter Zijlstra wrote: > On Thu, Nov 21, 2013 at 03:26:17PM +0200, Eliezer Tamir wrote: >> We don't override any limit the user has put on the system call. > > You are in fact, note how the normal select @endtime argument is only > set up _after_ you're done polling. So if

Re: [PATCH 1/2] i2c: exynos5: add support for HSI2C on Exynos5260 SoC

2013-11-21 Thread Yuvaraj Cd
On Fri, Nov 22, 2013 at 11:42 AM, Naveen Krishna Chatradhi wrote: > This patch adds new compatible to support HSI2C module on Exynos5260 > HSI2C module on Exynos5260 needs to be reset during during initialization. > > Signed-off-by: Naveen Krishna Chatradhi > --- >

Re: [PATCH V4 1/2] genirq: Add an accessor for IRQ_PER_CPU flag

2013-11-21 Thread Vinayak Kale
On Fri, Nov 22, 2013 at 6:24 AM, Stephen Boyd wrote: > On 11/20/13 22:10, Vinayak Kale wrote: >> [removing chris.sm...@st.com] >> >> On Thu, Nov 21, 2013 at 11:36 AM, Vinayak Kale wrote: >>> On Wed, Nov 20, 2013 at 11:46 PM, Stephen Boyd wrote: On 11/20/13 03:13, Vinayak Kale wrote: >

[RFC PATCH 3/4] sched: clean up __update_cpu_load

2013-11-21 Thread Alex Shi
Since we don't decay the rq->cpu_load, so we don't need the pending_updates. But we still want update rq->rt_avg, so still keep rq->last_load_update_tick and func __update_cpu_load. After remove the load_idx, in the most of time the source_load is equal to target_load, except only when source cpu

[RFC PATCH 2/4] sched: change rq->cpu_load[load_idx] array to rq->cpu_load

2013-11-21 Thread Alex Shi
Since load_idx effect removed in load balance, we don't need the load_idx decays in scheduler. that will save some time in sched_tick and others places. Signed-off-by: Alex Shi --- arch/ia64/include/asm/topology.h | 5 --- arch/metag/include/asm/topology.h | 5 ---

[RFC PATCH 4/4] sched/nohz_full: give correct cpu load for nohz_full cpu

2013-11-21 Thread Alex Shi
When a nohz_full cpu in tickless mode, it may update cpu_load in following chain: __tick_nohz_full_check tick_nohz_restart_sched_tick update_cpu_load_nohz then it will be set a incorrect cpu_load: 0. This patch try to fix it and give it the correct cpu_load value. Signed-off-by: Alex

[RFC PATCH 0/4] sched: remove cpu_load decay.

2013-11-21 Thread Alex Shi
The cpu_load decays on time according past cpu load of rq. New sched_avg decays on tasks' load of time. Now we has 2 kind decay for cpu_load. That is a kind of redundancy. And increase the system load in sched_tick etc. This patch trying to remove the cpu_load decay. And fixed a nohz_full bug

[RFC PATCH 1/4] sched: shortcut to remove load_idx effect

2013-11-21 Thread Alex Shi
Shortcut to remove rq->cpu_load[load_idx] effect in scheduler. In five load idx, only busy_idx, idle_idx are not zero. Newidle_idx, wake_idx and fork_idx are all zero in all archs. So, change the idx to zero here can fully remove load_idx. Signed-off-by: Alex Shi --- kernel/sched/fair.c | 2 +-

[PATCH] x86, efi: add efi_whitelist_table to use all efi variable storage

2013-11-21 Thread Yasuaki Ishimatsu
By following works, my system very often fails set_variable() to set new variable to efi variable storage and shows "efivars: set_variable() failed: status=-28" message. - commit 68d929862e29a8b52a7f2f2f86a0600423b093cd efi: be more paranoid about available space when creating variables -

Re: [PATCH] x86, efi: add no_bricked_efi whitelist

2013-11-21 Thread Yasuaki Ishimatsu
(2013/11/22 9:03), Matthew Garrett wrote: On Fri, 2013-11-22 at 09:00 +0900, Yasuaki Ishimatsu wrote: (2013/11/22 5:12), Matthew Garrett wrote: On Thu, 2013-11-21 at 18:35 +0900, Yasuaki Ishimatsu wrote: Remaining space is free space that can be used by efi variable. But by 5KB threshold, we

[PATCH 2/2] i2c: exynos5: configure fifo_depth based on HSI2C module version

2013-11-21 Thread Naveen Krishna Chatradhi
fifo_depth of the HSI2C is not constant Exynos5420 and Exynos5250 supports fifo_depth of 64bytes Exynos5260 supports fifo_depth of 16bytes This patch configures the fifo_depth based on HSI2C modules version. Signed-off-by: Naveen Krishna Chatradhi --- drivers/i2c/busses/i2c-exynos5.c | 29

[PATCH 1/2] i2c: exynos5: add support for HSI2C on Exynos5260 SoC

2013-11-21 Thread Naveen Krishna Chatradhi
This patch adds new compatible to support HSI2C module on Exynos5260 HSI2C module on Exynos5260 needs to be reset during during initialization. Signed-off-by: Naveen Krishna Chatradhi --- .../devicetree/bindings/i2c/i2c-exynos5.txt|6 +++- drivers/i2c/busses/i2c-exynos5.c

[PATCH 1/2] New Driver for IOSF-SB MBI access on Intel SOCs

2013-11-21 Thread David E. Box
From: "David E. Box" Current Intel SOC cores use a MailBox Interface (MBI) to provide access to unit devices connected to the system fabric. This driver implements the API required for other kernel drivers to configure the unit registers accessible through this interface. Drivers that will

[PATCH 2/2] ACPI / platform: Add ACPI ID for Intel IOSF-SB

2013-11-21 Thread David E. Box
From: "David E. Box" Adds ACPI ID for Intel IOSF-SB MailBox device found in BayTrail platforms. Signed-off-by: David E. Box --- drivers/acpi/acpi_platform.c |3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/acpi/acpi_platform.c b/drivers/acpi/acpi_platform.c

[git pull] drm fixes

2013-11-21 Thread Dave Airlie
Hi Linus, was going to leave this until post -rc1 but sysfs fixes broke hotplug in userspace, so I had to fix it harder, otherwise a set of pulls from intel, radeon and vmware, the vmware/ttm changes are bit larger but since its early and they are unlikely to break anything else I put them

Re: [PATCH 2/2] tracing/probes: Fix basic print type functions

2013-11-21 Thread Namhyung Kim
Hi Oleg, On Wed, 20 Nov 2013 16:22:45 +0100, Oleg Nesterov wrote: > On 11/18, Namhyung Kim wrote: >> >> -DEFINE_BASIC_PRINT_TYPE_FUNC(u8, "%x", unsigned int) >> -DEFINE_BASIC_PRINT_TYPE_FUNC(u16, "%x", unsigned int) >> -DEFINE_BASIC_PRINT_TYPE_FUNC(u32, "%lx", unsigned long) >>

Re: [PATCH V2 2/2] ARM: dts: Enable ahci sata and sata phy

2013-11-21 Thread Yuvaraj Kumar
Any comments on this patch? On Mon, Nov 11, 2013 at 2:02 PM, Yuvaraj Kumar C D wrote: > This patch adds dt entry for ahci sata controller and its > corresponding phy controller.phy node has been added w.r.t > new generic phy framework. > > Changes since V1: > 1.Minor changes to node name

Re: [PATCH V2 1/2] Phy: Exynos: Add Exynos5250 sata phy driver

2013-11-21 Thread Yuvaraj Kumar
Any comments on this patch? On Mon, Nov 11, 2013 at 2:02 PM, Yuvaraj Kumar C D wrote: > This patch adds the sata phy driver for Exynos5250.Exynos5250 sata > phy comprises of CMU and TRSV blocks which are of I2C register Map. > So this patch also adds a i2c client driver, which is used configure

Re: [PATCH] perf util: optimize util/machine.c:machines__find().

2013-11-21 Thread Dongsheng Yang
On 11/21/2013 07:06 PM, Arnaldo Carvalho de Melo wrote: This changes machines__find to always return the machine for the host (pid == 0). This function is also used for VM lookups. Nope: /* Native host kernel uses -1 as pid index in machine */ #define HOST_KERNEL_ID (-1)

RE: bug report about assert at [ kernel/fs/jbd2/transaction.c:2138 ]

2013-11-21 Thread Wang, Yalin
Hi Thanks for your reply very much ! Our kernel version is 3.4.0 , I am not sure if this version is the same with 2.6.29 ? I have a look at the fs/jbd2/commit.c file's git log . The latest commit is commit 99aa78466777083255b876293e9e83dec7cd809a jbd2: use GFP_NOFS for blkdev_issue_flush

Re: [RFC PATCH 0/4] Allow Link state changes for Hot-Plug

2013-11-21 Thread Bjorn Helgaas
I haven't had a chance yet, sorry. On Thu, Nov 21, 2013 at 6:16 AM, Rajat Jain wrote: > Hello Bjorn / Folks, > > Was wondering if you got a chance to look at this patchset? > > Thanks & Best Regards, > > Rajat Jain > > On Tue, Nov 19, 2013 at 2:39 PM, Rajat Jain wrote: >> >> Hello, >> >> This

[PATCH] intel_idle: shrink avn_cstates table and mark it with __initdata tag

2013-11-21 Thread Bartlomiej Zolnierkiewicz
This is a fixup for commit fab04b2 ("intel_idle: Support Intel Atom Processor C2000 Product Family") which didn't take into account changes done in commits eba682a ("intel_idle: shrink states tables") and 00f3e75 ("intel_idle: mark states tables with __initdata tag"). Cc: Len Brown

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

linux-kernel@vger.kernel.org

2013-11-21 Thread

  1   2   3   4   5   6   7   8   >