From: Kalle Valo
Date: Sat, 17 Oct 2015 08:26:19 +0300
> few small fixes I would like to get to 4.3 still. Please let me know if
> there are any problems.
Pulled, thanks Kalle.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Vineet Gupta writes:
>
> But this user space - so IMHO UP/SMP doesn't matter and we can't simulate
> them in
> C just by itself.
It matters when you access the perf ring buffer which is updated by kernel.
Also perf is now multi threaded to some degree.
-Andi
--
To unsubscribe from this list:
ASIU gpio controller's pins are muxed with pin-cntroller.
Add this mapping through property "gpio-ranges".
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
arch/arm/boot/dts/bcm-cygnus.dtsi | 53 +--
1 file changed, 51
This compatible string should be used for all new iproc based future
SoCs having the same GPIO controller hardware.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/pinctrl/bcm/pinctrl-cygnus-gpio.c | 1 +
1 file changed, 1 insertion(+)
diff --git
Rename gpio driver file name from pinctrl-cygnus-gpio.c to
pinctrl-iproc-gpio.c to make it more generic so that all
iproc based future SoCs using the same gpio block could
use this driver.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
Renamed gpio controller's driver name from cygnus to iproc to make it
more generic so that all iProc based SoCs having the same gpio controller
could use this.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
.../bindings/pinctrl/{brcm,cygnus-gpio.txt =>
Change functions, macros and variables name from cygnus to IP block,
iproc, so that it could be used in all iproc based future SoCs having
same GPIO controller block.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/pinctrl/bcm/pinctrl-cygnus-gpio.c |
Remove gpio to pinctrl pin mapping code from driver and
address this through standard property "gpio-ranges".
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
drivers/pinctrl/bcm/pinctrl-cygnus-gpio.c | 131 +-
1 file changed, 3
Generalized pinctrl-cygnus-gpio driver so that it could be used for all
iProc architecture based future SoCs having same gpio pin controller.
Generalization process made the below changes in driver-
1. Removed pin mapping from driver and addressed this via DT through
"gpio-ranges" property.
2.
If GPIO controller's pins are muxed, pin-controller subsystem
need to be intimated by defining mapping between gpio and
pinmux controller. This patch adds required properties to
define this mapping via DT.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
Add ngpios property to the gpio controller's DT node so that controller
driver extracts total number of gpio lines present in controller
from DT and removes dependency on driver.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
This new compatible string, "brcm,iproc-gpio", should be used for
all new iproc-based future SoCs.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
Documentation/devicetree/bindings/pinctrl/brcm,cygnus-gpio.txt | 4 ++--
1 file changed, 2 insertions(+), 2
Since identical hardware is used in several instances and all pins
are not routed to pinctrl hence getting total number of gpios from
DT make more sense hence stop using total number of gpios pins from
drivers and extract it from DT.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by:
Add ngpios property in cygnus ASIU, CCM and CRMU gpio controller's
node.
Signed-off-by: Pramod Kumar
Reviewed-by: Ray Jui
Reviewed-by: Scott Branden
---
arch/arm/boot/dts/bcm-cygnus.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/bcm-cygnus.dtsi
Currently, 8-bit (MMIO) and 32-bit (MMIO32) strides are supported for
the 8250 console, but 16-bit (MMIO16) stride is not. The 8250 UART
device on my board has 16-bit stride (reg-shift = <1>) and I am eager
to use earlycon with it.
Refer to arch/arm/boot/dts/uniphier-support-card.dtsi:
1/2: add MMIO16 register interface support
2/2: allow to input clock frequency from kernel parameter
Masahiro Yamada (2):
serial: support register interface with 16-bit stride for console
serial: earlycon: allow to specify uartclk in earlycon
kernel-parameter
The input clock frequency varies from device to device, but the
earlycon uses the fixed frequency (BASE_BAUD * 16). It makes
impossible to set the correct divisor to the register.
This commit allows to specify the input clock frequency from the
kernel-parameter.
[Example]
This patch implements a timer map type inherited from array map. eBPF
programs can deloy a timer by updating an entry in timer map, and
destroy that by deleting the entry. The timer delay time(ns) is set by
updating the value field of the entries.
Currently, an intended empty function is called
On Sun, 2015-10-18 at 14:01 +0300, Sergei Shtylyov wrote:
> Hello.
>
> On 10/18/2015 6:51 AM, Chunfeng Yun wrote:
>
> > add xHCI and phy drivers for MT8173-EVB
> >
> > Signed-off-by: Chunfeng Yun
>
> [...]
>
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8173.dtsi
> >
From: Santosh Shilimkar
Date: Fri, 16 Oct 2015 22:13:21 -0400
> Sowmini found hang with rds-ping while testing RDS over TCP. Its
> a corner case and doesn't happen always. The issue is not reproducible
> with IB transport. Its clear from below dump why we see it with RDS TCP.
...
> This happens
On 19.10.2015 13:37, Krzysztof Kozlowski wrote:
> After suspend to RAM the device stopped to work with ETIMEDOUT error:
>
> $ dd if=/dev/hwrng of=/dev/null bs=1 count=16
> dd: reading `/dev/hwrng': Connection timed out
>
> In the STATUS register the bits #5 (PRNG_DONE) and #1
>
Enable Pseudo Random Number Generator (PRNG) on Trats2 board. This
allows using hardware random number generator:
$ echo exynos > /sys/class/misc/hw_random/rng_current
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos4412-trats2.dts | 4
1 file changed, 4 insertions(+)
diff
Add Pseudo Random Number Generator (PRNG) node of Security Sub System
(SSS) to Exynos 4 DTSI.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/boot/dts/exynos4.dtsi | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4.dtsi b/arch/arm/boot/dts/exynos4.dtsi
index
Add a gate clock for controlling all clocks of Security Sub System
(SSS).
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/samsung/clk-exynos4.c | 1 +
include/dt-bindings/clock/exynos4.h | 1 +
2 files changed, 2 insertions(+)
diff --git a/drivers/clk/samsung/clk-exynos4.c
Hi,
The patchset adds necessary clock from Security SubSystem (SSS)
and enables the PRNG module of Exynos for Trats2 board.
The first patch (clock) is required for other ones so please
take everything in one step.
The actual Device Tree support (and compatible) was sent in separate
patch:
-
On Monday 19 October 2015 04:45 AM, Andi Kleen wrote:
> Alexey Brodkin writes:
>> So the best we may do is to implement detection of atomics in the toolchain
>> and if there's no atomics hard stop with
>> perf building.
> If your target is single cpu only you can always simulate them in C.
>
>
On Sun, Oct 18, 2015 at 7:20 AM, Borislav Petkov wrote:
> Ok,
>
> let's try this and see where it takes us. Patch has been only lightly
> tested in kvm - I'll hammer on it for real once we agree about the
> general form.
>
> Aanyway, this patch is something Peter and I have been talking about on
On Oct 18, 2015 3:16 AM, "tip-bot for Andy Lutomirski" wrote:
>
> Commit-ID: 657c1eea0019e80685a84cbb1919794243a187c9
> Gitweb: http://git.kernel.org/tip/657c1eea0019e80685a84cbb1919794243a187c9
> Author: Andy Lutomirski
> AuthorDate: Fri, 16 Oct 2015 15:42:54 -0700
> Committer: Ingo
Add Device Tree support for the driver. The Pseudo Random Number
Generator module is the same in almost all of Exynos SoCs, since
Exynos4210 (however the tests were done only on Trats2 board with
Exynos4412). There are some differences on newer Exynos Octa
(Exynos542x) SoCs.
Signed-off-by:
Document the bindings used by exynos-rng Pseudo Random Number Generator
driver.
Signed-off-by: Krzysztof Kozlowski
---
.../devicetree/bindings/rng/samsung,exynos-rng4.txt | 17 +
1 file changed, 17 insertions(+)
create mode 100644
After suspend to RAM the device stopped to work with ETIMEDOUT error:
$ dd if=/dev/hwrng of=/dev/null bs=1 count=16
dd: reading `/dev/hwrng': Connection timed out
In the STATUS register the bits #5 (PRNG_DONE) and #1
(SEED_SETTING_DONE) were not set. Instead PRNG_ERROR (seventh bit) was
high.
Driver may hang waiting indefinitely for PRNG to finish its
initialization stage. Instead of stalling return -ETIMEDOUT error.
Signed-off-by: Krzysztof Kozlowski
---
drivers/char/hw_random/exynos-rng.c | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
The register offset must be shifted by regshift, otherwise the
baudrate is not set. I missed the issue probably because the
divisor register was already set by the boot loader.
Fixes: 1a8d2903cb6a ("serial: 8250_uniphier: add UniPhier serial driver")
Signed-off-by: Masahiro Yamada
---
Hi Greg,
On Fri, 2015-10-16 at 22:05 +0200, Christophe JAILLET wrote:
> Hi,
> sorry if un-clear.
>
> What I mean is that in the patch related
> 'powerpc/sysdev/mpc5xxx_clocks.c', there was no call to 'be32_to_cpup'.
> So in the proposed patch, 'of_property_read_u32' adds it.
>
> While in the patch
Hi,
The patchset fixes known issues in Exynos hardware random number
generator and adds Device Tree support for it.
The device was tested on Trats2 board (Exynos4412). It should work
on other Exynos4 and Exynos5 as well... altough it seems that
on some of Exynos542x boards the SSS module is
On 10/17/2015 06:55 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.2.4 release.
There are 258 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/17/2015 06:56 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 4.1.11 release.
There are 202 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/17/2015 07:04 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.14.55 release.
There are 79 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
On 10/17/2015 07:05 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.10.91 release.
There are 54 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be
于 2015/10/17 6:06, Alexei Starovoitov 写道:
> On 10/16/15 12:42 AM, Kaixu Xia wrote:
>> This patch adds the flag dump_enable to control the trace data
>> output process when perf sampling. By setting this flag and
>> integrating with ebpf, we can control the data output process and
>> get the
On Wed, 2015-10-14 at 16:24 -0400, Tejun Heo wrote:
> But in terms of API consistency, it sucks to have queue_work()
> guarantee local queueing but not queue_delayed_work(). The ideal
> situation would be updating both so that neither guarantees.
You don't have to change anything to have
Hi Javier,
On 10/15/2015 10:21 PM, Javier Martinez Canillas wrote:
Hello,
The Exynos Chromebooks DTS don't use the correct card detection properties
since these were carried from the vendor tree that had a reason to do so.
There are two things that I noticed:
1) The Marvell WiFi SDIO is
From: Magnus Damm
Neither the ARM page table code enabled by IOMMU_IO_PGTABLE_LPAE
nor the IPMMU_VMSA driver actually depends on ARM_LPAE, so get
rid of the dependency.
Tested with ipmmu-vmsa on r8a7794 ALT and a kernel config using:
# CONFIG_ARM_LPAE is not set
Signed-off-by: Magnus Damm
On Sun, Oct 18, 2015 at 7:38 PM, Randy Dunlap wrote:
>
> When using 'patch' and patch-4.3-rc6.gz to create a Linux 4.3-rc6 source tree,
> scripts/kernel-doc-xml-ref is not created as executable. (This has been
> happening for several -rc releases now).
'patch' doesn't know anything about file
于 2015/10/17 6:06, Alexei Starovoitov 写道:
> On 10/16/15 12:42 AM, Kaixu Xia wrote:
>> This patch adds the flag dump_enable to control the trace data
>> output process when perf sampling. By setting this flag and
>> integrating with ebpf, we can control the data output process and
>> get the
From: Arnd Bergmann
Date: Fri, 16 Oct 2015 11:33:49 +0200
> The HNS MDIO driver fails to build on older ARM machines that are not
> yet converted to CONFIG_OF:
>
> drivers/net/ethernet/hisilicon/hns_mdio.c: In function 'hns_mdio_bus_name':
> drivers/net/ethernet/hisilicon/hns_mdio.c:405:14:
From: Arnd Bergmann
Date: Fri, 16 Oct 2015 12:00:51 +0200
> BITS_RX_EN is an 'unsigned long' constant, so the ones complement of that
> has bits set that do not fit into a 32-bit variable on 64-bit architectures,
> which causes a harmless gcc warning:
>
>
On 10/18/2015 09:00 PM, Greg KH wrote:
On Sun, Oct 18, 2015 at 12:02:53PM +0530, punit vara wrote:
One more thing I would like suggestion how can start switching this
driver to LIB80211 ,MAC80211 ? Which is the first file I should focus
? Simultaneously I am trying to understand the flow of
From: Arnd Bergmann
Date: Fri, 16 Oct 2015 11:30:56 +0200
> Some configurations fail to build the hns dsaf code because of
> a missing header file:
>
> ethernet/hisilicon/hns/hns_dsaf_main.c: In function 'hns_dsaf_init':
> ethernet/hisilicon/hns/hns_dsaf_main.c:1096:2: error: implicit
From: yankejian
Date: Fri, 16 Oct 2015 17:03:18 +0800
> This patchset fixes two bugs in hns driver.
> - fixes timeout when received pause frame from the connective ports
> - should be set by using ethtool -s when the devices are link down
Series applied, thanks.
--
To unsubscribe from
On 2015/10/15 21:32, Taku Izumi wrote:
> Xeon E7 v3 based systems supports Address Range Mirroring
> and UEFI BIOS complied with UEFI spec 2.5 can notify which
> ranges are reliable (mirrored) via EFI memory map.
> Now Linux kernel utilize its information and allocates
> boot time memory from
On 10/18/15 16:45, Linus Torvalds wrote:
>
When using 'patch' and patch-4.3-rc6.gz to create a Linux 4.3-rc6 source tree,
scripts/kernel-doc-xml-ref is not created as executable. (This has been
happening for several -rc releases now).
Am I doing something wrong? (other than not using git)
or
From: huangdaode
Date: Fri, 16 Oct 2015 11:54:15 +0800
> This patchset fixes the two bugs in HNS driver, one is remove the hnae sysfs
> interface
> according to the review comments from Arnd Bergmann , another
> is fixing the wrong mac_id judgement bug which is found during internal tests.
From: Daniel Borkmann
Date: Fri, 16 Oct 2015 03:09:21 +0200
> This set adds support for persistent maps/progs. Please see
> individual patches for further details.
>
> A man-page update to bpf(2) will be sent afterwards, also a
> iproute2 patch for support in tc.
>
> Thanks!
It seems like the
From: Ma Ling
All load instructions can run speculatively but they have to follow
memory order rule in multiple cores as below:
_x = _y = 0
Processor 0 Processor 1
mov r1, [ _y] //M1 mov [ _x], 1 //M3
mov r2, [ _x] //M2 mov
ACPICA commit 0dd68e16274cd38224aa4781eddc57dc2cbaa108
The quit/exit commands shouldn't invoke acpi_terminate_debugger() and
acpi_terminate() right in the user command loop, because when the debugger
exits, the kernel ACPI subsystem shouldn't be terminated (acpi_terminate())
and the debugger
ACPICA commit 35273add90da19cd8790fdb5735f52e3c9861684
When single step execution is not ended, executing another control methods
leads to dead locks around interpreter lock/namespace lock/method
serialization lock. So we should only allow one execution from the debugger
at same time. Lv Zheng.
This patch enables ACPICA debugger files using a configurable
CONFIG_ACPI_DEBUGGER configuration item. Those debugger related code that
was originally masked as ACPI_FUTURE_USAGE now gets unmasked.
Necessary OSL stubs are also added in this patch:
1. acpi_os_readable(): This should be arch
When the debugger is running in the kernel mode, acpi_db_single_step() may
also be invoked by the kernel runtime code path but the single stepping
command prompt may be erronously logged as the kernel logs and runtime code
path cannot proceed.
This patch fixes this issue by adding
From: Bob Moore
ACPICA commit e9c75ca267262326e80d49a290e8387a5963e2d2
Version 20150930.
Link: https://github.com/acpica/acpica/commit/e9c75ca2
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
include/acpi/acpixf.h |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
ACPICA commit 7e823714911480be47e310fb1b3590d289b9fd99
Segmentation fault can be seen for executing the "terminate" command. This
is because acpi_ut_subsystem_shutdown() is errnously called multiple times.
This patch cleans up acpi_ut_subsystem_shutdown() logics to fix this
issue. Lv Zheng.
From: Bob Moore
ACPICA commit fbe67c46830f10c839941f8512cac5bddcb86bd3
Index (, 2) is now supported by [2]
This patch doesn't affect Linux kernel.
Link: https://github.com/acpica/acpica/commit/fbe67c46
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
From: Bob Moore
ACPICA commit 8d0f96e2a11a4ceabb2cae4b41e0ce1f4d3786b9
Adds much stricter typechecking in the iASL compiler, and
also adds some additional checking in the interpreter.
Link: https://github.com/acpica/acpica/commit/8d0f96e2
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
From: Bob Moore
ACPICA commit bed456ed2976bdaafdef406b982fdf6c539befc0
Removed some extraneous defines, reordered others.
Link: https://github.com/acpica/acpica/commit/bed456ed
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
drivers/acpi/acpica/acapps.h |2 +-
From: Bob Moore
ACPICA commit ac1564c26d239348ef13455f61d5616f3961ff43
Used by the ACPICA applications.
This patch is a bit broken due to non-portable inclusion as on
some platforms, there is no such a header file for their lib-c exports.
Fortunately, Linux doesn't compile utfileio.c for
From: Bob Moore
ACPICA commit 534deab97fb416a13bfede15c538e2c9eac9384a
Updated one of the memory subtable flags to clarify.
Link: https://github.com/acpica/acpica/commit/534deab9
Signed-off-by: Bob Moore
Signed-off-by: Lv Zheng
---
drivers/acpi/nfit.c |6 +++---
drivers/acpi/nfit.h
From: Bob Moore
ACPICA commit 6b2701f619040e803313363f516b200e362a9100
Make these mutex objects independent of the deadlock detection mechanism.
This mechanism caused failures with the multithread debugger.
This patch doesn't affect Linux kernel as debugger is currently not fully
functioning
From: Bob Moore
ACPICA commit eea1f0e561893b6d6417913b2d224082fe3a0a5e
Remove use of ACPI_DEBUGGER and ACPI_DISASSEMBLER where these
defines are used around entire modules.
Note: This type of code also causes problems with IDEs.
Link: https://github.com/acpica/acpica/commit/eea1f0e5
On Sun, 2015-10-18 at 12:51PM -0500, Josh Cartwright wrote:
> On Fri, Oct 16, 2015 at 03:42:28PM -0700, Moritz Fischer wrote:
> > Signed-off-by: Moritz Fischer
> > ---
> >
> > v2:
> > - Clock names are now a required property
> > - Removed interrupt-parent property
> >
> > ---
> >
The 20150930 ACPICA kernel-resident subsystem updates are linuxized based
on the linux-pm/linux-next branch.
The patchset has passed the following build/boot tests.
Build tests are performed as follows:
1. i386 + allyes
2. i386 + allno
3. i386 + default + ACPI_DEBUGGER=y
4. i386 + default +
On 2015/10/16 17:30, Arnd Bergmann wrote:
On Friday 16 October 2015 11:54:15 huangdaode wrote:
This patchset fixes the two bugs in HNS driver, one is remove the hnae sysfs
interface
according to the review comments from Arnd Bergmann , another
is fixing the wrong mac_id judgement bug which is
From: Insu Yun
Date: Thu, 15 Oct 2015 18:02:28 +
> Since vzalloc can be failed in memory pressure,
> writes -ENOMEM to xenstore to indicate error.
>
> Signed-off-by: Insu Yun
Applied.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
From: Arun Parameswaran
Date: Thu, 15 Oct 2015 10:37:13 -0700
> The 'bcm-phy-lib.c', added as a part of the commit
> "net: phy: Add Broadcom phy library for common interfaces"
> was missing the module license. This was causing an issue
> when the library is built as a module; "module license
>
Got it ,
Thanks for your explanation .
> On Oct 16, 2015, at 18:57, Mark Rutland wrote:
>
> Hi,
>
> On Fri, Oct 16, 2015 at 06:46:07PM +0800, yalin wang wrote:
>> Change to use memmove(), in case the dest address overlap with the
>> source address.
>
> This cannot happen, and memove would not
On Sun, Oct 18, 2015 at 12:02:53PM +0530, punit vara wrote:
> On Sat, Oct 17, 2015 at 10:46 AM, Greg KH wrote:
> > On Wed, Oct 14, 2015 at 11:55:55PM +0530, Punit Vara wrote:
> >> Put constant on the right side of a test.Problem found using checkpatch:
> >>
> >> Warning:Comparisons should place
Hello Mark,
(I'm sorry for my late reply.)
Mark Salyzyn wrote:
>> I'm trying to make the feature of multiple pmsg instances for ramoops.
> I like it, in fact I encourage it.
Thank you.
> Multiple instances does allow one to control individual content aging or
> priority, I agree with your
On 2015/10/14 20:18, Joerg Roedel wrote:
> On Thu, Oct 08, 2015 at 03:45:47PM +0800, Chen Feng wrote:
>> +static int hi6220_smmu_attach_dev(struct iommu_domain *domain,
>> + struct device *dev)
>> +{
>> +struct hi6220_domain *m_domain = to_hi6220_domain(domain);
Sorry for the last patch, please use this to add stub for
debugfs_create_automount().
>From b3b877d8d9fd9795ea1055042039a272e47f4dc5 Mon Sep 17 00:00:00 2001
From: Jiaxing Wang
Date: Mon, 19 Oct 2015 09:46:12 +0800
Subject: [PATCH] debugfs: Add stub function for debugfs_create_automount().
Add
Neil Armstrong writes:
> This patch is based on an earlier patch by NeilBrown which is based on
> a older patch from Grant Erickson which provided PWM devices using
> the 'legacy' interface.
>
> The pwm driver was renamed to not be confused with the OMAP4 PWM dedicated
> hardware and was cleaned
On 17.10.2015 01:01, Daniel Thompson wrote:
> Currently this driver calls pm_runtime_get_sync() rampantly
> but never puts anything back. This makes it impossible for the
> device to autosuspend properly; it will remain fully active
> after the first use.
>
> Fix in the obvious way.
>
>
On Sun, Oct 18, 2015 at 10:13:54PM +0200, Tobias Markus wrote:
> On 17.10.2015 23:55, Serge E. Hallyn wrote:
> > On Sat, Oct 17, 2015 at 05:58:04PM +0200, Tobias Markus wrote:
> >> Add capability CAP_SYS_USER_NS.
> >> Tasks having CAP_SYS_USER_NS are allowed to create a new user namespace
> >>
From: Santosh Shilimkar
Date: Wed, 14 Oct 2015 14:15:31 -0700
> From: Santosh Shilimkar
>
> To further improve the RDS connection scalabilty on massive systems
> where number of sockets grows into tens of thousands of sockets, there
> is a need of larger bind hashtable. Pre-allocated 8K or
On Sun, Oct 18, 2015 at 12:44:00PM +0200, Stephan Mueller wrote:
> Hi,
>
> This patch set adds the AF_ALG user space API to externalize the
> asymmetric cipher API recently added to the kernel crypto API.
>
> The patch set is tested with the user space library of libkcapi [1].
> Use [1]
On Fri, Oct 09, 2015 at 10:40:39AM +0100, Will Deacon wrote:
> On Fri, Oct 09, 2015 at 10:31:38AM +0200, Peter Zijlstra wrote:
[snip]
> >
> > So lots of little confusions added up to complete fail :-{
> >
> > Mostly I think it was the UNLOCK x + LOCK x are fully ordered (where I
> > forgot: but
Hi Rafael,
Today's linux-next merge of the pm tree got a conflict in:
arch/arm/mach-omap2/timer.c
between commits:
3afbb9afe2c4 ("arm: omap2: timer: move realtime_counter_init() around")
9c46ffcd5214 ("arm: omap2: timer: always call clocksource_of_init() when DT")
from the omap tree and
On 2015/10/16 20:35, Ulf Hansson wrote:
On 11 September 2015 at 10:54, Shawn Lin wrote:
This patch adds Generic PHY access for sdhci-of-arasan. Driver
can get PHY handler from dt-binding, and power-on/init the PHY.
Also we add pm ops for PHY here if CONFIG_PM_SLEEP is enabled.
Signed-off-by:
On 18 Oct 2015 22:13, Tobias Markus wrote:
> On 17.10.2015 22:17, Richard Weinberger wrote:
> > On Sat, Oct 17, 2015 at 5:58 PM, Tobias Markus wrote:
> >> One question remains though: Does this break userspace executables that
> >> expect being able to create user namespaces without priviledge?
On Fri, Oct 16, 2015 at 04:34:43PM -0500, Bjorn Helgaas wrote:
> On Fri, Oct 02, 2015 at 11:25:03AM +0100, Phil Edworthy wrote:
> > Fixes and changes to get PCIe working on ARM64 with mulitple instances.
> >
> > I've tested these on ARM (Koelsch board), and it works fine.
> > I've also tested on
On Mon, 2015-10-19 at 03:09 +0300, Alexey Klimov wrote:
> 1) Change pr_warn()s to pr_err()s. These messages are actually
> errors and not warnings.
> 2) Add missing \n.
> 3) Error message for kzalloc() failure is removed per suggestion
> by Joe Perches. There is generic stack_dump() for allocation
On Thu, Oct 15, 2015 at 09:30:40AM -0700, Paul E. McKenney wrote:
> On Thu, Oct 15, 2015 at 12:48:03PM +0800, Boqun Feng wrote:
> > On Wed, Oct 14, 2015 at 08:07:05PM -0700, Paul E. McKenney wrote:
[snip]
> >
> > > Why not try creating a longer litmus test that requires P0's write to
> > > "a" to
On 16.10.2015 01:51, Javier Martinez Canillas wrote:
> The eMMC is non-removable so is marked with the non-removable DT
> property to avoid having to redetect it after a suspend/resume.
>
> But it also has the broken-cd property which is wrong since only
> one of the DT properties for card
On 16.10.2015 01:51, Javier Martinez Canillas wrote:
> The eMMC is non-removable so mark it using the non-removable DT
> property to avoid having to redetect it after a suspend/resume.
>
> Also remove the card-detect-delay property that is not needed with
> non-removable.
>
> Signed-off-by:
On 16.10.2015 01:51, Javier Martinez Canillas wrote:
> The eMMC is non-removable so is marked with the non-removable DT
> property to avoid having to redetect it after a suspend/resume.
>
> But it also has the broken-cd property which is wrong since only
> one of the DT properties for card
1) Change pr_warn()s to pr_err()s. These messages are actually
errors and not warnings.
2) Add missing \n.
3) Error message for kzalloc() failure is removed per suggestion
by Joe Perches. There is generic stack_dump() for allocation issues.
Signed-off-by: Alexey Klimov
---
On 16.10.2015 01:51, Javier Martinez Canillas wrote:
> The Exynos5800 Peach Pi Chromebook has a Marvell WiFi SDIO chip which
> can't neither be removed nor be detected. But the node isn't marked
> as non-removable and instead has the broken-cd DT property.
>
> This causes the device to be removed
Add error path to clear evt struct allocated by kzalloc()
in the beginning of function mtk_timer_init().
Acked-by: Matthias Brugger
Signed-off-by: Alexey Klimov
---
drivers/clocksource/mtk_timer.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git
It's a bit unclear what subsystem/driver emits some messages
to dmesg in function mtk_init_timer().
Use pr_fmt to auto-prefix the messages appropriately.
Acked-by: Matthias Brugger
Signed-off-by: Alexey Klimov
---
drivers/clocksource/mtk_timer.c | 2 ++
1 file changed, 2 insertions(+)
diff
On 16.10.2015 01:51, Javier Martinez Canillas wrote:
> The Exynos5250 Snow Chromebooks have a Marvell WiFi SDIO chip which
> can't neither be removed nor be detected. But the node isn't marked
> as non-removable and instead has the broken-cd DT property.
>
> This causes the device to be removed
On 16.10.2015 01:51, Javier Martinez Canillas wrote:
> The Exynos5420 Peach Pit Chromebook has a Marvell WiFi SDIO chip which
> can't neither be removed nor be detected. But the node isn't marked
> as non-removable and instead has the broken-cd DT property.
>
> This causes the device to be
Hi,
I recently upgraded the kernel in a Dell Latitude D600 and found that the
touchpad clicks failed. The problem was bisected to commit
92bac83dd79e60e65c475222e41a992a70434beb ("Input: alps - non interleaved V2
dualpoint has separate stick button bits"). The laptop has a combination
1 - 100 of 558 matches
Mail list logo
