> On 2017年9月6日, at 上午11:14, Alexei Starovoitov wrote:
>
> On 9/4/17 1:36 AM, Haishuang Yan wrote:
>> In collect_md mode, if the tun dev is down, it still can call
>> __ip6_tnl_rcv to receive on packets, and the rx statistics increase
>> improperly.
>>
>> Fixes: 8d79266bc48c ("ip6_tunnel: add col
From: Markus Elfring
Date: Wed, 6 Sep 2017 08:18:30 +0200
Add jump targets so that a bit of exception handling can be better reused
at the end of these functions.
This issue was detected by using the Coccinelle software.
Signed-off-by: Markus Elfring
---
v2:
* An approach to make a few checks
On 06.09.2017 06:47, Thang Q. Nguyen wrote:
On Tue, Sep 5, 2017 at 6:14 PM, Mathias Nyman mailto:mathias.ny...@linux.intel.com>> wrote:
On 24.08.2017 05 :53, Thang Q. Nguyen wrote:
On Sat, Aug 19, 2017 at 10:43 AM, Thang Q. Nguyen mailto:tqngu...@apm.com>> wrote:
From
This patch adds the binding documentation for Spreadtrum ADI
controller device.
Signed-off-by: Baolin Wang
---
.../devicetree/bindings/spi/spi-sprd-adi.txt | 44
1 file changed, 44 insertions(+)
create mode 100644 Documentation/devicetree/bindings/spi/spi-sprd-adi.t
This patch adds ADI driver based on SPI framework for
Spreadtrum SC9860 platform.
Signed-off-by: Baolin Wang
---
drivers/spi/Kconfig|6 +
drivers/spi/Makefile |1 +
drivers/spi/spi-sprd-adi.c | 431
3 files changed, 438 insertio
On Wed, Sep 06, 2017 at 12:13:38PM +0800, Yu Chen wrote:
> I agree, the driver could be rewritten, but it might take some time, so
> meanwhile I'm looking at also other possible optimization.
Which driver are we talking about anyway? Let's start looking at it
and fix the issue there.
On 06/09/17 05:44, Shawn Lin wrote:
> + Seraphime
>
> On 2017/9/6 3:47, Pavel Machek wrote:
>> Hi!
>>
>> I tried to write to the MMC card; process hung and I got this in the
>> dmesg.
>
>
> A similar report for 4.13 cycle was here:
>
> https://lkml.org/lkml/2017/8/10/824
>
> Seems 4.13-rc4 was
On Wed, Sep 06, 2017 at 08:58:26AM +0800, Yang, Wenyou wrote:
> Hi,
>
>
> On 2017/9/5 4:04, SF Markus Elfring wrote:
> > From: Markus Elfring
> > Date: Mon, 4 Sep 2017 21:44:55 +0200
> >
> > A few update suggestions were taken into account
> > from static source code analysis.
> Thank you for y
Hi Thomas,
On Wednesday, 31 May 2017 02:58:33 PDT Thomas Gleixner wrote:
> Shared interrupts do not go well with disabling auto enable:
>
> 1) The sharing interrupt might request it while it's still disabled and
>then wait for interrupts forever.
>
> 2) The interrupt might have been requeste
Hi all,
Please do not add any v4.15 related material to your linux-next
included branches until after v4.14-rc1 has been released.
Changes since 20170905:
The devicetree tree gained conflicts against Linus' and the sound trees.
The akpm-current tree lost its build failure.
Non-merge co
Code can be optimized more by making single exit point of function and calling
mutex_unlock at the end
Signed-off-by: Pushkar Jambhlekar
---
drivers/iommu/tegra-smmu.c | 8 +---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/drivers/iommu/tegra-smmu.c b/drivers/iommu/tegra-sm
On Wed, Sep 06, 2017 at 11:02:35AM +0800, Dennis Yang wrote:
> In release_stripe_plug(), if a stripe_head has its STRIPE_ON_UNPLUG_LIST
> set, it indicates that this stripe_head is already in the raid5_plug_cb
> list and release_stripe() would be called instead to drop a reference
> count. Otherwis
This patch adds the documentation for Spreadtrum watchdog driver.
Signed-off-by: Eric Long
---
.../devicetree/bindings/watchdog/sprd-wdt.txt | 19 +++
1 file changed, 19 insertions(+)
create mode 100644 Documentation/devicetree/bindings/watchdog/sprd-wdt.txt
diff --git
This patch adds the watchdog driver for Spreadtrum SC9860 platform.
Signed-off-by: Eric Long
---
drivers/watchdog/Kconfig| 8 +
drivers/watchdog/Makefile | 1 +
drivers/watchdog/sprd_wdt.c | 366
3 files changed, 375 insertions(+)
create mo
Fix brace style of if-else case
Signed-off-by: Pushkar Jambhlekar
---
drivers/staging/pi433/pi433_if.c | 162 +--
1 file changed, 54 insertions(+), 108 deletions(-)
diff --git a/drivers/staging/pi433/pi433_if.c b/drivers/staging/pi433/pi433_if.c
index 93c0168
Hi Baoquan,
At 09/06/2017 01:26 PM, Baoquan He wrote:
[...]
static void __init smp_cpu_index_default(void)
@@ -1335,19 +1295,20 @@ void __init native_smp_prepare_cpus(unsigned int
max_cpus)
Please also cleanup the passed in max_cpus since it's not used here any
more. And up to the caller:
On Tue, 2017-08-22 at 22:38 +0800, Joerg Roedel wrote:
> On Mon, Aug 21, 2017 at 07:00:13PM +0800, Yong Wu wrote:
> > Yong Wu (8):
> > dt-bindings: mediatek: Add binding for mt2712 IOMMU and SMI
> > iommu/mediatek: Move MTK_M4U_TO_LARB/PORT into mtk_iommu.c
> > iommu/mediatek: Add mt2712 IOMM
CC Catalin
On 2017/9/6 2:58, gengdongjiu wrote:
> when exit from guest, some host PSTATE bits may be lost, such as
> PSTATE.PAN or PSTATE.UAO. It is because host and hypervisor all run
> in the EL2, host PSTATE value cannot be saved and restored via
> SPSR_EL2. So if guest has changed the PSTATE,
Hi Lee,
On 9/5/2017 12:38 AM, Lee Jones wrote:
On Sat, 02 Sep 2017, sathyanarayanan.kuppusw...@linux.intel.com wrote:
From: Kuppuswamy Sathyanarayanan
Removed redundant IPC helper functions and refactored the driver to use
generic IPC device driver APIs.
This patch also cleans-up PMC IPC u
kernel/locking/rwsem.o: warning: objtool: downgrade_write()+0x22: call without
frame pointer save/setup
The warning means gcc 7.2.0 placed the __downgrade_write() inline asm (and
its call instruction) before the frame pointer setup in downgrade_write(),
which breaks frame pointer convention and c
Some warning were showed by objtool using gcc 7.2.0
kernel/locking/rwsem.o: warning: objtool: up_read()+0x11: call without frame
pointer save/setup
kernel/locking/rwsem.o: warning: objtool: up_write()+0x17: call without frame
pointer save/setup
kernel/locking/rwsem.o: warning: objtool: downgrade
kernel/locking/rwsem.o: warning: objtool: up_write()+0x17: call without frame
pointer save/setup
The warning means gcc 7.2.0 placed the __up_write() inline asm (and its
call instruction) before the frame pointer setup in up_write(),
which breaks frame pointer convention and can result in incorrec
kernel/locking/rwsem.o: warning: objtool: up_read()+0x11: call without frame
pointer save/setup
The warning means gcc 7.2.0 placed the __up_read() inline asm (and its
call instruction) before the frame pointer setup in up_read(),
which breaks frame pointer convention and can result in incorrect
s
On 09/06/17 at 12:25pm, Baoquan He wrote:
> On 08/28/17 at 11:20am, Dou Liyang wrote:
> > - /*
> > * Should not be necessary because the MP table should list the boot
> > * CPU too, but we do it for the sake of robustness anyway.
> > */
> > @@ -1254,29 +1237,6 @@ static int __init
On Wed, Sep 6, 2017 at 10:00 AM, Brendan Higgins
wrote:
> +++ b/Documentation/devicetree/bindings/arm/npcm/npcm.txt
> @@ -0,0 +1,6 @@
> +NPCM Platforms Device Tree Bindings
> +---
> +NPCM750 SoC
> +Required root node properties:
> + - compatible = "nuvoton,npc
I'm running e7d0c41ecc2e372a81741a30894f556afec24315 from Linus' tree
today, and I'm seeing abysmal scheduler performance. Running make -j4
ends up with all the tasks on CPU 3 most of the time (on my
4-logical-thread laptop). taskset -c 0 whatever puts whatever on CPU
0, but plain while true; do
ani
Acked-by: Niklas Cassel
---
Changes for v2:
- Done few changes as suggested by Niklas Cassel.
- Patch is rebased and built(ARCH=arm) on latest next-20170905.
---
arch/arm/boot/dts/artpec6.dtsi | 3 ---
1 file changed, 3 deletions(-)
diff --git a/arch/arm/boot/dts/artpec6.dtsi b/arch/ar
Hi,
I am hitting this bug when running the syzkaller fuzzer on kernel 4.13-rc7
Syzkaller hit 'UBSAN: Undefined behaviour in ./include/linux/log2.h:LINE' bug.
Guilty file: fs/pipe.c
Maintainers: []
UBSAN: Undefined behaviour in ./include/linux/log2.h:57:13
shift exponent 64 is too large for 64-
On Tue, Sep 5, 2017 at 9:30 PM, Shankara Pailoor wrote:
> Hi,
>
> I encountered this bug while fuzzing linux kernel 4.13-rc7 with syzkaller.
>
>
> UBSAN: Undefined behaviour in ./include/linux/time.h:233:27
> signed i
From: Joonsoo Kim
slub uses higher order allocation than it actually needs. In this case,
we don't want to do direct reclaim to make such a high order page since
it causes a big latency to the user. Instead, we would like to fallback
lower order allocation that it actually needs.
However, we als
From: Joonsoo Kim
High-order atomic allocation is difficult to succeed since we cannot
reclaim anything in this context. So, we reserves the pageblock for
this kind of request.
In slub, we try to allocate higher-order page more than it actually
needs in order to get the best performance. If this
From: Joonsoo Kim
Freepage on ZONE_HIGHMEM doesn't work for kernel memory so it's not that
important to reserve. When ZONE_MOVABLE is used, this problem would
theorectically cause to decrease usable memory for GFP_HIGHUSER_MOVABLE
allocation request which is mainly used for page cache and anon pa
Hi,
I encountered this bug while fuzzing linux kernel 4.13-rc7 with syzkaller.
UBSAN: Undefined behaviour in ./include/linux/time.h:233:27
signed integer overflow:
8391720337152500783 * 10 cannot be represent
On Wed, Sep 06, 2017 at 12:57:41AM +0200, Thomas Gleixner wrote:
> On Sun, 3 Sep 2017, Thomas Gleixner wrote:
>
> > On Fri, 1 Sep 2017, Chen Yu wrote:
> >
> > > This is the major logic to spread the vectors on different CPUs.
> > > The main idea is to choose the 'idlest' CPU which has assigned
>
On Sep 6 2017 01:18, Sebastian Andrzej Siewior wrote:
From: Thomas Gleixner
The tasklet is used to defer the execution of snd_pcm_period_elapsed() to
the softirq context. Using the CLOCK_MONOTONIC_SOFT base invokes the timer
callback in softirq context as well which renders the tasklet useless.
On 08/28/17 at 11:20am, Dou Liyang wrote:
> Calling native_smp_prepare_cpus() to prepare for SMP bootup, does
> some sanity checking, enables APIC mode and disables SMP feature.
>
> Now, APIC mode setup has been unified to apic_intr_mode_init(),
> some sanity checks are redundant and need to be cl
Hi David,
2017-09-06 11:09 GMT+09:00 David Daney :
> On 09/05/2017 06:40 PM, Masahiro Yamada wrote:
>>
>> IRQ_DOMAIN_HIERARCHY is not user-configurable, but supposed to be
>> selected by drivers that need IRQ domain hierarchy support.
>>
>> GPIO_THUNDERX is the only user of "depends on IRQ_DOMAIN
Hi Baoquan,
Thanks for your reply!
My answer is in below.
At 09/06/2017 08:55 AM, Baoquan He wrote:
Hi Liyang,
On 08/28/17 at 11:20am, Dou Liyang wrote:
Now, there are many switches in kernel which are used to determine
the final interrupt delivery mode, as shown below:
1) kconfig:
CONFI
Thanks for looking at this,
(please bear my slow response as I need to check related code
before replying.)
On Sun, Sep 03, 2017 at 08:17:04PM +0200, Thomas Gleixner wrote:
> On Fri, 1 Sep 2017, Chen Yu wrote:
>
> > This is the major logic to spread the vectors on different CPUs.
> > The main idea
From: zijun_hu
type bool is used to index three arrays in alloc_and_link_pwqs()
it doesn't look like conventional.
it is fixed by using type int to index the relevant arrays.
Signed-off-by: zijun_hu
---
kernel/workqueue.c | 9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --
Hi Jaegeuk,
Do we have time to test and stabilize this new feature before merge window?
Thanks,
On 2017/9/4 18:58, Chao Yu wrote:
> Now, in product, more and more features based on file encryption were
> introduced, their demand of xattr space is increasing, however, inline
> xattr has fixed-siz
It appears there is a regression for 32-bit kernels due to SME changes.
I bisected my particular problem (Xen PV guest) to
21729f81ce8ae76a6995681d40e16f7ce8075db4 but I also saw pmd_clear_bad()
errors on baremetal. This seems to be caused by sme_me_mask being an
unsigned long as opposed to ph
SVM AVIC hardware accelerates guest write to APIC_EOI register
(for edge-trigger interrupt), which means it does not trap to KVM.
So, only enable SVM AVIC only in split irqchip mode.
(e.g. launching qemu w/ option '-machine kernel_irqchip=split').
Suggested-by: Paolo Bonzini
Signed-off-by: Surav
Got the following report while fuzzing 4.9.47.
It seems that this bug has been reported by Dmitry Vyukov
[https://lkml.org/lkml/2017/1/27/828]
But I still can reproduce the bug on latest Ubuntu1604 (4.4.0-94-generic)
PoC:
https://gist.githubusercontent.com/dvyukov/3411518fa22baff19ae204cc4
Modify struct kvm_x86_ops.arch.apicv_active() to take struct kvm_vcpu
pointer as parameter in preparation to subsequent changes.
Signed-off-by: Suravee Suthikulpanit
---
arch/x86/include/asm/kvm_host.h | 2 +-
arch/x86/kvm/svm.c | 2 +-
arch/x86/kvm/vmx.c | 2 +-
arch/x
Preparing the base code for subsequent changes. This does not change
existing logic.
Signed-off-by: Suravee Suthikulpanit
---
arch/x86/kvm/svm.c | 28
1 file changed, 20 insertions(+), 8 deletions(-)
diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
index af256b7
Certain QEMU options fails to boot VM guest w/ SVM AVIC enabled
(e.g. modprobe kvm_amd avic=1). Investigation shows that this mainly
due to AVIC hardware does not trap into hypervisor when guest OS
writes to APIC_EOI register.
The boot hang is caused by missing timer interrupt when using in-kerne
Hi Alexei,
On Tue, Sep 5, 2017 at 8:24 PM, Alexei Starovoitov
wrote:
> On Sun, Sep 03, 2017 at 11:23:21AM -0700, Joel Fernandes wrote:
>> These patches fix issues seen when cross-compiling eBPF samples on arm64.
>> Compared to [1], I dropped the controversial inline-asm patch pending further
>> d
On Sun, Sep 03, 2017 at 11:23:21AM -0700, Joel Fernandes wrote:
> These patches fix issues seen when cross-compiling eBPF samples on arm64.
> Compared to [1], I dropped the controversial inline-asm patch pending further
> discussion on the right way to do it. However these patches are still a step
On 2017/9/6 11:10, Jaegeuk Kim wrote:
> On 09/06, Chao Yu wrote:
>> On 2017/9/6 5:06, Jaegeuk Kim wrote:
>>> This patch fixes bavail and bfree finally.
>>>
>>> longf_bfree;/* free blocks in fs */
>>> longf_bavail; /* free blocks avail to non-superuser */
>>>
>>> So, bfree represents a
On 2017/9/6 8:15, Jaegeuk Kim wrote:
> This patch renames functions regarding to buffer management via META_MAPPING
> used for encrypted blocks especially. We can actually use them in generic way.
Meta inode cache is more like bd_inode cache now. ;)
Reviewed-by: Chao Yu
Thanks,
>
> Signed-off
> On Fri, Sep 01, 2017 at 05:26:48PM +0800, Dennis Yang wrote:
> > >On Mon, Aug 28, 2017 at 08:01:59PM +0800, Dennis Yang wrote:
> > >> break_stripe_batch_list() did not preserve STRIPE_ON_UNPLUG_LIST which is
> > >> set when a stripe_head gets queued to the stripe_head list maintained by
> > >> ra
On 9/4/17 1:36 AM, Haishuang Yan wrote:
In collect_md mode, if the tun dev is down, it still can call
__ip6_tnl_rcv to receive on packets, and the rx statistics increase
improperly.
Fixes: 8d79266bc48c ("ip6_tunnel: add collect_md mode to IPv6 tunnels")
Cc: Alexei Starovoitov
Signed-off-by: Hai
On 2017/9/6 8:15, Jaegeuk Kim wrote:
> This patch replaces (f2fs_encrypted_inode() && S_ISREG()) with
> f2fs_encrypted_file(), which gives no functional change.
>
> Signed-off-by: Jaegeuk Kim
Reviewed-by: Chao Yu
Thanks,
> ---
> fs/f2fs/data.c | 10 +-
> fs/f2fs/f2fs.h | 5 +
On 09/06, Chao Yu wrote:
> On 2017/9/6 5:06, Jaegeuk Kim wrote:
> > This patch fixes bavail and bfree finally.
> >
> > longf_bfree;/* free blocks in fs */
> > longf_bavail; /* free blocks avail to non-superuser */
> >
> > So, bfree represents all the reserved blocks, while bavail do
On 2017/9/6 5:06, Jaegeuk Kim wrote:
> This patch fixes bavail and bfree finally.
>
> longf_bfree;/* free blocks in fs */
> longf_bavail; /* free blocks avail to non-superuser */
>
> So, bfree represents all the reserved blocks, while bavail does the space only
> visible to normal u
In release_stripe_plug(), if a stripe_head has its STRIPE_ON_UNPLUG_LIST
set, it indicates that this stripe_head is already in the raid5_plug_cb
list and release_stripe() would be called instead to drop a reference
count. Otherwise, the STRIPE_ON_UNPLUG_LIST bit would be set for this
stripe_head an
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/net/brcm,bgmac-nsp.txt
between commit:
ea6c3077678f ("dt-bindings: net: Remove duplicate NSP Ethernet MAC binding
document")
from Linus' tree and commit:
4da722ca19f3 ("dt-bindi
Hi all,
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/sound/rockchip,pdm.txt
between commit:
fce7358b54c6 ("ASoC: rockchip: separate pinctrl pins from each other")
from the sound tree and commit:
4da722ca19f3 ("dt-bindings: Remove "
Hi Rob,
Today's linux-next merge of the devicetree tree got a conflict in:
Documentation/devicetree/bindings/crypto/inside-secure-safexcel.txt
between commit:
6eb8844bf4be ("Documentation/bindings: crypto: remove the dma-mask property")
from Linus' tree and commit:
4da722ca19f3 ("dt-bin
Add devicetree bindings documentation file for rt5514 spi dsp codec.
Also update rt5514 i2c dt-binding's compatible to distinguish it from
rt5514 spi.
Signed-off-by: Jeffy Chen
---
Changes in v9:
Address comments from Brian.
.../devicetree/bindings/sound/rt5514-spi.txt | 29
Currently the rt5514 i2c driver and rt5514 spi driver are using the same
compatible string.
Add additional compatible strings to identify them for Gru boards.
Signed-off-by: Jeffy Chen
---
Changes in v9: None
arch/arm64/boot/dts/rockchip/rk3399-gru.dtsi | 4 ++--
1 file changed, 2 insertions(
On Tue, 2017-09-05 at 19:21 -0700, Sai Praneeth Prakhya wrote:
> > I get a similar crash on Qemu with linus's master branch and the V2
> > applied on top of it. Here are the details of my test environment:
> >
> > 1. I use the OVMF (EDK2) EFI firmware to launch the kernel:
> > edk2.git/ovmf-x64
>
+ Seraphime
On 2017/9/6 3:47, Pavel Machek wrote:
Hi!
I tried to write to the MMC card; process hung and I got this in the
dmesg.
A similar report for 4.13 cycle was here:
https://lkml.org/lkml/2017/8/10/824
Seems 4.13-rc4 was already broken for that but unfortuantely I didn't
reproduce th
Hi Brian,
On 09/06/2017 01:55 AM, Brian Norris wrote:
+This device supports SPI only.
>+
>+Required properties:
>+
>+- compatible : "realtek,rt5514".
You list one string here, but there's 2 in the example. The point of
this exercise was to document (not just in an Example) the strings
you're us
Add devicetree bindings documentation file for rt5514 spi dsp codec.
Also update rt5514 i2c dt-binding's compatible to distinguish it from
rt5514 spi.
Signed-off-by: Jeffy Chen
---
Changes in v9:
Address comments from Brian.
.../devicetree/bindings/sound/rt5514-spi.txt | 29
On Tue, Sep 5, 2017 at 7:54 AM, Steven Rostedt wrote:
> You can do what I did with trace_printk(). I have a buffer per context.
> Then you only need to use preempt_disable() to do the print. That is,
> trace_printk() has 4 buffers:
>
> 1. Normal context
> 2. softirq context
> 3. irq context
>
Hi Mathieu,
On Tue, 2017-09-05 at 23:29 +, Mathieu Desnoyers wrote:
> - On Sep 5, 2017, at 5:57 PM, Tom Zanussi tom.zanu...@linux.intel.com
> wrote:
>
> > The tracepoint infrastructure assumes statically-defined tracepoints
> > and uses static_keys for tracepoint enablement. In order to
> I get a similar crash on Qemu with linus's master branch and the V2
> applied on top of it. Here are the details of my test environment:
>
> 1. I use the OVMF (EDK2) EFI firmware to launch the kernel:
> edk2.git/ovmf-x64
>
> 2. I used linus's master branch (HEAD - commit:
> b1b6f83ac938d176742
Hi Jean-Philippe,
On 2017/9/5 20:54, Jean-Philippe Brucker wrote:
> On 31/08/17 09:20, Yisheng Xie wrote:
>> It is ILLEGAL to set STE.S1STALLD if STALL_MODEL is not 0b00, which
>> means we should not disable stall mode if stall/terminate mode is not
>> configuable.
>>
>> Meanwhile, it is also ILLE
On (09/05/17 10:54), Steven Rostedt wrote:
> On Mon, 4 Sep 2017 14:22:46 +0900
> Sergey Senozhatsky wrote:
>
> > like I said in another email, printk-safe buffer
> > is per-CPU and is also used for actual printk-safe, hence it must be
> > used with local IRQs disabled when we "borrow" the buffer
Hi, I find if I use a defined stack size to create a child thread,
then the max stack size from /proc/pid/task/child pid/limits still
shows "Max stack size8388608", it doesn't update to
the user defined size, is it a problem?
Here is the test code:
...
p
On 9/5/17 5:35 PM, Ross Zwisler wrote:
> The original intent of this series was to add a per-inode DAX flag to ext4
> so that it would be consistent with XFS. In my travels I found and fixed
> several related issues in both ext4 and XFS.
Hi Ross -
hch had a lot of reasons to nuke the dax flag fr
On Wed, Sep 06, 2017 at 09:25:36AM +0800, Bob Liu wrote:
> On 2017/9/6 2:54, Ross Zwisler wrote:
> > On Mon, Sep 04, 2017 at 10:38:27PM -0400, Jerome Glisse wrote:
> >> On Tue, Sep 05, 2017 at 09:13:24AM +0800, Bob Liu wrote:
> >>> On 2017/9/4 23:51, Jerome Glisse wrote:
> On Mon, Sep 04, 2017
On 09/05/2017 06:40 PM, Masahiro Yamada wrote:
IRQ_DOMAIN_HIERARCHY is not user-configurable, but supposed to be
selected by drivers that need IRQ domain hierarchy support.
GPIO_THUNDERX is the only user of "depends on IRQ_DOMAIN_HIERARCHY".
This means, we can not enable GPIO_THUNDERX unless oth
73233.doc
Description: MS-Word document
IRQ_DOMAIN_HIERARCHY is not user-configurable, but supposed to be
selected by drivers that need IRQ domain hierarchy support.
GPIO_THUNDERX is the only user of "depends on IRQ_DOMAIN_HIERARCHY".
This means, we can not enable GPIO_THUNDERX unless other drivers
select IRQ_DOMAIN_HIERARCHY elsewhere.
On Wed, Sep 06, 2017 at 08:42:11AM +0800, Boqun Feng wrote:
> > OK. If the workqueue is only user of the weird lockdep annotations, then
> > it might be better to defer introducing the extra state until needed.
> >
> > But, the 'might' thing I introduced would be necessary if more users
> > want t
On 2017/9/6 2:54, Ross Zwisler wrote:
> On Mon, Sep 04, 2017 at 10:38:27PM -0400, Jerome Glisse wrote:
>> On Tue, Sep 05, 2017 at 09:13:24AM +0800, Bob Liu wrote:
>>> On 2017/9/4 23:51, Jerome Glisse wrote:
On Mon, Sep 04, 2017 at 11:09:14AM +0800, Bob Liu wrote:
> On 2017/8/17 8:05, Jérôm
On 09/05/2017 02:38 PM, Mickaël Salaün wrote:
>
>
> On 28/08/2017 18:42, Shuah Khan wrote:
>> On 08/06/2017 05:23 PM, Mickaël Salaün wrote:
>>> When a test process is not able to write to TH_LOG_STREAM, this step
>>> mechanism enable to print the assert number which triggered the failure.
>>> Thi
On 2017/8/31 16:20, Yisheng Xie wrote:
Jean-Philippe has post a patchset for Adding PCIe SVM support to ARM SMMUv3:
https://www.spinics.net/lists/arm-kernel/msg565155.html
But for some platform devices(aka on-chip integrated devices), there is also
SVM requirement, which works based on the SMMU
Hi Jean-Philippe,
On 2017/9/6 8:51, Bob Liu wrote:
> On 2017/9/5 20:53, Jean-Philippe Brucker wrote:
>> On 31/08/17 09:20, Yisheng Xie wrote:
>>> From: Jean-Philippe Brucker
>>>
>>> Platform device can realise SVM function by using the stall mode. That
>>> is to say, when device access a memory v
Hi Jean-Philippe,
On 2017/9/5 20:56, Jean-Philippe Brucker wrote:
> On 31/08/17 09:20, Yisheng Xie wrote:
>> Jean-Philippe has post a patchset for Adding PCIe SVM support to ARM SMMUv3:
>> https://www.spinics.net/lists/arm-kernel/msg565155.html
>>
>> But for some platform devices(aka on-chip integ
Hi Shaohua,
On 17/9/6 05:02, Shaohua Li wrote:
> On Thu, Aug 31, 2017 at 09:24:23AM +0200, Paolo VALENTE wrote:
>>
>>> Il giorno 15 gen 2017, alle ore 04:42, Shaohua Li ha scritto:
>>>
>>> Hi,
>>>
>>> cgroup still lacks a good iocontroller. CFQ works well for hard disk, but
>>> not
>>> much for
On 09/05/2017 08:24 AM, Alan Cox wrote:
>>> anymore. But I'm already _running_ this program. If I could fork() I
>>> could already get a second copy of the sucker and call main() again
>>> myself if necessary, but I can't, so...
>
> You can - ptrace 8)
Oh I can call clone() with various flags and
Add specific dais name when components are registered. Component and dai
name will follow their parent dev name, if the name isn't described. In
case of this driver, each dais will have same name like '1144.i2s0' by
fmt_single_name function.
The problem having same name is that TM2 machine dr
Add specific cpu_dai_name to dai_link because samsung i2s driver registers
two dais and components. Selecting one of them clearly is needed more
information like cpu_dai_name, of_node. The reason why the dai_links have
to use 'samsung-i2s' for cpu_dai is that 'samsung-i2s-sec' doesn't have a
captur
Hello,
This patchset makes capture functionality working on TM2.
devm_gpiod_get is called with GPIOF_OUT_INIT_LOW but the function doesn't
allow the parameters. Unluckily, GPIOF_OUT_INIT_LOW is same value as
GPIOD_ASIS and gpio direction isn't set properly.
Muted stream comes up when I try recording some sounds on TM2. mic-bias
gpiod state can't be changed beca
On 2017/9/5 20:56, Jean-Philippe Brucker wrote:
> On 31/08/17 09:20, Yisheng Xie wrote:
>> Jean-Philippe has post a patchset for Adding PCIe SVM support to ARM SMMUv3:
>> https://www.spinics.net/lists/arm-kernel/msg565155.html
>>
>> But for some platform devices(aka on-chip integrated devices), the
Hi,
On 2017/9/5 4:04, SF Markus Elfring wrote:
From: Markus Elfring
Date: Mon, 4 Sep 2017 21:44:55 +0200
A few update suggestions were taken into account
from static source code analysis.
Thank you for your patches.
You can add my Acked-by for the patch series.
Acked-by: Wenyou Yang
Ma
Hi Liyang,
On 08/28/17 at 11:20am, Dou Liyang wrote:
> Now, there are many switches in kernel which are used to determine
> the final interrupt delivery mode, as shown below:
>
> 1) kconfig:
>CONFIG_X86_64; CONFIG_X86_LOCAL_APIC; CONFIG_x86_IO_APIC
> 2) kernel option: disable_apic; skip_ioapi
On 2017/9/5 20:53, Jean-Philippe Brucker wrote:
> On 31/08/17 09:20, Yisheng Xie wrote:
>> From: Jean-Philippe Brucker
>>
>> Platform device can realise SVM function by using the stall mode. That
>> is to say, when device access a memory via iova which is not populated,
>> it will stalled and when
On Tue, Sep 05, 2017 at 03:46:43PM +0200, Peter Zijlstra wrote:
> On Tue, Sep 05, 2017 at 07:58:38PM +0900, Byungchul Park wrote:
> > On Tue, Sep 05, 2017 at 07:31:44PM +0900, Byungchul Park wrote:
> > > Recursive-read and the hint I proposed(a.k.a. might) should be used for
> > > their different s
With the exception of one comment, which I have responded to
below, I have addressed your comments in my new version of
this patch: https://patchwork.kernel.org/patch/9914153/
On Mon, Sep 4, 2017 at 7:47 PM, Florian Fainelli wrote:
...
>> +
>> +ENTRY(v7_invalidate_l1_npcmX50)
>> + mov r0,
On Wed, Sep 06, 2017 at 08:52:35AM +0900, Byungchul Park wrote:
> On Tue, Sep 05, 2017 at 03:46:43PM +0200, Peter Zijlstra wrote:
> > On Tue, Sep 05, 2017 at 07:58:38PM +0900, Byungchul Park wrote:
> > > On Tue, Sep 05, 2017 at 07:31:44PM +0900, Byungchul Park wrote:
> > > > Recursive-read and the
Adds basic support for the Nuvoton NPCM750 BMC.
Signed-off-by: Brendan Higgins
---
arch/arm/Kconfig | 2 +
arch/arm/Makefile| 1 +
arch/arm/mach-npcm/Kconfig | 48
arch/arm/mach-npcm/Makefile | 3 ++
arch/arm/mach-npcm/headsmp.S | 17 +++
Add a common device tree for all Nuvoton NPCM750 BMCs and a board
specific device tree for the NPCM750 (Poleg) evaluation board.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
Tested-by: Tomer Maimon
Tested-by: Avi Fishman
---
.../arm/cpu-enable-method/nuvo
Addressed comments from:
- Florian: https://www.spinics.net/lists/arm-kernel/msg604948.html
Changes since previous update:
- Substanitally simplified the SMP code for NPCM750.
- No changes to device tree or MAINTAINERS since v2
Changes have been tested on the NPCM750 evaluation board.
Add maintainers and reviewers for the Nuvoton NPCM architecture.
Signed-off-by: Brendan Higgins
Reviewed-by: Tomer Maimon
Reviewed-by: Avi Fishman
---
MAINTAINERS | 13 +
1 file changed, 13 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 44cb004c765d..67064bf11904 10064
1 - 100 of 819 matches
Mail list logo
