The third parameter(u64 start_tstamp) of timecounter_init() should
be the start time by ns, not a cycle counter.
Here just set it to zero.
Cc: Stephen Boyd
Signed-off-by: Xiubo Li
---
drivers/clocksource/arm_arch_timer.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
diff --git
>From 14485894add32aedacb3e486ebb2cc2b73861abf Mon Sep 17 00:00:00 2001
From: Fu zhonghui
Date: Wed, 11 Jun 2014 11:06:55 +0800
Subject: [PATCH] brcmfmac: prevent watchdog from interfering with scanning and
connecting
Watchdog in brcmfmac driver may make WiFi chip enter sleep mode
before
Hi George,
On 06/16/2014 02:41 PM, George Cherian wrote:
> On 6/16/2014 10:29 AM, Guenter Roeck wrote:
>> On 06/15/2014 07:42 PM, George Cherian wrote:
>>> This is the driver for the USB ID pin detection. This driver
>>> handles only the USB ID pin changes generated by cable
>>>
On 6/16/2014 10:29 AM, Guenter Roeck wrote:
On 06/15/2014 07:42 PM, George Cherian wrote:
This is the driver for the USB ID pin detection. This driver
handles only the USB ID pin changes generated by cable
insertion/removal.
Signed-off-by: George Cherian
Hi George,
Curious: Why can't you
PPC KVM's CMA area management requires arbitrary bitmap granularity,
since they want to reserve very large memory and manage this region
with bitmap that one bit for several pages to reduce management overheads.
So support arbitrary bitmap granularity for following generalization.
v3: use
We don't need explicit 'CMA:' prefix, since we already define prefix
'cma:' in pr_fmt. So remove it.
Acked-by: Michal Nazarewicz
Reviewed-by: Zhang Yanfei
Signed-off-by: Joonsoo Kim
diff --git a/mm/cma.c b/mm/cma.c
index 9961120..4b251b0 100644
--- a/mm/cma.c
+++ b/mm/cma.c
@@ -225,12 +225,12
Now, we have general CMA reserved area management framework,
so use it for future maintainabilty. There is no functional change.
v3: add zeroing to CMA region (Aneesh)
fix compile error (Aneesh)
move VM_BUG_ON() to kvm_alloc_hpt() in book3s_hv_builtin.c (Aneesh)
Acked-by: Michal
Conventionally, we put output param to the end of param list
and put the 'base' ahead of 'size', but cma_declare_contiguous()
doesn't look like that, so change it.
Additionally, move down cma_areas reference code to the position
where it is really needed.
v3: put 'base' ahead of 'size' (Minchan)
Currently, there are two users on CMA functionality, one is the DMA
subsystem and the other is the KVM on powerpc. They have their own code
to manage CMA reserved area even if they looks really similar.
>From my guess, it is caused by some needs on bitmap management. KVM side
wants to maintain
We should free memory for bitmap when we find zone mis-match,
otherwise this memory will leak.
Additionally, I copy code comment from PPC KVM's CMA code to inform
why we need to check zone mis-match.
* Note
Minchan suggested to add a tag for the stable, but, I don't do it,
because I found this
To prepare future generalization work on CMA area management code,
we need to separate core CMA management codes from DMA APIs.
We will extend these core functions to cover requirements of
PPC KVM's CMA area management functionality in following patches.
This separation helps us not to touch DMA
Currently, there are two users on CMA functionality, one is the DMA
subsystem and the other is the KVM on powerpc. They have their own code
to manage CMA reserved area even if they looks really similar.
>From my guess, it is caused by some needs on bitmap management. Kvm side
wants to maintain
PPC KVM's CMA area management needs alignment constraint on
CMA region. So support it to prepare generalization of CMA area
management functionality.
Additionally, add some comments which tell us why alignment
constraint is needed on CMA region.
v3: fix wrongly spelled word,
We can remove one call sites for clear_cma_bitmap() if we first
call it before checking error number.
Acked-by: Minchan Kim
Reviewed-by: Michal Nazarewicz
Reviewed-by: Zhang Yanfei
Reviewed-by: Aneesh Kumar K.V
Signed-off-by: Joonsoo Kim
diff --git a/mm/cma.c b/mm/cma.c
index
On Sat, Jun 14, 2014 at 02:23:59PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim writes:
>
> > Now, we have general CMA reserved area management framework,
> > so use it for future maintainabilty. There is no functional change.
> >
> > Acked-by: Michal Nazarewicz
> > Acked-by: Paolo Bonzini
> >
On Sat, Jun 14, 2014 at 12:55:39PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim writes:
>
> > Currently, there are two users on CMA functionality, one is the DMA
> > subsystem and the other is the kvm on powerpc. They have their own code
> > to manage CMA reserved area even if they looks really
On Sat, Jun 14, 2014 at 03:35:33PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim writes:
>
> > Now, we have general CMA reserved area management framework,
> > so use it for future maintainabilty. There is no functional change.
> >
> > Acked-by: Michal Nazarewicz
> > Acked-by: Paolo Bonzini
> >
On Sat, Jun 14, 2014 at 03:46:44PM +0530, Aneesh Kumar K.V wrote:
> Joonsoo Kim writes:
>
> > Currently, there are two users on CMA functionality, one is the DMA
> > subsystem and the other is the kvm on powerpc. They have their own code
> > to manage CMA reserved area even if they looks really
On Thu, Jun 12, 2014 at 02:37:43PM +0900, Minchan Kim wrote:
> On Thu, Jun 12, 2014 at 12:21:40PM +0900, Joonsoo Kim wrote:
> > To prepare future generalization work on cma area management code,
> > we need to separate core cma management codes from DMA APIs.
> > We will extend these core
On Thu, Jun 12, 2014 at 12:19:54PM +0200, Michal Nazarewicz wrote:
> On Thu, Jun 12 2014, Joonsoo Kim wrote:
> > ppc kvm's cma region management requires arbitrary bitmap granularity,
> > since they want to reserve very large memory and manage this region
> > with bitmap that one bit for several
On Thu, Jun 12, 2014 at 12:02:38PM +0200, Michal Nazarewicz wrote:
> On Thu, Jun 12 2014, Joonsoo Kim wrote:
> > ppc kvm's cma area management needs alignment constraint on
>
> I've noticed it earlier and cannot seem to get to terms with this. It
> should IMO be PPC, KVM and CMA since those are
On Thu, Jun 12, 2014 at 11:53:16AM +0200, Michal Nazarewicz wrote:
> On Thu, Jun 12 2014, Michal Nazarewicz wrote:
> > I used “function(arg1, arg2, …)” at the *beginning* of functions when
> > the arguments passed to the function were included in the message. In
> > all other cases I left it at
On Jun 16, 2014, at 12:28 AM, Anil Belur wrote:
> From: Anil Belur
>
> fixed: WARNING: line over 80 characters and indent after the conditional
> statement
>
> Signed-off-by: Anil Belur
> ---
> drivers/staging/lustre/lustre/lclient/lcommon_cl.c | 9 ++---
> 1 file changed, 6
On 06/13/2014 12:44 AM, Sören Brinkmann wrote:
> Hi Jongsung,
Hi Sören,
> Does this interrupt need to be enabled? There is nothing checking
> that bit and handling this IRQ in the handler, AFAICT. And you solve
> this by simply clearing the bit. So, I wonder whether not enabling this
> IRQ in
On 06/15/2014 07:42 PM, George Cherian wrote:
This is the driver for the USB ID pin detection. This driver
handles only the USB ID pin changes generated by cable
insertion/removal.
Signed-off-by: George Cherian
Hi George,
Curious: Why can't you use extcon-gpio ?
Also, I thought that Linux
Hello!
On Jun 16, 2014, at 12:28 AM, Anil Belur wrote:
> From: Anil Belur
>
> Fixed "ERROR: need consistent spacing around '+' (ctx:WxV)"
>
> Signed-off-by: Anil Belur
> ---
> drivers/staging/lustre/lustre/lclient/glimpse.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
This patch series adds the support for cc2520 radio and
provides device tree bindings for cc2520
Varka Bhadram (3):
ieee802154: cc2520: driver for TI cc2520 radio
ieee802154: cc2520: add driver to kernel build system
devicetree: add devicetree bindings for cc2520 driver
Signed-off-by: Varka Bhadram
---
.../devicetree/bindings/net/ieee802154/cc2520.txt | 26
1 file changed, 26 insertions(+)
create mode 100644 Documentation/devicetree/bindings/net/ieee802154/cc2520.txt
diff --git
Signed-off-by: Varka Bhadram
---
drivers/net/ieee802154/cc2520.c | 805 +++
include/linux/spi/cc2520.h | 176 +
2 files changed, 981 insertions(+)
create mode 100644 drivers/net/ieee802154/cc2520.c
create mode 100644
Signed-off-by: Varka Bhadram
---
drivers/net/ieee802154/Kconfig | 11 +++
drivers/net/ieee802154/Makefile |1 +
2 files changed, 12 insertions(+)
diff --git a/drivers/net/ieee802154/Kconfig b/drivers/net/ieee802154/Kconfig
index 3e89bea..680422f 100644
---
This patch add S2MPU02 regulator device to existing S2MPS11 device driver
because of little difference between S2MPS1x and S2MPU02. The S2MPU02
regulator device includes LDO[1-28] and BUCK[1-7].
Signed-off-by: Chanwoo Choi
[Add missing linear_min_sel of S2MPU02 LDO regulators by Jonghwa Lee]
Add support for Samsung S2MPU02 PMIC device to the MFD sec-core driver.
The S2MPU02 device includes PMIC/RTC/Clock devices.
Signed-off-by: Chanwoo Choi
Reviewed-by: Krzysztof Kozlowski
---
drivers/mfd/sec-core.c | 19 +
drivers/mfd/sec-irq.c| 88
This patch add documentation for S2MPU02 PMIC device. S2MPU02 has a little
difference from S2MPS11/S2MPS14 PMIC and has LDO[1-28]/Buck[1-7].
Signed-off-by: Chanwoo Choi
Reviewed-by: Krzysztof Kozlowski
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
Cc:
his patchset add Samsung S2MPU02 PMIC device driver in exiting S2MPS11 PMIC
driver because S2MPU02 has a little different between S2MPU02 and S2MPS1x.
The S2MPU02 PMIC has LDO[1-28] and BUCK[1-7] regulators.
Changes from v4:
- This patchset is rebased on 'Linux 3.16-rc1'.
Changes from v3:
- Fix
Daniel,
On Sun, Jun 15, 2014 at 2:18 PM, Daniel Lezcano
wrote:
> On 06/04/2014 07:30 PM, Doug Anderson wrote:
>>
>> In (93bfb76 clocksource: exynos_mct: register sched_clock callback) we
>> supported using the MCT as a scheduler clock. We properly marked
>> exynos4_read_sched_clock() as
On 06/13/2014 06:20 PM, John Stultz wrote:
> On Fri, Jun 13, 2014 at 7:20 AM, Michael Kerrisk (man-pages)
> wrote:
>>
>> The general notion these days is that a (comprehensive) manual page
>> _should_ come *with* the system call, rather than after the fact. And
>> there's a lot of value in that.
From: Anil Belur
fixed: ERROR: inline keyword should sit between storage class and type
Signed-off-by: Anil Belur
---
drivers/staging/lustre/lustre/lclient/lcommon_cl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
From: Anil Belur
fixed: WARNING: line over 80 characters and indent after the conditional
statement
Signed-off-by: Anil Belur
---
drivers/staging/lustre/lustre/lclient/lcommon_cl.c | 9 ++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git
From: Anil Belur
fixed: WARNING: Missing a blank line after declarations
Signed-off-by: Anil Belur
---
drivers/staging/lustre/lustre/lclient/lcommon_cl.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
From: Anil Belur
fixed warning:
* WARNING: min() should probably be min_t(__u32, desc.ld_tgt_count,
LOV_MAX_STRIPE_COUNT)
Signed-off-by: Anil Belur
---
drivers/staging/lustre/lustre/lclient/lcommon_misc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
From: Anil Belur
fixed: ERROR: do not initialise statics to 0 or NULL
Signed-off-by: Anil Belur
---
drivers/staging/lustre/lustre/lclient/lcommon_cl.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/lclient/lcommon_cl.c
From: Anil Belur
fixed "WARNING: labels should not be indented"
Signed-off-by: Anil Belur
---
drivers/staging/lustre/lustre/lclient/glimpse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/lclient/glimpse.c
From: Anil Belur
Fixed "ERROR: need consistent spacing around '+' (ctx:WxV)"
Signed-off-by: Anil Belur
---
drivers/staging/lustre/lustre/lclient/glimpse.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/lustre/lustre/lclient/glimpse.c
On 2014/6/11 20:12, Jan Kara wrote:
> Hello,
>
> On Wed 11-06-14 16:19:12, Weng Meiling wrote:
>> We run vdbench test in our suse system with kernel 3.4, the vdbench test
>> is about different block size seq and rand read/write. Before the vdbench
> Hum, this looks like some relatively old
So it's been two weeks since the merge window opened, and rc1 is out
there and thus the merge window is closed.
It may have been a slightly unusual two week merge window, in that
it's only one week since the release of 3.15 and the first week
overlapped with the last -rc for that previous
Gidday,
The Linux man-pages maintainer proudly announces his 150th release
as project maintainer:
man-pages-3.69 - man pages for Linux
Tarball download:
http://www.kernel.org/doc/man-pages/download.html
Git repository:
https://git.kernel.org/cgit/docs/man-pages/man-pages.git/
Online
On Mon, Jun 16, 2014 at 04:36:04AM +0200, Andi Kleen wrote:
>
> At least versioning is always useful to have, just to have
> another tool for compatibility if changes are needed.
I disagree. Just like syscalls, vdso functions with new APIs/ABIs
should have new names. For example if a version of
On 06/15/14 06:06, Roman Pen wrote:
> The thing is that built-in modules are being inited before
> rootfs mount. Some of the modules can request firmware loading
> using async 'request_firmware_nowait' call just while inition,
> so we can catch this kind of race: rootfs does not exist yet,
> but
separate the mrf24j40 hardware initialisation from probe()
and adds the sanity checkings.
These checkings are required if somebody hasn't a right spi configuration
the probe function should fail. So we have to return from there.
Signed-off-by: Varka Bhadram
---
Seems the bug is fixed , don't worry about resent patch.
Thanks Nick
On Sun, Jun 15, 2014 at 11:21 PM, Nick Krause wrote:
> New Patch Just Fixed Typo for my email client.
> Signed-off-by: Nick
> ---
> drivers/clk/sunxi/clk-sunxi.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git
The filter() function is currently called by xlate() while it transfers
imx_dma_data as a local variable to the filter() but releases the data
right after returning a DMA channel pointer, which results chan->private
pointing an invalid memory space.
So this patch just stores the imx_dma_data into
Fair enjoy I was wondering if it fails I can run a goto statement and
then free the memory for the tx as needed.
Cheers Nick
P.S. That was really stupid I didn't think that through at all :)
On Sun, Jun 15, 2014 at 10:26 PM, David Miller wrote:
> From: Nick Krause
> Date: Sun, 15 Jun 2014
Shared Peripheral ASRC, running on SPBA, needs to use shp sciprts for
DMA transfer. So this patch just adds a new DMATYPE for it.
Signed-off-by: Nicolin Chen
---
Documentation/devicetree/bindings/dma/fsl-imx-sdma.txt | 1 +
drivers/dma/imx-sdma.c | 5 +
On Sat, Jun 14, 2014 at 11:44:04AM +0200, Richard Weinberger wrote:
> Hi!
>
> Am 03.06.2014 07:30, schrieb Real Name:
> > From: Honggang Li
> >
> > The patch based on linux-next-2014-06-02.
> >
> > The old init_maps function does two things:
> > 1) allocates and initializes one struct page
New Patch Just Fixed Typo for my email client.
Signed-off-by: Nick
---
drivers/clk/sunxi/clk-sunxi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/sunxi/clk-sunxi.
c b/drivers/clk/sunxi/clk-sunxi.c
index 4264834..6f4fc51 100644
--- a/drivers/clk/sunxi/clk-sunxi.c
+++
On Fri, Jun 13, 2014 at 10:19:36AM -0400, Alan Stern wrote:
> On Fri, 13 Jun 2014, Peter Chen wrote:
>
> > OK, we can keep our g_xxx gadget driver just support the basic feature. But
> > the bug that causes gadget driver load fail due to udc is probed deferral
> > should
> > be fixed, do you
On Sat, 14 Jun 2014, Alan Stern wrote:
> > dev->power.is_suspended is set after core suspends device during system
> suspend.
> > This flag mostly means device is not operational (all I/O been
> > quiesced, no more data read or write acceptible, etc.), hence it's
> > dangerous to access hardware
On Fri, 6 Jun 2014, Sasha Levin wrote:
> On 06/06/2014 02:49 PM, Kirill A. Shutemov wrote:
> > On Fri, Jun 06, 2014 at 11:26:14AM -0700, Linus Torvalds wrote:
> >> > On Fri, Jun 6, 2014 at 10:43 AM, Dave Jones wrote:
> >>> > >
> >>> > > RIP: 0010:[] []
> >>> > > copy_page_rep+0x5/0x10
> >> >
>
This bug based on the comments around it seems to need to closes
due to it being a code rework and not a bug. The If for the bug on
the Bugzilla is 72851 as stated in the bug log is that it's a code
rework idea and not a bug.
Cheers Nick
--
To unsubscribe from this list: send the line "unsubscribe
Hi all,
The powerpc allyesconfig is again broken more than usual.
Changes since 20140613:
Undropped trees: akpm-current, akpm
The imx-mxs tree gained a conflict against the arm-soc tree.
I added a provided patch to the akpm-current tree to fix its build
problems.
Non-merge commits (relative
Hey Netdev Team,
This bug seems, fixed https://bugzilla.kernel.org/show_bug.cgi?id=44611.
I seem to believe this bug is fixed after I checked the related file.
if (skb) { seems to fix the not checked for NULL in the related function.
I would close this bug unless there are other issues with
This is the driver for the USB ID pin detection. This driver
handles only the USB ID pin changes generated by cable
insertion/removal.
Signed-off-by: George Cherian
---
.../devicetree/bindings/extcon/extcon-dra7xx.txt | 15 ++
drivers/extcon/Kconfig | 5 +
On 2014年06月16日 10:35, Zheng, Lv wrote:
> Hi,
>
>> From: linux-acpi-ow...@vger.kernel.org
>> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Lan Tianyu
>> Sent: Monday, June 16, 2014 10:12 AM
>> To: David Rientjes
>> Cc: r...@rjwysocki.net; l...@kernel.org; nas...@ya.ru;
>>
On Fri, 2014-06-13 at 14:26 +0400, Denis Kirjanov wrote:
> On 6/13/14, Catalin Marinas wrote:
> > On Fri, Jun 13, 2014 at 08:12:08AM +0100, Denis Kirjanov wrote:
> >> On 6/12/14, Catalin Marinas wrote:
> >> > On Thu, Jun 12, 2014 at 01:00:57PM +0100, Denis Kirjanov wrote:
> >> >> On 6/12/14,
At least versioning is always useful to have, just to have
another tool for compatibility if changes are needed.
Not sure about weak, but it can't hurt. It seems to be standard practice
in glibc.
I haven't looked into this in detail, but my initial assumption would
be that it wouldn't be
Hi,
> From: linux-acpi-ow...@vger.kernel.org
> [mailto:linux-acpi-ow...@vger.kernel.org] On Behalf Of Lan Tianyu
> Sent: Monday, June 16, 2014 10:12 AM
> To: David Rientjes
> Cc: r...@rjwysocki.net; l...@kernel.org; nas...@ya.ru;
> linux-a...@vger.kernel.org; linux-kernel@vger.kernel.org
>
1) Fix checksumming regressions, from Tom Herbert.
2) Undo unintentional permissions changes for SCTP rto_alpha and
rto_beta sysfs knobs, from Denial Borkmann.
3) VXLAN, like other IP tunnels, should advertize it's encapsulation
size using dev->needed_headroom instead of
On Thu, 12 Jun 2014, Sasha Levin wrote:
> On 02/09/2014 08:41 PM, Sasha Levin wrote:
> > On 02/08/2014 10:25 PM, Hugh Dickins wrote:
> >> Would trinity be likely to have a thread or process repeatedly faulting
> >> in pages from the hole while it is being punched?
> >
> > I can see how trinity
This patch fixes memory by checking in function,
*get_skuff if it is be passing a Null skb
struct.
Cheers Nick
Signed-off-by: Nick
---
drivers/infiniband/hw/cxgb4/cm.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/infiniband/hw/cxgb4/cm.c
From: Nick Krause
Date: Sun, 15 Jun 2014 16:27:23 -0400
> From 62b0d77a1430f74b7f5c008c5e8bec11604b33b0 Mon Sep 17 00:00:00 2001
> From: Nick
> Date: Sun, 15 Jun 2014 16:16:14 -0400
> Subject: [PATCHv2] Fixes return logic of function of
> pch_gbe_alloc_tx_buffers()
> Here is the fixed patch
Use schedule_work() to avoid potentially taking the spinlock in
interrupt context.
Commit cc9fa74e2a ("slip/slcan: added locking in wakeup function") added
necessary locking to the wakeup function and 367525c8c2/ddcde142be ("can:
slcan: Fix spinlock variant") converted it to spin_lock_bh()
The commit "slip: Fix deadlock in write_wakeup" fixes a deadlock caused
by a change made in both slcan and slip. This is a direct port of that
fix.
Signed-off-by: Tyler Hall
Cc: Oliver Hartkopp
Cc: Andre Naujoks
Cc: David S. Miller
Cc: linux-kernel@vger.kernel.org
---
drivers/net/can/slcan.c
This driver a general version for tps611xx backlgiht chips of TI.
It supports tps61158, tps61161, tps61163 and tps61165 backlight driver
based on EasyScale protocol.
Daniel Jeong (2):
backlight: add new tps611xx backlight driver
backlight: add new tps611xx backlight device tree support
This commit is about tps611xx device tree documentation.
Signed-off-by: Daniel Jeong
---
.../video/backlight/tps611xx-backlight.txt | 16
1 file changed, 16 insertions(+)
create mode 100644
Documentation/devicetree/bindings/video/backlight/tps611xx-backlight.txt
This driver a general version for tps611xx backlgiht chips of TI.
It supports tps61158, tps61161, tps61163 and tps61165 backlight driver
based on EasyScale protocol.
Signed-off-by: Daniel Jeong
---
drivers/video/backlight/Kconfig |7 +
drivers/video/backlight/Makefile |
On 2014年06月14日 05:46, David Rientjes wrote:
> On Fri, 13 Jun 2014, Lan Tianyu wrote:
>
>> How about this?
>>
>> - result = acpi_battery_update(battery, false);
>> - if (result)
>> +
>> + /*
>> +* Some machines'(E,G Lenovo Z480) ECs are not stable
>> +* during
Signed-off-by: Axel Lin
---
drivers/regulator/max8952.c | 34 ++
1 file changed, 10 insertions(+), 24 deletions(-)
diff --git a/drivers/regulator/max8952.c b/drivers/regulator/max8952.c
index c2792f0..f7f9efc 100644
--- a/drivers/regulator/max8952.c
+++
Hi Naoya,
On Fri, 13 Jun 2014 11:12:06 -0400 Naoya Horiguchi
wrote:
>
> On Fri, Jun 13, 2014 at 03:05:50PM +1000, Stephen Rothwell wrote:
> >
> > After merging the akpm-current tree, today's linux-next build (powerpc
> > ppc64_defconfig)
> > failed like this:
> >
> > fs/proc/task_mmu.c: In
Hi Andrew,
After merging the akpm-current tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
In file included from arch/powerpc/include/asm/mmu-hash64.h:23:0,
from arch/powerpc/include/asm/mmu.h:197,
from
Hi all,
After merging the tip tree, today's linux-next build (x86_64
allmodconfig) produced this warning:
In file included from arch/x86/crypto/camellia_aesni_avx_glue.c:23:0:
arch/x86/include/asm/xsave.h:73:12: warning: 'xsave_state_booting' defined but
not used [-Wunused-function]
static int
Commit 0fb7a01af5b0 "random: simplify accounting code", introduced in
v3.15, has a very nasty accounting problem when the entropy pool has
has fewer bytes of entropy than the number of requested reserved
bytes. In that case, "have_bytes - reserved" goes negative, and since
size_t is unsigned, the
On Sun, Jun 15, 2014 at 03:12:54PM +0800, Jet Chen wrote:
> Hi Greg,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 0fb7a01af5b0cbe5bf365891fc4d186f2caa23f7
> Author: Greg
Signed-off-by: Axel Lin
---
drivers/regulator/twl-regulator.c | 13 +
1 file changed, 1 insertion(+), 12 deletions(-)
diff --git a/drivers/regulator/twl-regulator.c
b/drivers/regulator/twl-regulator.c
index fed28ab..0b4f866 100644
--- a/drivers/regulator/twl-regulator.c
+++
I was well aware of FALLOC_FL_ZERO_RANGE and FALLOC_FL_COLLAPSE_RANGE
support being added to fallocate(); but didn't realize until now that
I had been too stupid to future-proof shmem_fallocate() against new
additions. -EOPNOTSUPP instead of going on to ordinary fallocation.
Signed-off-by: Hugh
Hi, Peter
Ping...
thanks,
Lai
On 06/10/2014 09:21 AM, Lai Jiangshan wrote:
> On 06/09/2014 10:01 PM, Jason J. Herne wrote:
>> On 06/05/2014 06:54 AM, Lai Jiangshan wrote:
>>>
>>>
>>> Subject: [PATCH] sched: migrate the waking tasks
>>>
>>> Current code skips to migrate the waking
On Fri, Jun 13, 2014 at 07:00:17PM +0200, Daniel Kiper wrote:
> Use early_mem*() instead of early_io*() because all mapped EFI regions
> are true RAM not I/O regions. Additionally, I/O family calls do not work
> correctly under Xen in our case. AIUI, early_io*() maps/unmaps real machine
>
On Sunday, June 15, 2014 9:11 AM, Martin Kepplinger wrote:
>
> Fix a sparse warning: ttm_bo_reserve()'s last argument is a
> pointer to a struct, so use NULL as nullpointer.
>
> Signed-off-by: Martin Kepplinger
Reviewed-by: Jingoo Han
Best regards,
Jingoo Han
> ---
> this applies to
On Sun, Jun 15, 2014 at 10:05:47AM -0700, H. Peter Anvin wrote:
> On 06/15/2014 07:35 AM, Rich Felker wrote:
> >
> > Arguably, it was a mistake for the kernel to expose a virtual ELF to
> > begin with, and it should just have exposed a "lookup function by
> > name" operation to begin with. Yes
On Sun, Jun 15, 2014 at 12:14:04PM -0700, H. Peter Anvin wrote:
> If it doesn't, then you incur an additional indirection penalty. The
> strong __vdso symbol allows the libc wrapper to fall back to the
> vdso implementation, the weak symbol allows three to be no wrapper
> at all. This is good.
No
On Wed, 11 Jun 2014, Chen Yucong wrote:
> On Tue, 2014-06-10 at 16:33 -0700, Andrew Morton wrote:
> > > break;
> > >
> > > if (nr_file > nr_anon) {
> > > - unsigned long scan_target =
> > targets[LRU_INACTIVE_ANON] +
> > >
> > -
Linux doesn't have an ability to free pages lazy while other OS
already have been supported that named by madvise(MADV_FREE).
The gain is clear that kernel can discard freed pages rather than
swapping out or OOM if memory pressure happens.
Without memory pressure, freed pages would be reused by
On Sat, 14 Jun 2014, Fabian Frederick wrote:
> Use GFP_NOFS instead of its definition.
>
> Cc: Jens Axboe
> Signed-off-by: Fabian Frederick
> ---
> block/bio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/block/bio.c b/block/bio.c
> index 8c2e55e..ec5d172 100644
>
On Fri, 6 Jun 2014, Naoya Horiguchi wrote:
> There's a race between fork() and hugepage migration, as a result we try to
> "dereference" a swap entry as a normal pte, causing kernel panic.
> The cause of the problem is that copy_hugetlb_page_range() can't handle "swap
> entry" family (migration
Hi Shawn,
Today's linux-next merge of the imx-mxs tree got a conflict in
arch/arm/mach-imx/Kconfig between commit e49d9b375628 ("ARM: Remove
ARCH_HAS_CPUFREQ config option") from the arm-soc tree and commit
7de46855b1e7 ("ARM: imx5: move SOC_IMX5 and SOC_IMX51 into 'Device tree
only'") from the
On Sun, 2014-06-15 at 18:02 -0400, Alan Stern wrote:
> On Sun, 15 Jun 2014, Joe Perches wrote:
>
> > Use the zeroing function instead of dma_alloc_coherent & memset(,0,)
> >
> > Signed-off-by: Joe Perches
>
> ...
>
> > diff --git a/drivers/usb/host/uhci-hcd.c b/drivers/usb/host/uhci-hcd.c
> >
On Mon, 2014-06-16 at 00:16 +0200, Geert Uytterhoeven wrote:
> On Sun, Jun 15, 2014 at 10:37 PM, Joe Perches wrote:
> > diff --git a/drivers/video/fbdev/da8xx-fb.c b/drivers/video/fbdev/da8xx-fb.c
[]
> > @@ -1447,18 +1447,15 @@ static int fb_probe(struct platform_device *device)
> >
Hi Dmitry,
On Sun, 15 Jun 2014 13:31:24 +0400 Dmitry Eremin-Solenikov
wrote:
>
> On Sun, Jun 15, 2014 at 5:20 AM, Stephen Rothwell
> wrote:
> >
> > OK, the master branch of that tree is in linux-next as the "battery"
> > tree. My contact for that tree is Anton Vorontsov (cc'd) and its
> >
On Fri, Jun 13, 2014 at 7:58 PM, Thomas Glanzmann wrote:
> Hello Ben,
> commit
Hey Thomas,
Are you able to double-check that bisect? I'm not at all sure how
that particular commit could trigger the issue you're seeing. Some of
the others, certainly. It might be worth trying a couple of times
On Saturday, June 14, 2014 12:37:49 AM Kees Cook wrote:
> On Fri, Jun 13, 2014 at 5:39 PM, Rafael J. Wysocki wrote:
> > On Friday, June 13, 2014 05:08:21 PM Kees Cook wrote:
> >> On Fri, Jun 13, 2014 at 5:14 PM, Rafael J. Wysocki
> >> wrote:
> >> > On Friday, June 13, 2014 03:59:57 PM Kees Cook
On Saturday, June 14, 2014 09:41:19 AM H. Peter Anvin wrote:
> On 06/13/2014 05:39 PM, Rafael J. Wysocki wrote:
> >
> > -#define RESTORE_MAGIC 0x0123456789ABCDEFUL
> > +#define RESTORE_MAGIC 0x0123456789ABCDF0UL
> >
>
>
>
> Please don't pick numbers like this for magic numbers...
1 - 100 of 530 matches
Mail list logo
