On Mon 26-12-16 19:57:03, Nils Holland wrote:
> On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote:
> > On Fri 23-12-16 23:26:00, Nils Holland wrote:
> > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote:
> > > >
> > > > Nils, even though this is still highly experimental, c
Hi,
On Thursday 22 December 2016 03:12 PM, Jaehoon Chung wrote:
> If some ops-> callback function are not assigend, then it should do the
> unexpect behavior.
> To prevent the potential NULL pointer dereference, check the each
> callback functions before doing operation.
The call backs checks are
This chip is the same as RTL8168, but its device id is 0x8161.
Signed-off-by: Chun-Hao Lin
---
drivers/net/ethernet/realtek/r8169.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/ethernet/realtek/r8169.c
b/drivers/net/ethernet/realtek/r8169.c
index f9b97f5..44389c9 100644
--- a
Dear email user
Your mailbox has exceeded the storage limit which set by your administrator,you
may not be able to send or receive new mail until you re-validate your mailbox.
To re-validate your mailbox please send the following details below:
Name:
Username:
Password:
Retype Password:
Email A
On 12/27/2016 05:31 PM, Kishon Vijay Abraham I wrote:
> Hi,
>
> On Thursday 22 December 2016 03:12 PM, Jaehoon Chung wrote:
>> If some ops-> callback function are not assigend, then it should do the
>> unexpect behavior.
>> To prevent the potential NULL pointer dereference, check the each
>> callb
At 2016-12-27 15:52:18, "Wei Zhang" wrote:
>When we send a packet for our own local address on a non-loopback interface
>(e.g. eth0), due to the change had been introduced from commit 0b922b7a829c
>("net: original ingress device index in PKTINFO"), the original ingress
>device index would be set a
Below is the list of build error/warning regressions/improvements in
v4.10-rc1[1] compared to v4.9[2].
Summarized:
- build errors: +7243/-8
- build warnings: +1141/-479
#In addition, I've put the verbose summary at
As I haven't mastered kup yet, there's no verbose summary at
http://www.kernel
From: Hyungwon Hwang
This patch add the panel device tree node for S6E3HA2 display
controller to TM2 dts.
Signed-off-by: Hyungwon Hwang
Signed-off-by: Andrzej Hajda
Signed-off-by: Chanwoo Choi
Signed-off-by: Hoegeun Kwon
---
arch/arm64/boot/dts/exynos/exynos5433-tm2.dts | 33 +++
Purpose of this patch is add support for S6E3HA2 AMOLED panel on
the TM2 board. The first patch adds support for S6E3HA2 panel
device tree document and driver, the second patch add support for
S6E3HA2 panel device tree.
Changes for V2:
- Fixed the samsung,s6e3ha2.txt DT document.
- Added active
This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel
driver. This panel has 1440x2560 resolution in 5.7-inch physical
panel in the TM2 device.
Signed-off-by: Donghwa Lee
Signed-off-by: Hyungwon Hwang
Signed-off-by: Hoegeun Kwon
---
Changes for V2:
- Fixed the samsung,s6e3ha2.txt DT d
On Tue, Dec 13, 2016 at 03:51:15PM +0100, Corentin Labbe wrote:
> linux/sched.h is useless for hw_random/core.c.
> This patch remove it.
I see a schedule_timeout_interruptible call in core.c.
Cheers,
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apa
Hello,
Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well
with my wireless card, which is:
Intel Corporation Wireless 7260 (rev bb)
Boot message shows that no suitable firmware found:
# journalctl -kp3
Dec 27 16:38:00 kernel: Error parsing PCC subspaces from PCCT
For LS1046a and LS1043a v1.1, the MSI controller has 4 MSIRs and 4
CPUs. A GIC SPI interrupt of MSIR can be associated with a CPU.
When changing MSI interrupt affinity, this MSI will be moved to the
corresponding MSIR and MSI message data will be changed according to
MSIR. when requesting a MSI, th
"1" should be replaced by "l". This is a typo.
The patch is to fix it.
Signed-off-by: Minghuan Lian
---
arch/arm/boot/dts/ls1021a.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot/dts/ls1021a.dtsi
index 282d854..6651938 10
"1" should be replaced by "l". This is a typo.
The patch is to fix it.
Signed-off-by: Minghuan Lian
---
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi
b/arch/arm64/boot/dts/f
In order to maximize the use of MSI, a PCIe controller will share
all MSI controllers. The patch changes msi-parent to refer to all
MSI controller dts nodes.
Signed-off-by: Minghuan Lian
---
arch/arm/boot/dts/ls1021a.dtsi | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/ar
On Thu, Dec 22, 2016 at 11:01:04AM +0100, Pavel Machek wrote:
>
> Add driver for et8ek8 sensor, found in Nokia N900 main camera. Can be
> used for taking photos in 2.5MP resolution with fcam-dev.
>
> Signed-off-by: Ivaylo Dimitrov
> Signed-off-by: Pavel Machek
Thanks!
I fixed a few checkpatch
On 12/27/2016 03:49 AM, Jason Wang wrote:
After commit 73b62bd085f4737679ea9afc7867fa5f99ba7d1b ("virtio-net:
remove the warning before XDP linearizing"), there's no users for
bpf_warn_invalid_xdp_buffer(), so remove it. This is a revert for
commit f23bc46c30ca5ef58b8549434899fcbac41b2cfc.
Cc: D
Hi Jan:
On Mon, Dec 12, 2016 at 04:04:36PM +0100, Jan Glauber wrote:
>
> this series adds support for hardware accelerated compression & decompression
> as found on ThunderX (arm64) SOCs. I've been reviewing this driver internally
> for some time and would like to get feedback on the RFC to see i
On Mon 26-12-16 16:53:39, David Rientjes wrote:
> On Mon, 26 Dec 2016, Michal Hocko wrote:
>
> > But my primary argument is that if you tweak "defer" value behavior
> > then you lose the only "stall free yet allow background compaction"
> > option. That option is really important.
>
> Important t
The patch is to fix typo of the Layerscape SCFG MSI dts compatible
strings. "1" is replaced by "l".
Signed-off-by: Minghuan Lian
---
.../devicetree/bindings/interrupt-controller/fsl,ls-scfg-msi.txt| 6 +++---
drivers/irqchip/irq-ls-scfg-msi.c | 6 --
2 f
LS1046a includes 3 MSI controllers.
Each controller supports 128 interrupts.
Signed-off-by: Minghuan Lian
---
.../interrupt-controller/fsl,ls-scfg-msi.txt | 1 +
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 31 ++
2 files changed, 32 insertions(+)
diff --git
LS1046a includes 4 MSIRs, each MSIR is assigned a dedicate GIC
SPI interrupt and provides 32 MSI interrupts. Compared to previous
MSI, LS1046a's IBS(interrupt bit select) shift is changed to 2 and
total MSI interrupt number is changed to 128.
The patch adds structure 'ls_scfg_msir' to describe MSI
In order to maximize the use of MSI, a PCIe controller will share
all MSI controllers. The patch changes "msi-parent" to refer to all
MSI controller dts nodes.
Signed-off-by: Minghuan Lian
---
arch/arm64/boot/dts/freescale/fsl-ls1043a.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions
Hi Linus:
This push fixes a hash corruption bug in the marvell driver.
Please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus
Romain Perier (1):
crypto: marvell - Copy IVDIG before launching partial DMA ahash requests
drivers/crypto/marvell/cesa.h
Thanks!
On Mon, Dec 26, 2016 at 09:43:23PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 26 Dec 2016 18:14:33 +0100
>
> A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the correspond
When we send a packet for our own local address on a non-loopback
interface (e.g. eth0), due to the change had been introduced from
commit 0b922b7a829c ("net: original ingress device index in PKTINFO"), the
original ingress device index would be set as the loopback interface.
However, the packet sh
On Mon, Dec 26, 2016 at 10:08:48AM -0800, Andy Lutomirski wrote:
>
> According to Daniel, the networking folks want to let embedded systems
> include BPF without requiring the crypto core.
Last I checked the IPv4 stack depended on the crypto API so this
sounds bogus.
Cheers,
--
Email: Herbert Xu
Hello!
On 12/27/2016 10:52 AM, Wei Zhang wrote:
When we send a packet for our own local address on a non-loopback interface
(e.g. eth0), due to the change had been introduced from commit 0b922b7a829c
("net: original ingress device index in PKTINFO"), the original ingress
device index would be s
On Tue, Dec 13, 2016 at 03:30:59PM +0100, Corentin Labbe wrote:
> THe major content of drivers/crypto/Makefile is sorted, only recent
> addition break this sort.
>
> This patch bring back this alphabetical sorting.
>
> Signed-off-by: Corentin Labbe
Patch applied. Thanks.
--
Email: Herbert Xu
On Tue, Dec 13, 2016 at 03:51:09PM +0100, Corentin Labbe wrote:
> This patch fix the checkpatch warning "Please don't use multiple blank lines"
>
> Signed-off-by: Corentin Labbe
Patches 1-6 applied. Thanks.
--
Email: Herbert Xu
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://g
On Mon 26-12-16 13:18:11, Jaewon Kim wrote:
> There was no bitmap API which returns both next zero index and size of zeros
> from that index.
>
> This is helpful to look fragmentation. This is an test code to look size of
> zeros.
> Test result is '10+9+994=>1013 found of total: 1024'
>
> unsign
On Thu, Dec 15, 2016 at 02:31:01PM +0100, Jiri Slaby wrote:
> With this reproducer:
> struct sockaddr_alg alg = {
> .salg_family = 0x26,
> .salg_type = "hash",
> .salg_feat = 0xf,
> .salg_mask = 0x5,
> .salg_name = "digest_null",
> };
> int so
On Wed, Dec 21, 2016 at 12:32:54PM -0800, Laura Abbott wrote:
>
> Christopher Covington reported a crash on aarch64 on recent Fedora
> kernels:
>
> kernel BUG at ./include/linux/scatterlist.h:140!
> Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
> Modules linked in:
> CPU: 2 PID: 752 Comm: crypto
On Mon, Dec 19, 2016 at 10:20:43AM +0800, Ryder Lee wrote:
> Hello,
>
> This adds support for the MediaTek hardware accelerator on
> some SoCs.
>
> This driver currently implement:
> - SHA1 and SHA2 family(HMAC) hash algorithms.
> - AES block cipher in CBC/ECB mode with 128/196/256 bits keys.
>
On Sat 24-12-16 00:14:58, Minchan Kim wrote:
> Andreas reported [1] made a test in jemalloc hang in THP mode in arm64.
> http://lkml.kernel.org/r/mvmmvfy37g1@hawking.suse.de
>
> The problem is currently page fault handler doesn't supports dirty bit
> emulation of pmd for non-HW dirty-bit archi
Dear Alim,
On 12/27/2016 03:34 PM, Alim Akhtar wrote:
> Hi Jaehoon,
>
[snip]
>>
>> Ah. Right..And i'm doing the refactoring to reuse the current pci-exynos.c.
> There is a nice refactoring patch posted by Pankaj recently @
> https://lkml.org/lkml/2016/12/23/73
> I would suggest you to rebase your
Hi Stefan,
> On 2016-12-26 23:55, Lukasz Majewski wrote:
> > From: Sascha Hauer
> >
> > The use of the ipg clock was introduced with commit 7b27c160c681
> > ("pwm: i.MX: fix clock lookup").
> > In the commit message it was claimed that the ipg clock is enabled
> > for register accesses. This is
Use axp209.dtsi in sun7i-a20-olinuxino-lime2.dts and correct
some regulators.
DCDC2 is used for vdd-cpu so it should never be bellow 1V and above 1.4V
DCDC3 is used for VDD_INT so same as above.
LD01 is used for the RTC, and should have a typical value of 1.3V
LD02 is used for AVCC and should have
On Tue, Dec 27, 2016 at 12:09:22AM +0100, Sedat Dilek wrote:
> [ Add some pm | i915 | x86 folks ]
>
> Hi,
>
> I have built Linux v4.10-rc1 today on my Ubuntu/precise AMD64 system
> and I see some call-traces.
> It is reproducible on suspend and resume.
>
> I cannot say which area touches the pro
The spi0 controller on the A20 have up to 4 CS (Chip Select) while the
others three only have 1.
Add the num-cs property to each node.
The current driver doesn't read this property but this is useful for
downstream user of DTS (FreeBSD for example).
Signed-off-by: Emmanuel Vadot
---
Changes in v3
A MSI controller of LS1043a v1.0 only includes one MSIR and
is assigned one GIC interrupt. In order to support affinity,
LS1043a v1.1 MSI is assigned 4 MSIRs and 4 GIC interrupts.
But the MSIR has the different offset and only supports 8 MSIs.
The bits between variable bit_start and bit_end in stru
On Mon 2016-12-26 10:11:51, Bjorn Andersson wrote:
> From: Bjorn Andersson
>
> Implement support for initialization of the lm3533 backlight from Device
> Tree.
>
> Signed-off-by: Bjorn Andersson
> Signed-off-by: Bjorn Andersson
Bjorn, you may want to fix your email system:
: host
seldseg
On Tue 2016-12-27 22:42:36, Kweh, Hock Leong wrote:
> From: "Kweh, Hock Leong"
>
> If kernel module stmmac driver being loaded after OS booted, there is a
> race condition between stmmac_open() and stmmac_mdio_register(), which is
> invoked inside stmmac_dvr_probe(), and the error is showed in dm
Commit-ID: 7e164ce4e8ecd7e9a58a83750bd3ee03125df154
Gitweb: http://git.kernel.org/tip/7e164ce4e8ecd7e9a58a83750bd3ee03125df154
Author: Sedat Dilek
AuthorDate: Mon, 26 Dec 2016 11:05:11 +0100
Committer: Thomas Gleixner
CommitDate: Tue, 27 Dec 2016 11:42:12 +0100
perf/x86/amd/ibs: Fix ty
2016-12-26 9:01 GMT+01:00 Baolin Wang :
> On some platfroms(like x86 platform), when one core is running the USB gadget
> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also can
> respond other interrupts from dwc3 controller and modify the event buffer by
> dwc3_interrupt()
On Mon 2016-12-26 10:11:51, Bjorn Andersson wrote:
> From: Bjorn Andersson
>
> Implement support for initialization of the lm3533 backlight from Device
> Tree.
>
> Signed-off-by: Bjorn Andersson
> Signed-off-by: Bjorn Andersson
Acked-by: Pavel Machek
--
(english) http://www.livejournal.com
Hello,
With Linux 4.8, the sget() function in fs/super.c got a new permission
check: It now returns -EPERM if
(!(flags & MS_KERNMOUNT) && !ns_capable(user_ns, CAP_SYS_ADMIN)) .
I presume the first half is intented to detect in-kernel mounts? If so,
why doesn't mount_pseudo() (in fs/libfs.c) pass
Hi,
On 27 December 2016 at 18:52, Janusz Dziedzic wrote:
> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
>> On some platfroms(like x86 platform), when one core is running the USB gadget
>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also
>> can
>> respond other interrupts fro
Hi,
Lu Baolu writes:
> On 12/26/2016 04:01 PM, Baolin Wang wrote:
>> On some platfroms(like x86 platform), when one core is running the USB gadget
>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also
>> can
>> respond other interrupts from dwc3 controller and modify the
Hi,
Janusz Dziedzic writes:
> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
>> On some platfroms(like x86 platform), when one core is running the USB gadget
>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core also
>> can
>> respond other interrupts from dwc3 controller and modify
Hi,
Baolin Wang writes:
> Hi,
>
> On 27 December 2016 at 18:52, Janusz Dziedzic
> wrote:
>> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
>>> On some platfroms(like x86 platform), when one core is running the USB
>>> gadget
>>> irq thread handler by dwc3_thread_interrupt(), meanwhile another core a
On Thu, 22 Dec 2016, Sam Ravnborg wrote:
> Hi Thomas.
>
> On Wed, Dec 21, 2016 at 08:19:47PM +0100, Thomas Gleixner wrote:
> > The following series completes the cpuhotplug rework stage ONE.
>
> Just curious - what is the stage TWO (and onwards) plan?
> lwn had some coverage of this work but I as
Hi,
Alan Stern writes:
> On Tue, 6 Dec 2016, Andrey Konovalov wrote:
>
>> Hi!
>>
>> I've got the following error report while running the syzkaller fuzzer.
>>
>> ep0_write() doesn't check the length, so a user can cause an
>> out-of-bounds with both size and data controlled.
>> There's a comme
On Tue, Dec 27, 2016 at 09:08:38AM +0100, Michal Hocko wrote:
> On Mon 26-12-16 19:57:03, Nils Holland wrote:
> > On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote:
> > > On Fri 23-12-16 23:26:00, Nils Holland wrote:
> > > > On Fri, Dec 23, 2016 at 03:47:39PM +0100, Michal Hocko wrote:
>
Hi,
Chunfeng Yun writes:
> the issue is introduced when @is_u3_ip is used in mtu3_device_enabe()
> before initialized in mtu3_mem_alloc(), so get global IP information
> at first before used by following functins.
>
> Signed-off-by: Chunfeng Yun
patch doesn't apply to my testing/fixes. Please
On Tue 27-12-16 12:23:13, Nils Holland wrote:
> On Tue, Dec 27, 2016 at 09:08:38AM +0100, Michal Hocko wrote:
> > On Mon 26-12-16 19:57:03, Nils Holland wrote:
> > > On Mon, Dec 26, 2016 at 01:48:40PM +0100, Michal Hocko wrote:
> > > > On Fri 23-12-16 23:26:00, Nils Holland wrote:
> > > > > On Fri,
On Mon, 26 Dec 2016 11:07:52 -0800
Linus Torvalds wrote:
> On Sun, Dec 25, 2016 at 5:16 PM, Nicholas Piggin wrote:
> >
> > I did actually play around with that. I could not get my skylake
> > to forward the result from a lock op to a subsequent load (the
> > latency was the same whether you use
On Mon 26-12-16 12:00:53, Michal Hocko wrote:
> [CCing linux-mm]
>
> On Sun 25-12-16 21:52:52, Klaus Ethgen wrote:
> > Hello,
> >
> > The last days I compiled version 4.9 for my i386 laptop. (Lenovo x61s)
>
> Do you have memory cgroups enabled in runtime (aka does the same happen
> with cgroup_d
Hi Hoegeun Kwon,
Thanks for the patch.
On 27.12.2016 10:05, Hoegeun Kwon wrote:
> This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel
> driver. This panel has 1440x2560 resolution in 5.7-inch physical
> panel in the TM2 device.
>
> Signed-off-by: Donghwa Lee
> Signed-off-by: Hyungwon
On Thu, 2016-12-01 at 03:43 +0200, Andy Shevchenko wrote:
> While resource_size_t is repeating phys_addr_t, allocate %par
> specifier for
> that type for sake of consistency.
Does it make sense to anyone?
>
> Signed-off-by: Andy Shevchenko
> ---
> Documentation/printk-formats.txt | 13
Hi,
Andrey Konovalov writes:
> Hi!
>
> I've got the following error report while running the syzkaller fuzzer.
>
> On commit 3c49de52d5647cda8b42c4255cf8a29d1e22eff5 (Dec 2).
>
> WARNING: CPU: 0 PID: 5257 at drivers/usb/gadget/udc/dummy_hcd.c:672
> dummy_free_request+0x153/0x170
> Kernel panic -
On Wed, 2016-12-14 at 12:05 +, Vadim Pasternak wrote:
> The patch contains several styling fixes:
> - Make names of hotplug devices shorter;
> - Change register offset assignment to defines;
> - Add defines for the all event masks;
> - Use PLATFORM_DEVID_NONE instead of -1;
Pushed to t
On Mon, Dec 26, 2016 at 09:45:50PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 26 Dec 2016 19:19:49 +0100
>
> The script "checkpatch.pl" pointed information out like the following.
>
> WARNING: Possible unnecessary 'out of memory' message
>
> Thus fix the affected source
Hi Markus,
On Mon, Dec 26, 2016 at 09:41:19PM +0100, SF Markus Elfring wrote:
> From: Markus Elfring
> Date: Mon, 26 Dec 2016 21:30:12 +0100
>
> Some update suggestions were taken into account
> from static source code analysis.
>
> Markus Elfring (8):
> v4l2-async: Use kmalloc_array() in v4l
On Fri, Dec 16, 2016 at 4:46 PM, Michał Kępień wrote:
> The "radio components indicator" LED present in Lifebook E734/E744/E754
> should be lit when any radio transmitter is enabled, so set its default
> trigger to rfkill-any.
>
Pushed to testing, thanks!
> Signed-off-by: Michał Kępień
> ---
>
On Fri, Dec 23, 2016 at 11:00 AM, Michał Kępień wrote:
> All LED-setting functions in fujitsu-laptop are currently assigned to
> the brightness_set callback, which is incorrect because they can sleep
> (due to their use of call_fext_func(), which in turn issues ACPI calls)
> and the documentation
On Wed, Dec 21, 2016 at 11:55 AM, Ladislav Michl wrote:
> HP ZBook 17 laptop needs a non-standard mapping (xy_swap_yz_inverted).
>
Pushed to testing with fixed Subject (should be "platform/x86: ...").
Thanks.
> Signed-off-by: Ladislav Michl
> ---
> Test done on patched driver; reading /sys/dev
On Thu, Nov 3, 2016 at 2:18 AM, Lee, Chun-Yi wrote:
> The accelerometer event relies on on the ACERWMID_EVENT_GUID notify.
> So, this patch changes the codes to setup accelerometer input device
> when detected ACERWMID_EVENT_GUID. It avoids that the accel input
> device created on every acer machi
From: "Kweh, Hock Leong"
Fixing the gmac4 mdio write access to use MII_GMAC4_WRITE only instead of
OR together with MII_WRITE.
Signed-off-by: Kweh, Hock Leong
---
drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/drivers
Às 8:07 PM de 12/27/2016, Kweh, Hock Leong escreveu:
> From: "Kweh, Hock Leong"
>
> Fixing the gmac4 mdio write access to use MII_GMAC4_WRITE only instead of
> OR together with MII_WRITE.
>
> Signed-off-by: Kweh, Hock Leong
> ---
> drivers/net/ethernet/stmicro/stmmac/stmmac_mdio.c |4 +++-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
I was just to fast mentioning that my new 4.9 compile did well. Just
after I wrote the mail, I got the same issue again. Now being back to
4.7.
OOM:
[34629.315415] Unable to lock GPU to purge memory.
[34629.315542] wicd invoked oom-killer:
gf
Hi,
On 27 December 2016 at 19:11, Felipe Balbi wrote:
>
> Hi,
>
> Baolin Wang writes:
>> Hi,
>>
>> On 27 December 2016 at 18:52, Janusz Dziedzic
>> wrote:
>>> 2016-12-26 9:01 GMT+01:00 Baolin Wang :
On some platfroms(like x86 platform), when one core is running the USB
gadget
i
On Tue 27-12-16 12:48:24, Klaus Ethgen wrote:
[...]
> By the way, I find the following two messages often. Maybe they are
> unrelated, maybe not.
>[31633.189121] Purging GPU memory, 144 pages freed, 5692 pages still
> pinned.
>[31638.530025] Unable to lock GPU to purge memory.
I do not th
Since the new parameter being added is going to be a bool this patch
changes the shared flag from int to bool to match the new parameter.
Signed-off-by: Ramiro Oliveira
---
drivers/reset/core.c | 8
include/linux/reset.h | 32
2 files changed, 20 inser
v2:
- Make some comments more explicit
- Add optional flag to reduce code duplication
- Change shared flag from int to bool to match optional flag
Up until now optional functions in the reset API were similar to the non
optional.
This patch corrects that, while maintaining compatibility with
The optional functions weren't really optional so this patch makes them
really optional.
Signed-off-by: Ramiro Oliveira
---
drivers/reset/core.c | 35 +--
include/linux/reset.h | 45 ++---
2 files changed, 55 insertions(+),
On Thu, Dec 8, 2016 at 3:35 PM, Arvind Yadav wrote:
> In functions pxa2xx_build_functions, the memory allocated for
> 'functions' is live within the function only. After the
> allocation it is immediately freed with devm_kfree. There is
> no need to allocate memory for 'functions' with devm funct
Dell platform team told us that some (DMI whitelisted) Dell Latitude
machines have ST microelectronics accelerometer at i2c address 0x29. That
i2c address is not specified in DMI or ACPI, so runtime detection without
whitelist which is below is not possible.
Presence of that ST microelectronics ac
Dear,
My name is Mrs. Elizabeth murphy I am 63 years old, I am a dying woman who have
decided to donate what I have to you/churches/ mosque/ motherless babies/less
privileged/widows.I was diagnosed for cancer for about 2 years ago. I have been
touched by God to donate from what I have inherited
Hi!
Machine is plain Intel desktop.
Even power light does not turn on. Fun. If I force power off by
holding power button down, power light stays off during the next
boot. Interesting. I guess EC is confused.
Thinkpad X60 with similar kernel config works.
On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson
wrote:
> This change is inspired from the pinctrl-single architecture.
>
> The problem with current implementation is that it isn't possible
> to add/remove functions and/or groups dynamically. The radix tree
> offers an easy way to do so. The intent is
On Tue, Dec 27, 2016 at 11:05 AM, Linus Walleij
wrote:
> On Fri, Dec 2, 2016 at 5:35 PM, Gary Bisson
> wrote:
>
>> This change is inspired from the pinctrl-single architecture.
>>
>> The problem with current implementation is that it isn't possible
>> to add/remove functions and/or groups dynamic
Hi Herbert,
Thanks for your response
>Hi Jan:
On Mon, Dec 12, 2016 at 04:04:36PM +0100, Jan Glauber wrote:
> >
> >this series adds support for hardware accelerated compression & decompression
> >as found on ThunderX (arm64) SOCs. I've been reviewing this driver internally
> >for some time and w
Hi,
On Friday, December 23, 2016 04:26:27 PM Pankaj Dubey wrote:
> From: Niyas Ahmed S T
>
> Currently Exynos PCIe driver is only supported for Exynos5440 SoC.
> This patch does refactoring of Exynos PCIe driver to extend support
> for other Exynos SoC.
>
> Following are the main changes done
On Tuesday 27 December 2016 14:43:49 Wolfram Sang wrote:
> > Dell platform team told us that some (DMI whitelisted) Dell
> > Latitude machines have ST microelectronics accelerometer at i2c
> > address 0x29. That
> > i2c address is not specified in DMI or ACPI, so runtime detection
> > without
> > w
Dell platform team told us that some (DMI whitelisted) Dell Latitude
machines have ST microelectronics accelerometer at i2c address 0x29.
That
i2c address is not specified in DMI or ACPI, so runtime detection
without
whitelist which is below is not possible.
I'd think this should rather live
On Fri, Oct 07, 2016 at 04:52:48PM +0200, Peter Zijlstra wrote:
> Implement lock handoff to avoid lock starvation.
>
> Lock starvation is possible because mutex_lock() allows lock stealing,
> where a running (or optimistic spinning) task beats the woken waiter
> to the acquire.
>
> Lock stealing
Hello,
The following program triggers use-after-free in complete_emulated_mmio:
https://gist.githubusercontent.com/dvyukov/79c7ee10f568b0d5c33788534bb6edc9/raw/2c2d4ce0fe86398ed81e65281e8c215c7c3632fb/gistfile1.txt
BUG: KASAN: use-after-free in complete_emulated_mmio+0x8dd/0xb70
arch/x86/kvm/x86.
Hello,
This patch adds support for the Omnivision OV5647 sensor.
At the moment it only supports 640x480 in Raw 8.
This is the seventh version of the OV5647 camera driver patchset.
v7:
- Remove "0x" and leading 0 from DT documentation examples
v6:
- Add example to DT documentation
- Remove d
Create device tree bindings documentation.
Signed-off-by: Ramiro Oliveira
---
.../devicetree/bindings/media/i2c/ov5647.txt | 35 ++
1 file changed, 35 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt
diff --git a/Documentation/de
Modes supported:
- 640x480 RAW 8
Signed-off-by: Ramiro Oliveira
---
MAINTAINERS| 7 +
drivers/media/i2c/Kconfig | 12 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/ov5647.c | 718 +
4 files changed, 738 insertions(+)
cre
Sample size of 24 bits use in reality 32 bits for storage. We
can safelly enable this sample size and treat the data as
32 bits.
Tested in a x86_64 platform and in ARC AXS101 SDP platform.
Signed-off-by: Jose Abreu
Cc: Carlos Palminha
Cc: Liam Girdwood
Cc: Mark Brown
Cc: Jaroslav Kysela
Cc:
Up until now PIO mode offered only playback support. With
this patch we add support for record mode. The PCM was
refactored so that we could reuse the existing infrastructure
without many changes.
We have support for 16 and 32 bits of sample size using
only 2 channels.
Tested in a x86_64 platform
On 12/27/2016 10:58 AM, Herbert Xu wrote:
On Mon, Dec 26, 2016 at 10:08:48AM -0800, Andy Lutomirski wrote:
According to Daniel, the networking folks want to let embedded systems
include BPF without requiring the crypto core.
Last I checked the IPv4 stack depended on the crypto API so this
sou
Hello,
This patch set extends a lock-less NMI per-cpu buffers idea to
handle recursive printk() calls. The basic mechanism is pretty much the
same -- at the beginning of a deadlock-prone section we switch to lock-less
printk callback, and return back to a default printk implementation at t
This patch extends the idea of NMI per-cpu buffers to regions
that may cause recursive printk() calls and possible deadlocks.
Namely, printk() can't handle printk calls from schedule code
or printk() calls from lock debugging code (spin_dump() for instance);
because those may be called with `sem->l
Always use printk_deferred() in printk_safe_flush_line().
Flushing can be done from NMI or printk_safe contexts (when
we are in panic), so we can't call console drivers, yet still
want to store the messages in the logbuf buffer. Therefore we
use a deferred printk version.
Signed-off-by: Sergey Sen
vprintk(), just like printk(), better be using per-cpu printk_func
instead of direct vprintk_emit() call. Just in case if vprintk()
will ever be called from NMI, or from any other context that can
deadlock in printk().
Signed-off-by: Sergey Senozhatsky
Reviewed-by: Steven Rostedt
Reviewed-by: Pe
Use printk_safe per-CPU buffers in printk recursion-prone blocks:
-- around logbuf_lock protected sections in vprintk_emit() and
console_unlock()
-- around down_trylock_console_sem() and up_console_sem()
Note that this solution addresses deadlocks caused by printk()
recursive calls only. That i
1 - 100 of 357 matches
Mail list logo
