Re: [PATCH v2] clk: sunxi: fix build warning

On 10/24, Corentin Labbe wrote: > This patch fix the following build warning: > drivers/clk/sunxi/clk-factors.c:279:14: warning: variable 'name' set but not > used [-Wunused-but-set-variable] > > Fixes: 4cbeaebb8af1 ("clk: sunxi: factors: Add unregister function") > > Acked-by: Maxime Ripard

Re: [PATCH v2] clk: sunxi: fix build warning

On 10/24, Corentin Labbe wrote: > This patch fix the following build warning: > drivers/clk/sunxi/clk-factors.c:279:14: warning: variable 'name' set but not > used [-Wunused-but-set-variable] > > Fixes: 4cbeaebb8af1 ("clk: sunxi: factors: Add unregister function") > > Acked-by: Maxime Ripard >

Re: [PATCH 009/102] clk: sunxi: explicitly request exclusive reset control

On 07/19, Philipp Zabel wrote: > Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting > reset lines") started to transition the reset control request API calls > to explicitly state whether the driver needs exclusive or shared reset > control behavior. Convert all drivers

Re: [PATCH 009/102] clk: sunxi: explicitly request exclusive reset control

On 07/19, Philipp Zabel wrote: > Commit a53e35db70d1 ("reset: Ensure drivers are explicit when requesting > reset lines") started to transition the reset control request API calls > to explicitly state whether the driver needs exclusive or shared reset > control behavior. Convert all drivers

linux-next: manual merge of the kspp tree with the kvm tree

Hi Kees, Today's linux-next merge of the kspp tree got a conflict in: virt/kvm/kvm_main.c between commit: 46bea48ac241 ("kvm, mm: account kvm related kmem slabs to kmemcg") from the kvm tree and commit: 67ac5ee34976 ("kvm: whitelist struct kvm_vcpu_arch") from the kspp tree. I fixed

linux-next: manual merge of the kspp tree with the kvm tree

Hi Kees, Today's linux-next merge of the kspp tree got a conflict in: virt/kvm/kvm_main.c between commit: 46bea48ac241 ("kvm, mm: account kvm related kmem slabs to kmemcg") from the kvm tree and commit: 67ac5ee34976 ("kvm: whitelist struct kvm_vcpu_arch") from the kspp tree. I fixed

[PATCH v3] pids: introduce find_get_task_by_vpid helper

There are several functions that do find_task_by_vpid() followed by get_task_struct(). We can use a helper function instead. Signed-off-by: Mike Rapoport Acked-by: Oleg Nesterov --- v3: update arch/ia64/kernel/perfmon.c and security/yama/yama_lsm.c

[PATCH v3] pids: introduce find_get_task_by_vpid helper

There are several functions that do find_task_by_vpid() followed by get_task_struct(). We can use a helper function instead. Signed-off-by: Mike Rapoport Acked-by: Oleg Nesterov --- v3: update arch/ia64/kernel/perfmon.c and security/yama/yama_lsm.c that were missing in the previous versions

Re: [PATCH -mm -V3] mm, swap: Fix false error message in __swp_swapcount()

On Thu, Nov 02, 2017 at 01:42:25PM +0800, Huang, Ying wrote: > From: Huang Ying > > When a page fault occurs for a swap entry, the physical swap readahead > (not the VMA base swap readahead) may readahead several swap entries > after the fault swap entry. The

Re: [PATCH -mm -V3] mm, swap: Fix false error message in __swp_swapcount()

On Thu, Nov 02, 2017 at 01:42:25PM +0800, Huang, Ying wrote: > From: Huang Ying > > When a page fault occurs for a swap entry, the physical swap readahead > (not the VMA base swap readahead) may readahead several swap entries > after the fault swap entry. The readahead algorithm calculates some

Re: [PATCH v6 2/9] KVM: arm/arm64: vgic-its: Fix vgic_its_restore_collection_table returned value

On Thu, Oct 26, 2017 at 05:23:04PM +0200, Eric Auger wrote: > vgic_its_restore_cte returns +1 if the collection table entry > is valid and properly decoded. As a consequence, if the > collection table is fully filled with valid data that are > decoded without error,

Re: [PATCH v6 2/9] KVM: arm/arm64: vgic-its: Fix vgic_its_restore_collection_table returned value

On Thu, Oct 26, 2017 at 05:23:04PM +0200, Eric Auger wrote: > vgic_its_restore_cte returns +1 if the collection table entry > is valid and properly decoded. As a consequence, if the > collection table is fully filled with valid data that are > decoded without error,

[PATCH -mm -V3] mm, swap: Fix false error message in __swp_swapcount()

