[tip:x86/urgent] x86/timers: Move simple_udelay_calibration past init_hypervisor_platform

Commit-ID: 702644ec1cab10ffefcebb4060d4da46d4ef2c7f Gitweb: http://git.kernel.org/tip/702644ec1cab10ffefcebb4060d4da46d4ef2c7f Author: Jan Kiszka AuthorDate: Wed, 24 May 2017 20:04:41 +0200 Committer: Thomas Gleixner CommitDate: Fri, 26 May

[tip:x86/urgent] x86/timers: Move simple_udelay_calibration past init_hypervisor_platform

Commit-ID: 702644ec1cab10ffefcebb4060d4da46d4ef2c7f Gitweb: http://git.kernel.org/tip/702644ec1cab10ffefcebb4060d4da46d4ef2c7f Author: Jan Kiszka AuthorDate: Wed, 24 May 2017 20:04:41 +0200 Committer: Thomas Gleixner CommitDate: Fri, 26 May 2017 13:04:09 +0200 x86/timers: Move

RE: [PATCH v2] PCI: Add ATS-disable quirk for AMD Stoney GPUs

> -Original Message- > From: Joerg Roedel [mailto:jroe...@suse.de] > Sent: Wednesday, May 24, 2017 4:45 AM > To: Deucher, Alexander > Cc: 'David Woodhouse'; 'Joerg Roedel'; Bjorn Helgaas; linux- > p...@vger.kernel.org; linux-kernel@vger.kernel.org; Daniel Drake; Samuel > Sieb > Subject:

RE: [PATCH v2] PCI: Add ATS-disable quirk for AMD Stoney GPUs

> -Original Message- > From: Joerg Roedel [mailto:jroe...@suse.de] > Sent: Wednesday, May 24, 2017 4:45 AM > To: Deucher, Alexander > Cc: 'David Woodhouse'; 'Joerg Roedel'; Bjorn Helgaas; linux- > p...@vger.kernel.org; linux-kernel@vger.kernel.org; Daniel Drake; Samuel > Sieb > Subject:

Re: [PATCH 0/8] i2c: refactor core and break out blocks

On Fri, 26 May 2017, Wolfram Sang wrote: > Yes, I wanted to do this for years now... The I2C core became a huge > monolithic > blob getting harder and harder to maintain. This series breaks out some > functional parts into seperate files. This makes the code easier to handle

Re: [PATCH 0/8] i2c: refactor core and break out blocks

On Fri, 26 May 2017, Wolfram Sang wrote: > Yes, I wanted to do this for years now... The I2C core became a huge > monolithic > blob getting harder and harder to maintain. This series breaks out some > functional parts into seperate files. This makes the code easier to handle > because of the

[GIT][PULL] Improvements to max3421-hcd driver

The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are available in the git repository at: https://github.com/AlexanderAmelkin/linux-wandboard.git tags/max3421-improvements-1 for you to fetch changes up to

[GIT][PULL] Improvements to max3421-hcd driver

The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are available in the git repository at: https://github.com/AlexanderAmelkin/linux-wandboard.git tags/max3421-improvements-1 for you to fetch changes up to

Re: [PATCH 00/21] liblockdep fixes for v4.12

On Fri, May 26, 2017 at 01:21:51PM +0200, Ingo Molnar wrote: > > * Levin, Alexander (Sasha Levin) wrote: > > > Right, and as you can see from this patchset where we added to > > tools/include/ when needed and removed from lib/lockdep/uinclude, > > liblockdep is

Re: [PATCH 00/21] liblockdep fixes for v4.12

On Fri, May 26, 2017 at 01:21:51PM +0200, Ingo Molnar wrote: > > * Levin, Alexander (Sasha Levin) wrote: > > > Right, and as you can see from this patchset where we added to > > tools/include/ when needed and removed from lib/lockdep/uinclude, > > liblockdep is slowly creeping the "right" way.

Applied "ASoC: wm_adsp: Fix typo in algorithm list warning message" to the asoc tree

The patch ASoC: wm_adsp: Fix typo in algorithm list warning message has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Applied "ASoC: wm_adsp: Fix typo in algorithm list warning message" to the asoc tree

The patch ASoC: wm_adsp: Fix typo in algorithm list warning message has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours)

Re: [PATCH V2] x86/ftrace: Make sure that ftrace trampolines are not RWX

