[GIT PULL] HID

Linus, please pull from git://git.kernel.org/pub/scm/linux/kernel/git/jikos/hid.git for-linus to receive = - two cosmetic fixes from Daniel Axtens and Hans de Goede - fix for I2C command mismatch fix for cp2112 driver from Eudean Sun = Thanks.

Re: [PATCH 1/6] phy: sun4i-usb: add support for R40 USB PHY

在 2017年10月18日星期三 CST 下午7:46:08，Kishon Vijay Abraham I 写道： > On Wednesday 18 October 2017 05:12 PM, Maxime Ripard wrote: > > On Wed, Oct 18, 2017 at 05:09:00PM +0530, Kishon Vijay Abraham I wrote: > >> Hi, > >> > >> On Tuesday 10 October 2017 02:28 AM, Maxime Ripard wrote: > >>> On Sun, Oct 08,

Re: [PATCH v2] iio: adc: max9611: fix module auto-loading

> On Fri, 29 Dec 2017 17:30:39 +0200 > Andy Shevchenko wrote: >> Suggested-by: Andy Shevchenko >> I was not aware of this tag, that's what I wanted to write, thanks! On Fri, Dec 29, 2017 at 8:54 PM, Jonathan Cameron wrote:

[no subject]

Hello ; I have a proposal for you,kindly get back to me soon. Mrs Christy Walton.

Re: Graphics on thinkpad x270 after dock/undock works only for the first time (CPU pipe B FIFO underrun)

On Sat, 30 Dec 2017, Jiri Kosina wrote: > Seems like disabling RC6 on the kernel command line works this around, and > I can dock / undock several times in a row with the image always coming > up properly on the external display. > > On the first undock, the WARN_ONCE() below triggers, so I

[PATCH 2/2] ARM: imx: cpuidle-imx6q: configure CCM to RUN mode when CPU is active

There are two states in i.MX6Q cpuidle driver. state[1]: ARM WFI mode state[2]: i.MX6Q WAIT mode Take i.MX6DL as example, think out such a case: 1. CPU0/1 both run at normal mode 2. On CPU0, `sleep 1` is executed. And there are no workload on CPU1. 3. CPU0 first runs into state[2] and 'wfi'

[PATCH 1/2] ARM: imx: no unmask/mask GINT for WAIT_CLOCKED

WAIT_CLOCKED is for RUN mode, there is no need to unmask/mask IRQ32 in GPC. Signed-off-by: Peng Fan --- V1: This is to upstream patch: http://git.freescale.com/git/cgit.cgi/imx/linux-imx.git/commit/?h=imx_4.9.11_1.0.0_ga=0d980646ee068b92db71fd5e4e4efcbc33749cbd

Re: [PATCH] iio: adc: add driver for ti adc081s/adc101s/adc121s

On 12/29/2017 04:58 PM, Jonathan Cameron wrote: My comments are inline. I did not change patch, I am waiting comments from Lars-Peter and Michael On Mon, 25 Dec 2017 21:42:38 +0100 Milan Stevanovic wrote: +CC Lars-Peter and Michael to take a look and see if

[PATCH] arm64: Target aarch64elf emulation to allow bare-metal toolchains

This sets the LDFLAGS variable to target the aarch64elf emulation instead of aarch64linux, which is incompatible with bare-metal toolchains. This change allows the kernel to build with bare-metal toolchains again. Fixes: 3d6a7b99e3fa ("arm64: ensure the kernel is compiled for LP64") Cc:

Re: x86/pti: smp_processor_id() called while preemptible in resume-from-sleep

On 12/30/2017 07:30 AM, Dominik Brodowski wrote: > > native_cpu_up+0x447/0xa30: > kern_pcid at arch/x86/include/asm/tlbflush.h:105 > (inlined by) invalidate_user_asid at arch/x86/include/asm/tlbflush.h:342 > (inlined by) __native_flush_tlb at arch/x86/include/asm/tlbflush.h:351 > (inlined by)

[PATCH 3/5] kernel/printk: allow kmsg to be encrypted using public key encryption

From: Dan Aloni This commit enables the kernel to encrypt the free-form text that is generated by printk() before it is brought up to `dmesg` in userspace. The encryption is made using one of the trusted public keys which are kept built-in inside the kernel. These keys are

[PATCH 4/5] tools: add dmesg decryption program

From: Dan Aloni Example execution: dmesg | dmesg-decipher Signed-off-by: Dan Aloni --- tools/Makefile | 5 +- tools/kmsg/.gitignore | 1 + tools/kmsg/Makefile | 14 ++ tools/kmsg/dmesg-decipher.c | 316

[PATCH 2/5] certs: allow in-kernel access of trusted keys

