[PATCH v2 net-next 2/3] samples/bpf: add samples for more perf event types

From: Teng Qin This commit adds test code to attach BPF to HW_CACHE and RAW type events and updates clean-up logic to disable the perf events before closing pmu_fd. This commit also adds test code to read SOFTWARE, HW_CACHE, RAW and dynamic pmu events from BPF program using

[PATCH v2 net-next 2/3] samples/bpf: add samples for more perf event types

From: Teng Qin This commit adds test code to attach BPF to HW_CACHE and RAW type events and updates clean-up logic to disable the perf events before closing pmu_fd. This commit also adds test code to read SOFTWARE, HW_CACHE, RAW and dynamic pmu events from BPF program using

[PATCH v2 net-next 0/3] bpf: Add BPF support to all perf_event

v1->v2: address Peter's feedback. Refactor patch 1 to allow attaching bpf programs to all event types and reading counters from all of them as well patch 2 - more tests patch 3 - address Dave's feedback and document bpf_perf_event_read() and bpf_perf_event_output() properly Teng Qin (3): perf,

[PATCH v2 net-next 0/3] bpf: Add BPF support to all perf_event

v1->v2: address Peter's feedback. Refactor patch 1 to allow attaching bpf programs to all event types and reading counters from all of them as well patch 2 - more tests patch 3 - address Dave's feedback and document bpf_perf_event_read() and bpf_perf_event_output() properly Teng Qin (3): perf,

[PATCH v2 net-next 1/3] perf, bpf: Add BPF support to all perf_event types

From: Teng Qin Allow BPF program to attach to all perf_event types supported by the current bpf and perf code logic, including HW_CACHE, RAW, and dynamic pmu events. Also add support for reading these event counters using bpf_perf_event_read() helper. Signed-off-by: Teng Qin

[PATCH v2 net-next 3/3] bpf: update perf event helper functions documentation

From: Teng Qin This commit updates documentation of the bpf_perf_event_output and bpf_perf_event_read helpers to match their implementation. Signed-off-by: Teng Qin Signed-off-by: Alexei Starovoitov --- include/uapi/linux/bpf.h | 11

[PATCH v2 net-next 1/3] perf, bpf: Add BPF support to all perf_event types

From: Teng Qin Allow BPF program to attach to all perf_event types supported by the current bpf and perf code logic, including HW_CACHE, RAW, and dynamic pmu events. Also add support for reading these event counters using bpf_perf_event_read() helper. Signed-off-by: Teng Qin Signed-off-by:

[PATCH v2 net-next 3/3] bpf: update perf event helper functions documentation

From: Teng Qin This commit updates documentation of the bpf_perf_event_output and bpf_perf_event_read helpers to match their implementation. Signed-off-by: Teng Qin Signed-off-by: Alexei Starovoitov --- include/uapi/linux/bpf.h | 11 +++ tools/include/uapi/linux/bpf.h | 11

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

On May 24, 2017 4:17:39 AM PDT, "Andrey Jr. Melnikov" wrote: >In gmane.linux.kernel sean.w...@mediatek.com wrote: >> From: Sean Wang > >> MT7530 is a 7-ports Gigabit Ethernet Switch that could be found on >> Mediatek router platforms such as MT7623A

