Re: [PATCH] clk: imx6sx: disable unnecessary clocks during clock initialization

On Thu, May 17, 2018 at 01:00:47PM +0800, Anson Huang wrote: > Disable those unnecessary clocks during kernel boot up to save power, > those modules clock should be managed by modules driver in runtime. > > Signed-off-by: Anson Huang Acked-by: Shawn Guo

Re: [PATCH] clk: imx6sx: disable unnecessary clocks during clock initialization

On Thu, May 17, 2018 at 01:00:47PM +0800, Anson Huang wrote: > Disable those unnecessary clocks during kernel boot up to save power, > those modules clock should be managed by modules driver in runtime. > > Signed-off-by: Anson Huang Acked-by: Shawn Guo

Re: [PATCH] ARM: dts: imx51-zii-rdu1: cleanup eMMC node

On Wed, May 16, 2018 at 09:53:49AM +0300, Nikita Yushchenko wrote: > On RDU1, sdhc1 is used for eMMC, and that is 3.3V only. > > Thus configure device node not to probe it as SD/SDIO and not try 1.8V. > > Signed-off-by: Nikita Yushchenko Applied, thanks.

Re: [PATCH] ARM: dts: imx51-zii-rdu1: cleanup eMMC node

On Wed, May 16, 2018 at 09:53:49AM +0300, Nikita Yushchenko wrote: > On RDU1, sdhc1 is used for eMMC, and that is 3.3V only. > > Thus configure device node not to probe it as SD/SDIO and not try 1.8V. > > Signed-off-by: Nikita Yushchenko Applied, thanks.

Re: [PATCH] ARM: dts: vf610-zii-dev: enable vf610 builtin temp sensor

On Wed, May 16, 2018 at 09:39:21AM +0300, Nikita Yushchenko wrote: > Vybrid has single internal temperature sensor connected to both internal > ADC modules. > > vf610-zii-dev already has ADC0 enabled. Now, to get temperature sensor > captured by iio_hwmon driver, need to configure iio_hwmon node

Re: [PATCH] ARM: dts: vf610-zii-dev: enable vf610 builtin temp sensor

On Wed, May 16, 2018 at 09:39:21AM +0300, Nikita Yushchenko wrote: > Vybrid has single internal temperature sensor connected to both internal > ADC modules. > > vf610-zii-dev already has ADC0 enabled. Now, to get temperature sensor > captured by iio_hwmon driver, need to configure iio_hwmon node

Re: [PATCH] ARM: dts: imx7d: use operating-points-v2 for cpu

On Wed, May 16, 2018 at 12:48:17PM +0800, Anson Huang wrote: > This patch uses "operating-points-v2" instead of > "operating-points" to be more fit with cpufreq-dt > driver. > > Signed-off-by: Anson Huang > --- > arch/arm/boot/dts/imx7d.dtsi | 24 +++- >

Re: [PATCH] ARM: dts: imx7d: use operating-points-v2 for cpu

On Wed, May 16, 2018 at 12:48:17PM +0800, Anson Huang wrote: > This patch uses "operating-points-v2" instead of > "operating-points" to be more fit with cpufreq-dt > driver. > > Signed-off-by: Anson Huang > --- > arch/arm/boot/dts/imx7d.dtsi | 24 +++- > 1 file changed, 19

Re: [PATCH] Staging: rtl8192e: rtllib_tx: fix spelling issue.

On Sat, May 19, 2018 at 10:23:02PM +0200, Davide spataro wrote: > Fix a spelling warning from checkpatch.pl. > > Signed-off-by: Davide Spataro Doesn't match exactly with your "From:" line :( Yeah, picky, but it matters at times, sorry. Please fix and resend.

Re: [PATCH] Staging: rtl8192e: rtllib_tx: fix spelling issue.

On Sat, May 19, 2018 at 10:23:02PM +0200, Davide spataro wrote: > Fix a spelling warning from checkpatch.pl. > > Signed-off-by: Davide Spataro Doesn't match exactly with your "From:" line :( Yeah, picky, but it matters at times, sorry. Please fix and resend. thanks, greg k-h

Re: [PATCH] ARM: dts: imx7s-warp: remove unnecessary cpu regulator supply

On Tue, May 15, 2018 at 05:18:15PM +0800, Anson Huang wrote: > i.MX7S does NOT support CPU frequency scaling, so no > need to specify the CPU regulator supply. > > Signed-off-by: Anson Huang Applied, thanks.