From: Dan Aloni Signed-off-by: Dan Aloni --- certs/system_keyring.c| 56 ++- include/keys/system_keyring.h | 3 +++ 2 files changed, 58 insertions(+), 1 deletion(-) diff --git a/certs/system_keyring.c

[PATCH 5/5] docs: add dmesg encryption doc

From: Dan Aloni Signed-off-by: Dan Aloni --- Documentation/admin-guide/dmesg-encryption.rst | 77 ++ 1 file changed, 77 insertions(+) create mode 100644 Documentation/admin-guide/dmesg-encryption.rst diff --git

Re: 4.14.9 doesn't boot (regression)

On Sat, Dec 30, 2017 at 11:09:46AM -0600, Josh Poimboeuf wrote: > On Sat, Dec 30, 2017 at 11:45:13AM +0300, Alexander Tsoy wrote: > > В Пт, 29/12/2017 в 21:49 -0600, Josh Poimboeuf пишет: > > > On Fri, Dec 29, 2017 at 05:10:35PM -0700, Andy Lutomirski wrote: > > > > (Also, Josh, the oops code

[PATCH 1/5] crypto: fix memory leak in rsa-kcs1pad encryption

From: Dan Aloni The encryption mode of pkcs1pad never uses out_sg and out_buf, so there's no need to allocate the buffer, which presently is not even being freed. CC: Herbert Xu Signed-off-by: Dan Aloni ---

[PATCH 0/5] RFC: Public key encryption of dmesg by the kernel

From: Dan Aloni Hi All, There has been a lot of progress in recent times regarding the removal of sensitive information from dmesg (pointers, etc.), so I figured - why not encrypt it all? However, I have not found any existing discussions or references regarding this

Re: [RESEND,3/4] i2c: mpc: fix PORDEVSR2 mask for MPC8533/44

> /* >* Map and check POR Device Status Register 2 > - * (PORDEVSR2) at 0xE0014 > + * (PORDEVSR2) at 0xE0014. Note than while MPC8533 > + * and MPC8544 indicate SEC frequency ratio > +

Re: [RESEND, 4/4] i2c: mpc: always determine I2C clock prescaler at runtime

> static const struct of_device_id mpc_i2c_of_match[] = { > {.compatible = "mpc5200-i2c", .data = _i2c_data_52xx, }, > {.compatible = "fsl,mpc5200b-i2c", .data = _i2c_data_52xx, }, > {.compatible = "fsl,mpc5200-i2c", .data = _i2c_data_52xx, }, > {.compatible =

Re: x86/pti: smp_processor_id() called while preemptible in resume-from-sleep

On Sat, 30 Dec 2017, Dominik Brodowski wrote: > On Sat, Dec 30, 2017 at 04:03:07PM +0100, Thomas Gleixner wrote: > > On Sat, 30 Dec 2017, Dominik Brodowski wrote: > > > resume-from-sleep (mem/S3) on v4.15-rc5-149-g5aa90a845892 triggers the > > > following bug. If I boot with "pti=off", the kernel

Re: [RESEND, 1/4] i2c: mpc: get MPC8xxx I2C clock prescaler before using it in calculations

On Thu, Dec 07, 2017 at 05:20:00PM +0700, Arseny Solokha wrote: > Obtaining the actual I2C clock prescaler value in mpc_i2c_setup_8xxx() only > happens when the clock parameter is set to something other than > MPC_I2C_CLOCK_LEGACY. When the clock parameter is exactly > MPC_I2C_CLOCK_LEGACY, the

Re: [RESEND, 2/4] i2c: mpc: unify obtaining the MPC8533/44 I2C clock prescaler w/ MPC8xxx

On Thu, Dec 07, 2017 at 05:20:01PM +0700, Arseny Solokha wrote: > Commit 8ce795cb0c6b ("i2c: mpc: assign the correct prescaler from SVR") > introduced the common helper function for obtaining the actual clock > prescaler value for MPC85xx. However, getting the prescaler for MPC8544 > which depends

Re: x86/pti: smp_processor_id() called while preemptible in resume-from-sleep

On Sat, 30 Dec 2017, Dave Hansen wrote: > On 12/30/2017 07:30 AM, Dominik Brodowski wrote: > > > > native_cpu_up+0x447/0xa30: > > kern_pcid at arch/x86/include/asm/tlbflush.h:105 > > (inlined by) invalidate_user_asid at arch/x86/include/asm/tlbflush.h:342 > > (inlined by) __native_flush_tlb at

Re: [PATCH] USB: host: Use zeroing memory allocator rather than allocator/memset

On Sat, Dec 30, 2017 at 11:41:19AM -0500, Alan Stern wrote: > On Sat, 30 Dec 2017, Himanshu Jha wrote: > > > Use dma_zalloc_coherent for allocating zeroed > > memory and remove unnecessary memset function. > > > > Done using Coccinelle. > > Generated-by:

[PATCHv2 6/8] MIPS: Loongson64: cleanup all mach files to use SPDX Identifier

To reduce unnecessary license text. Signed-off-by: Jiaxun Yang --- arch/mips/loongson64/Makefile | 1 + arch/mips/loongson64/Platform | 1 + 2 files changed, 2 insertions(+) diff --git a/arch/mips/loongson64/Makefile b/arch/mips/loongson64/Makefile index

[PATCHv2 7/8] MIPS: Loongson64: cleanup all include files to use SPDX Identifier

To reduce unnecessary license text. Signed-off-by: Jiaxun Yang --- arch/mips/include/asm/mach-loongson64/cpu-feature-overrides.h | 5 ++--- arch/mips/include/asm/mach-loongson64/dma-coherence.h | 6 ++ arch/mips/include/asm/mach-loongson64/ec_kb3310b.h

Cleanup loongson64 mach to use SPDX copyright format v2

This patchset should based on "Add YeeLoong support v6" v1 -> v2 Fix the issue raised by Philippe to use the corret style

[PATCHv2 1/8] MIPS: Loongson64: cleanup all cs5536 files to use SPDX Identifier

To reduce unnecessary license text. Signed-off-by: Jiaxun Yang --- arch/mips/loongson64/common/cs5536/Makefile | 1 + arch/mips/loongson64/common/cs5536/cs5536_acc.c | 6 ++ arch/mips/loongson64/common/cs5536/cs5536_ehci.c | 6 ++

[PATCHv2 2/8] MIPS: Loongson64: cleanup all loongson common files to use SPDX Identifier

To reduce unnecessary license text. Signed-off-by: Jiaxun Yang --- arch/mips/loongson64/common/bonito-irq.c | 6 ++ arch/mips/loongson64/common/cmdline.c | 7 ++- arch/mips/loongson64/common/early_printk.c | 6 ++ arch/mips/loongson64/common/env.c

[PATCHv2 4/8] MIPS: Loongson64: cleanup all lemote-2f files to use SPDX Identifier

To reduce unnecessary license text. Signed-off-by: Jiaxun Yang --- arch/mips/loongson64/lemote-2f/Makefile | 1 + arch/mips/loongson64/lemote-2f/clock.c | 5 ++--- arch/mips/loongson64/lemote-2f/ec_kb3310b.c | 6 ++ arch/mips/loongson64/lemote-2f/irq.c

[PATCHv2 5/8] MIPS: Loongson64: cleanup all loongson-3 files to use SPDX Identifier

To reduce unnecessary license text. Signed-off-by: Jiaxun Yang --- arch/mips/loongson64/loongson-3/Makefile | 1 + arch/mips/loongson64/loongson-3/cop2-ex.c | 5 ++--- arch/mips/loongson64/loongson-3/numa.c | 7 ++-

[PATCHv2 3/8] MIPS: Loongson64: cleanup all fuloong-2e files to use SPDX Identifier

To reduce unnecessary license text. Signed-off-by: Jiaxun Yang --- arch/mips/loongson64/fuloong-2e/Makefile | 1 + arch/mips/loongson64/fuloong-2e/irq.c| 6 ++ arch/mips/loongson64/fuloong-2e/reset.c | 6 ++ 3 files changed, 5 insertions(+), 8 deletions(-)

Re: x86/pti: smp_processor_id() called while preemptible in resume-from-sleep

On Sat, Dec 30, 2017 at 10:20 AM, Thomas Gleixner wrote: > On Sat, 30 Dec 2017, Dominik Brodowski wrote: >> >> native_cpu_up+0x2f0/0xa30: >> invalidate_user_asid at arch/x86/include/asm/tlbflush.h:343 > > Ah, that makes sense. Missed that in the maze. > > What makes less sense

Review of KPTI patchset

Hi Thomas, Here is some feedback on the KPTI patchset. Sorry for not replying to the patch, I was not CC'd on the original email, and don't have it in my inbox. I notice that fill_ldt() sets the desc->type with "|= 1", whereas all other operations on the desc type are done with a type enum based

Re: [PATCH] b43: Replace mdelay with msleep in b43_radio_2057_init_post

On 12/30/2017 05:08 AM, Jia-Ju Bai wrote: b43_radio_2057_init_post is not called in an interrupt handler nor holding a spinlock. The function mdelay in it can be replaced with msleep, to reduce busy wait. Signed-off-by: Jia-Ju Bai checkpatch.pl reports the following

Re: [PATCH 2/5] certs: allow in-kernel access of trusted keys

On 12/30/2017 09:58 AM, Dan Aloni wrote: > From: Dan Aloni > > Signed-off-by: Dan Aloni > --- > certs/system_keyring.c| 56 > ++- > include/keys/system_keyring.h | 3 +++ > 2 files changed, 58

Re: x86/pti: smp_processor_id() called while preemptible in resume-from-sleep

On 12/30/2017 10:40 AM, Linus Torvalds wrote: > The __native_flush_tlb() function looks _very_ broken. ... > So I'd suggest moving the preempt_disable() up to the top of that > function, regardless of whether we could then remove that seemingly > stale TLB flush in that crazy >

4.15-rc5 was ath5k: WARN_ON in ieee80211_rx_napi()

Hi! I'm getting WARN_ON() on heavy wifi use, thinkpad T40p... Any ideas? BTW can we get rid of the ath5k: ath5k_hw_get_isr: ISR: 0x0080 IMR: 0x80081035 debugging print? Thanks, Pavel [0.00] Linux version

Re: [PATCH v2 5/9] arch: sh: migor: Use new renesas-ceu camera driver

-ci/linux/commits/Jacopo-Mondi/Renesas-Capture-Engine-Unit-CEU-V4L2-driver/20171230-212202 base: git://linuxtv.org/media_tree.git master config: sh-migor_defconfig (attached as .config) compiler: sh4-linux-gnu-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https://raw.githubusercontent.com

Re: [kernel-hardening] [PATCH 5/5] docs: add dmesg encryption doc

On Sat, Dec 30, 2017 at 12:58 PM, Dan Aloni wrote: > From: Dan Aloni > > Signed-off-by: Dan Aloni > --- > Documentation/admin-guide/dmesg-encryption.rst | 77 > ++ > 1 file changed, 77 insertions(+) > create

Re: [PATCH] USB: host: Use zeroing memory allocator rather than allocator/memset

On Sat, 30 Dec 2017, Himanshu Jha wrote: > Use dma_zalloc_coherent for allocating zeroed > memory and remove unnecessary memset function. > > Done using Coccinelle. > Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci > 0-day tested with no failures. > > Suggested-by: Luis R.

Re: [PATCH v2] fixdep: exit with error code in error branches of do_config_file()

2017-12-22 4:10 GMT+09:00 Lukas Bulwahn : > do_config_file() should exit with an error code, and not return if it fails > as then the error in do_config_file() would go unnoticed in the current > code and allow the build to continue. The exit with error code will make >

[PATCH 2/2] i2c: piix4: Use usleep_range()

The piix4 i2c driver is extremely slow. Replacing msleep() with usleep_range() increases its speed substantially. Signed-off-by: Guenter Roeck --- drivers/i2c/busses/i2c-piix4.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 1/2] i2c: piix4: Use request_muxed_region

Accesses to SB800_PIIX4_SMB_IDX can occur from multiple drivers. Use request_muxed_region() to ensure synchronization. Signed-off-by: Guenter Roeck --- drivers/i2c/busses/i2c-piix4.c | 50 ++ 1 file changed, 21 insertions(+), 29

Re: [PATCH 4.14 00/74] 4.14.10-stable review

On 29 December 2017 at 10:35, Milosz Wasilewski wrote: > On 29 December 2017 at 09:18, Greg Kroah-Hartman > wrote: >> On Thu, Dec 28, 2017 at 11:29:04AM +0530, Naresh Kamboju wrote: >>> On 27 December 2017 at 22:15, Greg Kroah-Hartman >>>

Re: 4.14.9 doesn't boot (regression)

On Sat, Dec 30, 2017 at 11:45:13AM +0300, Alexander Tsoy wrote: > В Пт, 29/12/2017 в 21:49 -0600, Josh Poimboeuf пишет: > > On Fri, Dec 29, 2017 at 05:10:35PM -0700, Andy Lutomirski wrote: > > > (Also, Josh, the oops code should have printed the contents of the > > > struct pt_regs at the top of

Re: [PATCH] sky2: Replace mdelay with msleep in sky2_vpd_wait

On Sat, 30 Dec 2017 19:09:47 +0800 Jia-Ju Bai wrote: > sky2_vpd_wait is not called in an interrupt handler nor holding a spinlock. > The function mdelay in it can be replaced with msleep, to reduce busy wait. > > Signed-off-by: Jia-Ju Bai > --- >

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

Hi Marcin, On Sat, Dec 30, 2017 at 05:34:23PM +0100, Marcin Wojtas wrote: > Yes, I already split the series and will send first one right away. I > will be followed by MDIO bus / PHY handling proposal, including the > bits related to phylink. I'm looking forward to your opinion on that > once

[PATCH v4 6/6] arm64: allwinner: a64: add HDMI regulator to all DTs' simplefb_hdmi

On usual A64 board design the power of HDMI controller is connected to DLDO1 of the AXP803 PMIC. If this regulator is shut down, the HDMI output will be blank. Therefore the simplefb driver should keep this regulator on. Add the regulator to all currently available A64 boards' simplefb_hdmi

[PATCH V2] ARM: imx: introduce imx_l2c310_write_sec

Some PL310 registers could only be wrote in secure world, so introduce imx_l2c310_write_sec to support Linux running in non-secure world configure PL310. Signed-off-by: Peng Fan Cc: Shawn Guo Cc: Sascha Hauer Cc: Fabio Estevam

Re: general protection fault in skb_segment

On Sat, Dec 30, 2017 at 7:54 PM, Willem de Bruijn wrote: >> So this is a packet socket writing something that apparently looks >> like an SCTP packet, is only 42 bytes long, but has GSO set in its >> virtio_net_hdr struct. >> >> It crashes in skb_segment seemingly

[PATCH v2 4/8] watchdog: JZ4740: Drop module remove function

When the watchdog was configured for nowayout, and after the userspace watchdog daemon closed the dev node without sending the magic character, unloading this module stopped the watchdog hardware, which was clearly a problem. Besides, unloading the module is not possible when the userspace

[PATCH v2 7/8] MIPS: qi_lb60: Enable the jz4740-wdt driver

The watchdog is an useful piece of hardware, so there's no reason not to enable it. This commit enables the Kconfig option in the qi_lb60 defconfig. Signed-off-by: Paul Cercueil --- arch/mips/configs/qi_lb60_defconfig | 2 ++ 1 file changed, 2 insertions(+) v2: No

[PATCH v2 8/8] MIPS: jz4740: Drop old platform reset code

This work is now performed by the watchdog driver directly. Signed-off-by: Paul Cercueil --- arch/mips/jz4740/reset.c | 31 --- 1 file changed, 31 deletions(-) v2: No change diff --git a/arch/mips/jz4740/reset.c b/arch/mips/jz4740/reset.c

[PATCH v2 2/8] watchdog: jz4740: Use devm_* functions

- Use devm_clk_get instead of clk_get - Use devm_watchdog_register_device instead of watchdog_register_device Signed-off-by: Paul Cercueil --- drivers/watchdog/jz4740_wdt.c | 27 --- 1 file changed, 8 insertions(+), 19 deletions(-) v2: No change

[PATCH v2 3/8] watchdog: JZ4740: Register a restart handler

The watchdog driver can restart the system by simply configuring the hardware for a timeout of 0 seconds. Signed-off-by: Paul Cercueil Reviewed-by: Guenter Roeck --- drivers/watchdog/jz4740_wdt.c | 9 + 1 file changed, 9 insertions(+) v2: No

[PATCH v2 6/8] MIPS: jz4780: dts: Fix watchdog node

- The previous node requested a memory area of 0x100 bytes, while the driver only manipulates four registers present in the first 0x10 bytes. - The driver requests for the "rtc" clock, but the previous node did not provide any. Signed-off-by: Paul Cercueil Reviewed-by:

Re: [PATCH V2] ARM: imx: introduce imx_l2c310_write_sec

On Sat, Dec 30, 2017 at 1:34 PM, Peng Fan wrote: > Some PL310 registers could only be wrote in secure world, so > introduce imx_l2c310_write_sec to support Linux running in > non-secure world configure PL310. > > Signed-off-by: Peng Fan > Cc: Shawn Guo

RE: [PATCH V2] ARM: imx: introduce imx_l2c310_write_sec

> -Original Message- > From: Philippe Ombredanne [mailto:pombreda...@nexb.com] > Sent: Saturday, December 30, 2017 10:17 PM > To: Peng Fan > Cc: Shawn Guo ; moderated list:ARM/FREESCALE IMX > / MXC ARM ARCHITECTURE

Re: 4.14.9 broke nvidia 384.98 kernel module

On Sat, Dec 30, 2017 at 01:36:33PM +0100, Hans-Peter Jansen wrote: > On Freitag, 29. Dezember 2017 10:23:56 Greg KH wrote: > > On Fri, Dec 29, 2017 at 02:08:08AM +0100, Hans-Peter Jansen wrote: > > > Hi Greg, > > > > > > I know, everybody hates NVidia and their proprietary stuff around here. > >

Re: [PATCH] x86/AMD: Apply Erratum 688 fix when BIOS

Hello Borris, thank you both. It was about time... Thanks for your effort though! Ingo is right here any modification must be advertised. The patch was sent on October but I didn't fell on it until... yesterday when I saw that it was routed for 3.16! [3.16,136/204] x86/cpu/AMD: Apply the

Re: [tip:x86/urgent] x86/microcode/intel: Disable late loading on model 79

I suppose it is for Broadwell EX(Expandable or Expensive, whichever you like). The patch description is wrong! Document 334165-010US describes erratum BDF90: Loading Microcode Updates or Executing an Authenticated Code Module May Result in a System Hang I have not read such a bug in the past.

[PATCH] qed: Use zeroing memory allocator than allocator/memset

Use dma_zalloc_coherent and vzalloc for allocating zeroed memory and remove unnecessary memset function. Done using Coccinelle. Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci 0-day tested with no failures. Suggested-by: Luis R. Rodriguez Signed-off-by:

[PATCH] IB/ocrdma: Use zeroing memory allocator than allocator/memset

Use dma_zalloc_coherent for allocating zeroed memory and remove unnecessary memset function. Done using Coccinelle. Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci 0-day tested with no failures. Suggested-by: Luis R. Rodriguez Signed-off-by: Himanshu Jha

[PATCH] USB: host: Use zeroing memory allocator rather than allocator/memset

Use dma_zalloc_coherent for allocating zeroed memory and remove unnecessary memset function. Done using Coccinelle. Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci 0-day tested with no failures. Suggested-by: Luis R. Rodriguez Signed-off-by: Himanshu Jha

[PATCH] ethernet/broadcom: Use zeroing memory allocator than allocator/memset

Use dma_zalloc_coherent for allocating zeroed memory and remove unnecessary memset function. Done using Coccinelle. Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci 0-day tested with no failures. Suggested-by: Luis R. Rodriguez Signed-off-by: Himanshu Jha

Re: About the try to remove cross-release feature entirely by Ingo

On Fri, Dec 29, 2017 at 10:16:24PM -0800, Matthew Wilcox wrote: > > I think this is a terminology problem. To me (and, I suspect Ted), a > waiter is a subject of a verb while a lock is an object. So Ted is asking > whether we have to classify the users, while I think you're saying we > have

[PATCH] scsi: megaraid: Use zeroing memory allocator than allocator/memset

Use pci_zalloc_consistent for allocating zeroed memory and remove unnecessary memset function. Done using Coccinelle. Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci 0-day tested with no failures. Suggested-by: Luis R. Rodriguez Signed-off-by: Himanshu Jha

[PATCH] brcmfmac: Use zeroing memory allocator than allocator/memset

Use dma_zalloc_coherent for allocating zeroed memory and remove unnecessary memset function. Done using Coccinelle. Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci 0-day tested with no failures. Suggested-by: Luis R. Rodriguez Signed-off-by: Himanshu Jha

[PATCH] scsi: fnic: Use eth_broadcast_addr instead of memset

Use eth_broadcasr_addr Networking API instead of memset to assign the broadcast address to the given address array. 0-day tested with no failures. Signed-off-by: Himanshu Jha --- drivers/scsi/fnic/fnic_scsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] tools: usb: usbip: fix fd leak in case of 'fread' failure

Fix possible resource leak: fd Signed-off-by: Elad Wexler --- tools/usb/usbip/libsrc/usbip_device_driver.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/tools/usb/usbip/libsrc/usbip_device_driver.c b/tools/usb/usbip/libsrc/usbip_device_driver.c

[PATCH] [media] pulse8-cec: Eliminate use of time_t and time_to_tm

Eliminate the use of time_t type and time_to_tm function as they are deprecated due to the 32-Bit interface which will overflow in year 2038. Therefore use the 64-Bit type interface which is time64_t and time64_to_tm instead to avoid y2038 overflow problem. 0-day tested without any issues!

Re: [PATCH v2 2/8] watchdog: jz4740: Use devm_* functions

On 12/30/2017 05:51 AM, Paul Cercueil wrote: - Use devm_clk_get instead of clk_get - Use devm_watchdog_register_device instead of watchdog_register_device Signed-off-by: Paul Cercueil Reviewed-by: Guenter Roeck --- drivers/watchdog/jz4740_wdt.c

Re: [PATCH v2 4/8] watchdog: JZ4740: Drop module remove function

On 12/30/2017 05:51 AM, Paul Cercueil wrote: When the watchdog was configured for nowayout, and after the userspace watchdog daemon closed the dev node without sending the magic character, unloading this module stopped the watchdog hardware, which was clearly a problem. Besides, unloading the

[PATCH] tools: usb: usbip_device_driver: prefer 'unsigned int' to 'unsigned'

Fixup a coding style issue Signed-off-by: Elad Wexler --- tools/usb/usbip/libsrc/usbip_device_driver.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/tools/usb/usbip/libsrc/usbip_device_driver.c b/tools/usb/usbip/libsrc/usbip_device_driver.c index

Re: [PATCH net-next 5/6] arm64: dts: marvell: mcbin: enable the fourth network interface

Hi Russell and Stefan, 2017-12-29 12:38 GMT+01:00 Russell King - ARM Linux : > On Fri, Dec 29, 2017 at 12:12:15PM +0100, Marcin Wojtas wrote: >> Hi Russell, >> >> I see that I misspelled your email address, hence the series remained >> unnoticed: >>

Re: [PATCH 01/33] clk_ops: change round_rate() to return unsigned long

FWIW, we had this problem some years ago with the Tegra CPU clock - then it was determined that a simpler solution was to have the determine_rate callback support unsigned long rates - so clock drivers that need to return rates higher than 2^31 can instead implement the determine_rate

[PATCH v4 3/6] clk: sunxi-ng: add support for Allwinner A64 DE2 CCU

Allwinner A64's DE2 needs to claim a section of SRAM (SRAM C) to work. Add support for it. Signed-off-by: Icenowy Zheng --- Changes in v4: - Use a struct to maintain both ccu desc and quirks as Chen-Yu Tsai suggested. drivers/clk/sunxi-ng/ccu-sun8i-de2.c | 117

[PATCH v4 5/6] arm64: allwinner: a64: add simplefb for A64 SoC

The A64 SoC features two display pipelines, one has a LCD output, the other has a HDMI output. Add support for simplefb for these pipelines on A64 SoC. Signed-off-by: Icenowy Zheng --- Changes in v4: - Dropped extra clocks. - Added labels to the SimpleFB device tree nodes as

[PATCH v4 2/6] dt-bindings: add binding for A64 DE2 CCU SRAM

A64's Display Engine 2.0 needs a section of SRAM (SRAM C) to be claimed, otherwise the whole DE2 memory zone cannot be accessed (kept to all 0). Add binding for this, in order to make the DE2 CCU able to claim the SRAM and enable access to the DE2 clock and reset registers. Acked-by: Rob Herring

[PATCH v4 0/6] Allwinner H3/H5/A64(DE2) SimpleFB support (Part 2)

This patchset is the remaining part of Allwinner DE2 SimpleFB support in Linux. Some H3/5-related patches are already applied into the sunxi tree. PATCH 1 adds the final SimpleFB nodes to the H3/H5 device tree. With it applied the SimpleFB will be usable on H3/H5. PATCH 2/3 are for the SRAM

[PATCH v4 1/6] ARM: sunxi: h3/h5: add simplefb nodes

The H3/H5 SoCs have a HDMI output and a TV Composite output. Add simplefb nodes for these outputs. Signed-off-by: Icenowy Zheng --- Changes in v4: - Dropped extra clocks (bus clocks and HDMI DDC clocks), only keep the clocks that are needed to display framebuffer to the

[PATCH v4 4/6] arm64: allwinner: a64: add DE2 CCU for A64 SoC

The A64 SoC features a DE2 CCU like the one in H5, but needs to claim a section of SRAM (SRAM C) to be accessed. Adds the device tree nodes for the SRAM controller and the DE2 CCU. Signed-off-by: Icenowy Zheng --- Changes in v3: - Fixed the alliwnner,sram property (the 1 after

Re: [PATCH v5 03/12] dt-bindings: display: sun4i-drm: Add LVDS properties

Hi Maxime, Dne četrtek, 21. december 2017 ob 12:02:29 CET je Maxime Ripard napisal(a): > Some clocks and resets supposed to drive the LVDS logic in the display > engine have been overlooked when the driver was first introduced. > > Add those additional resources to the binding, and we'll deal

Re: [PATCH V2 4/4] cpu_cooling: Drop static-power related stuff

On Tue, Dec 05, 2017 at 11:02:46AM +0530, Viresh Kumar wrote: > No one has used it for the last two and half years (since it was > introduced by commit c36cf0717631 ("thermal: cpu_cooling: implement the > power cooling device API")), get rid of it. That commit c36cf0717631 ("thermal: cpu_cooling:

Re: general protection fault in skb_segment

> So this is a packet socket writing something that apparently looks > like an SCTP packet, is only 42 bytes long, but has GSO set in its > virtio_net_hdr struct. > > It crashes in skb_segment seemingly on a NULL list_skb. > > (gdb) list *(skb_segment+0x2a4) > 0x8167cc24 is in skb_segment

Re: 4.14.9 broke nvidia 384.98 kernel module

On Freitag, 29. Dezember 2017 10:23:56 Greg KH wrote: > On Fri, Dec 29, 2017 at 02:08:08AM +0100, Hans-Peter Jansen wrote: > > Hi Greg, > > > > I know, everybody hates NVidia and their proprietary stuff around here. > > > > Anyway, I wanted to let you and followers of 4.14 know, that changes > >

Re: 4.14.9 doesn't boot (regression)

On 12/30/2017 02:13 AM, Alexander Tsoy wrote: > You are right, It's due to fstack-check enabled in gentoo's gcc spec. > "-fstack-check=no" in KBUILD_CFLAGS fixed this problem for me. =/ This made the issue go away : diff --git a/Makefile b/Makefile index ac8c441866b7..11a12947c550 100644 ---

Re: 4.14.9 doesn't boot (regression)

On Sat, 30 Dec 2017, Toralf Förster wrote: > This made the issue go away : > > diff --git a/Makefile b/Makefile > index ac8c441866b7..11a12947c550 100644 > --- a/Makefile > +++ b/Makefile > @@ -414,7 +414,7 @@ LINUXINCLUDE:= \ > > KBUILD_AFLAGS := -D__ASSEMBLY__ > KBUILD_CFLAGS :=

x86/pti: smp_processor_id() called while preemptible in resume-from-sleep

Dear all, resume-from-sleep (mem/S3) on v4.15-rc5-149-g5aa90a845892 triggers the following bug. If I boot with "pti=off", the kernel does not show this issue, and neither did kernels before pti was merged: [0.00] microcode: microcode updated early to revision 0x25, date = 2017-01-27 [

v4.15-rc5 warning: suspicious RCU usage in net/wireless/util.c:778

On Fri, Dec 22, 2017 at 08:20:12AM +0100, Dominik Brodowski wrote: > Dear all, > > once the (wifi) link becomes ready, the following warning is emitted on > mainline (v4.15-rc4-202-gead68f216110) on my notebook: ... and it is still present as of v4.15-rc5-149-g5aa90a845892 > [ 22.770422]

[PATCH v2 1/8] watchdog: JZ4740: Disable clock after stopping counter

Previously, the clock was disabled first, which makes the watchdog component insensitive to register writes. Signed-off-by: Paul Cercueil Reviewed-by: Guenter Roeck --- drivers/watchdog/jz4740_wdt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH v2 5/8] MIPS: jz4740: dts: Add bindings for the jz4740-wdt driver

Also remove the watchdog platform_device from platform.c, since it wasn't used anywhere anyway. Signed-off-by: Paul Cercueil --- arch/mips/boot/dts/ingenic/jz4740.dtsi | 8 arch/mips/jz4740/platform.c| 16 2 files changed, 8

Re: x86/pti: smp_processor_id() called while preemptible in resume-from-sleep

On Sat, 30 Dec 2017, Dominik Brodowski wrote: > Dear all, > > resume-from-sleep (mem/S3) on v4.15-rc5-149-g5aa90a845892 triggers the > following bug. If I boot with "pti=off", the kernel does not show this > issue, and neither did kernels before pti was merged: > > [ 39.951703] ACPI:

[PATCH 0/3] axp20x backup battery charging

This series introduces support for axp20x backup battery charging, with a dedicated device-tree property. I wondered whether to include this in a power-supply driver or not. Since it does not, in fact, supply power to the whole system and because no status changes over time, I thought it would be

[PATCH 1/3] dt-bindings: mfd: axp20x: Document backup battery charging property

This adds documentation for the "backup" property of the axp20x driver, that controls the charging mechanism for the backup battery on axp20x. Signed-off-by: Paul Kocialkowski diff --git a/Documentation/devicetree/bindings/mfd/axp20x.txt

[PATCH 2/3] mfd: axp20x: Add support for backup battery charging

This adds support for backup battery charging for axp20x PMICs, that is configured through a dedicated device-tree property. It supports 4 different charging voltages and as many charging currents. This is especially useful to allow the on-chip RTC (on the SoC side) to be powered when the rest of

[PATCH 3/3] ARM: dts: sun7i: lamobo-r1: Add backup battery charging property

This adds the axp20x backup property to the lamobo-r1 device-tree, that allows charging the backup battery attached to its AXP209. It is especially useful since the battery is used for the RTC module. Signed-off-by: Paul Kocialkowski diff --git

[PATCH 8/9] scsi: bfa: Use zeroing allocator rather than allocator/memset

Use vzalloc instead of vmalloc followed by memset 0. Generated-by: scripts/coccinelle/api/alloc/kzalloc-simple.cocci Suggested-by: Luis R. Rodriguez Signed-off-by: Himanshu Jha --- drivers/scsi/bfa/bfad.c | 3 +--

Re: stable-rc build: 0 warnings 7 failures (stable-rc/v3.18.90-13-g444eb56)

On Fri, Dec 29, 2017 at 10:19:14AM +0100, gregkh wrote: > On Thu, Dec 28, 2017 at 09:39:22AM +0100, Arnd Bergmann wrote: > > On Thu, Dec 28, 2017 at 8:38 AM, Olof's autobuilder wrote: > > > Here are the build results from automated periodic testing. > > > > > > The tree being

  1   2   3   4   5   >