Re: [PATCH] s390/crypto: make cca_public_sec and cca_token_hdr const

On Sun, Aug 06, 2017 at 11:22:27AM +0530, Bhumika Goyal wrote: > Declare cca_public_sec and cca_token_hdr structures as const as they are > only used during copy operations. > > Signed-off-by: Bhumika Goyal > --- > drivers/s390/crypto/zcrypt_cca_key.h | 6 +++--- > 1 file

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On Wed, Aug 9, 2017 at 11:13 AM, Oza Oza wrote: > On Wed, Aug 9, 2017 at 10:57 AM, Ray Jui wrote: >> >> >> On 8/8/2017 10:22 PM, Oza Oza wrote: >>> >>> On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: Please send

Re: [PATCH] s390/crypto: make cca_public_sec and cca_token_hdr const

On Sun, Aug 06, 2017 at 11:22:27AM +0530, Bhumika Goyal wrote: > Declare cca_public_sec and cca_token_hdr structures as const as they are > only used during copy operations. > > Signed-off-by: Bhumika Goyal > --- > drivers/s390/crypto/zcrypt_cca_key.h | 6 +++--- > 1 file changed, 3

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On Wed, Aug 9, 2017 at 11:13 AM, Oza Oza wrote: > On Wed, Aug 9, 2017 at 10:57 AM, Ray Jui wrote: >> >> >> On 8/8/2017 10:22 PM, Oza Oza wrote: >>> >>> On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: Please send bindings to DT list. >>> >>> Sure, will do that. >>> On Mon, Aug