Re: [PATCH 2/5] staging: lustre: Fix block comments style

On Wed, May 16, 2018 at 08:27:07PM +0200, Sabin Mihai Rapan wrote: > This patch fixes the checkpatch.pl warning: > > WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate > line > > Signed-off-by: Sabin Mihai Rapan > --- >

Re: [PATCH] ARM: dts: imx7s-warp: remove unnecessary cpu regulator supply

On Tue, May 15, 2018 at 05:18:15PM +0800, Anson Huang wrote: > i.MX7S does NOT support CPU frequency scaling, so no > need to specify the CPU regulator supply. > > Signed-off-by: Anson Huang Applied, thanks.

Re: [PATCH 2/5] staging: lustre: Fix block comments style

On Wed, May 16, 2018 at 08:27:07PM +0200, Sabin Mihai Rapan wrote: > This patch fixes the checkpatch.pl warning: > > WARNING:BLOCK_COMMENT_STYLE: Block comments use a trailing */ on a separate > line > > Signed-off-by: Sabin Mihai Rapan > --- >

Re: [PATCH 1/5] staging: lustre: Fix inclusion of local headers

On Wed, May 16, 2018 at 08:26:36PM +0200, Sabin Mihai Rapan wrote: > This patch fixes the checkpatch.pl error: > > ERROR:UAPI_INCLUDE: No #include in ...include/uapi/... should use a uapi/ path > prefix > > Signed-off-by: Sabin Mihai Rapan > --- >

Re: [PATCH 1/5] staging: lustre: Fix inclusion of local headers

On Wed, May 16, 2018 at 08:26:36PM +0200, Sabin Mihai Rapan wrote: > This patch fixes the checkpatch.pl error: > > ERROR:UAPI_INCLUDE: No #include in ...include/uapi/... should use a uapi/ path > prefix > > Signed-off-by: Sabin Mihai Rapan > --- >

Re: [PATCH V2] ARM: dts: imx7d: correct cpu supply name for voltage scaling

On Wed, May 16, 2018 at 10:25:48AM +0800, Anson Huang wrote: > Correct CPU supply name to meet cpufreq-dt driver's > requirement for voltage scaling. > > Signed-off-by: Anson Huang > Reviewed-by: Fabio Estevam Applied, thanks.

Re: [PATCH V2] ARM: dts: imx7d: correct cpu supply name for voltage scaling

On Wed, May 16, 2018 at 10:25:48AM +0800, Anson Huang wrote: > Correct CPU supply name to meet cpufreq-dt driver's > requirement for voltage scaling. > > Signed-off-by: Anson Huang > Reviewed-by: Fabio Estevam Applied, thanks.

Re: [PATCH] ARM: dts: imx51-zii-rdu1: limit usbh1 to full-speed

On Tue, May 15, 2018 at 11:45:02AM +0300, Nikita Yushchenko wrote: > On RDU1, imx51 usbh1 interface is either not used, or used via external > block that breaks USB2 signalling. > > To keep things working if high-speed device gets connected to that > block, use ChipIdea feature to limit port to

Re: [PATCH] ARM: dts: imx51-zii-rdu1: limit usbh1 to full-speed

On Tue, May 15, 2018 at 11:45:02AM +0300, Nikita Yushchenko wrote: > On RDU1, imx51 usbh1 interface is either not used, or used via external > block that breaks USB2 signalling. > > To keep things working if high-speed device gets connected to that > block, use ChipIdea feature to limit port to

[PATCH 2/2] rtc: st-lpc: add range

The RTC has a 64 bit counter. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-st-lpc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/rtc/rtc-st-lpc.c b/drivers/rtc/rtc-st-lpc.c index 2f1ef2c28740..df467ace397b 100644 ---

[PATCH 1/2] rtc: st-lpc: fix possible race condition

The IRQ is requested before the struct rtc is allocated and registered, but this struct is used in the IRQ handler. This may lead to a NULL pointer dereference. Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc before requesting the IRQ. Signed-off-by: Alexandre Belloni

[PATCH 2/2] rtc: st-lpc: add range