Heiko Carstens writes: > On Fri, May 26, 2017 at 09:03:13AM +0200, Thomas Gleixner wrote: >> > It seems like it really should. That would put it in a single place >> > and avoid this mistake again in the future. Does module_memfree() have >> > access to the allocation

Re: [PATCH V2] x86/ftrace: Make sure that ftrace trampolines are not RWX

Heiko Carstens writes: > On Fri, May 26, 2017 at 09:03:13AM +0200, Thomas Gleixner wrote: >> > It seems like it really should. That would put it in a single place >> > and avoid this mistake again in the future. Does module_memfree() have >> > access to the allocation size, or does that need to

Applied "spi: st-ssc4: whitespace cleanup" to the spi tree

The patch spi: st-ssc4: whitespace cleanup has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the

Applied "spi: st-ssc4: whitespace cleanup" to the spi tree

The patch spi: st-ssc4: whitespace cleanup has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the

Applied "regulator: tps65917: Add support for SMPS12" to the regulator tree

The patch regulator: tps65917: Add support for SMPS12 has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: omap2-mcspi: remove redundant check for error status" to the spi tree

The patch spi: omap2-mcspi: remove redundant check for error status has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "regulator: tps65917: Add support for SMPS12" to the regulator tree

The patch regulator: tps65917: Add support for SMPS12 has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "spi: omap2-mcspi: remove redundant check for error status" to the spi tree

The patch spi: omap2-mcspi: remove redundant check for error status has been applied to the spi tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

[PATCH 5/5] efi/bgrt: Skip efi_bgrt_init in case of non-efi boot

From: Dave Young Sabrina Dubroca reported an early panic below, it was introduced by commit 7b0a911478c7 ("efi/x86: Move the EFI BGRT init code to early init code"). The cause is on this machine even for legacy boot firmware still provide the ACPI BGRT table which should be

[PATCH 5/5] efi/bgrt: Skip efi_bgrt_init in case of non-efi boot

From: Dave Young Sabrina Dubroca reported an early panic below, it was introduced by commit 7b0a911478c7 ("efi/x86: Move the EFI BGRT init code to early init code"). The cause is on this machine even for legacy boot firmware still provide the ACPI BGRT table which should be EFI only. Thus the

[PATCH 1/5] efi: Don't issue error message when booted under xen

From: Juergen Gross When booted as Xen dom0 there won't be an EFI memmap allocated. Avoid issuing an error message in this case: [0.144079] efi: Failed to allocate new EFI memmap Signed-off-by: Juergen Gross Cc: "H. Peter Anvin" Cc: Ingo