Re: [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code

Vivek, On Tuesday 08 August 2017 09:20 PM, Vivek Gautam wrote: > Hi Koshon, > > On 2017-08-08 17:39, Kishon Vijay Abraham I wrote: >> Hi, >> >> On Friday 04 August 2017 12:18 PM, Vivek Gautam wrote: >>> Refactoring the qcom-ufs phy and host controller code to move >>> further towards the generic

Re: [PATCH 0/5] qcom-ufs: phy/hcd: Refactor phy initialization code

Vivek, On Tuesday 08 August 2017 09:20 PM, Vivek Gautam wrote: > Hi Koshon, > > On 2017-08-08 17:39, Kishon Vijay Abraham I wrote: >> Hi, >> >> On Friday 04 August 2017 12:18 PM, Vivek Gautam wrote: >>> Refactoring the qcom-ufs phy and host controller code to move >>> further towards the generic

Kdump not working with rt patch, tested under 4.4.32/4.4.79

Test case: https://github.com/saiyamd/softlockup_test/blob/master/softlockup_test.c

Kdump not working with rt patch, tested under 4.4.32/4.4.79

Test case: https://github.com/saiyamd/softlockup_test/blob/master/softlockup_test.c

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On Wed, Aug 9, 2017 at 10:57 AM, Ray Jui wrote: > > > On 8/8/2017 10:22 PM, Oza Oza wrote: >> >> On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: >>> >>> Please send bindings to DT list. >> >> Sure, will do that. >> >>> On Mon, Aug 7, 2017 at 11:44 PM,

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On Wed, Aug 9, 2017 at 10:57 AM, Ray Jui wrote: > > > On 8/8/2017 10:22 PM, Oza Oza wrote: >> >> On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: >>> >>> Please send bindings to DT list. >> >> Sure, will do that. >> >>> On Mon, Aug 7, 2017 at 11:44 PM, Oza Pawandeep >>> wrote: Add

Re: [PATCH v4 0/3] Introduce USB charger support in USB phy

Hi Felipe, On 27 July 2017 at 13:14, Baolin Wang wrote: > Currently the Linux kernel does not provide any standard integration of this > feature that integrates the USB subsystem with the system power regulation > provided by PMICs meaning that either vendors must add

Re: [PATCH v4 0/3] Introduce USB charger support in USB phy

Hi Felipe, On 27 July 2017 at 13:14, Baolin Wang wrote: > Currently the Linux kernel does not provide any standard integration of this > feature that integrates the USB subsystem with the system power regulation > provided by PMICs meaning that either vendors must add this in their kernels > or

[PATCH] perf: Util.py add_stats() computes the mean correctly

add_stats() is a utility function for perf scripts to accumulate a value, and keep track of some statistics. The mean is one of the statistics it keeps track of, but due to a bug, this wasn't being computed properly. This patch makes the computation correct Signed-off-by: Dima Kogan

[PATCH] perf: Util.py add_stats() computes the mean correctly

add_stats() is a utility function for perf scripts to accumulate a value, and keep track of some statistics. The mean is one of the statistics it keeps track of, but due to a bug, this wasn't being computed properly. This patch makes the computation correct Signed-off-by: Dima Kogan ---

[PATCH v2 1/4] phy: phy-mt65xx-usb3: add PCIe PHY support

From: Ryder Lee This patch adds PCIe PHY setting part. Signed-off-by: Ryder Lee Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 228 ++ 1 file changed, 206

[PATCH v2 1/4] phy: phy-mt65xx-usb3: add PCIe PHY support

From: Ryder Lee This patch adds PCIe PHY setting part. Signed-off-by: Ryder Lee Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 228 ++ 1 file changed, 206 insertions(+), 22 deletions(-) diff --git a/drivers/phy/phy-mt65xx-usb3.c

[PATCH v2 2/4] phy: phy-mt65xx-usb3: add SATA PHY support

From: Ryder Lee This patch adds SATA setting part. Signed-off-by: Ryder Lee Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 133 -- 1 file changed, 129

[PATCH v2 2/4] phy: phy-mt65xx-usb3: add SATA PHY support

From: Ryder Lee This patch adds SATA setting part. Signed-off-by: Ryder Lee Signed-off-by: Chunfeng Yun --- drivers/phy/phy-mt65xx-usb3.c | 133 -- 1 file changed, 129 insertions(+), 4 deletions(-) diff --git a/drivers/phy/phy-mt65xx-usb3.c

[PATCH v2 3/4] phy: phy-mt65xx-usb3: add mediatek directory and rename file

The driver is actually for T-PHY which supports USB3.0, PCIe and SATA, and supports more SoCs now, but not just only for series of mt65xx SoCs, so the name of file, data struct, functions etc with 'mt65xx' may cause misunderstanding when new SoCs are supported. Here rename them to reflect the real

[PATCH v2 3/4] phy: phy-mt65xx-usb3: add mediatek directory and rename file

The driver is actually for T-PHY which supports USB3.0, PCIe and SATA, and supports more SoCs now, but not just only for series of mt65xx SoCs, so the name of file, data struct, functions etc with 'mt65xx' may cause misunderstanding when new SoCs are supported. Here rename them to reflect the real

[PATCH v2 4/4] dt-bindings: phy-mt65xx-usb: supports PCIe, SATA and rename file

add support for PCIe and SATA, also add some new compatibles. due to phy-mt65xx-usb.txt holds the bindings for all mediatek SoCs with T-PHY controller, change the name to phy-mtk-tphy.txt to reflect that. Signed-off-by: Chunfeng Yun --- .../phy/{phy-mt65xx-usb.txt =>

[PATCH v2 4/4] dt-bindings: phy-mt65xx-usb: supports PCIe, SATA and rename file

add support for PCIe and SATA, also add some new compatibles. due to phy-mt65xx-usb.txt holds the bindings for all mediatek SoCs with T-PHY controller, change the name to phy-mtk-tphy.txt to reflect that. Signed-off-by: Chunfeng Yun --- .../phy/{phy-mt65xx-usb.txt => phy-mtk-tphy.txt}|

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On 8/8/2017 10:22 PM, Oza Oza wrote: On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: Please send bindings to DT list. Sure, will do that. On Mon, Aug 7, 2017 at 11:44 PM, Oza Pawandeep wrote: Add description for optional device tree property

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On 8/8/2017 10:22 PM, Oza Oza wrote: On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: Please send bindings to DT list. Sure, will do that. On Mon, Aug 7, 2017 at 11:44 PM, Oza Pawandeep wrote: Add description for optional device tree property 'brcm,pci-hotplug' for PCI hotplug

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: > Please send bindings to DT list. Sure, will do that. > > On Mon, Aug 7, 2017 at 11:44 PM, Oza Pawandeep wrote: >> Add description for optional device tree property >> 'brcm,pci-hotplug' for PCI

Re: [patch v2 1/2] drivers: jtag: Add JTAG core driver

Hi Oleksandr, [auto build test ERROR on linus/master] [also build test ERROR on v4.13-rc4 next-20170808] [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/Oleksandr-Shamray/drivers-jtag-Add-JTAG

Re: [PATCH 2/2] PCI: iproc: Add optional brcm,pci-hotplug

On Tue, Aug 8, 2017 at 7:50 PM, Rob Herring wrote: > Please send bindings to DT list. Sure, will do that. > > On Mon, Aug 7, 2017 at 11:44 PM, Oza Pawandeep wrote: >> Add description for optional device tree property >> 'brcm,pci-hotplug' for PCI hotplug feature. >> >> Signed-off-by: Oza

Re: [patch v2 1/2] drivers: jtag: Add JTAG core driver

Hi Oleksandr, [auto build test ERROR on linus/master] [also build test ERROR on v4.13-rc4 next-20170808] [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/Oleksandr-Shamray/drivers-jtag-Add-JTAG

Re: [PATCH v4 02/19] crypto: ccm: use -EAGAIN for transient busy indication

On Tue, Aug 8, 2017 at 6:24 PM, Gary R Hook wrote: > On 08/08/2017 07:03 AM, Gilad Ben-Yossef wrote: >> >> Replace -EBUSY with -EAGAIN when reporting transient busy >> indication in the absence of backlog. >> >> Signed-off-by: Gilad Ben-Yossef > > > Could

Re: [PATCH v4 02/19] crypto: ccm: use -EAGAIN for transient busy indication

On Tue, Aug 8, 2017 at 6:24 PM, Gary R Hook wrote: > On 08/08/2017 07:03 AM, Gilad Ben-Yossef wrote: >> >> Replace -EBUSY with -EAGAIN when reporting transient busy >> indication in the absence of backlog. >> >> Signed-off-by: Gilad Ben-Yossef > > > Could we use "ccp" in the subject line,

Re: [PATCH] modpost: simplify sec_name()

On Tue, Aug 8, 2017 at 8:18 PM, Masahiro Yamada wrote: > There is code duplication between sec_name() and sech_name(). > Simplify sec_name() by re-using sech_name(). Also, move them up > to remove the forward declaration of sec_name(). > > Signed-off-by: Masahiro

Re: [PATCH] modpost: simplify sec_name()

On Tue, Aug 8, 2017 at 8:18 PM, Masahiro Yamada wrote: > There is code duplication between sec_name() and sech_name(). > Simplify sec_name() by re-using sech_name(). Also, move them up > to remove the forward declaration of sec_name(). > > Signed-off-by: Masahiro Yamada Reviewed-by: Kees Cook

[PATCH] net: dsa: make dsa_switch_ops const

Make these structures const as they are only stored in the ops field of a dsa_switch structure, which is const. Done using Coccinelle. Signed-off-by: Bhumika Goyal --- drivers/net/dsa/dsa_loop.c | 2 +- drivers/net/dsa/lan9303-core.c | 2 +- drivers/net/dsa/mt7530.c

[PATCH] net: dsa: make dsa_switch_ops const

Make these structures const as they are only stored in the ops field of a dsa_switch structure, which is const. Done using Coccinelle. Signed-off-by: Bhumika Goyal --- drivers/net/dsa/dsa_loop.c | 2 +- drivers/net/dsa/lan9303-core.c | 2 +- drivers/net/dsa/mt7530.c | 2 +- 3 files

[BUG] resolver strangeness in 4.12

No idea where to begin tracking this down :-(. After approximately six days of uptime with a 4.12.0 kernel, the DNS resolver simply quits working. All query attempts come back with "no DNS servers can be reached". External hosts can still query the BIND server running on the host with the

[BUG] resolver strangeness in 4.12

No idea where to begin tracking this down :-(. After approximately six days of uptime with a 4.12.0 kernel, the DNS resolver simply quits working. All query attempts come back with "no DNS servers can be reached". External hosts can still query the BIND server running on the host with the

Re: [PATCH] acpi: apei: fix GHES estatus iteration

On Wed, Aug 09, 2017 at 02:52:06AM +0200, Rafael J. Wysocki wrote: > Actually I will if Boris ACKs these. It's all on the TODO list for when I get back from vacation next week. Unless Tony gets to them before me... Thanks. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer,

Re: [PATCH] acpi: apei: fix GHES estatus iteration

On Wed, Aug 09, 2017 at 02:52:06AM +0200, Rafael J. Wysocki wrote: > Actually I will if Boris ACKs these. It's all on the TODO list for when I get back from vacation next week. Unless Tony gets to them before me... Thanks. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer,

linux-next: manual merge of the rpmsg tree with the qcom tree

Hi Bjorn, Today's linux-next merge of the rpmsg tree got a conflict in: drivers/soc/qcom/Kconfig between commit: 2a464815d326 ("soc: qcom: bring all qcom drivers into a submenu") from the qcom tree and commit: c4d77d5fcd8b ("soc: qcom: GLINK SSR notifier") from the rpmsg tree. I

linux-next: manual merge of the rpmsg tree with the qcom tree

Hi Bjorn, Today's linux-next merge of the rpmsg tree got a conflict in: drivers/soc/qcom/Kconfig between commit: 2a464815d326 ("soc: qcom: bring all qcom drivers into a submenu") from the qcom tree and commit: c4d77d5fcd8b ("soc: qcom: GLINK SSR notifier") from the rpmsg tree. I

Re: [PATCH v1] crypto: caam - set hwrng quality level

On Thu, Aug 03, 2017 at 07:48:51AM +, Horia Geantă wrote: > > Right now it's configured as a DRBG. > If I read correctly, it doesn't matter it's using the internal TRNG for > (automated) seeding, it still shouldn't use hwrng. > This means it's broken since the very beginning: > e24f7c9e87d4

Re: [PATCH v1] crypto: caam - set hwrng quality level

On Thu, Aug 03, 2017 at 07:48:51AM +, Horia Geantă wrote: > > Right now it's configured as a DRBG. > If I read correctly, it doesn't matter it's using the internal TRNG for > (automated) seeding, it still shouldn't use hwrng. > This means it's broken since the very beginning: > e24f7c9e87d4

[PATCH] cpufreq: Return 0 from ->fast_switch() on errors

CPUFREQ_ENTRY_INVALID is a special symbol which is used to specify that an entry in the cpufreq table is invalid. But using it outside of the scope of the cpufreq table looks a bit incorrect. We can represent an invalid frequency by writing it as 0 instead if we need. Note that it is already done

[PATCH] cpufreq: Return 0 from ->fast_switch() on errors

CPUFREQ_ENTRY_INVALID is a special symbol which is used to specify that an entry in the cpufreq table is invalid. But using it outside of the scope of the cpufreq table looks a bit incorrect. We can represent an invalid frequency by writing it as 0 instead if we need. Note that it is already done

[RFT v2] mfd: exynos-lpass: Handle return value of clk_prepare_enable

clk_prepare_enable() can fail here and we must check its return value. we must call pm_runtime_disable() and pm_runtime_set_suspended(), If exynos_lpass_probe is not successful. Signed-off-by: Arvind Yadav --- changes in v2: added regmap_exit(lpass->top)

[RFT v2] mfd: exynos-lpass: Handle return value of clk_prepare_enable

clk_prepare_enable() can fail here and we must check its return value. we must call pm_runtime_disable() and pm_runtime_set_suspended(), If exynos_lpass_probe is not successful. Signed-off-by: Arvind Yadav --- changes in v2: added regmap_exit(lpass->top) and blank line before

Re: [PATCH] mfd: exynos-lpass: Handle return value of clk_prepare_enable

Thanks :) On Tuesday 08 August 2017 11:55 PM, Krzysztof Kozlowski wrote: On Tue, Aug 08, 2017 at 05:20:55PM +0530, Arvind Yadav wrote: clk_prepare_enable() can fail here and we must check its return value. we must call pm_runtime_disable() and pm_runtime_set_suspended(), If exynos_lpass_probe

Re: [PATCH] mfd: exynos-lpass: Handle return value of clk_prepare_enable

Thanks :) On Tuesday 08 August 2017 11:55 PM, Krzysztof Kozlowski wrote: On Tue, Aug 08, 2017 at 05:20:55PM +0530, Arvind Yadav wrote: clk_prepare_enable() can fail here and we must check its return value. we must call pm_runtime_disable() and pm_runtime_set_suspended(), If exynos_lpass_probe

Re: [PATCH net] Revert "vhost: cache used event for better performance"

On Wed, Aug 09, 2017 at 10:38:10AM +0800, Jason Wang wrote: > I think don't think current code can work well if vq.num is grater than > 2^15. Since all cached idx is u16. This looks like a bug which needs to be > fixed. That's a limitation of virtio 1.0. > > * else if the interval of vq.num is

Re: [PATCH net] Revert "vhost: cache used event for better performance"

On Wed, Aug 09, 2017 at 10:38:10AM +0800, Jason Wang wrote: > I think don't think current code can work well if vq.num is grater than > 2^15. Since all cached idx is u16. This looks like a bug which needs to be > fixed. That's a limitation of virtio 1.0. > > * else if the interval of vq.num is

Re: [RFC] hwmon: (ibmpowernv) Add support for reset-history sensors

On 07/25/2017 10:55 PM, Shilpasri G Bhat wrote: In P9, OCC allows for clearing the sensor min-max history. This patch exports attribute to reset history when set will clear the history of all the sensors owned by CSM and belonging to the chip. Signed-off-by: Shilpasri G Bhat

Re: [RFC] hwmon: (ibmpowernv) Add support for reset-history sensors

On 07/25/2017 10:55 PM, Shilpasri G Bhat wrote: In P9, OCC allows for clearing the sensor min-max history. This patch exports attribute to reset history when set will clear the history of all the sensors owned by CSM and belonging to the chip. Signed-off-by: Shilpasri G Bhat --- This patch is

Re: [PATCH v2 18/18] cpufreq: scmi: add support for fast frequency switching

On 04-08-17, 15:31, Sudeep Holla wrote: > The cpufreq core provides option for drivers to implement fast_switch > callback which is invoked for frequency switching from interrupt context. > > This patch adds support for fast_switch callback in SCMI cpufreq driver > by making use of polling based

Re: [PATCH v2 18/18] cpufreq: scmi: add support for fast frequency switching

On 04-08-17, 15:31, Sudeep Holla wrote: > The cpufreq core provides option for drivers to implement fast_switch > callback which is invoked for frequency switching from interrupt context. > > This patch adds support for fast_switch callback in SCMI cpufreq driver > by making use of polling based

Re: [v3, 1/2] hwmon: (it87) Split out chip registers setting code on probe path

On Wed, Aug 02, 2017 at 01:06:23AM +0200, Maciej S. Szmigiero wrote: > This commit splits out chip registers setting code on probe path to > separate functions so they can be reused for setting the device properly > again when system resumes from suspend. > > While we are at it let's also make

Re: [v3, 1/2] hwmon: (it87) Split out chip registers setting code on probe path

On Wed, Aug 02, 2017 at 01:06:23AM +0200, Maciej S. Szmigiero wrote: > This commit splits out chip registers setting code on probe path to > separate functions so they can be reused for setting the device properly > again when system resumes from suspend. > > While we are at it let's also make

Re: [PATCH v2 0/4] Optimise 64-bit IOVA allocations

On 2017/8/9 11:24, Ganapatrao Kulkarni wrote: > On Wed, Aug 9, 2017 at 7:12 AM, Leizhen (ThunderTown) > wrote: >> >> >> On 2017/8/8 20:03, Ganapatrao Kulkarni wrote: >>> On Wed, Jul 26, 2017 at 4:47 PM, Leizhen (ThunderTown) >>> wrote:

Re: [PATCH v2 0/4] Optimise 64-bit IOVA allocations

On 2017/8/9 11:24, Ganapatrao Kulkarni wrote: > On Wed, Aug 9, 2017 at 7:12 AM, Leizhen (ThunderTown) > wrote: >> >> >> On 2017/8/8 20:03, Ganapatrao Kulkarni wrote: >>> On Wed, Jul 26, 2017 at 4:47 PM, Leizhen (ThunderTown) >>> wrote: On 2017/7/26 19:08, Joerg Roedel wrote:

Re: [PATCH v2 17/18] cpufreq: add support for CPU DVFS based on SCMI message protocol

On 04-08-17, 15:31, Sudeep Holla wrote: I don't think its the Microsoft exchange server which screwed up tabs and spaces, but you. > diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm > index 2011fec2d6ad..c34633855bc7 100644 > --- a/drivers/cpufreq/Kconfig.arm > +++

Re: [PATCH v2 17/18] cpufreq: add support for CPU DVFS based on SCMI message protocol

On 04-08-17, 15:31, Sudeep Holla wrote: I don't think its the Microsoft exchange server which screwed up tabs and spaces, but you. > diff --git a/drivers/cpufreq/Kconfig.arm b/drivers/cpufreq/Kconfig.arm > index 2011fec2d6ad..c34633855bc7 100644 > --- a/drivers/cpufreq/Kconfig.arm > +++

Re: [v2] hwmon: adt7475: constify attribute_group structures

yes, Sorry for noise. After rebase, it' was showing unchanged. On Wednesday 09 August 2017 07:35 AM, Guenter Roeck wrote: On Mon, Aug 07, 2017 at 03:06:29PM +0530, Arvind Yadav wrote: attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by

Re: [v2] hwmon: adt7475: constify attribute_group structures

yes, Sorry for noise. After rebase, it' was showing unchanged. On Wednesday 09 August 2017 07:35 AM, Guenter Roeck wrote: On Mon, Aug 07, 2017 at 03:06:29PM +0530, Arvind Yadav wrote: attribute_group are not supposed to change at runtime. All functions working with attribute_group provided by

Re: [PATCH 2/2] lib: add test for bitmap_parselist()

Hi Yury, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc4 next-20170808] [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/Yury-Norov/lib-make-bitmap_parselist

Re: [PATCH 2/2] lib: add test for bitmap_parselist()

Hi Yury, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc4 next-20170808] [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/Yury-Norov/lib-make-bitmap_parselist

Re: [PATCH] hv_set_ifconfig.sh double check before setting ip

From: Eduardo Otubo Date: Tue, 8 Aug 2017 15:53:45 +0200 > This patch fixes the behavior of the hv_set_ifconfig script when setting > the interface ip. Sometimes the interface has already been configured by > network daemon, in this case hv_set_ifconfig causes "RTNETLINK: file

Re: [PATCH] hv_set_ifconfig.sh double check before setting ip

From: Eduardo Otubo Date: Tue, 8 Aug 2017 15:53:45 +0200 > This patch fixes the behavior of the hv_set_ifconfig script when setting > the interface ip. Sometimes the interface has already been configured by > network daemon, in this case hv_set_ifconfig causes "RTNETLINK: file > exists error";

Re: [PATCH 33/35] wireless: realtek: rtl8192cu: constify usb_device_id

On 08/08/2017 11:05 AM, Arvind Yadav wrote: usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- Acked-by:

Re: [PATCH 33/35] wireless: realtek: rtl8192cu: constify usb_device_id

On 08/08/2017 11:05 AM, Arvind Yadav wrote: usb_device_id are not supposed to change at runtime. All functions working with usb_device_id provided by work with const usb_device_id. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- Acked-by: Larry Finger Thanks,

Re: [PATCH][next] net: phy: mdio-bcm-unimac: fix unsigned wrap-around when decrementing timeout

From: Colin King Date: Tue, 8 Aug 2017 10:52:32 +0100 > From: Colin Ian King > > Change post-decrement compare to pre-decrement to avoid an > unsigned integer wrap-around on timeout. This leads to the following > !timeout check to never to

Re: [PATCH][next] net: phy: mdio-bcm-unimac: fix unsigned wrap-around when decrementing timeout

From: Colin King Date: Tue, 8 Aug 2017 10:52:32 +0100 > From: Colin Ian King > > Change post-decrement compare to pre-decrement to avoid an > unsigned integer wrap-around on timeout. This leads to the following > !timeout check to never to be true so -ETIMEDOUT is never returned. > >

[PATCH] parse-maintainers: Add ability to specify filenames

parse-maintainers.pl is convenient, but currently hard-code the filenames that are used. Allow user-specified filenames to simplify the use of the script. Miscellanea: o Change the file permissions to 755 to the script is executable Signed-off-by: Joe Perches ---

[PATCH] parse-maintainers: Add ability to specify filenames

parse-maintainers.pl is convenient, but currently hard-code the filenames that are used. Allow user-specified filenames to simplify the use of the script. Miscellanea: o Change the file permissions to 755 to the script is executable Signed-off-by: Joe Perches --- scripts/parse-maintainers.pl

Re: [PATCH] net: phy: Use tab for indentation in Kconfig

From: Michal Simek Date: Tue, 8 Aug 2017 11:32:25 +0200 > Using tabs instead of space for indentaion > > Signed-off-by: Michal Simek This really isn't appropriate for the 'net' tree, it doesn't fix anything it just makes the spacing

Re: [PATCH] net: phy: Use tab for indentation in Kconfig

From: Michal Simek Date: Tue, 8 Aug 2017 11:32:25 +0200 > Using tabs instead of space for indentaion > > Signed-off-by: Michal Simek This really isn't appropriate for the 'net' tree, it doesn't fix anything it just makes the spacing consistent. Please respin this patch against net-next,

Re: [PATCH net] rds: Reintroduce statistics counting

From: Håkon Bugge Date: Tue, 8 Aug 2017 11:13:32 +0200 > In commit 7e3f2952eeb1 ("rds: don't let RDS shutdown a connection > while senders are present"), refilling the receive queue was removed > from rds_ib_recv(), along with the increment of >

Re: [PATCH net] rds: Reintroduce statistics counting

From: Håkon Bugge Date: Tue, 8 Aug 2017 11:13:32 +0200 > In commit 7e3f2952eeb1 ("rds: don't let RDS shutdown a connection > while senders are present"), refilling the receive queue was removed > from rds_ib_recv(), along with the increment of > s_ib_rx_refill_from_thread. > > Commit

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

Hi Marc, 2017-08-08 16:39 GMT+09:00 Marc Zyngier : > On 08/08/17 02:30, Masahiro Yamada wrote: >> Hi Marc, >> >> 2017-08-07 17:17 GMT+09:00 Marc Zyngier : >>> On 07/08/17 05:45, Masahiro Yamada wrote: Hi Marc, 2017-08-03 22:30

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

Hi Marc, 2017-08-08 16:39 GMT+09:00 Marc Zyngier : > On 08/08/17 02:30, Masahiro Yamada wrote: >> Hi Marc, >> >> 2017-08-07 17:17 GMT+09:00 Marc Zyngier : >>> On 07/08/17 05:45, Masahiro Yamada wrote: Hi Marc, 2017-08-03 22:30 GMT+09:00 Marc Zyngier : > On 03/08/17 13:52,

Re: [PATCH v9 2/2] mmc: dw_mmc-k3: add sd support for hi3660

On 2017/8/9 11:25, Li Wei wrote: Add sd card support for hi3660 soc Signed-off-by: Li Wei Signed-off-by: Chen Jun I did some comment for your v6 but probably you miss them. And it's still incorrect for your changelog.

Re: [PATCH v9 2/2] mmc: dw_mmc-k3: add sd support for hi3660

On 2017/8/9 11:25, Li Wei wrote: Add sd card support for hi3660 soc Signed-off-by: Li Wei Signed-off-by: Chen Jun I did some comment for your v6 but probably you miss them. And it's still incorrect for your changelog. -- Major changes

Re: [PATCH RFC v2 3/5] samples/bpf: Fix inline asm issues building samples on arm64

From: Joel Fernandes Date: Mon, 7 Aug 2017 18:20:49 -0700 > On Mon, Aug 7, 2017 at 11:28 AM, David Miller wrote: >> The amount of hellish hacks we are adding to deal with this is getting >> way out of control. > > I agree with you that hellish hacks are

Re: [PATCH RFC v2 3/5] samples/bpf: Fix inline asm issues building samples on arm64

From: Joel Fernandes Date: Mon, 7 Aug 2017 18:20:49 -0700 > On Mon, Aug 7, 2017 at 11:28 AM, David Miller wrote: >> The amount of hellish hacks we are adding to deal with this is getting >> way out of control. > > I agree with you that hellish hacks are being added which is why it > keeps

Re: [PATCH v1 2/6] fs: use on-stack-bio if backing device has BDI_CAP_SYNC capability

On Wed, Aug 09, 2017 at 10:51:13AM +0900, Minchan Kim wrote: > On Tue, Aug 08, 2017 at 06:29:04AM -0700, Matthew Wilcox wrote: > > On Tue, Aug 08, 2017 at 05:49:59AM -0700, Matthew Wilcox wrote: > > > + struct bio sbio; > > > + struct bio_vec sbvec; > > > > ... this needs to be sbvec[nr_pages],

Re: [PATCH v1 2/6] fs: use on-stack-bio if backing device has BDI_CAP_SYNC capability

On Wed, Aug 09, 2017 at 10:51:13AM +0900, Minchan Kim wrote: > On Tue, Aug 08, 2017 at 06:29:04AM -0700, Matthew Wilcox wrote: > > On Tue, Aug 08, 2017 at 05:49:59AM -0700, Matthew Wilcox wrote: > > > + struct bio sbio; > > > + struct bio_vec sbvec; > > > > ... this needs to be sbvec[nr_pages],

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

On Tue, Aug 08, 2017 at 05:12:03PM -0500, Rob Landley wrote: > If your rootfs has a size= in /proc/mounts it's tmpfs, ala: > > rootfs / rootfs rw,size=126564k,nr_inodes=31641 0 0 You're right, I have it and thought about it. Anyway the point is that it works transparently for me. Apparently

Re: INITRAMFS_SOURCE broken by 6e19eded3684dc184181093af3bff2ff440f5b53?

On Tue, Aug 08, 2017 at 05:12:03PM -0500, Rob Landley wrote: > If your rootfs has a size= in /proc/mounts it's tmpfs, ala: > > rootfs / rootfs rw,size=126564k,nr_inodes=31641 0 0 You're right, I have it and thought about it. Anyway the point is that it works transparently for me. Apparently

Re: [PATCH 2/2] lib: add test for bitmap_parselist()

Hi Yury, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc4 next-20170808] [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/Yury-Norov/lib-make-bitmap_parselist

Re: [PATCH 2/2] lib: add test for bitmap_parselist()

Hi Yury, [auto build test WARNING on linus/master] [also build test WARNING on v4.13-rc4 next-20170808] [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/Yury-Norov/lib-make-bitmap_parselist

[PATCH v9 1/2] mmc: dw_mmc: move controller reset before driver init

This commit modifies dw_mci_probe(), it moves reset assertion before drv_data->init(host) Some driver needs to access controller registers in its .init() ops. So, in order to make such access safe, we should do controller reset before .init() being called. Signed-off-by: Wei Li

[PATCH v9 1/2] mmc: dw_mmc: move controller reset before driver init

This commit modifies dw_mci_probe(), it moves reset assertion before drv_data->init(host) Some driver needs to access controller registers in its .init() ops. So, in order to make such access safe, we should do controller reset before .init() being called. Signed-off-by: Wei Li Signed-off-by:

[PATCH v9 2/2] mmc: dw_mmc-k3: add sd support for hi3660

Add sd card support for hi3660 soc Signed-off-by: Li Wei Signed-off-by: Chen Jun -- Major changes in v3: - solve review comments from Heiner Kallweit. *use the GENMASK and FIELD_PREP macros replace

[PATCH v9 2/2] mmc: dw_mmc-k3: add sd support for hi3660

Add sd card support for hi3660 soc Signed-off-by: Li Wei Signed-off-by: Chen Jun -- Major changes in v3: - solve review comments from Heiner Kallweit. *use the GENMASK and FIELD_PREP macros replace the bit shift operation. *use

Re: [PATCH v9 2/4] PCI: Disable PCIe Relaxed Ordering if unsupported

On Tue, Aug 08, 2017 at 09:22:39PM -0500, Bjorn Helgaas wrote: > On Sat, Aug 05, 2017 at 03:15:11PM +0800, Ding Tianhong wrote: > > When bit4 is set in the PCIe Device Control register, it indicates > > whether the device is permitted to use relaxed ordering. > > On some platforms using relaxed

Re: [PATCH v9 2/4] PCI: Disable PCIe Relaxed Ordering if unsupported

On Tue, Aug 08, 2017 at 09:22:39PM -0500, Bjorn Helgaas wrote: > On Sat, Aug 05, 2017 at 03:15:11PM +0800, Ding Tianhong wrote: > > When bit4 is set in the PCIe Device Control register, it indicates > > whether the device is permitted to use relaxed ordering. > > On some platforms using relaxed

Re: [PATCH v2 0/4] Optimise 64-bit IOVA allocations

On Wed, Aug 9, 2017 at 7:12 AM, Leizhen (ThunderTown) wrote: > > > On 2017/8/8 20:03, Ganapatrao Kulkarni wrote: >> On Wed, Jul 26, 2017 at 4:47 PM, Leizhen (ThunderTown) >> wrote: >>> >>> >>> On 2017/7/26 19:08, Joerg Roedel wrote: Hi

Re: [PATCH v2 0/4] Optimise 64-bit IOVA allocations

On Wed, Aug 9, 2017 at 7:12 AM, Leizhen (ThunderTown) wrote: > > > On 2017/8/8 20:03, Ganapatrao Kulkarni wrote: >> On Wed, Jul 26, 2017 at 4:47 PM, Leizhen (ThunderTown) >> wrote: >>> >>> >>> On 2017/7/26 19:08, Joerg Roedel wrote: Hi Robin. On Fri, Jul 21, 2017 at 12:41:57PM

[PATCH] modpost: simplify sec_name()

There is code duplication between sec_name() and sech_name(). Simplify sec_name() by re-using sech_name(). Also, move them up to remove the forward declaration of sec_name(). Signed-off-by: Masahiro Yamada --- scripts/mod/modpost.c | 27

[PATCH] modpost: simplify sec_name()

There is code duplication between sec_name() and sech_name(). Simplify sec_name() by re-using sech_name(). Also, move them up to remove the forward declaration of sec_name(). Signed-off-by: Masahiro Yamada --- scripts/mod/modpost.c | 27 +++ 1 file changed, 11

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

Hi Shaohua, After merging the md tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/md/raid5-cache.c: In function 'r5c_journal_mode_show': drivers/md/raid5-cache.c:2535:2: warning: ignoring return value of 'mddev_lock', declared with attribute

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

Hi Shaohua, After merging the md tree, today's linux-next build (powerpc ppc64_defconfig) produced this warning: drivers/md/raid5-cache.c: In function 'r5c_journal_mode_show': drivers/md/raid5-cache.c:2535:2: warning: ignoring return value of 'mddev_lock', declared with attribute

  1   2   3   4   5   6   7   8   9   10   >