The RTC has a 64 bit counter. Signed-off-by: Alexandre Belloni --- drivers/rtc/rtc-st-lpc.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/rtc/rtc-st-lpc.c b/drivers/rtc/rtc-st-lpc.c index 2f1ef2c28740..df467ace397b 100644 --- a/drivers/rtc/rtc-st-lpc.c +++

[PATCH 1/2] rtc: st-lpc: fix possible race condition

The IRQ is requested before the struct rtc is allocated and registered, but this struct is used in the IRQ handler. This may lead to a NULL pointer dereference. Switch to devm_rtc_allocate_device/rtc_register_device to allocate the rtc before requesting the IRQ. Signed-off-by: Alexandre Belloni

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

output for "dmesg | mcelog --ascii" command related -> microcode: microcode updated early to revision 0x2a, date = 2018-01-18 Linux

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

output for "dmesg | mcelog --ascii" command related -> microcode: microcode updated early to revision 0x2a, date = 2018-01-18 Linux

Re: [PATCH 2/3] drm/rockchip: lvds: avoid duplicating drm_bridge_attach

Am Mittwoch, 2. Mai 2018, 09:40:24 CEST schrieb Peter Rosin: > drm_bridge_attach takes care of these assignments, so there is no need > to open-code them a second time. > > Signed-off-by: Peter Rosin applied to drm-misc-next Thanks Heiko

Re: [PATCH 2/3] drm/rockchip: lvds: avoid duplicating drm_bridge_attach

Am Mittwoch, 2. Mai 2018, 09:40:24 CEST schrieb Peter Rosin: > drm_bridge_attach takes care of these assignments, so there is no need > to open-code them a second time. > > Signed-off-by: Peter Rosin applied to drm-misc-next Thanks Heiko

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

ignore this "i did not find this message in a typical 4.9.x kernel" line On Sun, May 20, 2018 at 4:05 PM, Jeffrin Thalakkottoor wrote: > as far as i know , may be there is not much change in system behavior. > i just found these messages during boot time > i did not

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

ignore this "i did not find this message in a typical 4.9.x kernel" line On Sun, May 20, 2018 at 4:05 PM, Jeffrin Thalakkottoor wrote: > as far as i know , may be there is not much change in system behavior. > i just found these messages during boot time > i did not find this message in a

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

that system is normally not crashing. as far as i know, there are no other bad effects it happens during every boot.it is not a one time message. output for "sudo dmesg | grep -B 40 44919" command related

Re: PROBLEM: mce: [Hardware Error] from dmesg -l emerg

that system is normally not crashing. as far as i know, there are no other bad effects it happens during every boot.it is not a one time message. output for "sudo dmesg | grep -B 40 44919" command related

Re: [PATCH 06/14] net: sched: implement reference counted action release

