Please take a look.
thanks,
julia
On Wed, 25 Mar 2015, kbuild test robot wrote:
TO: Peter Chen peter.c...@freescale.com
CC: Greg Kroah-Hartman gre...@linuxfoundation.org
CC: linux-...@vger.kernel.org
CC: linux-kernel@vger.kernel.org
drivers/usb/chipidea/usbmisc_imx.c:277:5-8: Unneeded
This patch series contains two patches to address iProc PCIe Kconfig related
issues. The first patch adds more protection to PCIE_IPROC so it cannot be
accidentally enabled for non-ARM based platforms. The second patch changes the
config name of the iProc PCIe platform driver from PCIE_IPROC_PLTFM
Change the config name of the iProc PCIe platform bus driver from
PCIE_IPROC_PLTFM to PCIE_IPROC_PLATFORM
Signed-off-by: Ray Jui r...@broadcom.com
---
drivers/pci/host/Kconfig |2 +-
drivers/pci/host/Makefile |2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Change the config name of the iProc PCIe platform bus driver from
PCIE_IPROC_PLTFM to PCIE_IPROC_PLATFORM. Also change the driver name
from pcie-iproc-pltfm.c to pcie-iproc-platform.c to match the config
name
Signed-off-by: Ray Jui r...@broadcom.com
---
drivers/pci/host/Kconfig
This patch series contains two patches to address iProc PCIe Kconfig related
issues. The first patch adds more protection to PCIE_IPROC so it cannot be
accidentally enabled for non-ARM based platforms. The second patch changes the
config name of the iProc PCIe platform driver from PCIE_IPROC_PLTFM
Make PCIE_IPROC depending on both OF and ARM and default to be disabled,
so it cannot be accidentally enabled by other platforms
PCIE_IPROC is meant to be enabled by a front-end bus driver. Curenntly
it's enabled by PCIE_IPROC_PLTFM driver
Signed-off-by: Ray Jui r...@broadcom.com
---
On Tue, Mar 24, 2015 at 10:30:19PM +, Srinivas Kandagatla wrote:
This patch adds just consumers part of the framework just to enable easy
review.
Up until now, EEPROM drivers were stored in drivers/misc, where they all had
to
duplicate pretty much the same code to register a sysfs
Before commit 593669c2ac0f (x86/PCI/ACPI: Use common ACPI resource
interfaces to simplify implementation), arch/x86/pci/acpi.c applies
following rules when parsing ACPI resources for PCI host bridge:
1) Ignore IO port resources defined by acpi_resource_io and
acpi_resource_fixed_io, which
On Sun, Feb 22, 2015 at 12:45:43AM +0900, Namjae Jeon wrote:
From: Namjae Jeon namjae.j...@samsung.com
FALLOC_FL_INSERT_RANGE command is the opposite command of
FALLOC_FL_COLLAPSE_RANGE that is needed for advertisers or someone who want to
add some data in the middle of file.
Setting oom_killer_disabled to false is atomic, there is no need for
further synchronization with ongoing allocations trying to OOM-kill.
Signed-off-by: Johannes Weiner han...@cmpxchg.org
---
mm/oom_kill.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/mm/oom_kill.c b/mm/oom_kill.c
index
Hi Thierry,
After merging the drm-panel tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:
drivers/video/fbdev/Kconfig:5:error: recursive dependency detected!
drivers/video/fbdev/Kconfig:5: symbol FB is selected by DRM_KMS_FB_HELPER
drivers/gpu/drm/Kconfig:34:
-out/zsmalloc-do-not-remap-dst-page-while-prepare-next-src-page.patch
Heesub Shin has reported that this patch causes BUG_ON on ARM
(with CONFIG_DEBUG_HIGHMEM enabled). Could you please revert
it in linux-next 20150325?
Done.
--
Cheers,
Stephen Rothwells
On Wed, Mar 25, 2015 at 12:23:19PM +0530, rtat...@codeaurora.org wrote:
From: Rupesh Tatiya rtat...@codeaurora.org
USB 2.01+ full-speed devices can have extended descriptor as well
and can support LPM.
Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
We can't take patches with this in
On 03/24/2015 07:51 PM, Lorenzo Pieralisi wrote:
On Tue, Mar 24, 2015 at 09:54:02AM +, Daniel Lezcano wrote:
Add kernel-doc format documentation in the code.
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
---
[ ... ]
+ * Returns:
+ * 0 on success,
+ * -ENODEV if it fails to
On Wed, Mar 25, 2015 at 7:00 AM, Andrew Morton
a...@linux-foundation.org wrote:
On Thu, 19 Mar 2015 23:04:39 +0900 Roman Pen r.peni...@gmail.com wrote:
If suitable block can't be found, new block is allocated and put into a head
of a free list, so on next iteration this new block will be found
In the squashfs_symlink_readpage(), the return value should be -EIO
instead of 0 when the code fails in obtaining the information about
the symlink metadata.
Signed-off-by: Sanidhya Kashyap sanidhya.gat...@gmail.com
---
fs/squashfs/symlink.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Hi everybody,
in the recent past we've had several reports and discussions on how to
deal with allocations hanging in the allocator upon OOM.
The idea of this series is mainly to make the mechanism of detecting
OOM situations reliable enough that we can be confident about failing
allocations,
exit_oom_victim() already knows that TIF_MEMDIE is set, and nobody
else can clear it concurrently. Use clear_thread_flag() directly.
Signed-off-by: Johannes Weiner han...@cmpxchg.org
---
mm/oom_kill.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/mm/oom_kill.c
Rename unmark_oom_victim() to exit_oom_victim(). Marking and
unmarking are related in functionality, but the interface is not
symmetrical at all: one is an internal OOM killer function used during
the killing, the other is for an OOM victim to signal its own death on
exit later on. This has
The zonelist locking and the oom_sem are two overlapping locks that
are used to serialize global OOM killing against different things.
The historical zonelist locking serializes OOM kills from allocations
with overlapping zonelists against each other to prevent killing more
tasks than necessary
On Wed, Mar 25, 2015 at 07:23:52AM +0100, Julia Lawall wrote:
Please take a look.
It is strange why I did not receive it.
The patch is ok.
Signed-off-by: Peter Chen peter.c...@freescale.com
thanks,
julia
On Wed, 25 Mar 2015, kbuild test robot wrote:
TO: Peter Chen
Around Tue 24 Mar 2015 18:31:22 +0300 or thereabout, Andrey Ryabinin wrote:
Almost all arches define ELF_ET_DYN_BASE as 2/3 of TASK_SIZE.
Though it seems that some architectures do this in a wrong way.
The problem is that 2*TASK_SIZE may overflow 32-bits so
the real ELF_ET_DYN_BASE becomes
I apologize for bringing this to the list, but after several hours of
google, testing, and so forth I'm coming up blank. I've been unable
to reproduce this state in targeted tests, however the application
itself does it on a semi-regular basis.
I currently have an application with the following
On Fri, 20 Mar 2015 08:32:12 -0500
, Rob Herring robherri...@gmail.com
wrote:
On Fri, Mar 20, 2015 at 7:25 AM, Grant Likely grant.lik...@linaro.org wrote:
On Fri, 23 Jan 2015 17:10:04 +0100
, Geert Uytterhoeven geert+rene...@glider.be
wrote:
Currently OF_DYNAMIC and OF_OVERLAY are not
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
3.19-stable review patch. If anyone has any objections, please let me know.
--
From: RafaÅ MiÅecki zaj...@gmail.com
commit 0ff66cffde47de51c155ebdd2356403276c04cc4 upstream.
It was incorrectly detected as 2 GHz
On 25.03.2015 01:44, David Sterba wrote:
On Tue, Mar 24, 2015 at 12:27:25PM +0100, Krzysztof Kolasa wrote:
lz4: fix system halted at boot kernel x86_64 compressed lz4
Decompression process ends with an error when loading kernel:
Decoding failed
-- System halted
Serious regression detected
On Wed, Mar 25, 2015 at 2:01 AM, Christoph Hellwig h...@lst.de wrote:
On Tue, Mar 24, 2015 at 06:53:07PM +0800, Ming Lei wrote:
If you have better one, please just ignore this patchset.
Here is a straight forward port of my old one. It's got light testing but
still could use a better
GFP_NOFS allocations are not allowed to invoke the OOM killer since
their reclaim abilities are severely diminished. However, without the
OOM killer available there is no hope of progress once the reclaimable
pages have been exhausted.
Don't risk hanging these allocations. Leave it to the
When both page reclaim and the OOM killer fail to free memory, there
are no more options for the allocator to make progress on its own.
Don't risk hanging these allocations. Leave it to the allocation site
to implement the fallback policy for failing allocations.
Signed-off-by: Johannes Weiner
There is not much point in rushing back to the freelists and burning
CPU cycles in direct reclaim when somebody else is in the process of
OOM killing, or right after issuing a kill ourselves, because it could
take some time for the OOM victim to release memory.
This is a very cold error path, so
__GFP_NOFAIL allocations can deadlock the OOM killer when they're
holding locks that the OOM victim might need to exit. When that
happens the allocation may never complete, which has disastrous
effects on things like in-flight filesystem transactions.
When the system is OOM, allow __GFP_NOFAIL
The should_alloc_retry() function was meant to encapsulate retry
conditions of the allocator slowpath, but there are still checks
remaining in the main function, and much of how the retrying is
performed also depends on the OOM killer progress. The physical
separation of those conditions make the
The OOM killer connects random tasks in the system with unknown
dependencies between them, and the OOM victim might well get blocked
behind the task that is trying to allocate. That means that while
allocations can issue OOM kills to improve the low memory situation,
which generally frees more
It turns out that the mechanism to wait for exiting OOM victims is
less generic than it looks: it won't issue wakeups unless the OOM
killer is disabled.
The reason this check was added was the thought that, since only the
OOM disabling code would wait on this queue, wakeup operations could
be
On 24 March 2015 at 18:58, Lorenzo Pieralisi lorenzo.pieral...@arm.com wrote:
If acpi=force is passed on the command line, it forces ACPI to be
the only available boot method, hence it must be left enabled even
if the initialization and sanity checks on ACPI tables fails.
This patch refactors
Disabling the OOM killer needs to exclude allocators from entering,
not existing victims from exiting.
Right now the only waiter is suspend code, which achieves quiescence
by disabling the OOM killer. But later on we want to add waits that
hold the lock instead to stop new victims from showing
Hi Rob,
On 15-03-22 06:20 PM, Rob Herring wrote:
On 03/20/2015 08:06 PM, Scott Branden wrote:
This patchset attempts to standardize the naming of dt-bindings
documents based on the Broadcom vendor prefix of brcm.
Although there are no guidelines currently present for how to name
the
Make PCIE_IPROC depending on both OF and ARM and default to be disabled,
so it cannot be accidentally enabled by other platforms
PCIE_IPROC is meant to be enabled by a front-end bus driver. Curenntly
it's enabled by PCIE_IPROC_PLTFM driver
Signed-off-by: Ray Jui r...@broadcom.com
---
From: Rupesh Tatiya rtat...@codeaurora.org
USB 2.01+ full-speed devices can have extended descriptor as well
and can support LPM.
Change-Id: Ic055d51c02651810d3eb7141bab20a090fe8453b
Signed-off-by: Rupesh Tatiya rtat...@codeaurora.org
---
drivers/usb/core/hub.c | 2 +-
1 file changed, 1
On Tue, Mar 24, 2015 at 10:30:30PM +, Srinivas Kandagatla wrote:
This patch adds bindings for simple eeprom framework which allows eeprom
consumers to talk to eeprom providers to get access to eeprom cell data.
Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com
[Maxime Ripard:
On Tue, Mar 24, 2015 at 7:22 AM, James Hogan james.ho...@imgtec.com wrote:
Hi Andrew,
On 04/03/15 23:59, Andrew Bresticker wrote:
If a machine-specific hook is not implemented for restart, poweroff,
or halt, fall back to halting secondary CPUs, disabling interrupts,
and spinning. In the
On 03/24/2015 11:24 PM, Nicholas Krause wrote:
Fixes memory leaks in the function,sa11xx_drv_pcmcia_probe for
when either clk_get returns a error value or when we cannot allocate
memory with the pointer sinfo to memory required for this function
to continue and return successfully. Further
Hi Bjorn,
On 3/24/2015 5:28 PM, Bjorn Helgaas wrote:
On Tue, Mar 24, 2015 at 12:33 AM, Ray Jui r...@broadcom.com wrote:
Make PCIE_IPROC depending on both OF and ARM and default to be disabled,
so it cannot be accidentally enabled by other platforms
PCIE_IPROC is meant to be enabled by a
On Thu, 19 Mar 2015 19:39:27 +
, Will Deacon will.dea...@arm.com
wrote:
On Thu, Mar 19, 2015 at 10:17:27AM +, Lorenzo Pieralisi wrote:
On Thu, Mar 19, 2015 at 04:09:33AM +, Hanjun Guo wrote:
On 2015/3/19 3:05, Will Deacon wrote:
On Wed, Mar 11, 2015 at 12:39:26PM +,
Hi all,
Changes since 20150324:
The vfs tree still had its build failure for which I applied a patch.
The net-next tree gained a conflict against the net tree.
I reverted a commit from the akpm-current tree by request.
Non-merge commits (relative to Linus' tree): 6285
5820 files changed,
On 2015/3/25 7:58, Daniel Axtens wrote:
On Tue, 2015-03-24 at 11:34 +0800, Yijing Wang wrote:
Now we could use pci_scan_host_bridge() to scan
pci buses, provide powerpc specific pci_host_bridge_ops.
Signed-off-by: Yijing Wang wangyij...@huawei.com
CC: Benjamin Herrenschmidt
From: kongxinwei kong.kongxin...@hisilicon.com
This adds documentation of device tree bindings for the
thermal sensor controller of hi6220 SoC.
Signed-off-by: Leo Yan leo@linaro.org
Signed-off-by: kongxinwei kong.kongxin...@hisilicon.com
---
.../bindings/thermal/hisilicon-thermal.txt
From: kongxinwei kong.kongxin...@hisilicon.com
This patch adds the support for hisilicon thermal sensor, within
hisilicon SoC. there will register sensors for thermal framework
and use device tree to bind cooling device.
Signed-off-by: Leo Yan leo@linaro.org
Signed-off-by: kongxinwei
From: kongxinwei kong.kongxin...@hisilicon.com
Thank you all for giving this RFC patches stages some comments. Here is v1
patches and address all the issues raised as part of RFC review.
The Linaro connect introduce 96boards series in Hong Kong,The HiKey board
is the first board to be certified
Hi,
Can you please pull from the following URL?
git://git.chelsio.net/pub/git/linux-firmware.git for-upstream
The following changes since commit f404336ba808cbd57547196e13367079a23b822c:
brcm: upgrade firmware for BCM4354 SDIO device (2015-03-20 09:33:43 -0400)
are available in the git
On Tue, Mar 24, 2015 at 05:50:49PM -0700, Jim Kukunas wrote:
XIP isn't a general feature that distros are going to be enabling. It's
designed for a very specific usage where people are building very custom
kernels.
So something very very special which is not going to be enabled on
distros...
On Mon, Mar 23, 2015 at 09:41:20PM -0400, Dave Jones wrote:
On Mon, Mar 23, 2015 at 11:33:42AM -0400, Josh Boyer wrote:
I have a machine that no longer boots in a headless manner with -rc5.
It's an Celeron based NUC device. I blacklisted the i915 driver and
it boots fine, then I ran
* carlossilveir...@gmail.com carlossilveir...@gmail.com wrote:
From: Carlos Roberto Silveira Junior carlossilveir...@gmail.com
---
kernel/sched/fair.c | 9 -
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index
The of_xlate callback should return ERR_PTR on error.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/phy/phy-spear1340-miphy.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/phy/phy-spear1340-miphy.c
b/drivers/phy/phy-spear1340-miphy.c
index
Hi Rafael,
this PR request has the following content:
- Removed the duplicate header inclusion (Daniel Lezcano).
- Unified the generic cpuidle ARM driver with ARM64. Each platform can
now define their 'enable-method' in the DT thus allowing to split the
low level PM code from the generic
ARM32 and ARM64 have the same DT definitions and the same approaches.
The generic ARM cpuidle driver can be put in common for those two
architectures.
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
Acked-by: Kevin Hilman khil...@linaro.org
Acked-by: Rob Herring robherri...@gmail.com
If the cpuidle init cpu operation returns -ENXIO, therefore reporting HW
failure or misconfiguration, the CPUidle driver skips the respective
cpuidle device initialization because the associated platform back-end HW
is not operational.
That prevents the system to crash and allows to handle the
Call the common ARM/ARM64 'arm_cpuidle_suspend' instead of cpu_suspend function
which is specific to ARM64.
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
Acked-by: Kevin Hilman khil...@linaro.org
Acked-by: Rob Herring robherri...@gmail.com
Acked-by: Lorenzo Pieralisi
With this change the cpuidle-arm64.c file calls the same function name
for both ARM and ARM64.
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
Acked-by: Kevin Hilman khil...@linaro.org
Acked-by: Rob Herring robherri...@gmail.com
Acked-by: Catalin Marinas catalin.mari...@arm.com
Tested-by:
Add kernel-doc format documentation in the code.
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
---
arch/arm/kernel/cpuidle.c | 59 +++
1 file changed, 59 insertions(+)
diff --git a/arch/arm/kernel/cpuidle.c b/arch/arm/kernel/cpuidle.c
index
In the next patch, this driver will be common across ARM/ARM64. Remove all refs
to ARM64 as it will be shared with ARM32.
Signed-off-by: Daniel Lezcano daniel.lezc...@linaro.org
Acked-by: Kevin Hilman khil...@linaro.org
Acked-by: Rob Herring robherri...@gmail.com
Acked-by: Lorenzo Pieralisi
Commit-ID: 9ed8e7d86061e7c3fb3855358d51ba4abb19ceb1
Gitweb: http://git.kernel.org/tip/9ed8e7d86061e7c3fb3855358d51ba4abb19ceb1
Author: Denys Vlasenko dvlas...@redhat.com
AuthorDate: Thu, 19 Mar 2015 18:17:47 +0100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Mar 2015
Signed-off-by: Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com
[mpe: Fix the 32-bit code also]
Signed-off-by: Michael Ellerman m...@ellerman.id.au
---
arch/powerpc/include/asm/kvm_book3s_64.h | 12 +++-
arch/powerpc/mm/dma-noncoherent.c| 2 +-
arch/powerpc/mm/fsl_booke_mmu.c
Commit-ID: ef593260f0cae2699874f098fb5b19fb46502cb3
Gitweb: http://git.kernel.org/tip/ef593260f0cae2699874f098fb5b19fb46502cb3
Author: Denys Vlasenko dvlas...@redhat.com
AuthorDate: Thu, 19 Mar 2015 18:17:46 +0100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Mar 2015
The callers of setbat() are actually passing a pgprot_t for the flags
parameter. This doesn't matter unless STRICT_MM_TYPECHECKS is enabled.
So we can turn that on without breaking the build, change setbat() to
take a pgprot_t and have it convert it to an unsigned long internally.
Signed-off-by:
Commit-ID: dca5b52ad76b10c3adc29e2a006d4b1721c44a8d
Gitweb: http://git.kernel.org/tip/dca5b52ad76b10c3adc29e2a006d4b1721c44a8d
Author: Ingo Molnar mi...@kernel.org
AuthorDate: Tue, 24 Mar 2015 19:44:42 +0100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Mar 2015 20:57:31
Am 25.03.2015 um 10:11 schrieb Michael Ellerman:
If STRICT_MM_TYPECHECKS is enabled the generic gup code fails to build
because we are using ACCESS_ONCE on non-scalar types.
Convert all uses to READ_ONCE.
There is a similar patch from Jason Low in Andrews patch.
If that happens in 4.0-rc, we
On Tue, Mar 24, 2015 at 06:06:26PM -0400, Chris Metcalf wrote:
On 3/24/2015 5:14 PM, Peter Zijlstra wrote:
On Tue, Mar 24, 2015 at 03:21:32PM -0400, cmetc...@ezchip.com wrote:
From: Chris Metcalf cmetc...@ezchip.com
Tile includes a hypervisor hook to deliver messages to arbitrary
tiles, so
At Mon, 23 Mar 2015 09:25:06 +0100,
Daniel Vetter wrote:
On Mon, Mar 23, 2015 at 07:25:27AM +0100, Sedat Dilek wrote:
Hi,
I did my weekly update of the Linux RC (here: v4.0-rc5) and fell over
some warning in the drm area.
Please have a look...
Just to confirm: Both are new in
On Tue, Mar 24, 2015 at 07:50:07PM -0700, Guenter Roeck wrote:
On 03/24/2015 08:45 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.37 release.
There are 79 patches in this series, all will be posted as a response
to this one. If anyone has any issues
The of_xlate callback should return ERR_PTR on error.
Signed-off-by: Axel Lin axel@ingics.com
---
drivers/phy/phy-spear1310-miphy.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/phy/phy-spear1310-miphy.c
b/drivers/phy/phy-spear1310-miphy.c
index
As there isn't a way for the firmware on the Nyan chromebooks to hand
over the display to the kernel, and the kernel isn't redoing the whole
configuration at present.
With this patch, the SOR is brought to a known state and we get correct
display on every boot.
Signed-off-by: Tomeu Vizoso
The current state of the different cpuidle drivers is the different PM
operations are passed via the platform_data using the platform driver
paradigm.
This approach allowed to split the low level PM code from the arch specific
and the generic cpuidle code.
Unfortunately there are complaints
* John Stultz john.stu...@linaro.org wrote:
Ingo, Peter, Thomas,
The following patches from Daniel extend the arch-generic sched_clock
implementation so that it can be safely called from NMI (or FIQ on ARM)
context. They also optimize the sched_clock logic to improve cache
performance.
The STRICT_MM_TYPECHECKS code has bit-rotted over the years. To make it
possible to easily build test it, make it a CONFIG option.
Signed-off-by: Michael Ellerman m...@ellerman.id.au
---
arch/powerpc/Kconfig.debug | 8
arch/powerpc/include/asm/page.h | 4 +---
Commit-ID: f9d71854b4fe9b22ca199c4676da5a6ece1e5c17
Gitweb: http://git.kernel.org/tip/f9d71854b4fe9b22ca199c4676da5a6ece1e5c17
Author: Ingo Molnar mi...@kernel.org
AuthorDate: Tue, 24 Mar 2015 19:44:11 +0100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Mar 2015 20:57:31
Commit-ID: 1ddc6f3c60d75a7577dd33bc441e309febe2fc76
Gitweb: http://git.kernel.org/tip/1ddc6f3c60d75a7577dd33bc441e309febe2fc76
Author: Ingo Molnar mi...@kernel.org
AuthorDate: Tue, 24 Mar 2015 19:43:11 +0100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Mar 2015 20:57:30
This is already declared in mmu_decl.h, so we don't need a second
version in the C file.
Signed-off-by: Michael Ellerman m...@ellerman.id.au
---
arch/powerpc/mm/pgtable_32.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/powerpc/mm/pgtable_32.c b/arch/powerpc/mm/pgtable_32.c
index
Commit-ID: 65c2377486c0b68f149f7d8770499a86b15786b6
Gitweb: http://git.kernel.org/tip/65c2377486c0b68f149f7d8770499a86b15786b6
Author: Denys Vlasenko dvlas...@redhat.com
AuthorDate: Thu, 19 Mar 2015 18:17:49 +0100
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Mar 2015
Commit-ID: b3494a4ab20f6bdf74cdf2badf7918bb65ee8a00
Gitweb: http://git.kernel.org/tip/b3494a4ab20f6bdf74cdf2badf7918bb65ee8a00
Author: Andy Lutomirski l...@kernel.org
AuthorDate: Mon, 23 Mar 2015 12:32:54 -0700
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 24 Mar 2015 21:08:28
If STRICT_MM_TYPECHECKS is enabled the generic gup code fails to build
because we are using ACCESS_ONCE on non-scalar types.
Convert all uses to READ_ONCE.
Cc: a...@linux-foundation.org
Cc: kirill.shute...@linux.intel.com
Cc: aarca...@redhat.com
Cc: borntrae...@de.ibm.com
Cc:
Hi David,
your commit 9861908f081f (MIPS: OCTEON: Enable little endian kernel.)
adds the following conditional select to arch/mips/Kconfig:
+ select SYS_SUPPORTS_HOTPLUG_CPU if CONFIG_CPU_BIG_ENDIAN
The problem is the 'CONFIG_' prefix for 'CPU_BIG_ENDIAN'. The item is
always off since
--- a/include/linux/oom.h
+++ b/include/linux/oom.h
@@ -32,6 +32,8 @@ enum oom_scan_t {
/* Thread is the potential origin of an oom condition; kill first on oom */
#define OOM_FLAG_ORIGIN ((__force oom_flags_t)0x1)
+extern struct mutex oom_lock;
+
static inline void
On Wed, Mar 25, 2015 at 08:55:38AM +0200, Kalle Valo wrote:
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
3.19-stable review patch. If anyone has any objections, please let me know.
--
From: RafaÅ MiÅecki zaj...@gmail.com
commit
On Tue, Mar 10, 2015 at 10:57 AM, Antoine Tenart
antoine.ten...@free-electrons.com wrote:
I think we better wait for the simple-mfd patch to make it to ARM SoC
first.
I got impatient waiting for subsys ACKs and sent a pull request for
this today.
Yours,
Linus Walleij
--
To unsubscribe from
On Tue, Mar 24, 2015 at 07:36:01PM -0700, Guenter Roeck wrote:
On 03/24/2015 08:45 AM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.19.3 release.
There are 123 patches in this series, all will be posted as a response
to this one. If anyone has any issues
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
On Wed, Mar 25, 2015 at 08:55:38AM +0200, Kalle Valo wrote:
Greg Kroah-Hartman gre...@linuxfoundation.org writes:
3.19-stable review patch. If anyone has any objections, please let me
know.
--
From: Rafał
On Wed, 2015-03-25 at 12:23 +0530, rtat...@codeaurora.org wrote:
From: Rupesh Tatiya rtat...@codeaurora.org
USB 2.01+ full-speed devices can have extended descriptor as well
and can support LPM.
Yes, they in theory can, but what happens if they are actually
asked to do so? On how many
On Thu, 2015-03-12 at 21:34 +0100, Fabian Frederick wrote:
directly return recover_head() and ubifs_leb_unmap()
instead of storing value in err and testing it.
Signed-off-by: Fabian Frederick f...@skynet.be
---
Pushed to linux-ubifs/master, thanks!
--
To unsubscribe from this list: send
On 25 March 2015 at 02:39, Bjorn Andersson
bjorn.anders...@sonymobile.com wrote:
Signed-off-by: Bjorn Andersson bjorn.anders...@sonymobile.com
Thanks! Applied.
Kind regards
Uffe
---
drivers/mmc/host/mmci.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
On 23 March 2015 at 17:47, Georgi Djakov georgi.dja...@linaro.org wrote:
Some versions of this controller do not advertise their 3.0v and
8bit bus-width support capabilities. It is required to explicitly
set these capabilities for the specific controller versions.
Signed-off-by: Georgi Djakov
Hi Thomas and Jason,
Do you have any comment for this patch ? In this series,
pci_bus_add_devices()
has been ripped out from pci_scan_root_bus(), so I think the
pci_scan_root_bus() is
almost the same as pci_create_root_bus + pci_scan_child_bus(). And in this
series,
we try to unexport
On 2015/3/24 0:48, Bjorn Helgaas wrote:
On Mon, Mar 23, 2015 at 03:22:14PM +0800, Jiang Liu wrote:
snit
---
arch/x86/pci/acpi.c |5 ++---
drivers/acpi/resource.c |3 +++
2 files changed, 5 insertions(+), 3 deletions(-)
diff --git a/arch/x86/pci/acpi.c b/arch/x86/pci/acpi.c
tree: git://git.kernel.org/pub/scm/linux/kernel/git/dgc/linux-xfs
fallocate-insert-range
head: a904b1ca5751faf5ece8600e18cd3b674afcca1b
commit: a904b1ca5751faf5ece8600e18cd3b674afcca1b [10/10] xfs: Add support
FALLOC_FL_INSERT_RANGE for fallocate
reproduce:
# apt-get install sparse
git
Signed-off-by: Fengguang Wu fengguang...@intel.com
---
xfs_bmap_util.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/xfs_bmap_util.c b/fs/xfs/xfs_bmap_util.c
index fe1f11b..e867573 100644
--- a/fs/xfs/xfs_bmap_util.c
+++ b/fs/xfs/xfs_bmap_util.c
@@ -1383,7 +1383,7
On Tue 24-03-15 11:30:35, Jason Low wrote:
On Tue, 2015-03-24 at 11:30 +0100, Michal Hocko wrote:
On Mon 23-03-15 15:44:40, Jason Low wrote:
Commit 38c5ce936a08 converted ACCESS_ONCE usage in gup_pmd_range() to
READ_ONCE, since ACCESS_ONCE doesn't work reliably on non-scalar types.
Hi,
Am 25.03.2015 um 02:45 schrieb Sebastian Reichel s...@kernel.org:
Hi,
On Tue, Mar 24, 2015 at 06:58:15PM +0100, Dr. H. Nikolaus Schaller wrote:
So you propose that the parent-child relationship is “control”? I.e. some
channel which allows to address some bus client (through reg) and
Marc,
On 03/24/2015 07:00 PM, Marc Zyngier wrote:
Hi Takahiro,
On 23/03/15 11:53, AKASHI Takahiro wrote:
Cpu must be put back into its initial state, at least, in the
following cases in order to shutdown the system and/or re-initialize cpus
later on:
1) kexec/kdump
2) cpu hotplug (offline)
3)
Pushing it higher is not a big deal as far as the implementation goes, though
16 bits might be stealing a bit too much space for this. On 32-bit archs, we
have 18 bits currently free that we can abuse. The Samsung device supports
16 streams. That's honestly a lot more than I would expect most
Hi,
On 03/13/2015 02:36 PM, Daniel Vetter wrote:
On Fri, Mar 13, 2015 at 11:55:07AM +0530, Archit Taneja wrote:
On 03/11/2015 08:47 PM, Daniel Vetter wrote:
On Wed, Mar 11, 2015 at 01:51:02PM +0530, Archit Taneja wrote:
On 03/10/2015 05:47 PM, Daniel Vetter wrote:
On Tue, Mar 10, 2015
1 - 100 of 2000 matches
Mail list logo