From: Huang Ying When a page fault occurs for a swap entry, the physical swap readahead (not the VMA base swap readahead) may readahead several swap entries after the fault swap entry. The readahead algorithm calculates some of the swap entries to readahead via

[PATCH -mm -V3] mm, swap: Fix false error message in __swp_swapcount()

From: Huang Ying When a page fault occurs for a swap entry, the physical swap readahead (not the VMA base swap readahead) may readahead several swap entries after the fault swap entry. The readahead algorithm calculates some of the swap entries to readahead via increasing the offset of the

Re: [PATCH 0/3] Make core_pattern support namespace

ping 在 2017年08月02日 14:37, Cao Shufeng 写道: This patchset includes following function points: 1: Let usermodehelper function possible to set pid namespace done by: [PATCH_v4.1_1/3] Make call_usermodehelper_exec possible to set namespaces 2: Let pipe_type core_pattern write dump into

Re: [PATCH 0/3] Make core_pattern support namespace

ping 在 2017年08月02日 14:37, Cao Shufeng 写道: This patchset includes following function points: 1: Let usermodehelper function possible to set pid namespace done by: [PATCH_v4.1_1/3] Make call_usermodehelper_exec possible to set namespaces 2: Let pipe_type core_pattern write dump into

Re: linux-next: build failure after merge of the gpio tree

Hi Stephen, 2017-11-02 14:20 GMT+09:00 Stephen Rothwell : > Hi Linus, > > After merging the gpio tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/gpio/gpio-uniphier.c:324:14: error: initialization from incompatible > pointer type

Re: linux-next: build failure after merge of the gpio tree

Hi Stephen, 2017-11-02 14:20 GMT+09:00 Stephen Rothwell : > Hi Linus, > > After merging the gpio tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > drivers/gpio/gpio-uniphier.c:324:14: error: initialization from incompatible > pointer type

Re: [PATCH v6 1/6] ARM: imx6q: provide documentation for new fsl,pmic-stby-poweroff property

On 10/27, Oleksij Rempel wrote: > Signed-off-by: Oleksij Rempel > Acked-by: Rob Herring > --- Acked-by: Stephen Boyd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH v6 1/6] ARM: imx6q: provide documentation for new fsl,pmic-stby-poweroff property

On 10/27, Oleksij Rempel wrote: > Signed-off-by: Oleksij Rempel > Acked-by: Rob Herring > --- Acked-by: Stephen Boyd -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project

Re: [PATCH 1/2] perf mmap: Fix perf backward recording

Hi Kan, On Wed, Nov 01, 2017 at 04:22:53PM +, Liang, Kan wrote: > > On 2017/11/1 21:57, Liang, Kan wrote: > > >> On 2017/11/1 20:00, Namhyung Kim wrote: > > >>> On Wed, Nov 01, 2017 at 06:32:50PM +0800, Wangnan (F) wrote: > > > There are only four test cases which set overwrite, > > >

Re: [PATCH 1/2] perf mmap: Fix perf backward recording

Hi Kan, On Wed, Nov 01, 2017 at 04:22:53PM +, Liang, Kan wrote: > > On 2017/11/1 21:57, Liang, Kan wrote: > > >> On 2017/11/1 20:00, Namhyung Kim wrote: > > >>> On Wed, Nov 01, 2017 at 06:32:50PM +0800, Wangnan (F) wrote: > > > There are only four test cases which set overwrite, > > >

Re: [RFC PATCH] clk: move of_clk_get_parent_count() declaration to

On 10/29, Masahiro Yamada wrote: > 2017-10-13 8:17 GMT+09:00 Stephen Boyd : > > > USB has a > > similar case, which I think Shawn Guo/Dong Aisheng was trying to > > add an OF based bulk clk_get() API called of_clk_bulk_get() > > for[1]. If this get all clks API works there

Re: [RFC PATCH] clk: move of_clk_get_parent_count() declaration to

On 10/29, Masahiro Yamada wrote: > 2017-10-13 8:17 GMT+09:00 Stephen Boyd : > > > USB has a > > similar case, which I think Shawn Guo/Dong Aisheng was trying to > > add an OF based bulk clk_get() API called of_clk_bulk_get() > > for[1]. If this get all clks API works there too then we should > >

[PATCH resend] Documentation: Update of broken link

The link of devicetree.org was broken. Site has been moved to elinux.org. Signed-off-by: Claudia Meitinger --- Documentation/devicetree/usage-model.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/usage-model.txt

[PATCH resend] Documentation: Update of broken link