Re: [PATCH net-next v3 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch

On May 24, 2017 4:17:39 AM PDT, "Andrey Jr. Melnikov" wrote: >In gmane.linux.kernel sean.w...@mediatek.com wrote: >> From: Sean Wang > >> MT7530 is a 7-ports Gigabit Ethernet Switch that could be found on >> Mediatek router platforms such as MT7623A or MT7623N platform which >> includes 7-port

[PATCH] ARM: dts: rockchip:add sd card support

firefly reload board not support sd card yet. so support it. Signed-off-by: Eddie Cai --- arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi | 31 +++ 1 file changed, 31 insertions(+) diff --git a/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi

[PATCH] ARM: dts: rockchip:add sd card support

firefly reload board not support sd card yet. so support it. Signed-off-by: Eddie Cai --- arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi | 31 +++ 1 file changed, 31 insertions(+) diff --git a/arch/arm/boot/dts/rk3288-firefly-reload-core.dtsi

Re: [PATCH] drm/rockchip: Don't allow zero sized gem buffer

On Fri, May 26, 2017 at 10:30:09AM +0800, jeffy wrote: > Hi sean, > > On 05/25/2017 11:30 PM, Sean Paul wrote: > > On Tue, May 23, 2017 at 02:39:43PM +0800, Jeffy Chen wrote: > > > The system would crash when trying to alloc zero sized gem buffer: > > > [6.712435] Unable to handle kernel NULL

Re: [PATCH] drm/rockchip: Don't allow zero sized gem buffer

On Fri, May 26, 2017 at 10:30:09AM +0800, jeffy wrote: > Hi sean, > > On 05/25/2017 11:30 PM, Sean Paul wrote: > > On Tue, May 23, 2017 at 02:39:43PM +0800, Jeffy Chen wrote: > > > The system would crash when trying to alloc zero sized gem buffer: > > > [6.712435] Unable to handle kernel NULL

Re: [PATCH v2] PCI/msi: fix the pci_alloc_irq_vectors_affinity stub

Bjorn, can you take this regression fix and sent it to Linux before -rc3? I had hope we could get it into -rc2 but already missed that, and I haven't heard a comment since.. On Sat, May 20, 2017 at 06:59:54PM +0200, Christoph Hellwig wrote: > We need to return an error for any call that asks for

Re: [PATCH v2] PCI/msi: fix the pci_alloc_irq_vectors_affinity stub

Bjorn, can you take this regression fix and sent it to Linux before -rc3? I had hope we could get it into -rc2 but already missed that, and I haven't heard a comment since.. On Sat, May 20, 2017 at 06:59:54PM +0200, Christoph Hellwig wrote: > We need to return an error for any call that asks for

Re: [PATCH V2 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

Michael Bringmann writes: > Removing or adding memory via the PowerPC hotplug interface shows > anomalies in the association between memory and nodes. What anomalies? Please describe the actual problem you're seeing, with details, and why you think this is the correct

Re: [PATCH V2 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

Michael Bringmann writes: > Removing or adding memory via the PowerPC hotplug interface shows > anomalies in the association between memory and nodes. What anomalies? Please describe the actual problem you're seeing, with details, and why you think this is the correct fix. This is a revert of

[PATCH] iscsi-target: Fix initial login PDU asynchronous socket close OOPs

From: Nicholas Bellinger This patch fixes a OOPs originally introduced by: commit bb048357dad6d604520c91586334c9c230366a14 Author: Nicholas Bellinger Date: Thu Sep 5 14:54:04 2013 -0700 iscsi-target: Add sk->sk_state_change to cleanup

[PATCH] iscsi-target: Fix initial login PDU asynchronous socket close OOPs

From: Nicholas Bellinger This patch fixes a OOPs originally introduced by: commit bb048357dad6d604520c91586334c9c230366a14 Author: Nicholas Bellinger Date: Thu Sep 5 14:54:04 2013 -0700 iscsi-target: Add sk->sk_state_change to cleanup after TCP failure which would trigger a

[PATCH] Input: mousedev - fix implicit conversion warning

Clang warns: drivers/input/mousedev.c:653:63: error: implicit conversion from 'int' to 'signed char' changes value from 200 to -56 [-Wconstant-conversion] client->ps2[1] = 0x60; client->ps2[2] = 3; client->ps2[3] = 200; ~ ^~~ As far

[PATCH] Input: mousedev - fix implicit conversion warning

Clang warns: drivers/input/mousedev.c:653:63: error: implicit conversion from 'int' to 'signed char' changes value from 200 to -56 [-Wconstant-conversion] client->ps2[1] = 0x60; client->ps2[2] = 3; client->ps2[3] = 200; ~ ^~~ As far

Ich brauche deine Hilfe!

Lieber Freund, Ich bin Frau Dionisia Denis Perman aus Island, verheiratet mit Late Engineer Denis Perman {PhD}, der mit MULTINATIONAL OIL COMPANY EXXON AS A gearbeitet hat DRILLING RIG SUPPLIER in Kuwait seit 19 Jahren, bevor er auf der 22. August 2009. Wir waren seit vierundzwanzig Jahren

Ich brauche deine Hilfe!

Lieber Freund, Ich bin Frau Dionisia Denis Perman aus Island, verheiratet mit Late Engineer Denis Perman {PhD}, der mit MULTINATIONAL OIL COMPANY EXXON AS A gearbeitet hat DRILLING RIG SUPPLIER in Kuwait seit 19 Jahren, bevor er auf der 22. August 2009. Wir waren seit vierundzwanzig Jahren

[PATCH linux-next v3 1/1] spi: imx: dynamic burst length adjust for PIO mode

From: Jiada Wang previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch uses 32 bits transfer to simulate lower bits transfer, and adjusts burst

Re: [PATCH v5 31/32] x86: Add sysfs support for Secure Memory Encryption

On 05/26/2017 at 10:49 AM, Dave Young wrote: > Ccing Xunlei he is reading the patches see what need to be done for > kdump. There should still be several places to handle to make kdump work. > > On 05/18/17 at 07:01pm, Borislav Petkov wrote: >> On Tue, Apr 18, 2017 at 04:22:12PM -0500, Tom

[PATCH linux-next v3 1/1] spi: imx: dynamic burst length adjust for PIO mode

From: Jiada Wang previously burst length (BURST_LENGTH) is always set to equal to bits_per_word, causes a 10us gap between each word in transfer, which significantly affects performance. This patch uses 32 bits transfer to simulate lower bits transfer, and adjusts burst length runtimely to use

Re: [PATCH v5 31/32] x86: Add sysfs support for Secure Memory Encryption

On 05/26/2017 at 10:49 AM, Dave Young wrote: > Ccing Xunlei he is reading the patches see what need to be done for > kdump. There should still be several places to handle to make kdump work. > > On 05/18/17 at 07:01pm, Borislav Petkov wrote: >> On Tue, Apr 18, 2017 at 04:22:12PM -0500, Tom

Re: [RESEND: PATCH v4 2/4] remoteproc: qcom: refactor mss fw image loading sequence

Hi Bjorn, On 5/26/2017 12:33 AM, Bjorn Andersson wrote: > On Mon 22 May 06:26 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote: >> On 5/22/2017 4:07 PM, Sricharan R wrote: >>> Hi, >>> >>> On 5/22/2017 3:03 PM, Dwivedi, Avaneesh Kumar (avani) wrote: On 5/20/2017 8:25 AM, Sricharan R

Re: [RESEND: PATCH v4 2/4] remoteproc: qcom: refactor mss fw image loading sequence

Hi Bjorn, On 5/26/2017 12:33 AM, Bjorn Andersson wrote: > On Mon 22 May 06:26 PDT 2017, Dwivedi, Avaneesh Kumar (avani) wrote: >> On 5/22/2017 4:07 PM, Sricharan R wrote: >>> Hi, >>> >>> On 5/22/2017 3:03 PM, Dwivedi, Avaneesh Kumar (avani) wrote: On 5/20/2017 8:25 AM, Sricharan R

Re: [PATCH V4 00/17] thermal: cpu_cooling: improve interaction with cpufreq core

On 26-04-17, 11:41, Lukasz Luba wrote: > Hi Viresh, > > I went through the v4 code and it looks good to me. > Feel free to add for the v4 series > Reviewed-by: Lukasz Luba @Eduardo: You missed adding this to the patches. -- viresh

Re: [PATCH V4 00/17] thermal: cpu_cooling: improve interaction with cpufreq core

On 26-04-17, 11:41, Lukasz Luba wrote: > Hi Viresh, > > I went through the v4 code and it looks good to me. > Feel free to add for the v4 series > Reviewed-by: Lukasz Luba @Eduardo: You missed adding this to the patches. -- viresh

RE: [PATCH] pinctrl/amd: Use regular interrupt instead of chained

Hi Thomas, Thanks for the patch. However, we have received this issue from multiple people and different disro but it occurs only on Gigabyte hardware. With reference AM4 ryzen board we are not facing this issue. We are in discussion with gigabyte to check the BIOS part. Once we have clarity

RE: [PATCH] pinctrl/amd: Use regular interrupt instead of chained

Hi Thomas, Thanks for the patch. However, we have received this issue from multiple people and different disro but it occurs only on Gigabyte hardware. With reference AM4 ryzen board we are not facing this issue. We are in discussion with gigabyte to check the BIOS part. Once we have clarity

[PATCH] selftests/ftrace: Add a testcase for many kprobe events

Add a testcase to test kprobes via ftrace interface with many concurrent kprobe events. This tries to add many kprobe events (up to 256) on kernel functions. To avoid making ftrace-based kprobes (kprobes on fentry), it skips first N bytes (on x86 N=5, on ppc or arm N=4) of function entry. After

[PATCH] selftests/ftrace: Add a testcase for many kprobe events

Add a testcase to test kprobes via ftrace interface with many concurrent kprobe events. This tries to add many kprobe events (up to 256) on kernel functions. To avoid making ftrace-based kprobes (kprobes on fentry), it skips first N bytes (on x86 N=5, on ppc or arm N=4) of function entry. After

Re: [Patch v2] mm/vmscan: fix unsequenced modification and access warning

On Tue, May 16, 2017 at 10:27:46AM +0200, Michal Hocko wrote: > I guess it is worth reporting this to clang bugzilla. Could you take > care of that Nick? >From https://bugs.llvm.org//show_bug.cgi?id=33065#c5 it seems that this is indeed a sequence bug in the previous version of this code and not

Re: [Patch v2] mm/vmscan: fix unsequenced modification and access warning

On Tue, May 16, 2017 at 10:27:46AM +0200, Michal Hocko wrote: > I guess it is worth reporting this to clang bugzilla. Could you take > care of that Nick? >From https://bugs.llvm.org//show_bug.cgi?id=33065#c5 it seems that this is indeed a sequence bug in the previous version of this code and not

[git pull] drm fixes for v4.12-rc3

Hi Linus, Not a whole lot happening here, a set of amdgpu fixes and one core deadlock fix, and some misc drivers fixes. Dave. The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are available in the git repository at:

[git pull] drm fixes for v4.12-rc3

Hi Linus, Not a whole lot happening here, a set of amdgpu fixes and one core deadlock fix, and some misc drivers fixes. Dave. The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are available in the git repository at:

Re: [PATCH v5 06/10] drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback

On 05/25/2017 07:49 PM, Jose Abreu wrote: Now that we have a callback to check if bridge supports a given mode we can use it in Analogix bridge so that we restrict the number of probbed modes to the ones we can actually display. Also, there is no need to use mode_fixup() callback as

Re: [PATCH v5 06/10] drm/bridge: analogix-anx78xx: Use bridge->mode_valid() callback

On 05/25/2017 07:49 PM, Jose Abreu wrote: Now that we have a callback to check if bridge supports a given mode we can use it in Analogix bridge so that we restrict the number of probbed modes to the ones we can actually display. Also, there is no need to use mode_fixup() callback as

Re: [PATCHv1, RFC 0/8] Boot-time switching between 4- and 5-level paging

On Thu, May 25, 2017 at 05:40:16PM -0700, Andy Lutomirski wrote: > On Thu, May 25, 2017 at 4:24 PM, Linus Torvalds > wrote: > > On Thu, May 25, 2017 at 1:33 PM, Kirill A. Shutemov > > wrote: > >> Here' my first attempt to bring

Re: [PATCHv1, RFC 0/8] Boot-time switching between 4- and 5-level paging

On Thu, May 25, 2017 at 05:40:16PM -0700, Andy Lutomirski wrote: > On Thu, May 25, 2017 at 4:24 PM, Linus Torvalds > wrote: > > On Thu, May 25, 2017 at 1:33 PM, Kirill A. Shutemov > > wrote: > >> Here' my first attempt to bring boot-time between 4- and 5-level paging. > >> It looks not too

Re: [PATCH v5 02/10] drm: Introduce drm_bridge_mode_valid()

On 05/25/2017 07:49 PM, Jose Abreu wrote: Introduce a new helper function which calls mode_valid() callback for all bridges in an encoder chain. Reviewed-by: Archit Taneja Signed-off-by: Jose Abreu Reviewed-by: Daniel Vetter

Re: [PATCH v5 02/10] drm: Introduce drm_bridge_mode_valid()

On 05/25/2017 07:49 PM, Jose Abreu wrote: Introduce a new helper function which calls mode_valid() callback for all bridges in an encoder chain. Reviewed-by: Archit Taneja Signed-off-by: Jose Abreu Reviewed-by: Daniel Vetter Cc: Carlos Palminha Cc: Ville Syrjälä Cc: Dave Airlie Cc:

Re: [PATCH 5/5] drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC

On 05/26/2017 09:46 AM, Archit Taneja wrote: Hi, On 05/25/2017 05:04 AM, Kuninori Morimoto wrote: Hi Mark Cc: DRM maintainer ALSA SoC needs to know connected DAI ID for probing. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device

Re: [PATCH 5/5] drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC

On 05/26/2017 09:46 AM, Archit Taneja wrote: Hi, On 05/25/2017 05:04 AM, Kuninori Morimoto wrote: Hi Mark Cc: DRM maintainer ALSA SoC needs to know connected DAI ID for probing. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device

Re: [PATCH v5 28/32] x86/mm, kexec: Allow kexec to be used with SME

On 04/19/2017 at 05:21 AM, Tom Lendacky wrote: > Provide support so that kexec can be used to boot a kernel when SME is > enabled. > > Support is needed to allocate pages for kexec without encryption. This > is needed in order to be able to reboot in the kernel in the same manner > as originally

Re: [PATCH 5/5] drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC

Hi, On 05/25/2017 05:04 AM, Kuninori Morimoto wrote: Hi Mark Cc: DRM maintainer ALSA SoC needs to know connected DAI ID for probing. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device includes both Video/Sound, like HDMI. As far as I

Re: [PATCH v5 28/32] x86/mm, kexec: Allow kexec to be used with SME

On 04/19/2017 at 05:21 AM, Tom Lendacky wrote: > Provide support so that kexec can be used to boot a kernel when SME is > enabled. > > Support is needed to allocate pages for kexec without encryption. This > is needed in order to be able to reboot in the kernel in the same manner > as originally

Re: [PATCH 5/5] drm: dw-hdmi-i2s: add .get_dai_id callback for ALSA SoC

Hi, On 05/25/2017 05:04 AM, Kuninori Morimoto wrote: Hi Mark Cc: DRM maintainer ALSA SoC needs to know connected DAI ID for probing. It is not a big problem if device/driver was only for sound, but getting DAI ID will be difficult if device includes both Video/Sound, like HDMI. As far as I

Re: [PATCH] mm/zsmalloc: fix -Wunneeded-internal-declaration warning

On Wed, May 24, 2017 at 05:16:18PM +0900, Sergey Senozhatsky wrote: > On (05/23/17 22:38), Nick Desaulniers wrote: > > Fixes the following warning, found with Clang: > well, no objections from my side. MM seems to be getting more and > more `__maybe_unused' annotations because of clang. Indeed,

Re: [PATCH] mm/zsmalloc: fix -Wunneeded-internal-declaration warning

On Wed, May 24, 2017 at 05:16:18PM +0900, Sergey Senozhatsky wrote: > On (05/23/17 22:38), Nick Desaulniers wrote: > > Fixes the following warning, found with Clang: > well, no objections from my side. MM seems to be getting more and > more `__maybe_unused' annotations because of clang. Indeed,

Re: [PATCH] KVM: x86: dynamically allocate large struct in em_fxrstor

On Thu, May 25, 2017 at 04:07:08PM +0200, Paolo Bonzini wrote: > I think we should do the fixup backwards. > > That is: > > - first do get_fpu > > - if the fixup is necessary, i.e. ctxt->mode < X86EMUL_MODE_PROT64, do > fxsave into > > - then do segmented_read_std with the correct size, which

Re: [PATCH] KVM: x86: dynamically allocate large struct in em_fxrstor

On Thu, May 25, 2017 at 04:07:08PM +0200, Paolo Bonzini wrote: > I think we should do the fixup backwards. > > That is: > > - first do get_fpu > > - if the fixup is necessary, i.e. ctxt->mode < X86EMUL_MODE_PROT64, do > fxsave into > > - then do segmented_read_std with the correct size, which

Re: [PATCH net] sky2: Do not deadlock on sky2_hw_down

From: Stephen Hemminger Date: Thu, 25 May 2017 15:05:02 -0700 > Ok, the issue is that lockdep is being stupid and thinking that > seqcount's behave like locks. Well.. they do. That's why they have that annotation.

Re: [PATCH net] sky2: Do not deadlock on sky2_hw_down

From: Stephen Hemminger Date: Thu, 25 May 2017 15:05:02 -0700 > Ok, the issue is that lockdep is being stupid and thinking that > seqcount's behave like locks. Well.. they do. That's why they have that annotation.

Re: [linux-sunxi] [PATCH 1/3] arm64: allwinner: a64: Add initial Orangepi Win/WinPlus support

On Fri, May 26, 2017 at 6:30 AM, André Przywara wrote: > On 25/05/17 20:26, Jagan Teki wrote: >> From: Jagan Teki >> >> Orangepi Win/WinPlus is an open-source single-board computer >> using the Allwinner A64 SOC. >> >> A64 Orangepi Win/WinPlus

Re: [linux-sunxi] [PATCH 1/3] arm64: allwinner: a64: Add initial Orangepi Win/WinPlus support

On Fri, May 26, 2017 at 6:30 AM, André Przywara wrote: > On 25/05/17 20:26, Jagan Teki wrote: >> From: Jagan Teki >> >> Orangepi Win/WinPlus is an open-source single-board computer >> using the Allwinner A64 SOC. >> >> A64 Orangepi Win/WinPlus has >> - A64 Quad-core Cortex-A53 64bit >> -

Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

Reza Arbab writes: > On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote: >>The commit message for 3af229f2071f says: >> >>In practice, we never see a system with 256 NUMA nodes, and in fact, we >>do not support node hotplug on power in the first

Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

Reza Arbab writes: > On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote: >>The commit message for 3af229f2071f says: >> >>In practice, we never see a system with 256 NUMA nodes, and in fact, we >>do not support node hotplug on power in the first place, so the nodes >>

Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On Thu, 25 May 2017 10:10:11 -0500 Reza Arbab wrote: > On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote: > >The commit message for 3af229f2071f says: > > > >In practice, we never see a system with 256 NUMA nodes, and in fact, we > >do not support

Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On Thu, 25 May 2017 10:10:11 -0500 Reza Arbab wrote: > On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote: > >The commit message for 3af229f2071f says: > > > >In practice, we never see a system with 256 NUMA nodes, and in fact, we > >do not support node hotplug on power in

Re: [PATCH v4 6/6] Documentation/dev-tools: Add kselftest_harness documentation

On Thu, May 25, 2017 at 5:20 PM, Mickaël Salaün wrote: > Add metadata to kselftest_harness.h to be able to include the comments > in the Sphinx documentation. > > Changes since v3: > * document macros as actual functions (suggested by Jonathan Corbet) > * remove the TEST_API()

Re: [PATCH v4 6/6] Documentation/dev-tools: Add kselftest_harness documentation

On Thu, May 25, 2017 at 5:20 PM, Mickaël Salaün wrote: > Add metadata to kselftest_harness.h to be able to include the comments > in the Sphinx documentation. > > Changes since v3: > * document macros as actual functions (suggested by Jonathan Corbet) > * remove the TEST_API() wrapper to expose

Re: [PATCH v3] add the option of fortified string.h functions

On Mon, May 22, 2017 at 4:10 PM, Daniel Micay wrote: > diff --git a/arch/x86/include/asm/string_64.h > b/arch/x86/include/asm/string_64.h > index 733bae07fb29..3c5b26e07b85 100644 > --- a/arch/x86/include/asm/string_64.h > +++ b/arch/x86/include/asm/string_64.h > @@ -77,6

Re: [PATCH v3] add the option of fortified string.h functions

On Mon, May 22, 2017 at 4:10 PM, Daniel Micay wrote: > diff --git a/arch/x86/include/asm/string_64.h > b/arch/x86/include/asm/string_64.h > index 733bae07fb29..3c5b26e07b85 100644 > --- a/arch/x86/include/asm/string_64.h > +++ b/arch/x86/include/asm/string_64.h > @@ -77,6 +77,11 @@ int

Re: [PATCH 2/4] pinctrl: rockchip: Add iomux-route switching support for rk3228

Hi Heiko, 在 2017/5/26 5:12, Heiko Stuebner 写道: Requiring developers to calculate this pin-bit-value for each bank is cumbersome and error-prone. With the routes-struct known in the driver (see above and below), you can keep the the value element in rockchip_pin_bank, but calculate the per-bank

Re: [PATCH 2/4] pinctrl: rockchip: Add iomux-route switching support for rk3228

Hi Heiko, 在 2017/5/26 5:12, Heiko Stuebner 写道: Requiring developers to calculate this pin-bit-value for each bank is cumbersome and error-prone. With the routes-struct known in the driver (see above and below), you can keep the the value element in rockchip_pin_bank, but calculate the per-bank

Re: [PATCH 02/20] ipc: merge ipc_rcu and kern_ipc_perm

On Thu, May 25, 2017 at 12:34 PM, Kees Cook wrote: > On Thu, May 25, 2017 at 11:50 AM, Manfred Spraul > wrote: >> ipc has two management structures that exist for every id: >> - struct kern_ipc_perm, it contains e.g. the permissions. >> - struct

Re: [PATCH 02/20] ipc: merge ipc_rcu and kern_ipc_perm

On Thu, May 25, 2017 at 12:34 PM, Kees Cook wrote: > On Thu, May 25, 2017 at 11:50 AM, Manfred Spraul > wrote: >> ipc has two management structures that exist for every id: >> - struct kern_ipc_perm, it contains e.g. the permissions. >> - struct ipc_rcu, it contains the rcu head for rcu handling

[PATCH 0/2] reset: Basic reset controller

Hello, In the Aspeed SoCs we have some reset registers spread out in various parts of the soc: in the system controller IP, as well as other peripherals. I need to be able to deassert those resets before other drivers work. In writing a driver to do this I realised it was very generic. So

[PATCH 2/2] reset: Add basic single-register reset driver

This driver is a basic single-register reset controller driver that supports clearing a single bit in a register. Signed-off-by: Joel Stanley --- drivers/reset/Kconfig | 6 +++ drivers/reset/Makefile | 1 + drivers/reset/reset-basic.c | 109

[PATCH 1/2] dt-bindings: reset: Add bindings for basic reset controller

This adds the bindings documentation for a basic single-register reset controller. The bindings describe a single 32-bit register that contains up to 32 reset lines, each deasserted by clearing the appropriate bit in the register. Signed-off-by: Joel Stanley ---

[PATCH 0/2] reset: Basic reset controller

Hello, In the Aspeed SoCs we have some reset registers spread out in various parts of the soc: in the system controller IP, as well as other peripherals. I need to be able to deassert those resets before other drivers work. In writing a driver to do this I realised it was very generic. So

[PATCH 2/2] reset: Add basic single-register reset driver

This driver is a basic single-register reset controller driver that supports clearing a single bit in a register. Signed-off-by: Joel Stanley --- drivers/reset/Kconfig | 6 +++ drivers/reset/Makefile | 1 + drivers/reset/reset-basic.c | 109

[PATCH 1/2] dt-bindings: reset: Add bindings for basic reset controller

This adds the bindings documentation for a basic single-register reset controller. The bindings describe a single 32-bit register that contains up to 32 reset lines, each deasserted by clearing the appropriate bit in the register. Signed-off-by: Joel Stanley ---

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Thu, 25 May 2017, Marcelo Tosatti wrote: > Argument? We're showing you the data that this is causing a latency > problem for us. Sorry I am not sure where the data shows a latency problem. There are interrupts and scheduler ticks. But what does this have to do with vmstat? Show me your dpdk

Re: [patch 2/2] MM: allow per-cpu vmstat_threshold and vmstat_worker configuration

On Thu, 25 May 2017, Marcelo Tosatti wrote: > Argument? We're showing you the data that this is causing a latency > problem for us. Sorry I am not sure where the data shows a latency problem. There are interrupts and scheduler ticks. But what does this have to do with vmstat? Show me your dpdk

Re: [PATCH V2 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On Thu, 25 May 2017 12:37:40 -0500 Michael Bringmann wrote: > Removing or adding memory via the PowerPC hotplug interface shows > anomalies in the association between memory and nodes. The code > was updated to ensure that all nodes found at boot are still available >

Re: [PATCH V2 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On Thu, 25 May 2017 12:37:40 -0500 Michael Bringmann wrote: > Removing or adding memory via the PowerPC hotplug interface shows > anomalies in the association between memory and nodes. The code > was updated to ensure that all nodes found at boot are still available > to subsequent DLPAR

Re: [PATCH] reset: hisilicon: Fix hi6220 module license

looks good to me. On 2017/5/25 17:22, Andreas Färber wrote: > The hi6220_reset driver fails to load: > > [ 10.423640] hi6220_reset: module license 'unspecified' taints kernel. > [ 10.423644] Disabling lock debugging due to kernel taint > [ 10.423735] hi6220_reset: Unknown symbol

Re: [PATCH] reset: hisilicon: Fix hi6220 module license

looks good to me. On 2017/5/25 17:22, Andreas Färber wrote: > The hi6220_reset driver fails to load: > > [ 10.423640] hi6220_reset: module license 'unspecified' taints kernel. > [ 10.423644] Disabling lock debugging due to kernel taint > [ 10.423735] hi6220_reset: Unknown symbol

Re: [PATCH v9 6/7] LPC: Add the ACPI LPC support

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc2 next-20170525] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Gabriele-Paoloni/LPC-legacy-ISA-I-O

Re: [PATCH v9 6/7] LPC: Add the ACPI LPC support

Hi zhichang.yuan, [auto build test ERROR on linus/master] [also build test ERROR on v4.12-rc2 next-20170525] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Gabriele-Paoloni/LPC-legacy-ISA-I-O

linux-next: Tree for May 26

Hi all, Changes since 20170525: New tree: realtek Non-merge commits (relative to Linus' tree): 2775 3084 files changed, 111008 insertions(+), 61381 deletions(-) I have created today's linux-next tree at git

linux-next: Tree for May 26

Hi all, Changes since 20170525: New tree: realtek Non-merge commits (relative to Linus' tree): 2775 3084 files changed, 111008 insertions(+), 61381 deletions(-) I have created today's linux-next tree at git

[PATCH 3/4] test: firmwware: add signature test to driver_data loader test

Add the following tests: No.15 - verify loaded data witha signature No.16 - verify loaded data witha signature under signature enforcing For each test, there are several test cases: * no signature provided * valid signature provided * invalid signature provided Signed-off-by: AKASHI Takahiro

[PATCH 3/4] test: firmwware: add signature test to driver_data loader test

Add the following tests: No.15 - verify loaded data witha signature No.16 - verify loaded data witha signature under signature enforcing For each test, there are several test cases: * no signature provided * valid signature provided * invalid signature provided Signed-off-by: AKASHI Takahiro

[PATCH 4/4] firmware: document signature verification for driver data

add descriptions and usage about firmware signing in driver data APIs. Signed-off-by: AKASHI Takahiro Cc: Luis R. Rodriguez --- Documentation/driver-api/firmware/driver_data.rst | 6 ++ .../driver-api/firmware/fallback-mechanisms.rst| 5 +-

[PATCH 2/4] scripts: sign-file: add firmware-signing option

This new option (-f) allows us to create a signature file (*.p7s) for firmware binary. Signed-off-by: AKASHI Takahiro Cc: Luis R. Rodriguez --- scripts/sign-file.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[PATCH 4/4] firmware: document signature verification for driver data

add descriptions and usage about firmware signing in driver data APIs. Signed-off-by: AKASHI Takahiro Cc: Luis R. Rodriguez --- Documentation/driver-api/firmware/driver_data.rst | 6 ++ .../driver-api/firmware/fallback-mechanisms.rst| 5 +- Documentation/driver-api/firmware/signing.rst

[PATCH 2/4] scripts: sign-file: add firmware-signing option

This new option (-f) allows us to create a signature file (*.p7s) for firmware binary. Signed-off-by: AKASHI Takahiro Cc: Luis R. Rodriguez --- scripts/sign-file.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/scripts/sign-file.c b/scripts/sign-file.c index

[PATCH 1/4] firmware: add firmware signing

Systems that have module signing currently enabled may wish to extend vetting of firmware passed to the kernel as well. We can re-use most of the code for module signing for firmware signature verification and signing. This will also later enable re-use of this same code for subsystems that wish

[PATCH 1/4] firmware: add firmware signing

Systems that have module signing currently enabled may wish to extend vetting of firmware passed to the kernel as well. We can re-use most of the code for module signing for firmware signature verification and signing. This will also later enable re-use of this same code for subsystems that wish

[PATCH 0/4] firmware: signature verification

This is my first version of patch series for adding signature verification to firmware loading. The original idea and code came from the work by Luis some time ago, and I migrated it with some improvements to new driver data APIs, leaving request_firmware() intact. For details about how it

[PATCH 0/4] firmware: signature verification

This is my first version of patch series for adding signature verification to firmware loading. The original idea and code came from the work by Luis some time ago, and I migrated it with some improvements to new driver data APIs, leaving request_firmware() intact. For details about how it

[PATCH] staging: lustre: Replace printk_ratelimited with pr_warn_ratelimited

This patch fixes the checkpoint.pl warning: WARNING: Prefer printk_ratelimited or pr__ratelimited to printk_ratelimit Signed-off-by: Konrad Malkowski --- drivers/staging/lustre/lnet/libcfs/tracefile.c | 12 +--- 1 file changed, 5 insertions(+), 7

[PATCH] staging: lustre: Replace printk_ratelimited with pr_warn_ratelimited

This patch fixes the checkpoint.pl warning: WARNING: Prefer printk_ratelimited or pr__ratelimited to printk_ratelimit Signed-off-by: Konrad Malkowski --- drivers/staging/lustre/lnet/libcfs/tracefile.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git

  1   2   3   4   5   6   7   8   9   10   >