[PATCH] radix-tree: optimization for radix_tree_init_maxnodes

if i == 0, height_to_maxnodes[i] = 0, if i >= 1, height_to_maxnodes[i] = height_to_maxnodes[i-1] + __maxindex(i-1) + 1. so delete height_to_maxindex and optimize the calculation of height_to_maxnodes array. Signed-off-by: Wang Long --- lib/radix-tree.c | 13

[PATCH] radix-tree: optimization for radix_tree_init_maxnodes

if i == 0, height_to_maxnodes[i] = 0, if i >= 1, height_to_maxnodes[i] = height_to_maxnodes[i-1] + __maxindex(i-1) + 1. so delete height_to_maxindex and optimize the calculation of height_to_maxnodes array. Signed-off-by: Wang Long --- lib/radix-tree.c | 13

Re: WARNING: kernel stack frame pointer has bad value (2)

syzbot has found a reproducer for the following crash on: HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern.. git tree: bpf console output: https://syzkaller.appspot.com/x/log.txt?x=14800f0a40 kernel config:

Re: WARNING: kernel stack frame pointer has bad value (2)

syzbot has found a reproducer for the following crash on: HEAD commit:28619527b8a7 Merge git://git.kernel.org/pub/scm/linux/kern.. git tree: bpf console output: https://syzkaller.appspot.com/x/log.txt?x=14800f0a40 kernel config:

[GIT pull] x86 fixes for 4.19

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus A set of fixes for x86: - Prevent multiplication result truncation on 32bit. Introduced with the early timestamp reworrk. - Ensure

[GIT pull] x86 fixes for 4.19

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus A set of fixes for x86: - Prevent multiplication result truncation on 32bit. Introduced with the early timestamp reworrk. - Ensure

[GIT pull] timekeeping fixes for 4.19

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus Two fixes for timekeeping: - Revert to the previous kthread based update, which is unfortunately required due to lock ordering issues.

[GIT pull] timekeeping fixes for 4.19

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus Two fixes for timekeeping: - Revert to the previous kthread based update, which is unfortunately required due to lock ordering issues.

[GIT pull] smp/hotplug fixes for 4.19

Linus, please pull the latest smp-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-urgent-for-linus Two fixes for the hotplug state machine code: - Move the misplaces smb() in the hotplug thread function to the proper place, otherwise a half

[GIT pull] smp/hotplug fixes for 4.19

Linus, please pull the latest smp-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git smp-urgent-for-linus Two fixes for the hotplug state machine code: - Move the misplaces smb() in the hotplug thread function to the proper place, otherwise a half

[GIT pull] irq fix for 4.19

Linus, please pull the latest irq-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus A single fix to prevent allocating excessive memory in the GIC/ITS driver. While the subject of the patch might suggest otherwise this is a real

[GIT pull] irq fix for 4.19

Linus, please pull the latest irq-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq-urgent-for-linus A single fix to prevent allocating excessive memory in the GIC/ITS driver. While the subject of the patch might suggest otherwise this is a real

[PATCH v2 3/3] mm: Add build time sanity chcek for struct page size

Size of struct page might be larger than 64 bytes if debug options enabled, or fields added for debugging intentionally. Yet an upper limit need be added at build time to trigger an alert in case the size is too big to boot up system, warning people to check if it's be done on purpose in advance.

[PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the initial size of the direct mapping region. This is right in the old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, 46bit, and only 4-level mode was supported. Later, in commit: b83ce5ee91471d ("x86/mm/64: Make

[PATCH v2 2/3] x86/mm/KASLR: Calculate the actual size of vmemmap region

Vmemmap region has different maximum size depending on paging mode. Now its size is hardcoded as 1TB in memory KASLR, this is not right for 5-level paging mode. It will cause overflow if vmemmap region is randomized to be adjacent to cpu_entry_area region and its actual size is bigger than 1TB.

[PATCH v2 3/3] mm: Add build time sanity chcek for struct page size

Size of struct page might be larger than 64 bytes if debug options enabled, or fields added for debugging intentionally. Yet an upper limit need be added at build time to trigger an alert in case the size is too big to boot up system, warning people to check if it's be done on purpose in advance.

[PATCH v2 1/3] x86/mm/KASLR: Fix the wrong calculation of kalsr region initial size

In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the initial size of the direct mapping region. This is right in the old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS, 46bit, and only 4-level mode was supported. Later, in commit: b83ce5ee91471d ("x86/mm/64: Make

[PATCH v2 2/3] x86/mm/KASLR: Calculate the actual size of vmemmap region

Vmemmap region has different maximum size depending on paging mode. Now its size is hardcoded as 1TB in memory KASLR, this is not right for 5-level paging mode. It will cause overflow if vmemmap region is randomized to be adjacent to cpu_entry_area region and its actual size is bigger than 1TB.

Re: INFO: rcu detected stall in vcpu_enter_guest

syzbot has found a reproducer for the following crash on: HEAD commit:f8f65382c98a Merge tag 'for-linus' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13af4cda40 kernel config:

Re: INFO: rcu detected stall in vcpu_enter_guest

syzbot has found a reproducer for the following crash on: HEAD commit:f8f65382c98a Merge tag 'for-linus' of git://git.kernel.org.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=13af4cda40 kernel config:

[GIT PULL] random fixes for 4.19-rc3

The following changes since commit 9a47249d444d344051c7c0e909fad0e88515a5c2: random: Make crng state queryable (2018-08-02 17:33:06 -0400) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/for_linus for you to fetch changes up to

[GIT PULL] random fixes for 4.19-rc3

The following changes since commit 9a47249d444d344051c7c0e909fad0e88515a5c2: random: Make crng state queryable (2018-08-02 17:33:06 -0400) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/for_linus for you to fetch changes up to

[PATCH] jump_label: Use static_key_linked() accessor

From: Borislav Petkov ... instead of open-coding it, in static_key_mod(). No functional changes. Signed-off-by: Borislav Petkov Cc: Ingo Molnar Cc: Josh Poimboeuf Cc: Peter Zijlstra Cc: "Steven Rostedt (VMware)" Cc: Jason Baron --- kernel/jump_label.c | 2 +- 1 file changed, 1

[PATCH] jump_label: Use static_key_linked() accessor

From: Borislav Petkov ... instead of open-coding it, in static_key_mod(). No functional changes. Signed-off-by: Borislav Petkov Cc: Ingo Molnar Cc: Josh Poimboeuf Cc: Peter Zijlstra Cc: "Steven Rostedt (VMware)" Cc: Jason Baron --- kernel/jump_label.c | 2 +- 1 file changed, 1

Re: [PATCH v7] Add udmabuf misc device

I am by no means a kernel expert, but Tomeu asked whether I could review this. Generally the patch looks okay, it applied (on top of 4.18.5-gentoo), and compiled without problems. However, running the experimental qemu branch I get a kernel bug: BUG: unable to handle kernel NULL pointer

Re: [PATCH v7] Add udmabuf misc device

I am by no means a kernel expert, but Tomeu asked whether I could review this. Generally the patch looks okay, it applied (on top of 4.18.5-gentoo), and compiled without problems. However, running the experimental qemu branch I get a kernel bug: BUG: unable to handle kernel NULL pointer

Re: [PATCH] arm64: defconfig: enable EFI_ARMSTUB_DTB_LOADER

On Wed, Sep 05, 2018 at 11:04:36AM -0700, Scott Branden wrote: > On 18-09-05 11:00 AM, Grant Likely wrote: > > On Wed, Sep 5, 2018 at 6:27 PM Scott Branden > > wrote: > > > On 18-09-05 02:40 AM, Ard Biesheuvel wrote: > > > > On 4 September 2018 at 19:19, Scott Branden > > > > wrote: > > > > >

Re: [PATCH] arm64: defconfig: enable EFI_ARMSTUB_DTB_LOADER

On Wed, Sep 05, 2018 at 11:04:36AM -0700, Scott Branden wrote: > On 18-09-05 11:00 AM, Grant Likely wrote: > > On Wed, Sep 5, 2018 at 6:27 PM Scott Branden > > wrote: > > > On 18-09-05 02:40 AM, Ard Biesheuvel wrote: > > > > On 4 September 2018 at 19:19, Scott Branden > > > > wrote: > > > > >

Re: [PATCH v2] HID: i2c-hid: Don't reset device upon system resume

Hi, On 06-09-18 04:55, Kai-Heng Feng wrote: Raydium touchscreen triggers interrupt storm after system-wide suspend: [ 179.085033] i2c_hid i2c-CUST:00: i2c_hid_get_input: incomplete report (58/65535) According to Raydium, Windows driver does not reset the device after system resume. The

Re: [PATCH v2] HID: i2c-hid: Don't reset device upon system resume

Hi, On 06-09-18 04:55, Kai-Heng Feng wrote: Raydium touchscreen triggers interrupt storm after system-wide suspend: [ 179.085033] i2c_hid i2c-CUST:00: i2c_hid_get_input: incomplete report (58/65535) According to Raydium, Windows driver does not reset the device after system resume. The

[PATCH v5 1/2] dt-bindings: leds: document Panasonic AN30259A bindings

Signed-off-by: Simon Shields Acked-by: Pavel Machek Reviewed-by: Rob Herring --- .../bindings/leds/leds-an30259a.txt | 43 +++ 1 file changed, 43 insertions(+) create mode 100644 Documentation/devicetree/bindings/leds/leds-an30259a.txt diff --git

[PATCH v5 1/2] dt-bindings: leds: document Panasonic AN30259A bindings

Signed-off-by: Simon Shields Acked-by: Pavel Machek Reviewed-by: Rob Herring --- .../bindings/leds/leds-an30259a.txt | 43 +++ 1 file changed, 43 insertions(+) create mode 100644 Documentation/devicetree/bindings/leds/leds-an30259a.txt diff --git

[PATCH v5 0/2] Panasonic AN30259A support

Hi, This patch series adds DT bindings (patch #1) and the corresponding driver (patch #2) for the Panasonic AN30259A 3-channel LED driver. AN30259A uses an internal clock for controlling brightness/on-off cycles, but also supports using an external PWM/clock input. This patch series only

[PATCH v5 2/2] leds: add Panasonic AN30259A support

AN30259A is a 3-channel LED driver which uses I2C. It supports timed operation via an internal PWM clock, and variable brightness. This driver offers support for basic hardware-based blinking and brightness control. The datasheet is freely available:

[PATCH v5 0/2] Panasonic AN30259A support

Hi, This patch series adds DT bindings (patch #1) and the corresponding driver (patch #2) for the Panasonic AN30259A 3-channel LED driver. AN30259A uses an internal clock for controlling brightness/on-off cycles, but also supports using an external PWM/clock input. This patch series only

[PATCH v5 2/2] leds: add Panasonic AN30259A support

AN30259A is a 3-channel LED driver which uses I2C. It supports timed operation via an internal PWM clock, and variable brightness. This driver offers support for basic hardware-based blinking and brightness control. The datasheet is freely available:

Re: [PATCH] kernel/sched/core.c: Avoid unused variable on non-SMP configs

On Sat, Sep 08, 2018 at 09:05:53PM +0200, Miguel Ojeda wrote: > On non-SMP configs, when only one of CONFIG_{PARAVIRT,IRQ_TIME}_ACCOUNTING > is defined, we are declaring a variable (irq_delta or steal) which > is not used: > > kernel/sched/core.c: In function ‘update_rq_clock_task’: >

Re: [PATCH] kernel/sched/core.c: Avoid unused variable on non-SMP configs

On Sat, Sep 08, 2018 at 09:05:53PM +0200, Miguel Ojeda wrote: > On non-SMP configs, when only one of CONFIG_{PARAVIRT,IRQ_TIME}_ACCOUNTING > is defined, we are declaring a variable (irq_delta or steal) which > is not used: > > kernel/sched/core.c: In function ‘update_rq_clock_task’: >

Linux 4.18.7

I'm announcing the release of the 4.18.7 kernel. All users of the 4.18 kernel series must upgrade. The updated 4.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.18.y and can be browsed at the normal kernel.org git web browser:

Linux 4.18.7

I'm announcing the release of the 4.18.7 kernel. All users of the 4.18 kernel series must upgrade. The updated 4.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.18.y and can be browsed at the normal kernel.org git web browser:

Re: [PATCH 4.4 34/47] userns: move user access out of the mutex

On Sun, Sep 09, 2018 at 11:16:33AM +0200, Greg KH wrote: > On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote: > > Greg, > > > > On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman > > wrote: > > > > > > 4.4-stable review patch. If anyone has any objections, please let me > > >

Re: [PATCH 4.4 34/47] userns: move user access out of the mutex

On Sun, Sep 09, 2018 at 11:16:33AM +0200, Greg KH wrote: > On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote: > > Greg, > > > > On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman > > wrote: > > > > > > 4.4-stable review patch. If anyone has any objections, please let me > > >

Re: [PATCH 3.18 00/29] 3.18.122-stable review

On Sat, Sep 08, 2018 at 02:12:54PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.122 release. > > There are 29 patches in this series, all will be posted as a response > > to this one. If anyone has

Re: [PATCH 3.18 00/29] 3.18.122-stable review

On Sat, Sep 08, 2018 at 02:12:54PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:10 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 3.18.122 release. > > There are 29 patches in this series, all will be posted as a response > > to this one. If anyone has

Re: [PATCH 4.4 00/47] 4.4.155-stable review

On Sun, Sep 09, 2018 at 10:22:27AM +0530, Naresh Kamboju wrote: > On 8 September 2018 at 02:39, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.4.155 release. > > There are 47 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.4 00/47] 4.4.155-stable review

On Sun, Sep 09, 2018 at 10:22:27AM +0530, Naresh Kamboju wrote: > On 8 September 2018 at 02:39, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.4.155 release. > > There are 47 patches in this series, all will be posted as a response > > to this one. If

Re: [PATCH 4.4 34/47] userns: move user access out of the mutex

On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote: > Greg, > > On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman > wrote: > > > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Jann Horn > > > > commit

Re: [PATCH 4.4 34/47] userns: move user access out of the mutex

On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote: > Greg, > > On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman > wrote: > > > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Jann Horn > > > > commit

Re: [PATCH 4.4 34/47] userns: move user access out of the mutex

On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote: > Greg, > > On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman > wrote: > > > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Jann Horn > > > > commit

Re: [PATCH 4.4 34/47] userns: move user access out of the mutex

On Sun, Sep 09, 2018 at 12:56:45AM -0300, Rafael David Tinoco wrote: > Greg, > > On Fri, Sep 7, 2018 at 6:41 PM Greg Kroah-Hartman > wrote: > > > > 4.4-stable review patch. If anyone has any objections, please let me know. > > > > -- > > > > From: Jann Horn > > > > commit

Re: [PATCH 4.4 00/47] 4.4.155-stable review

On Sat, Sep 08, 2018 at 02:13:48PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.155 release. > > There are 47 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.4 00/47] 4.4.155-stable review

On Sat, Sep 08, 2018 at 02:13:48PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.4.155 release. > > There are 47 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.9 00/63] 4.9.126-stable review

On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.126 release. > > There are 63 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.9 00/63] 4.9.126-stable review

On Sat, Sep 08, 2018 at 02:14:53PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:09 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.9.126 release. > > There are 63 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.14 00/89] 4.14.69-stable review