The link of devicetree.org was broken. Site has been moved to elinux.org. Signed-off-by: Claudia Meitinger --- Documentation/devicetree/usage-model.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Documentation/devicetree/usage-model.txt

PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)

Hi, On my Asus C201 laptop (rk3288) the HDMI has been behaving weirdly after Linux upgrade. ~50% of the time after a hotplug, there is a vertical pink bar on the left of the display area and audio is not working at all. According to the sink device the display size is 1282x720 which seems

PROBLEM: Asus C201 video mode problems on HDMI hotplug (regression)

Hi, On my Asus C201 laptop (rk3288) the HDMI has been behaving weirdly after Linux upgrade. ~50% of the time after a hotplug, there is a vertical pink bar on the left of the display area and audio is not working at all. According to the sink device the display size is 1282x720 which seems

linux-next: build failure after merge of the gpio tree

Hi Linus, After merging the gpio tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/gpio/gpio-uniphier.c:324:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .activate = uniphier_gpio_irq_domain_activate,

linux-next: build failure after merge of the gpio tree

Hi Linus, After merging the gpio tree, today's linux-next build (arm multi_v7_defconfig) failed like this: drivers/gpio/gpio-uniphier.c:324:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types] .activate = uniphier_gpio_irq_domain_activate,

[PATCH] regulator: qcom_spmi: Include offset when translating voltages

This driver converts voltages from a non-linear range in hardware to a linear range in software and vice versa. During the conversion, we exclude certain voltages that are invalid to use because the software interface is more flexible than reality. For example, the FTSMPS2P5 regulators have a

[PATCH] regulator: qcom_spmi: Include offset when translating voltages

This driver converts voltages from a non-linear range in hardware to a linear range in software and vice versa. During the conversion, we exclude certain voltages that are invalid to use because the software interface is more flexible than reality. For example, the FTSMPS2P5 regulators have a

linux-next: manual merge of the gpio tree with the tip tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: include/linux/bitops.h between commit: cbe96375025e ("bitops: Add clear/set_bit32() to linux/bitops.h") from the tip tree and commit: 5307e2ad69ab ("bitops: Introduce assign_bit()") from the gpio tree. I fixed it

linux-next: manual merge of the gpio tree with the tip tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: include/linux/bitops.h between commit: cbe96375025e ("bitops: Add clear/set_bit32() to linux/bitops.h") from the tip tree and commit: 5307e2ad69ab ("bitops: Introduce assign_bit()") from the gpio tree. I fixed it

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 01-11-17, 14:43, Stephen Boyd wrote: > On 11/01, Rob Herring wrote: > > On Tue, Oct 31, 2017 at 9:17 PM, Viresh Kumar > > wrote: > > > On 31 October 2017 at 16:02, Rob Herring wrote: > > >> Why not a new property for magic values? opp-magic? Don't

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 01-11-17, 14:43, Stephen Boyd wrote: > On 11/01, Rob Herring wrote: > > On Tue, Oct 31, 2017 at 9:17 PM, Viresh Kumar > > wrote: > > > On 31 October 2017 at 16:02, Rob Herring wrote: > > >> Why not a new property for magic values? opp-magic? Don't we want to > > >> know when we have magic

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 01-11-17, 15:39, Rob Herring wrote: > On Tue, Oct 31, 2017 at 9:17 PM, Viresh Kumar wrote: > > On 31 October 2017 at 16:02, Rob Herring wrote: > >> Why not a new property for magic values? opp-magic? Don't we want to > >> know when we have magic

USB is not resumed(disconnected) after suspend to disk

Hi all, I am trying to support suspend to disk(hibernate) on Hikey with 4.4 kernel. During suspend, I could see the usb devices getting reset and I can access them properly. Message can be seen as below: usb 1-1: reset high-speed USB device number 2 using dwc2 usb 1-1.2: reset high-speed USB

Re: [RFC V7 2/2] OPP: Allow "opp-hz" and "opp-microvolt" to contain magic values

On 01-11-17, 15:39, Rob Herring wrote: > On Tue, Oct 31, 2017 at 9:17 PM, Viresh Kumar wrote: > > On 31 October 2017 at 16:02, Rob Herring wrote: > >> Why not a new property for magic values? opp-magic? Don't we want to > >> know when we have magic values? > > > > I have kept a separate property

USB is not resumed(disconnected) after suspend to disk

Hi all, I am trying to support suspend to disk(hibernate) on Hikey with 4.4 kernel. During suspend, I could see the usb devices getting reset and I can access them properly. Message can be seen as below: usb 1-1: reset high-speed USB device number 2 using dwc2 usb 1-1.2: reset high-speed USB

Re: [PATCH] mailbox: add support for doorbell/signal mode controllers