On Sun 20 May 2018 at 06:22, Jiri Pirko wrote: > Sat, May 19, 2018 at 11:43:27PM CEST, marcelo.leit...@gmail.com wrote: >>On Mon, May 14, 2018 at 05:27:07PM +0300, Vlad Buslov wrote: >>... >>> @@ -1052,6 +1088,36 @@ static int tca_action_flush(struct net *net, struct >>>

Re: [PATCH 06/14] net: sched: implement reference counted action release

On Sun 20 May 2018 at 06:22, Jiri Pirko wrote: > Sat, May 19, 2018 at 11:43:27PM CEST, marcelo.leit...@gmail.com wrote: >>On Mon, May 14, 2018 at 05:27:07PM +0300, Vlad Buslov wrote: >>... >>> @@ -1052,6 +1088,36 @@ static int tca_action_flush(struct net *net, struct >>> nlattr *nla, >>>

Re: [reset-control] How to initialize hardware state with the shared reset line?

Hi, On Thu, May 10, 2018 at 11:16 AM, Masahiro Yamada wrote: [snip] > I may be missing something, but > one solution might be reset hogging on the > reset provider side. This allows us to describe > the initial state of reset lines in the reset controller. > > The

Re: [reset-control] How to initialize hardware state with the shared reset line?

Hi, On Thu, May 10, 2018 at 11:16 AM, Masahiro Yamada wrote: [snip] > I may be missing something, but > one solution might be reset hogging on the > reset provider side. This allows us to describe > the initial state of reset lines in the reset controller. > > The idea for "reset-hog" is

Re: [PATCH 02/14] net: sched: change type of reference and bind counters

On Sat 19 May 2018 at 21:04, Marcelo Ricardo Leitner wrote: > On Mon, May 14, 2018 at 05:27:03PM +0300, Vlad Buslov wrote: >> Change type of action reference counter to refcount_t. >> >> Change type of action bind counter to atomic_t. >> This type is used to allow

Re: [PATCH 02/14] net: sched: change type of reference and bind counters

On Sat 19 May 2018 at 21:04, Marcelo Ricardo Leitner wrote: > On Mon, May 14, 2018 at 05:27:03PM +0300, Vlad Buslov wrote: >> Change type of action reference counter to refcount_t. >> >> Change type of action bind counter to atomic_t. >> This type is used to allow decrementing bind counter

Re: [PATCH v2 2/2] iio:dac:ad5686: Add AD5681R/AD5682R/AD5683/AD5683R support

On Fri, 18 May 2018 18:23:34 +0300 Stefan Popa wrote: > The AD5681R/AD5682R/AD5683/AD5683R are a family of one channel DACs with > 12-bit, 14-bit and 16-bit precision respectively. The devices have either > no built-in reference, or built-in 2.5V reference. > > These

Re: [PATCH v2 2/2] iio:dac:ad5686: Add AD5681R/AD5682R/AD5683/AD5683R support

On Fri, 18 May 2018 18:23:34 +0300 Stefan Popa wrote: > The AD5681R/AD5682R/AD5683/AD5683R are a family of one channel DACs with > 12-bit, 14-bit and 16-bit precision respectively. The devices have either > no built-in reference, or built-in 2.5V reference. > > These devices are similar to

Re: [PATCH v5 0/2] usb: dwc2: fix isoc split in transfer issue

Am Freitag, 11. Mai 2018, 11:46:30 CEST schrieb William Wu: > This patch fix dma unaligned problem and data lost problem for > isoc split in transfer. > > Test on rk3288 platform, use an usb hs Hub (GL852G-12) and an usb > fs audio device (Plantronics headset) to capture and playback. > >

Re: [PATCH v5 0/2] usb: dwc2: fix isoc split in transfer issue

Am Freitag, 11. Mai 2018, 11:46:30 CEST schrieb William Wu: > This patch fix dma unaligned problem and data lost problem for > isoc split in transfer. > > Test on rk3288 platform, use an usb hs Hub (GL852G-12) and an usb > fs audio device (Plantronics headset) to capture and playback. > >

Re: [PATCH v2 1/2] iio:dac:ad5686: Add AD5691R/AD5692R/AD5693/AD5693R support

On Fri, 18 May 2018 18:22:50 +0300 Stefan Popa wrote: > The AD5691R/AD5692R/AD5693/AD5693R are a family of one channel DACs with > 12-bit, 14-bit and 16-bit precision respectively. The devices have either > no built-in reference, or built-in 2.5V reference. > > These

Re: [PATCH v2 1/2] iio:dac:ad5686: Add AD5691R/AD5692R/AD5693/AD5693R support

On Fri, 18 May 2018 18:22:50 +0300 Stefan Popa wrote: > The AD5691R/AD5692R/AD5693/AD5693R are a family of one channel DACs with > 12-bit, 14-bit and 16-bit precision respectively. The devices have either > no built-in reference, or built-in 2.5V reference. > > These devices are pretty similar

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

as far as i know , may be there is not much change in system behavior. i just found these messages during boot time i did not find this message in a typical 4.9.x kernel On Mon, May 14, 2018 at 4:04 AM, Andy Shevchenko wrote: > On Sun, May 13, 2018 at 5:20 PM,

Re: PROBLEM: "ACPI Error: Method parse/execution failed" and "ACPI BIOS Error (bug): Failure looking up" related

as far as i know , may be there is not much change in system behavior. i just found these messages during boot time i did not find this message in a typical 4.9.x kernel On Mon, May 14, 2018 at 4:04 AM, Andy Shevchenko wrote: > On Sun, May 13, 2018 at 5:20 PM, Jeffrin Thalakkottoor > wrote:

Re: [PATCH] iio: adc: stm32-dfsdm: include stm32-dfsdm-adc.h

On Tue, 15 May 2018 17:19:17 +0200 Fabrice Gasnier wrote: > Fix the following sparse warnings: > CHECK drivers/iio/adc/stm32-dfsdm-adc.c > symbol 'stm32_dfsdm_get_buff_cb' was not declared. Should it be static? > symbol 'stm32_dfsdm_release_buff_cb' was not declared.

Re: [PATCH] iio: adc: stm32-dfsdm: include stm32-dfsdm-adc.h

On Tue, 15 May 2018 17:19:17 +0200 Fabrice Gasnier wrote: > Fix the following sparse warnings: > CHECK drivers/iio/adc/stm32-dfsdm-adc.c > symbol 'stm32_dfsdm_get_buff_cb' was not declared. Should it be static? > symbol 'stm32_dfsdm_release_buff_cb' was not declared. Should it be static? >

[PATCH v1 0/5] Initial support of Trusted Foundations on Tegra30

Hello, This series of patches brings initial support of Trusted Foundations to Tegra30, that is to the consumer-grade Tegra30 devices which do not allow to easily replace the proprietary bootloader. Support is initial because this series implements only a proper CPU boot-up (main + secondary

[PATCH v1 0/5] Initial support of Trusted Foundations on Tegra30

Hello, This series of patches brings initial support of Trusted Foundations to Tegra30, that is to the consumer-grade Tegra30 devices which do not allow to easily replace the proprietary bootloader. Support is initial because this series implements only a proper CPU boot-up (main + secondary

[PATCH v1 2/5] ARM: trusted_foundations: Provide information about whether firmware is registered

Add a helper that provides information about whether Trusted Foundations firmware operations have been registered. Signed-off-by: Dmitry Osipenko --- arch/arm/firmware/trusted_foundations.c| 5 + arch/arm/include/asm/trusted_foundations.h | 7 +++ 2 files changed,

[PATCH v1 3/5] ARM: tegra: Setup L2 cache using Trusted Foundations firmware

On Tegra20/30 L2 cache must be initialized using firmware call if CPU is running in insecure mode. Initialize L2 cache and setup the outer-cache callbacks in early boot using the firmware API. Signed-off-by: Dmitry Osipenko --- arch/arm/mach-tegra/tegra.c | 15 +++

[PATCH v1 2/5] ARM: trusted_foundations: Provide information about whether firmware is registered

Add a helper that provides information about whether Trusted Foundations firmware operations have been registered. Signed-off-by: Dmitry Osipenko --- arch/arm/firmware/trusted_foundations.c| 5 + arch/arm/include/asm/trusted_foundations.h | 7 +++ 2 files changed, 12 insertions(+)

[PATCH v1 3/5] ARM: tegra: Setup L2 cache using Trusted Foundations firmware

On Tegra20/30 L2 cache must be initialized using firmware call if CPU is running in insecure mode. Initialize L2 cache and setup the outer-cache callbacks in early boot using the firmware API. Signed-off-by: Dmitry Osipenko --- arch/arm/mach-tegra/tegra.c | 15 +++ 1 file changed,

[PATCH v1 5/5] ARM: tegra: Always boot CPU in ARM-mode

CPU always jumps into the reset handler in ARM-mode from the Trusted Foundations firmware, hence make CPU to always jump into kernel in ARM-mode regardless of the firmware presence to support Thumb2 kernel + TF case. Signed-off-by: Dmitry Osipenko ---

[PATCH v1 4/5] ARM: tegra: Don't apply CPU erratas in insecure mode

CPU isn't allowed to touch secure registers while running under secure monitor. Hence skip applying CPU erratas in the reset handler if Trusted Foundations firmware presents. Signed-off-by: Dmitry Osipenko --- arch/arm/mach-tegra/reset-handler.S | 27

[PATCH v1 1/5] ARM: trusted_foundations: Implement L2 cache initialization callback

Implement L2 cache initialization firmware callback that should be invoked early in boot to enable cache HW. Signed-off-by: Dmitry Osipenko --- arch/arm/firmware/trusted_foundations.c | 23 +++ 1 file changed, 23 insertions(+) diff --git

[PATCH v1 5/5] ARM: tegra: Always boot CPU in ARM-mode

CPU always jumps into the reset handler in ARM-mode from the Trusted Foundations firmware, hence make CPU to always jump into kernel in ARM-mode regardless of the firmware presence to support Thumb2 kernel + TF case. Signed-off-by: Dmitry Osipenko --- arch/arm/mach-tegra/reset-handler.S | 1 +

[PATCH v1 4/5] ARM: tegra: Don't apply CPU erratas in insecure mode

CPU isn't allowed to touch secure registers while running under secure monitor. Hence skip applying CPU erratas in the reset handler if Trusted Foundations firmware presents. Signed-off-by: Dmitry Osipenko --- arch/arm/mach-tegra/reset-handler.S | 27 +++

[PATCH v1 1/5] ARM: trusted_foundations: Implement L2 cache initialization callback

Implement L2 cache initialization firmware callback that should be invoked early in boot to enable cache HW. Signed-off-by: Dmitry Osipenko --- arch/arm/firmware/trusted_foundations.c | 23 +++ 1 file changed, 23 insertions(+) diff --git

Re: [PATCH v2 4/5] kconfig: refactor ncurses package checks for building mconf

Hi Masahiro On Sun, May 20, 2018 at 05:16:52PM +0900, Masahiro Yamada wrote: > The mconf (or its infrastructure, lxdiaglog) depends on ncurses. > Move and rename check-lxdialog.sh to mconf-cfg.sh to make it work in > the same way as for qconf and gconf. > > According to Randy's report, we still

Re: [PATCH v2 4/5] kconfig: refactor ncurses package checks for building mconf

Hi Masahiro On Sun, May 20, 2018 at 05:16:52PM +0900, Masahiro Yamada wrote: > The mconf (or its infrastructure, lxdiaglog) depends on ncurses. > Move and rename check-lxdialog.sh to mconf-cfg.sh to make it work in > the same way as for qconf and gconf. > > According to Randy's report, we still

Re: [PATCH V3 2/5] X86: Hyper-V: Enable IPI enlightenments

://github.com/0day-ci/linux/commits/kys-linuxonhyperv-com/X86-Hyper-V-APIC-enlightenments/20180520-040432 config: x86_64-randconfig-s5-05201710 (attached as .config) compiler: gcc-7 (Debian 7.3.0-16) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors

Re: [PATCH V3 2/5] X86: Hyper-V: Enable IPI enlightenments

://github.com/0day-ci/linux/commits/kys-linuxonhyperv-com/X86-Hyper-V-APIC-enlightenments/20180520-040432 config: x86_64-randconfig-s5-05201710 (attached as .config) compiler: gcc-7 (Debian 7.3.0-16) 7.3.0 reproduce: # save the attached .config to linux build tree make ARCH=x86_64 All errors

Re: [PATCH v2 2/5] kconfig: refactor Qt package checks for building qconf

Hi Masahiro This commit (and the rest of the series) do wonders for the readability of the Makefile - nice work. Some nits below. On Sun, May 20, 2018 at 05:16:50PM +0900, Masahiro Yamada wrote: > Currently, the necessary package checks for building qconf is > surrounded by ifeq

Re: [PATCH v2 2/5] kconfig: refactor Qt package checks for building qconf

Hi Masahiro This commit (and the rest of the series) do wonders for the readability of the Makefile - nice work. Some nits below. On Sun, May 20, 2018 at 05:16:50PM +0900, Masahiro Yamada wrote: > Currently, the necessary package checks for building qconf is > surrounded by ifeq

Re: [PATCH] iio: tsl2583: correct values in integration_time_available

On Sat, 12 May 2018 20:20:39 -0400 Brian Masney wrote: > The times reported by the in_illuminance_integration_time_available > sysfs attribute are actually in milliseconds, not microseconds. This > patch corrects the times with the correct unit. > > Signed-off-by: Brian

Re: [PATCH] iio: tsl2583: correct values in integration_time_available

On Sat, 12 May 2018 20:20:39 -0400 Brian Masney wrote: > The times reported by the in_illuminance_integration_time_available > sysfs attribute are actually in milliseconds, not microseconds. This > patch corrects the times with the correct unit. > > Signed-off-by: Brian Masney Hi Brian, In

[GIT pull] x86 fixes for 4.17

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus An unfortunately larger set of fixes, but a large portion is selftests. Part of that pull-request was already sent with the core pull request

[GIT pull] x86 fixes for 4.17

Linus, please pull the latest x86-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-urgent-for-linus An unfortunately larger set of fixes, but a large portion is selftests. Part of that pull-request was already sent with the core pull request

[GIT pull] timer fix for 4.17

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus Address the for_each_cpu() oddity on UP kernels in the tick broadcast code which causes boot failures because the CPU0 bit is always

[GIT pull] timer fix for 4.17

Linus, please pull the latest timers-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-urgent-for-linus Address the for_each_cpu() oddity on UP kernels in the tick broadcast code which causes boot failures because the CPU0 bit is always

[GIT pull] scheduler fixes for 4.17

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus Three trivial fixlets for the scheduler: - Move print_rt_rq() and print_dl_rq() declarations to the right place - Make grub_reclaim()

[GIT pull] scheduler fixes for 4.17

Linus, please pull the latest sched-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched-urgent-for-linus Three trivial fixlets for the scheduler: - Move print_rt_rq() and print_dl_rq() declarations to the right place - Make grub_reclaim()

[GIT pull] ras fix for 4.17

Linus, please pull the latest ras-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-urgent-for-linus Address the regression with the new AMD SMCA code which issues an SMP function call from the early interrupt disabled region of CPU hotplug. To

[GIT pull] ras fix for 4.17

Linus, please pull the latest ras-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras-urgent-for-linus Address the regression with the new AMD SMCA code which issues an SMP function call from the early interrupt disabled region of CPU hotplug. To

[GIT pull] perf fixes for 4.17

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus Address issues on the perf tooling side: - Fix segfault when processing unknown threads in cs-etm - Fix "perf test inet_pton" on s390

[GIT pull] perf fixes for 4.17

Linus, please pull the latest perf-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git perf-urgent-for-linus Address issues on the perf tooling side: - Fix segfault when processing unknown threads in cs-etm - Fix "perf test inet_pton" on s390

[GIT pull] locking fixes for 4.17

Linus, please pull the latest locking-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-for-linus Two fixes to address shortcomings of the rwsem/percpu-rwsem lock debugging code which emits false positive warnings when the rwsem is

[GIT pull] locking fixes for 4.17

Linus, please pull the latest locking-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking-urgent-for-linus Two fixes to address shortcomings of the rwsem/percpu-rwsem lock debugging code which emits false positive warnings when the rwsem is

[PATCH] rcu: Speed up calling of RCU tasks callbacks

From: "Joel Fernandes (Google)" RCU tasks callbacks can take atleast 1 second before the callbacks are executed. This happens even if the hold-out tasks enter their quiescent states quickly. I noticed this when I was testing trampoline callback execution. To test the

[PATCH] rcu: Speed up calling of RCU tasks callbacks

From: "Joel Fernandes (Google)" RCU tasks callbacks can take atleast 1 second before the callbacks are executed. This happens even if the hold-out tasks enter their quiescent states quickly. I noticed this when I was testing trampoline callback execution. To test the trampoline freeing, I wrote

[GIT pull] efi fixes for 4.17

Linus, please pull the latest efi-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus Two EFI fixes: - Use explicitely sized type for the romimage pointer in the 32bit EFI protocol struct so a 64bit kernel does not expand

[GIT pull] efi fixes for 4.17

Linus, please pull the latest efi-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git efi-urgent-for-linus Two EFI fixes: - Use explicitely sized type for the romimage pointer in the 32bit EFI protocol struct so a 64bit kernel does not expand

Re: INFO: rcu detected stall in is_bpf_text_address

On Sat, May 19, 2018 at 11:57 PM, Eric Dumazet wrote: > SCTP experts, please take a look. > > On 05/19/2018 08:55 AM, syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:73fcb1a370c7 Merge branch 'akpm' (patches from Andrew) >> git

Re: INFO: rcu detected stall in is_bpf_text_address

On Sat, May 19, 2018 at 11:57 PM, Eric Dumazet wrote: > SCTP experts, please take a look. > > On 05/19/2018 08:55 AM, syzbot wrote: >> Hello, >> >> syzbot found the following crash on: >> >> HEAD commit:73fcb1a370c7 Merge branch 'akpm' (patches from Andrew) >> git tree: upstream >>

Re: [PATCH 4/5] kconfig: refactor ncurses package checks for building mconf

2018-05-20 3:02 GMT+09:00 Randy Dunlap : > On 05/17/18 21:52, Masahiro Yamada wrote: >> The mconf (or its infrastructure, lxdiaglog) depends on ncurses. >> check-lxdialog.sh has additional checks in case pkg-config is not >> available. However, qconf and gconf already rely

Re: [PATCH 4/5] kconfig: refactor ncurses package checks for building mconf

2018-05-20 3:02 GMT+09:00 Randy Dunlap : > On 05/17/18 21:52, Masahiro Yamada wrote: >> The mconf (or its infrastructure, lxdiaglog) depends on ncurses. >> check-lxdialog.sh has additional checks in case pkg-config is not >> available. However, qconf and gconf already rely on pkg-config to >>

[GIT pull] core fixes for 4.17

Linus, please pull the latest core-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-for-linus The pull request provides: - Unbreak the BPF compilation which got broken by the unconditional requirement of asm-goto, which is not

[GIT pull] core fixes for 4.17

Linus, please pull the latest core-urgent-for-linus git tree from: git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git core-urgent-for-linus The pull request provides: - Unbreak the BPF compilation which got broken by the unconditional requirement of asm-goto, which is not

[PATCH v2 5/5] kconfig: refactor ncurses package checks for building nconf

Building nconf requires ncurses, but its presence is not checked. Check and configure necessary packages by a shell script like the other GUI frontends. Signed-off-by: Masahiro Yamada --- Changes in v2: - Add fallback code in case distributions cannot find

[PATCH v2 5/5] kconfig: refactor ncurses package checks for building nconf

Building nconf requires ncurses, but its presence is not checked. Check and configure necessary packages by a shell script like the other GUI frontends. Signed-off-by: Masahiro Yamada --- Changes in v2: - Add fallback code in case distributions cannot find ncurses by pkg-config.

[PATCH v2 1/5] kbuild: do not display CHK for filechk

filechk displays two short logs; CHK for creating a temporary file, and UPD for really updating the target. IMHO, the build system can be quiet when the target file has not been updated. Signed-off-by: Masahiro Yamada --- Changes in v2: None

[PATCH v2 0/5] kconfig: refactor package checks for GUI frontends

Kconfig supports 4 GUI frontends. Each of them needs some support packages, but checks them differently: qconf, gconf: check packages in Makefile (pkg-config is required) mconf: lxdialog/check-lxdialog.sh nconf: needs ncurses, but its presence is not checked This series refactor the

[PATCH v2 1/5] kbuild: do not display CHK for filechk

filechk displays two short logs; CHK for creating a temporary file, and UPD for really updating the target. IMHO, the build system can be quiet when the target file has not been updated. Signed-off-by: Masahiro Yamada --- Changes in v2: None scripts/Kbuild.include | 1 - 1 file changed, 1

[PATCH v2 0/5] kconfig: refactor package checks for GUI frontends

Kconfig supports 4 GUI frontends. Each of them needs some support packages, but checks them differently: qconf, gconf: check packages in Makefile (pkg-config is required) mconf: lxdialog/check-lxdialog.sh nconf: needs ncurses, but its presence is not checked This series refactor the

[PATCH v2 4/5] kconfig: refactor ncurses package checks for building mconf

The mconf (or its infrastructure, lxdiaglog) depends on ncurses. Move and rename check-lxdialog.sh to mconf-cfg.sh to make it work in the same way as for qconf and gconf. According to Randy's report, we still need to carry the fallback code in case the pkg-config fails to find ncurses.

[PATCH v2 4/5] kconfig: refactor ncurses package checks for building mconf

The mconf (or its infrastructure, lxdiaglog) depends on ncurses. Move and rename check-lxdialog.sh to mconf-cfg.sh to make it work in the same way as for qconf and gconf. According to Randy's report, we still need to carry the fallback code in case the pkg-config fails to find ncurses.

[PATCH v2 3/5] kconfig: refactor GTK+ package checks for building gconf

Refactor the package checks for gconf in the same way as for qconf. Signed-off-by: Masahiro Yamada Tested-by: Randy Dunlap Acked-by: Randy Dunlap --- Changes in v2: None scripts/kconfig/Makefile | 43

[PATCH v2 3/5] kconfig: refactor GTK+ package checks for building gconf

Refactor the package checks for gconf in the same way as for qconf. Signed-off-by: Masahiro Yamada Tested-by: Randy Dunlap Acked-by: Randy Dunlap --- Changes in v2: None scripts/kconfig/Makefile | 43 +-- scripts/kconfig/gconf-cfg.sh | 23

<    1   2   3   4   5   6   7   >