On Sat, Sep 08, 2018 at 02:16:02PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:08 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.69 release. > > There are 89 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.14 00/89] 4.14.69-stable review

On Sat, Sep 08, 2018 at 02:16:02PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:08 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.69 release. > > There are 89 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.18 000/145] 4.18.7-stable review

On Sat, Sep 08, 2018 at 02:16:40PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:07 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.7 release. > > There are 145 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH 4.18 000/145] 4.18.7-stable review

On Sat, Sep 08, 2018 at 02:16:40PM -0700, Guenter Roeck wrote: > On 09/07/2018 02:07 PM, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.18.7 release. > > There are 145 patches in this series, all will be posted as a response > > to this one. If anyone has any

Re: [PATCH] kallsyms: remove left-over Blackfin code

2018-09-04 9:42 GMT+09:00 Masahiro Yamada : > These symbols were added by commit 028f042613c3 ("kallsyms: support > kernel symbols in Blackfin on-chip memory") for Blackfin. > > The Blackfin support was removed by commit 4ba66a976072 ("arch: remove > blackfin port"). > > Signed-off-by: Masahiro

Re: [PATCH] kallsyms: remove left-over Blackfin code

2018-09-04 9:42 GMT+09:00 Masahiro Yamada : > These symbols were added by commit 028f042613c3 ("kallsyms: support > kernel symbols in Blackfin on-chip memory") for Blackfin. > > The Blackfin support was removed by commit 4ba66a976072 ("arch: remove > blackfin port"). > > Signed-off-by: Masahiro