On Thu, Nov 2, 2017 at 8:57 AM, Bjorn Andersson wrote: > On Wed 01 Nov 20:02 PDT 2017, Jassi Brar wrote: > >> On Thu, Nov 2, 2017 at 3:47 AM, Bjorn Andersson >> wrote: >> > On Wed 01 Nov 11:15 PDT 2017, Sudeep Holla wrote: >> >> >> >> 80

Re: [PATCH] mailbox: add support for doorbell/signal mode controllers

On Thu, Nov 2, 2017 at 8:57 AM, Bjorn Andersson wrote: > On Wed 01 Nov 20:02 PDT 2017, Jassi Brar wrote: > >> On Thu, Nov 2, 2017 at 3:47 AM, Bjorn Andersson >> wrote: >> > On Wed 01 Nov 11:15 PDT 2017, Sudeep Holla wrote: >> >> >> >> 80 writel_relaxed(msg->cmd, mb->mbox_base + >> >>

Re: [PATCH V2] of: platform: Create dummy routines for !CONFIG_OF_ADDRESS

On 01-11-17, 16:14, Rob Herring wrote: > On Sat, Oct 28, 2017 at 03:56:46PM +0530, Viresh Kumar wrote: > > Few routines don't have their dummy counterparts which results in build > > failures where these routines are used without CONFIG_OF_ADDRESS > > enabled. > > > > Fix those by defining the

Re: [PATCH V2] of: platform: Create dummy routines for !CONFIG_OF_ADDRESS

On 01-11-17, 16:14, Rob Herring wrote: > On Sat, Oct 28, 2017 at 03:56:46PM +0530, Viresh Kumar wrote: > > Few routines don't have their dummy counterparts which results in build > > failures where these routines are used without CONFIG_OF_ADDRESS > > enabled. > > > > Fix those by defining the

linux-next: build warnings after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: drivers/staging/rtlwifi/base.c: In function 'rtl_watch_dog_timer_callback': drivers/staging/rtlwifi/base.c:2167:23: warning: unused variable 'hw' [-Wunused-variable] struct

linux-next: build warnings after merge of the staging tree

Hi Greg, After merging the staging tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: drivers/staging/rtlwifi/base.c: In function 'rtl_watch_dog_timer_callback': drivers/staging/rtlwifi/base.c:2167:23: warning: unused variable 'hw' [-Wunused-variable] struct

linux-next: manual merge of the staging tree with the v4l-dvb tree

Hi Greg, Today's linux-next merge of the staging tree got a conflict in: drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm_bo.c between commit: 309167b966b6 ("media: staging: atomisp: cleanup out of memory messages") from the v4l-dvb tree and commit: 63342e75e661 ("Staging: media:

linux-next: manual merge of the staging tree with the v4l-dvb tree

Hi Greg, Today's linux-next merge of the staging tree got a conflict in: drivers/staging/media/atomisp/pci/atomisp2/hmm/hmm_bo.c between commit: 309167b966b6 ("media: staging: atomisp: cleanup out of memory messages") from the v4l-dvb tree and commit: 63342e75e661 ("Staging: media:

Re: 答复: [PATCH] mm: extend reuse_swap_page range as much as possible

On Thu, Nov 02, 2017 at 02:09:57AM +, zhouxianrong wrote: > writes: > > > From: zhouxianrong > > > > origanlly reuse_swap_page requires that the sum of page's mapcount and > > swapcount less than or equal to one. > > in this case we can

Re: 答复: [PATCH] mm: extend reuse_swap_page range as much as possible

On Thu, Nov 02, 2017 at 02:09:57AM +, zhouxianrong wrote: > writes: > > > From: zhouxianrong > > > > origanlly reuse_swap_page requires that the sum of page's mapcount and > > swapcount less than or equal to one. > > in this case we can reuse this page and avoid COW currently. > > > > now

linux-next: manual merge of the char-misc tree with the tip tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/misc/lkdtm_core.c between commit: 8776fe75dc0e ("lkdtm, kprobes: Convert from jprobes to kprobes") from the tip tree and commits: 31c5c870a112 ("lkdtm: Convert from jprobe to kprobe") 75f98b7ab748

linux-next: manual merge of the char-misc tree with the tip tree

Hi all, Today's linux-next merge of the char-misc tree got a conflict in: drivers/misc/lkdtm_core.c between commit: 8776fe75dc0e ("lkdtm, kprobes: Convert from jprobes to kprobes") from the tip tree and commits: 31c5c870a112 ("lkdtm: Convert from jprobe to kprobe") 75f98b7ab748

linux-next: build warnings after merge of the usb tree

Hi Greg, After merging the usb tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: In file included from include/linux/printk.h:327:0, from include/linux/kernel.h:13, from include/asm-generic/bug.h:15, from

linux-next: build warnings after merge of the usb tree

Hi Greg, After merging the usb tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: In file included from include/linux/printk.h:327:0, from include/linux/kernel.h:13, from include/asm-generic/bug.h:15, from

linux-next: build warning after merge of the usb tree

Hi Greg, After merging the usb tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: arch/arm/boot/dts/stih410-b2120.dtb: Warning (gpios_property): hdmi,hpd-gpio property size (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000

linux-next: build warning after merge of the usb tree

Hi Greg, After merging the usb tree, today's linux-next build (arm multi_v7_defconfig) produced this warning: arch/arm/boot/dts/stih410-b2120.dtb: Warning (gpios_property): hdmi,hpd-gpio property size (8) too small for cell size 2 in /soc/sti-display-subsystem/sti-hdmi@8d04000

Re: [PATCH] dma-buf: Cleanup comments on dma_buf_map_attachment()

On Wed, Nov 1, 2017 at 10:06 AM, Liviu Dudau wrote: > Mappings need to be unmapped by calling dma_buf_unmap_attachment() and > not by calling again dma_buf_map_attachment(). Also fix some spelling > mistakes. > > Signed-off-by: Liviu Dudau Reviewed-by:

Re: [PATCH] dma-buf: Cleanup comments on dma_buf_map_attachment()

On Wed, Nov 1, 2017 at 10:06 AM, Liviu Dudau wrote: > Mappings need to be unmapped by calling dma_buf_unmap_attachment() and > not by calling again dma_buf_map_attachment(). Also fix some spelling > mistakes. > > Signed-off-by: Liviu Dudau Reviewed-by: Alex Deucher > --- >

linux-next: manual merge of the ipmi tree with the modules tree

Hi Corey, Today's linux-next merge of the ipmi tree got a conflict in: drivers/char/ipmi/ipmi_si_intf.c between commit: e4dca7b7aa08 ("treewide: Fix function prototypes for module_param_call()") from the modules tree and commit: 44814ec982d2 ("ipmi_si: Move the hotmod handling to

linux-next: manual merge of the ipmi tree with the modules tree

Hi Corey, Today's linux-next merge of the ipmi tree got a conflict in: drivers/char/ipmi/ipmi_si_intf.c between commit: e4dca7b7aa08 ("treewide: Fix function prototypes for module_param_call()") from the modules tree and commit: 44814ec982d2 ("ipmi_si: Move the hotmod handling to

[PATCH] PCI: Fail pci_map_rom if the PCI ROM is invalid

From: Changbin Du If we detected a invalid PCI ROM (e.g. Invalid PCI ROM header signature), we should unmap it immediately and fail. It doesn't make any sense that return a mapped area with size of 0. I have seen this case on Intel GVTg vGPU, which have no vbios. It will

[PATCH] PCI: Fail pci_map_rom if the PCI ROM is invalid

From: Changbin Du If we detected a invalid PCI ROM (e.g. Invalid PCI ROM header signature), we should unmap it immediately and fail. It doesn't make any sense that return a mapped area with size of 0. I have seen this case on Intel GVTg vGPU, which have no vbios. It will not cause a real

[PATCH v2 2/3] hwmon: (aspeed-pwm-tacho) Deassert reset in probe

The ASPEED SoC must deassert a reset in order to use the PWM/tach peripheral. Signed-off-by: Joel Stanley --- v2: - Correct horrible mistakes - Boot tested and hwmon sysfs files checked --- drivers/hwmon/aspeed-pwm-tacho.c | 21 + 1 file changed, 21

[PATCH v2 2/3] hwmon: (aspeed-pwm-tacho) Deassert reset in probe

The ASPEED SoC must deassert a reset in order to use the PWM/tach peripheral. Signed-off-by: Joel Stanley --- v2: - Correct horrible mistakes - Boot tested and hwmon sysfs files checked --- drivers/hwmon/aspeed-pwm-tacho.c | 21 + 1 file changed, 21 insertions(+) diff

[PATCH v2 3/3] dt-bindings: hwmon: aspeed-pwm-tacho: Add reset node

The device tree bindings are updated to document the resets phandle, and the example is updated to match what is expected for both the reset and clock phandle. Note that the bindings should have always had the reset controller, as the hardware is unusable without it. Signed-off-by: Joel Stanley

[PATCH v2 3/3] dt-bindings: hwmon: aspeed-pwm-tacho: Add reset node

The device tree bindings are updated to document the resets phandle, and the example is updated to match what is expected for both the reset and clock phandle. Note that the bindings should have always had the reset controller, as the hardware is unusable without it. Signed-off-by: Joel Stanley

[PATCH v2 0/3] hwmon: Add reset support to aspeed-pwm-tach

Gunter, This adds reset controller support to the ASPEED pwm/tach driver. The reset controller and clock driver is currently under review, so to test those patches must be merged in to fully test these changes[1]. To address your concerns from v1: This driver was not usable as-is upstream. I

[PATCH v2 1/3] hwmon: (aspeed-pwm-tacho) Sort headers

Sort the headers in preperation for future changes. Signed-off-by: Joel Stanley --- drivers/hwmon/aspeed-pwm-tacho.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/hwmon/aspeed-pwm-tacho.c b/drivers/hwmon/aspeed-pwm-tacho.c index

[PATCH v2 0/3] hwmon: Add reset support to aspeed-pwm-tach

Gunter, This adds reset controller support to the ASPEED pwm/tach driver. The reset controller and clock driver is currently under review, so to test those patches must be merged in to fully test these changes[1]. To address your concerns from v1: This driver was not usable as-is upstream. I

[PATCH v2 1/3] hwmon: (aspeed-pwm-tacho) Sort headers

Sort the headers in preperation for future changes. Signed-off-by: Joel Stanley --- drivers/hwmon/aspeed-pwm-tacho.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/hwmon/aspeed-pwm-tacho.c b/drivers/hwmon/aspeed-pwm-tacho.c index f914e5f41048..63a95e23ca81

Re: [PATCH net-next V2 1/3] tun: abstract flow steering logic

On 2017年11月02日 11:45, Michael S. Tsirkin wrote: On Thu, Nov 02, 2017 at 11:43:48AM +0800, Jason Wang wrote: On 2017年11月02日 09:11, Willem de Bruijn wrote: On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote: tun now use flow caches based automatic queue steering method.

Re: [PATCH net-next V2 1/3] tun: abstract flow steering logic

On 2017年11月02日 11:45, Michael S. Tsirkin wrote: On Thu, Nov 02, 2017 at 11:43:48AM +0800, Jason Wang wrote: On 2017年11月02日 09:11, Willem de Bruijn wrote: On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote: tun now use flow caches based automatic queue steering method. This may not suffice

Re: [PATCH net-next V2 3/3] tun: add eBPF based queue selection method

On 2017年11月01日 21:59, Michael S. Tsirkin wrote: On Wed, Nov 01, 2017 at 09:02:03PM +0800, Jason Wang wrote: On 2017年11月01日 00:45, Michael S. Tsirkin wrote: +static void __tun_set_steering_ebpf(struct tun_struct *tun, + struct bpf_prog *new) +{ +

Re: [PATCH net-next V2 1/3] tun: abstract flow steering logic

On Thu, Nov 02, 2017 at 11:43:48AM +0800, Jason Wang wrote: > > > On 2017年11月02日 09:11, Willem de Bruijn wrote: > > On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote: > > > tun now use flow caches based automatic queue steering method. This > > > may not suffice all user

Re: [PATCH net-next V2 3/3] tun: add eBPF based queue selection method

On 2017年11月01日 21:59, Michael S. Tsirkin wrote: On Wed, Nov 01, 2017 at 09:02:03PM +0800, Jason Wang wrote: On 2017年11月01日 00:45, Michael S. Tsirkin wrote: +static void __tun_set_steering_ebpf(struct tun_struct *tun, + struct bpf_prog *new) +{ +

Re: [PATCH net-next V2 1/3] tun: abstract flow steering logic

On Thu, Nov 02, 2017 at 11:43:48AM +0800, Jason Wang wrote: > > > On 2017年11月02日 09:11, Willem de Bruijn wrote: > > On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote: > > > tun now use flow caches based automatic queue steering method. This > > > may not suffice all user cases. To extend it to

Re: [PATCH net-next V2 1/3] tun: abstract flow steering logic

On 2017年11月02日 09:11, Willem de Bruijn wrote: On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote: tun now use flow caches based automatic queue steering method. This may not suffice all user cases. To extend it to be able to use more flow steering policy, this patch

Re: [PATCH net-next V2 1/3] tun: abstract flow steering logic

On 2017年11月02日 09:11, Willem de Bruijn wrote: On Tue, Oct 31, 2017 at 7:32 PM, Jason Wang wrote: tun now use flow caches based automatic queue steering method. This may not suffice all user cases. To extend it to be able to use more flow steering policy, this patch abstracts flow steering

Re: [PATCH] timer: Add parenthesis around timer_setup() macro arguments

Hi Kees, On Wed, 1 Nov 2017 20:04:05 -0700 Kees Cook wrote: > > On Wed, Nov 1, 2017 at 7:33 PM, Stephen Rothwell > wrote: > > Hi Kees, > > > > On Wed, 1 Nov 2017 07:32:50 -0700 Kees Cook wrote: > >> > >> In the case where

Re: [PATCH] timer: Add parenthesis around timer_setup() macro arguments

Hi Kees, On Wed, 1 Nov 2017 20:04:05 -0700 Kees Cook wrote: > > On Wed, Nov 1, 2017 at 7:33 PM, Stephen Rothwell > wrote: > > Hi Kees, > > > > On Wed, 1 Nov 2017 07:32:50 -0700 Kees Cook wrote: > >> > >> In the case where expressions are passed as macro arguments, the LOCKDEP > >> version

linux-next: build failure after merge of the workqueues tree

Hi Tejun, After merging the workqueues tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/workqueue.c: In function 'workqueue_init_early': kernel/workqueue.c:5561:56: error: 'cpu_isolated_map' undeclared (first use in this function)

linux-next: build failure after merge of the workqueues tree

Hi Tejun, After merging the workqueues tree, today's linux-next build (arm multi_v7_defconfig) failed like this: kernel/workqueue.c: In function 'workqueue_init_early': kernel/workqueue.c:5561:56: error: 'cpu_isolated_map' undeclared (first use in this function)

Re: [PATCH net-next 3/9] net: hns3: Refactor the initialization of command queue

Hi, Lipeng On 2017/11/1 22:47, Lipeng wrote: > From: qumingguang > > There is no necessary to reallocate the descriptor and remap the descriptor > memory in reset process, But there is still some other action exit in both exit -> exist > reset process and

Re: [PATCH net-next 3/9] net: hns3: Refactor the initialization of command queue

Hi, Lipeng On 2017/11/1 22:47, Lipeng wrote: > From: qumingguang > > There is no necessary to reallocate the descriptor and remap the descriptor > memory in reset process, But there is still some other action exit in both exit -> exist > reset process and initialization process. > > To reuse

Re: Regression: commit da029c11e6b1 broke toybox xargs.

On Wed, Nov 1, 2017 at 4:34 PM, Rob Landley wrote: > Toybox has been trying to figure out how big an xargs is allowed to be > for a while: > > http://lists.landley.net/pipermail/toybox-landley.net/2017-October/009186.html > > We're trying to avoid the case where you can run

Re: Regression: commit da029c11e6b1 broke toybox xargs.

On Wed, Nov 1, 2017 at 4:34 PM, Rob Landley wrote: > Toybox has been trying to figure out how big an xargs is allowed to be > for a while: > > http://lists.landley.net/pipermail/toybox-landley.net/2017-October/009186.html > > We're trying to avoid the case where you can run something from the >

Re: [PATCH 4/7] MIPS: Octeon: Add Free Pointer Unit (FPA) support.

Le 11/01/17 à 17:36, David Daney a écrit : > From: Carlos Munoz > > From the hardware user manual: "The FPA is a unit that maintains > pools of pointers to free L2/DRAM memory. To provide QoS, the pools > are referenced indirectly through 1024 auras. Both core software > and

Re: [PATCH 4/7] MIPS: Octeon: Add Free Pointer Unit (FPA) support.

Le 11/01/17 à 17:36, David Daney a écrit : > From: Carlos Munoz > > From the hardware user manual: "The FPA is a unit that maintains > pools of pointers to free L2/DRAM memory. To provide QoS, the pools > are referenced indirectly through 1024 auras. Both core software > and hardware units

Re: [PATCH] mailbox: add support for doorbell/signal mode controllers

On Wed 01 Nov 20:02 PDT 2017, Jassi Brar wrote: > On Thu, Nov 2, 2017 at 3:47 AM, Bjorn Andersson > wrote: > > On Wed 01 Nov 11:15 PDT 2017, Sudeep Holla wrote: > >> > >> 80 writel_relaxed(msg->cmd, mb->mbox_base + > >> MAILBOX_A2B_CMD(chans->idx)); > >> 81

Re: [PATCH] mailbox: add support for doorbell/signal mode controllers

On Wed 01 Nov 20:02 PDT 2017, Jassi Brar wrote: > On Thu, Nov 2, 2017 at 3:47 AM, Bjorn Andersson > wrote: > > On Wed 01 Nov 11:15 PDT 2017, Sudeep Holla wrote: > >> > >> 80 writel_relaxed(msg->cmd, mb->mbox_base + > >> MAILBOX_A2B_CMD(chans->idx)); > >> 81

Re: [alsa-devel] [PATCH 08/14] soundwire: Add Slave status handling helpers

On Wed, Nov 01, 2017 at 04:10:08PM -0500, Pierre-Louis Bossart wrote: > On 11/1/17 4:08 AM, Vinod Koul wrote: > >On Wed, Nov 01, 2017 at 02:49:15AM +0530, Pierre-Louis Bossart wrote: > >>> > >>>BUT given that we have seen stuff i am inclined to add a counter, we cant > >>>have more than 11 device

Re: [alsa-devel] [PATCH 08/14] soundwire: Add Slave status handling helpers

On Wed, Nov 01, 2017 at 04:10:08PM -0500, Pierre-Louis Bossart wrote: > On 11/1/17 4:08 AM, Vinod Koul wrote: > >On Wed, Nov 01, 2017 at 02:49:15AM +0530, Pierre-Louis Bossart wrote: > >>> > >>>BUT given that we have seen stuff i am inclined to add a counter, we cant > >>>have more than 11 device

Re: [PATCH net-next V2 3/3] tun: add eBPF based queue selection method

On 2017年11月02日 03:12, Alexei Starovoitov wrote: On Wed, Nov 01, 2017 at 03:59:48PM +0200, Michael S. Tsirkin wrote: On Wed, Nov 01, 2017 at 09:02:03PM +0800, Jason Wang wrote: On 2017年11月01日 00:45, Michael S. Tsirkin wrote: +static void __tun_set_steering_ebpf(struct tun_struct *tun, +

Re: [PATCH net-next V2 3/3] tun: add eBPF based queue selection method

On 2017年11月02日 03:12, Alexei Starovoitov wrote: On Wed, Nov 01, 2017 at 03:59:48PM +0200, Michael S. Tsirkin wrote: On Wed, Nov 01, 2017 at 09:02:03PM +0800, Jason Wang wrote: On 2017年11月01日 00:45, Michael S. Tsirkin wrote: +static void __tun_set_steering_ebpf(struct tun_struct *tun, +

Re: [PATCH net-next] vhost_net: conditionally enable tx polling

On 2017年11月01日 23:03, Michael S. Tsirkin wrote: On Wed, Nov 01, 2017 at 08:51:36PM +0800, Jason Wang wrote: On 2017年11月01日 00:36, Michael S. Tsirkin wrote: On Tue, Oct 31, 2017 at 06:27:20PM +0800, Jason Wang wrote: We always poll tx for socket, this is sub optimal since: - we only want

Re: [PATCH net-next] vhost_net: conditionally enable tx polling

On 2017年11月01日 23:03, Michael S. Tsirkin wrote: On Wed, Nov 01, 2017 at 08:51:36PM +0800, Jason Wang wrote: On 2017年11月01日 00:36, Michael S. Tsirkin wrote: On Tue, Oct 31, 2017 at 06:27:20PM +0800, Jason Wang wrote: We always poll tx for socket, this is sub optimal since: - we only want

RE: [PATCH 2/2] Documentation: fsl: dspi: Add a compatible string for ls1088a DSPI

Hi Rob, Thanks a lot for the ack! > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: 2017年11月2日 8:14 > To: Z.q. Hou > Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; > devicet...@vger.kernel.org;

RE: [PATCH 2/2] Documentation: fsl: dspi: Add a compatible string for ls1088a DSPI

Hi Rob, Thanks a lot for the ack! > -Original Message- > From: Rob Herring [mailto:r...@kernel.org] > Sent: 2017年11月2日 8:14 > To: Z.q. Hou > Cc: linux-arm-ker...@lists.infradead.org; linux-kernel@vger.kernel.org; > devicet...@vger.kernel.org; linux-...@vger.kernel.org;

Re: [PATCH] sh: remove pointless select of KBUILD_DEFCONFIG

SH developers, No comment? Looks like the SH maintainers are no more picking up any patches. If nobody takes care of this patch, I will apply it to Kbuild tree. 2017-10-04 18:33 GMT+09:00 Masahiro Yamada : > KBUILD_DEFCONFIG := shx3_defconfig > > is never

Re: [PATCH] sh: remove pointless select of KBUILD_DEFCONFIG

SH developers, No comment? Looks like the SH maintainers are no more picking up any patches. If nobody takes care of this patch, I will apply it to Kbuild tree. 2017-10-04 18:33 GMT+09:00 Masahiro Yamada : > KBUILD_DEFCONFIG := shx3_defconfig > > is never used in a sensible way.

  1   2   3   4   5   6   7   8   9   10   >