Re: [PATCH 4/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator

On Fri, May 26, 2017 at 02:35:16PM +0800, Guodong Xu wrote: Overall this driver needs quite a lot of modernization, it's at least a couple of years out of date in how it's using the framework - there's barely any use of helpers. It does look like it should be fairly easy to get it up to date

[PATCH 1/5] efi: Don't issue error message when booted under xen

From: Juergen Gross When booted as Xen dom0 there won't be an EFI memmap allocated. Avoid issuing an error message in this case: [0.144079] efi: Failed to allocate new EFI memmap Signed-off-by: Juergen Gross Cc: "H. Peter Anvin" Cc: Ingo Molnar Cc: Thomas Gleixner Cc: Ard Biesheuvel

Re: [PATCH 4/6] regulator: hi6421v530: add driver for hi6421v530 voltage regulator

On Fri, May 26, 2017 at 02:35:16PM +0800, Guodong Xu wrote: Overall this driver needs quite a lot of modernization, it's at least a couple of years out of date in how it's using the framework - there's barely any use of helpers. It does look like it should be fairly easy to get it up to date

[PATCH 4/5] x86/efi: Correct ident mapping of efi old_map when kalsr enabled

From: Baoquan He For EFI with 'efi=old_map' kernel option specified, Kernel will panic when kaslr is enabled. The back trace is: BUG: unable to handle kernel paging request at 7febd57e IP: 0x7febd57e PGD 1025a067 PUD 0 Oops: 0010 [#1] SMP [ ... ] Call Trace: ?

[PATCH 4/5] x86/efi: Correct ident mapping of efi old_map when kalsr enabled

From: Baoquan He For EFI with 'efi=old_map' kernel option specified, Kernel will panic when kaslr is enabled. The back trace is: BUG: unable to handle kernel paging request at 7febd57e IP: 0x7febd57e PGD 1025a067 PUD 0 Oops: 0010 [#1] SMP [ ... ] Call Trace: ? efi_call+0x58/0x90 ?

[PATCH 3/5] x86/efi: Disable runtime services on kexec kernel if booted with efi=old_map

From: Sai Praneeth Booting kexec kernel with "efi=old_map" in kernel command line hits kernel panic as shown below. BUG: unable to handle kernel paging request at 88007fe78070 IP: virt_efi_set_variable.part.7+0x63/0x1b0 PGD 7ea28067 PUD 7ea2b067 PMD

[PATCH 3/5] x86/efi: Disable runtime services on kexec kernel if booted with efi=old_map

From: Sai Praneeth Booting kexec kernel with "efi=old_map" in kernel command line hits kernel panic as shown below. BUG: unable to handle kernel paging request at 88007fe78070 IP: virt_efi_set_variable.part.7+0x63/0x1b0 PGD 7ea28067 PUD 7ea2b067 PMD 7ea2d067 PTE 0 [...] Call Trace:

[GIT PULL 0/5] EFI urgent fixes

Hi folks, Please pull the following fixes. There are patches that resolve a few boot crashes and some minor build and boot log cleanups. The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are available in the git repository

[GIT PULL 0/5] EFI urgent fixes

Hi folks, Please pull the following fixes. There are patches that resolve a few boot crashes and some minor build and boot log cleanups. The following changes since commit 08332893e37af6ae779367e78e444f8f9571511d: Linux 4.12-rc2 (2017-05-21 19:30:23 -0700) are available in the git repository

[PATCH 2/5] efi: Remove duplicate 'const' specifiers

From: Arnd Bergmann gcc-7 shows a harmless warning: drivers/firmware/efi/libstub/secureboot.c:19:27: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier] static const efi_char16_t const efi_SecureBoot_name[] = {

[PATCH 2/5] efi: Remove duplicate 'const' specifiers

From: Arnd Bergmann gcc-7 shows a harmless warning: drivers/firmware/efi/libstub/secureboot.c:19:27: error: duplicate 'const' declaration specifier [-Werror=duplicate-decl-specifier] static const efi_char16_t const efi_SecureBoot_name[] = { drivers/firmware/efi/libstub/secureboot.c:22:27:

Re: [PATCH V2] ARM: dts: rockchip:add sd card support for firefly reload board

On 26/05/17 08:07, Eddie Cai wrote: > firefly reload board not support sd card yet. so support it. I'm confused... According to pictures and the schematic the microSD socket and vcc_sd supply are on the baseboard, not the core module, and these nodes already exist in rk3288-firefly-reload.dts :/

Re: [PATCH V2] ARM: dts: rockchip:add sd card support for firefly reload board

On 26/05/17 08:07, Eddie Cai wrote: > firefly reload board not support sd card yet. so support it. I'm confused... According to pictures and the schematic the microSD socket and vcc_sd supply are on the baseboard, not the core module, and these nodes already exist in rk3288-firefly-reload.dts :/

[PATCH 3/3] usb: max3421-hcd: Remove function name from dev_dbg calls

NOTE: Please don't use the plain text here as a patch because it most probably is corrupted by my webmail client. Attached is a copy of the following text guaranteed to have correct tabs/spaces. - From b9a7559d24c0b2cb6e69124d861a943f79272681 Mon Sep 17 00:00:00 2001

[PATCH 3/3] usb: max3421-hcd: Remove function name from dev_dbg calls

NOTE: Please don't use the plain text here as a patch because it most probably is corrupted by my webmail client. Attached is a copy of the following text guaranteed to have correct tabs/spaces. - From b9a7559d24c0b2cb6e69124d861a943f79272681 Mon Sep 17 00:00:00 2001

Re: [PATCH v3] scripts/gdb: make lx-dmesg command work (reliably)

On 2017-05-26 13:22, André Draszik wrote: > lx-dmesg needs access to the log_buf symbol from printk.c. > Unfortunately, the symbol log_buf also exists in BPF's > verifier.c and hence gdb can pick one or the other. If it > happens to pick BPF's log_buf, lx-dmesg doesn't work: > > (gdb) lx-dmesg

Re: [PATCH v3] scripts/gdb: make lx-dmesg command work (reliably)

On 2017-05-26 13:22, André Draszik wrote: > lx-dmesg needs access to the log_buf symbol from printk.c. > Unfortunately, the symbol log_buf also exists in BPF's > verifier.c and hence gdb can pick one or the other. If it > happens to pick BPF's log_buf, lx-dmesg doesn't work: > > (gdb) lx-dmesg

[PATCH 2/3] usb: max3421-hcd: Fix crash on the driver removal

NOTE: Please don't use the plain text here as a patch because it most probably is corrupted by my webmail client. Attached is a copy of the following text guaranteed to have correct tabs/spaces. - From 8c4c65d3892df3721474023836216a02e03fb23e Mon Sep 17 00:00:00 2001

Memory corruption kernel issue (potentially exploitable), request for help

Dear Kernel hackers, I have a machine with a self-built, non-tainted kernel, which exhibits memory corruption as soon as I execute while true; do cat /proc/self/net/dev > /dev/null; done as normal user. I am running 4.11.3 (almost vanilla, only Gentoo patches in) on mostly standard hardware

[PATCH 2/3] usb: max3421-hcd: Fix crash on the driver removal

NOTE: Please don't use the plain text here as a patch because it most probably is corrupted by my webmail client. Attached is a copy of the following text guaranteed to have correct tabs/spaces. - From 8c4c65d3892df3721474023836216a02e03fb23e Mon Sep 17 00:00:00 2001

Memory corruption kernel issue (potentially exploitable), request for help

Dear Kernel hackers, I have a machine with a self-built, non-tainted kernel, which exhibits memory corruption as soon as I execute while true; do cat /proc/self/net/dev > /dev/null; done as normal user. I am running 4.11.3 (almost vanilla, only Gentoo patches in) on mostly standard hardware

Re: [PATCH 7/7] DWARF: add the config option

On 05/26/2017, 08:54 AM, Jiri Slaby wrote: > On 05/19/2017, 11:35 PM, Josh Poimboeuf wrote: >> >> https://github.com/jpoimboe/linux/blob/undwarf/arch/x86/kernel/unwind_undwarf.c > > JFYI, it crashes in sha1_transform_avx due to crypto changes. You > perhaps missed that this beast uses ebp (not

Re: [PATCH 7/7] DWARF: add the config option

On 05/26/2017, 08:54 AM, Jiri Slaby wrote: > On 05/19/2017, 11:35 PM, Josh Poimboeuf wrote: >> >> https://github.com/jpoimboe/linux/blob/undwarf/arch/x86/kernel/unwind_undwarf.c > > JFYI, it crashes in sha1_transform_avx due to crypto changes. You > perhaps missed that this beast uses ebp (not

[PATCH 1/3] usb: max3421-hcd: Add devicetree support to the driver

NOTE: Please don't use the plain text here as a patch because it most probably is corrupted by my webmail client. Attached is a copy of the following text guaranteed to have correct tabs/spaces. - Before this patch the max3421-hcd driver could only use statically

Re: linux-next: build warning after merge of the akpm-current tree

On 05/26/2017 05:16 AM, Jeff Layton wrote: > On Fri, 2017-05-26 at 12:43 +1000, Stephen Rothwell wrote: >> Hi Andrew, >> >> After merging the akpm-current tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this warning: >> >> fs/jfs/jfs_metapage.c: In function 'force_metapage':

Re: linux-next: build warning after merge of the akpm-current tree

On 05/26/2017 05:16 AM, Jeff Layton wrote: > On Fri, 2017-05-26 at 12:43 +1000, Stephen Rothwell wrote: >> Hi Andrew, >> >> After merging the akpm-current tree, today's linux-next build (powerpc >> ppc64_defconfig) produced this warning: >> >> fs/jfs/jfs_metapage.c: In function 'force_metapage':

[PATCH 1/3] usb: max3421-hcd: Add devicetree support to the driver

NOTE: Please don't use the plain text here as a patch because it most probably is corrupted by my webmail client. Attached is a copy of the following text guaranteed to have correct tabs/spaces. - Before this patch the max3421-hcd driver could only use statically

[PATCH] ARM: imx_v6_v7_defconfig: Explicitly restore CONFIG_DEBUG_FS

ux-next since next-20170517. This is bad, DEBUG_FS is extremely useful for kernel introspection and testing. Signed-off-by: Leonard Crestez <leonard.cres...@nxp.com> --- Patch is against next-20170526. Applying it to shawnguo/imx/defconfig and cycling via savedefconfig makes this diff go away. Alt

[PATCH] ARM: imx_v6_v7_defconfig: Explicitly restore CONFIG_DEBUG_FS

ux-next since next-20170517. This is bad, DEBUG_FS is extremely useful for kernel introspection and testing. Signed-off-by: Leonard Crestez --- Patch is against next-20170526. Applying it to shawnguo/imx/defconfig and cycling via savedefconfig makes this diff go away. Alternatively maybe

[PATCH v3] scripts/gdb: make lx-dmesg command work (reliably)

lx-dmesg needs access to the log_buf symbol from printk.c. Unfortunately, the symbol log_buf also exists in BPF's verifier.c and hence gdb can pick one or the other. If it happens to pick BPF's log_buf, lx-dmesg doesn't work: (gdb) lx-dmesg Python Exception Cannot access memory at address

[PATCH v3] scripts/gdb: make lx-dmesg command work (reliably)

lx-dmesg needs access to the log_buf symbol from printk.c. Unfortunately, the symbol log_buf also exists in BPF's verifier.c and hence gdb can pick one or the other. If it happens to pick BPF's log_buf, lx-dmesg doesn't work: (gdb) lx-dmesg Python Exception Cannot access memory at address

Re: [PATCH 00/21] liblockdep fixes for v4.12

* Levin, Alexander (Sasha Levin) wrote: > Right, and as you can see from this patchset where we added to > tools/include/ when needed and removed from lib/lockdep/uinclude, > liblockdep is slowly creeping the "right" way. > > perf, like liblockdep, didn't finish

Re: [PATCH 00/21] liblockdep fixes for v4.12

* Levin, Alexander (Sasha Levin) wrote: > Right, and as you can see from this patchset where we added to > tools/include/ when needed and removed from lib/lockdep/uinclude, > liblockdep is slowly creeping the "right" way. > > perf, like liblockdep, didn't finish the switch to exclusively use >

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

+ zhaoyifan (Added Orangepi member for data-sheet upload confirmation) On Fri, May 26, 2017 at 2:29 PM, Andre Przywara wrote: > Hi, > > On 26/05/17 04:54, Chen-Yu Tsai wrote: >> On Fri, May 26, 2017 at 6:30 AM, André Przywara >> wrote: >>> On

Re: [PATCH] powerpc/perf: Fix Power9 test_adder field

On 2017-05-26 13:38, Madhavan Srinivasan wrote: Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 DD1') was added to restrict the use of PMC5 in Power9 DD1. Intend is to diable the use of PMC5 using raw event code. Commit instead of updating "power9_isa207_pmu" structure,

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

+ zhaoyifan (Added Orangepi member for data-sheet upload confirmation) On Fri, May 26, 2017 at 2:29 PM, Andre Przywara wrote: > Hi, > > On 26/05/17 04:54, Chen-Yu Tsai wrote: >> On Fri, May 26, 2017 at 6:30 AM, André Przywara >> wrote: >>> On 25/05/17 20:26, Jagan Teki wrote: From: Jagan

Re: [PATCH] powerpc/perf: Fix Power9 test_adder field

On 2017-05-26 13:38, Madhavan Srinivasan wrote: Commit 8d911904f3ce4 ('powerpc/perf: Add restrictions to PMC5 in power9 DD1') was added to restrict the use of PMC5 in Power9 DD1. Intend is to diable the use of PMC5 using raw event code. Commit instead of updating "power9_isa207_pmu" structure,

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

"Fuzzey, Martin" writes: > On 25 May 2017 at 06:13, Andy Lutomirski wrote: Can you give a simple example of what's going on and why it matters? > > > Here is the use case in which I ran into this problem. > > I have a driver which does

Re: [PATCH v2] firmware: fix sending -ERESTARTSYS due to signal on fallback

"Fuzzey, Martin" writes: > On 25 May 2017 at 06:13, Andy Lutomirski wrote: Can you give a simple example of what's going on and why it matters? > > > Here is the use case in which I ran into this problem. > > I have a driver which does request_firmware() when a write() is done >

Dear Andrey

Dear Andrey.docx Description: MS-Word 2007 document

Dear Andrey

Dear Andrey.docx Description: MS-Word 2007 document

[PATCH v5 1/2] mfd: intel_soc_pmic: Select designware i2c-bus driver

The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which is why INTEL_SOC_PMIC is a bool. Just having the driver is not enough, the driver for the i2c-bus must also be built in, to ensure this, this patch adds a select for

[PATCH v5 1/2] mfd: intel_soc_pmic: Select designware i2c-bus driver

The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which is why INTEL_SOC_PMIC is a bool. Just having the driver is not enough, the driver for the i2c-bus must also be built in, to ensure this, this patch adds a select for

[PATCH v5 2/2] mfd: axp20x-i2c: Document that this must be builtin on x86

On x86 the axp288 PMIC provides an ACPI OpRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if the mfd, OpRegionr and i2c-bus drivers are built in. Since the axp20x mfd code is used on non X86 too we cannot simply change this into a bool,

[PATCH v5 2/2] mfd: axp20x-i2c: Document that this must be builtin on x86

On x86 the axp288 PMIC provides an ACPI OpRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if the mfd, OpRegionr and i2c-bus drivers are built in. Since the axp20x mfd code is used on non X86 too we cannot simply change this into a bool,

[PATCH] serial: uartps: Fix kernel doc warnings

From: Nava kishore Manne This patch fixes the kernel doc warnings in the driver. Signed-off-by: Nava kishore Manne Signed-off-by: Michal Simek --- drivers/tty/serial/xilinx_uartps.c | 1 + 1 file changed, 1 insertion(+) diff

[PATCH] serial: uartps: Fix kernel doc warnings

From: Nava kishore Manne This patch fixes the kernel doc warnings in the driver. Signed-off-by: Nava kishore Manne Signed-off-by: Michal Simek --- drivers/tty/serial/xilinx_uartps.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/tty/serial/xilinx_uartps.c

Re: [PATCH v4 2/2] mfd: axp20x-i2c: Document that this must be builtin on x86

Hi, On 22-05-17 12:56, Lee Jones wrote: On Mon, 15 May 2017, Hans de Goede wrote: On x86 the axp288 PMIC provides an ACPI OpRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if the mfd, OpRegionr and i2c-bus drivers are built in.

Re: [PATCH v4 2/2] mfd: axp20x-i2c: Document that this must be builtin on x86

Hi, On 22-05-17 12:56, Lee Jones wrote: On Mon, 15 May 2017, Hans de Goede wrote: On x86 the axp288 PMIC provides an ACPI OpRegion handler, which must be available before other drivers using it are loaded, which can only be ensured if the mfd, OpRegionr and i2c-bus drivers are built in.

[PATCH v2] scripts/gdb: make lx-dmesg command work (reliably)

lx-dmesg needs access to the log_buf symbol from printk.c. Unfortunately, the symbol log_buf also exists in BPF's verifier.c and hence gdb can pick one or the other. If it happens to pick BPF's log_buf, lx-dmesg doesn't work: (gdb) lx-dmesg Python Exception Cannot access memory at address

[PATCH v2] scripts/gdb: make lx-dmesg command work (reliably)

lx-dmesg needs access to the log_buf symbol from printk.c. Unfortunately, the symbol log_buf also exists in BPF's verifier.c and hence gdb can pick one or the other. If it happens to pick BPF's log_buf, lx-dmesg doesn't work: (gdb) lx-dmesg Python Exception Cannot access memory at address

Re: [PATCH] scripts/gdb: make lx-dmesg command work (reliably)

On 2017-05-26 13:04, André Draszik wrote: > lx-dmesg needs access to the log_buf symbol from printk.c. > Unfortunately, the symbol log_buf also exists in BPF's > verifier.c and hence gdb can pick one or the other. If it > happens to pick BPF's log_buf, lx-dmesg doesn't work: > > (gdb) lx-dmesg

Re: [PATCH] scripts/gdb: make lx-dmesg command work (reliably)

On 2017-05-26 13:04, André Draszik wrote: > lx-dmesg needs access to the log_buf symbol from printk.c. > Unfortunately, the symbol log_buf also exists in BPF's > verifier.c and hence gdb can pick one or the other. If it > happens to pick BPF's log_buf, lx-dmesg doesn't work: > > (gdb) lx-dmesg

Re: [PATCH v4 1/2] mfd: intel_soc_pmic: Select designware i2c-bus driver

Hi, On 22-05-17 12:57, Lee Jones wrote: On Mon, 15 May 2017, Hans de Goede wrote: The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which is why INTEL_SOC_PMIC is a bool. Just having the driver is not enough, the driver

Re: [PATCH v4 1/2] mfd: intel_soc_pmic: Select designware i2c-bus driver

Hi, On 22-05-17 12:57, Lee Jones wrote: On Mon, 15 May 2017, Hans de Goede wrote: The Crystal Cove PMIC provides an ACPI OPRegion handler, which must be available before other drivers using it are loaded, which is why INTEL_SOC_PMIC is a bool. Just having the driver is not enough, the driver

Re: [PATCH v3] Added "Preserve Boot Time Support"

On Fri, May 19, 2017 at 01:16:23PM +0300, Bogdan Mirea wrote: > This option enables Boot Time Preservation between Bootloader and > Linux Kernel. It is based on the idea that the Bootloader (or any > other early firmware) will start the HW Timer and Linux Kernel will > count the time starting with

Re: [PATCH v3] Added "Preserve Boot Time Support"

On Fri, May 19, 2017 at 01:16:23PM +0300, Bogdan Mirea wrote: > This option enables Boot Time Preservation between Bootloader and > Linux Kernel. It is based on the idea that the Bootloader (or any > other early firmware) will start the HW Timer and Linux Kernel will > count the time starting with

Re: [PATCH 1/4] Introduce regmap infrastructure over Maxim/Dalas OneWire (W1) bus

On Thu, May 25, 2017 at 11:14:39PM +0300, Evgeniy Polyakov wrote: > Frankly saying, your non-regmap version was so much simpler, smaller and > cleaner. > I wonder why did people force you to use regmap. > Guys, please speak up, if you want driver authors to use THIS, it is really > flawed. >

Re: [PATCH 1/4] Introduce regmap infrastructure over Maxim/Dalas OneWire (W1) bus

On Thu, May 25, 2017 at 11:14:39PM +0300, Evgeniy Polyakov wrote: > Frankly saying, your non-regmap version was so much simpler, smaller and > cleaner. > I wonder why did people force you to use regmap. > Guys, please speak up, if you want driver authors to use THIS, it is really > flawed. >

[PATCH v3 3/4] dt-bindings: power: tps65217_charger: add NTC type for battery temperature measurement.

The TS pin of the TPS56217 connects to the NTC resistor in the battery pack. By default the device is setup to support a 10-kohm but can also be configured to support a 100-kohm. Add a propietry to configure the connected NTC resistor. Therefore, the charger would get the wrong temperature

[PATCH v3 3/4] dt-bindings: power: tps65217_charger: add NTC type for battery temperature measurement.

The TS pin of the TPS56217 connects to the NTC resistor in the battery pack. By default the device is setup to support a 10-kohm but can also be configured to support a 100-kohm. Add a propietry to configure the connected NTC resistor. Therefore, the charger would get the wrong temperature

[PATCH] scripts/gdb: make lx-dmesg command work (reliably)

lx-dmesg needs access to the log_buf symbol from printk.c. Unfortunately, the symbol log_buf also exists in BPF's verifier.c and hence gdb can pick one or the other. If it happens to pick BPF's log_buf, lx-dmesg doesn't work: (gdb) lx-dmesg Python Exception Cannot access memory at address

[PATCH] scripts/gdb: make lx-dmesg command work (reliably)

lx-dmesg needs access to the log_buf symbol from printk.c. Unfortunately, the symbol log_buf also exists in BPF's verifier.c and hence gdb can pick one or the other. If it happens to pick BPF's log_buf, lx-dmesg doesn't work: (gdb) lx-dmesg Python Exception Cannot access memory at address

[PATCH v3 2/4] power: supply: core: add charging voltage/current battery info

Add the parameters to define the battery charging voltage and charging current. Charger driver can get this information from the struct power_supply_battery_info and apply the desired value. Signed-off-by: Enric Balletbo i Serra --- Changes since v2: - Requested by

[PATCH v3 2/4] power: supply: core: add charging voltage/current battery info

Add the parameters to define the battery charging voltage and charging current. Charger driver can get this information from the struct power_supply_battery_info and apply the desired value. Signed-off-by: Enric Balletbo i Serra --- Changes since v2: - Requested by Sebastian Reichel - Move

[PATCH v3 4/4] power: tps65217_charger: add support for NTC type, voltage and current charge

Allow the possibility to configure the charge and the current voltage of the charger and also the NTC type for battery temperature measurement. Signed-off-by: Enric Balletbo i Serra --- Changes since v2: - Requested by Sebastian Reichel - Use the simple-battery

[PATCH v3 4/4] power: tps65217_charger: add support for NTC type, voltage and current charge

Allow the possibility to configure the charge and the current voltage of the charger and also the NTC type for battery temperature measurement. Signed-off-by: Enric Balletbo i Serra --- Changes since v2: - Requested by Sebastian Reichel - Use the simple-battery framework - Use

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

Hi Teng, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Alexei-Starovoitov/bpf-Add-BPF-support-to-all-perf_event/20170526-171542 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https

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

Hi Teng, [auto build test ERROR on net-next/master] url: https://github.com/0day-ci/linux/commits/Alexei-Starovoitov/bpf-Add-BPF-support-to-all-perf_event/20170526-171542 config: ia64-allmodconfig (attached as .config) compiler: ia64-linux-gcc (GCC) 6.2.0 reproduce: wget https

[PATCH v3 1/4] dt-bindings: power: supply: add battery charge voltage/current

Add charging voltage and current characteristics to the battery DT for proper handling of the battery by fuel-gauge and charger chips. Signed-off-by: Enric Balletbo i Serra --- Changes since v2: - Requested by Sebastian Reichel - Move to its own patch and apply

[PATCH v3 1/4] dt-bindings: power: supply: add battery charge voltage/current

Add charging voltage and current characteristics to the battery DT for proper handling of the battery by fuel-gauge and charger chips. Signed-off-by: Enric Balletbo i Serra --- Changes since v2: - Requested by Sebastian Reichel - Move to its own patch and apply to simple-battery framework.

[tip:timers/core] posix-timers: Make posix_clocks immutable

Commit-ID: 74377deb3c19639ab5c0a8c2b5301d67c45ba83c Gitweb: http://git.kernel.org/tip/74377deb3c19639ab5c0a8c2b5301d67c45ba83c Author: Christoph Hellwig AuthorDate: Fri, 26 May 2017 12:03:11 +0300 Committer: Thomas Gleixner CommitDate: Fri, 26 May 2017

[tip:timers/core] posix-timers: Make posix_clocks immutable

Commit-ID: 74377deb3c19639ab5c0a8c2b5301d67c45ba83c Gitweb: http://git.kernel.org/tip/74377deb3c19639ab5c0a8c2b5301d67c45ba83c Author: Christoph Hellwig AuthorDate: Fri, 26 May 2017 12:03:11 +0300 Committer: Thomas Gleixner CommitDate: Fri, 26 May 2017 12:52:20 +0200 posix-timers:

[tip:timers/core] mmtimer: Remove the SGI SN2 mmtimer driver

Commit-ID: 07903ada96139ced48f2f893fe57a26a8fbc6043 Gitweb: http://git.kernel.org/tip/07903ada96139ced48f2f893fe57a26a8fbc6043 Author: Christoph Hellwig AuthorDate: Fri, 26 May 2017 12:03:10 +0300 Committer: Thomas Gleixner CommitDate: Fri, 26 May 2017

[tip:timers/core] mmtimer: Remove the SGI SN2 mmtimer driver

Commit-ID: 07903ada96139ced48f2f893fe57a26a8fbc6043 Gitweb: http://git.kernel.org/tip/07903ada96139ced48f2f893fe57a26a8fbc6043 Author: Christoph Hellwig AuthorDate: Fri, 26 May 2017 12:03:10 +0300 Committer: Thomas Gleixner CommitDate: Fri, 26 May 2017 12:52:19 +0200 mmtimer: Remove

Re: [PATCH 00/21] liblockdep fixes for v4.12

On Fri, May 26, 2017 at 08:52:52AM +0200, Ingo Molnar wrote: > > * Levin, Alexander (Sasha Levin) wrote: > > > MAINTAINERS| 2 +- > > tools/Makefile | 8 +++-- > > tools/include/linux/bitops.h

Re: [PATCH 00/21] liblockdep fixes for v4.12

On Fri, May 26, 2017 at 08:52:52AM +0200, Ingo Molnar wrote: > > * Levin, Alexander (Sasha Levin) wrote: > > > MAINTAINERS| 2 +- > > tools/Makefile | 8 +++-- > > tools/include/linux/bitops.h | 10

<    5   6   7   8   9   10   11   12   13   14   >