[GIT PULL] Kbuild fixes for v4.19-rc3

Hi Linus, Please pull some Kbuild fixes. Thanks! The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3: Linux 4.19-rc1 (2018-08-26 14:11:59 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git

[GIT PULL] Kbuild fixes for v4.19-rc3

Hi Linus, Please pull some Kbuild fixes. Thanks! The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3: Linux 4.19-rc1 (2018-08-26 14:11:59 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/masahiroy/linux-kbuild.git

Re: [PATCH v23 3/4] arm64: dts: mt8173: Add GCE node

On Wed, 2018-08-15 at 09:48 +0800, houlong wei wrote: > On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote: > > This patch adds the device node of the GCE hardware for CMDQ module. > > [...] Hello Matthias, Sorry to disturb you. Are you availabe to review this patch and give your comment?

Re: [PATCH v23 3/4] arm64: dts: mt8173: Add GCE node

On Wed, 2018-08-15 at 09:48 +0800, houlong wei wrote: > On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote: > > This patch adds the device node of the GCE hardware for CMDQ module. > > [...] Hello Matthias, Sorry to disturb you. Are you availabe to review this patch and give your comment?

Re: [PATCH v2] modules_install: warn when missing System.map file

2018-09-07 8:37 GMT+09:00 Randy Dunlap : > From: Randy Dunlap > > If there is no System.map file for "make modules_install", > scripts/depmod.sh will silently exit with success, having done > nothing. Since this is an unexpected situation, change it to > report a Warning for the missing file.

Re: [PATCH v2] modules_install: warn when missing System.map file

2018-09-07 8:37 GMT+09:00 Randy Dunlap : > From: Randy Dunlap > > If there is no System.map file for "make modules_install", > scripts/depmod.sh will silently exit with success, having done > nothing. Since this is an unexpected situation, change it to > report a Warning for the missing file.

Re: [PATCH v23 4/4] soc: mediatek: Add Mediatek CMDQ helper

On Wed, 2018-08-15 at 09:46 +0800, houlong wei wrote: > On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote: > > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code. > >[...] Hello Matthias, Sorry to disturb you. Could you please review this patch and give your comment?

Re: [PATCH v23 4/4] soc: mediatek: Add Mediatek CMDQ helper

On Wed, 2018-08-15 at 09:46 +0800, houlong wei wrote: > On Wed, 2018-07-25 at 09:26 +0800, Houlong Wei wrote: > > Add Mediatek CMDQ helper to create CMDQ packet and assemble GCE op code. > >[...] Hello Matthias, Sorry to disturb you. Could you please review this patch and give your comment?

<    1   2   3