[PATCH v3 1/1] partitions/msdos: FreeBSD UFS2 file systems are not recognized

The code in block/partitions/msdos.c recognizes FreeBSD, OpenBSD and NetBSD partitions and does a reasonable job picking out OpenBSD and NetBSD UFS subpartitions. But for FreeBSD the subpartitions are always "bad". Kernel: Cc: Andries Brouwer Cc: linux-bl...@vger.kernel.org

[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 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

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 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 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 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 v5 2/2] mfd: axp20x-i2c: Document that this must be builtin on x86

On Fri, May 26, 2017 at 7:15 PM, 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. Extra "r"

[PATCH] livepatch: Make livepatch dependent on !TRIM_UNUSED_KSYMS

If TRIM_UNUSED_KSYMS is enabled, all unneeded exported symbols are made unexported. Two-pass build of the kernel is done to find out which symbols are needed based on a configuration. This effectively complicates things for out-of-tree modules. Livepatch exports functions to (un)register and

[tip:x86/apic] x86/ioapic: Remove unused IO_APIC_irq_trigger() function

Commit-ID: 9df8109fd7969b94ed2332ae828e0b08ae8cbf9a Gitweb: http://git.kernel.org/tip/9df8109fd7969b94ed2332ae828e0b08ae8cbf9a Author: Matthias Kaehlcke AuthorDate: Mon, 22 May 2017 16:20:35 -0700 Committer: Thomas Gleixner CommitDate: Fri, 26 May

Re: [PATCHv1, RFC 0/8] Boot-time switching between 4- and 5-level paging

On Thu, May 25, 2017 at 04:24:24PM -0700, Linus Torvalds wrote: > On Thu, May 25, 2017 at 1:33 PM, Kirill A. Shutemov > wrote: > > Here' my first attempt to bring boot-time between 4- and 5-level paging. > > It looks not too terrible to me. I've expected it to be

Re: [RESEND: PATCH v4 1/4] firmware: scm: Add new SCM call for switching memory ownership

On 5/26/2017 11:33 AM, Bjorn Andersson wrote: On Tue 16 May 11:01 PDT 2017, Avaneesh Kumar Dwivedi wrote: diff --git a/drivers/firmware/qcom_scm-32.c b/drivers/firmware/qcom_scm-32.c index 93e3b96..4eb7d59 100644 --- a/drivers/firmware/qcom_scm-32.c +++ b/drivers/firmware/qcom_scm-32.c @@

Re: Change PAGE_SIZE from minimum 4k to 12k

On Thu, May 25, 2017 at 5:55 PM, Pavel Machek wrote: > Hi! > >> >> > Would it be possible to have a custom block device driver read/write >> >> > in increments of 12k instead of reading/writing data in 4k increments? >> >> > In other words, I would like to change the default page

Re: [PATCH v2] arm: dma-mapping: Reset the device's dma_ops

Hi Sricharan, Thank you for the patch. On Friday 26 May 2017 16:13:37 Sricharan R wrote: > arch_teardown_dma_ops() being the inverse of arch_setup_dma_ops() > ,dma_ops should be cleared in the teardown path. Currently, only the > device's iommu mapping structures are cleared in

Re: [PATCH v2 2/2] xen: add sysfs node for guest type

On 05/26/2017 08:56 AM, Juergen Gross wrote: > Currently there is no reliable user interface inside a Xen guest to > determine its type (e.g. HVM, PV or PVH). Instead of letting user mode > try to determine this by various rather hacky mechanisms (parsing of > boot messages before they are gone,

Re: [PATCH 2/2] arm64: dts: Add Mediatek SoC MT2712 and evaluation board dts and Makefile

On Tue, 2017-05-23 at 10:01 -0500, Rob Herring wrote: > On Fri, May 19, 2017 at 07:09:46PM +0800, YT Shen wrote: > > This adds basic chip support for Mediatek 2712 > > > > Signed-off-by: YT Shen > > --- > > arch/arm64/boot/dts/mediatek/Makefile | 1 + > >

[PATCH v2] arm: dma-mapping: Reset the device's dma_ops

arch_teardown_dma_ops() being the inverse of arch_setup_dma_ops() ,dma_ops should be cleared in the teardown path. Currently, only the device's iommu mapping structures are cleared in arch_teardown_dma_ops, but not the dma_ops. So on the next reprobe, dma_ops left in place is stale from the first

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

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

[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

Applied "spi: Document SPI slave controller support" to the spi tree

The patch spi: Document SPI slave controller support 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

Applied "spi: sh-msiof: Add slave mode support" to the spi tree

The patch spi: sh-msiof: Add slave mode support 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

Applied "spi: slave: Add SPI slave handler reporting uptime at previous message" to the spi tree

The patch spi: slave: Add SPI slave handler reporting uptime at previous message 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

Re: pxa3xx-nand failing to find device on linux-next

Le Thu, 25 May 2017 22:12:12 +, Chris Packham a écrit : > On 25/05/17 18:19, Boris Brezillon wrote: > > Le Wed, 24 May 2017 22:58:53 +, > > Chris Packham a écrit : > > > >> On 25/05/17 10:36, Boris Brezillon wrote:

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

On Fri, May 26, 2017 at 01:29:01PM +0200, Jiri Slaby wrote: > 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

[PATCH 2/2] perf tests: Rename cycles event to HW event

The 'hardware' suits better now when we could also use instructions event in addition to cycles. Link: http://lkml.kernel.org/n/tip-rfaab0tmwh6oepsqtm75z...@git.kernel.org Signed-off-by: Jiri Olsa --- tools/perf/tests/switch-tracking.c | 64

Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

I am running into this problem on PowerPC systems where Balbir's patch set was targeted. So, yes, I do need to be able to add/enable a new numa node during system execution in cases where more resources (memory, virtual processors) are added to the system dynamically. On 05/25/2017 10:46 PM,

[PATCH 1/2] perf tests: Fix switch tracking test for P4

The switch tracking test keeps failing on P4 cpu, when NMI watchdog is enabled. The reason is that P4 pmu uses substitute event for cycles when it's already taken (in our case by NMI watchdog), but this event does not give even results like cycles, and we could end up with no samples at all for

Re: [PATCH v3 2/2] dt-bindings: net: Add Cortina device tree bindings

> + cs4340_phy@1 { > + compatible = "ethernet-phy-id13e5.1002"; > + reg = <0x10>; The @1 and the reg value should be the same. Please change it to cs4340_phy@10. Andrew

Re: [PATCHv1, RFC 0/8] Boot-time switching between 4- and 5-level paging

> Even ignoring all of above, I don't see much benefit of having per-mm > switching. It adds complexity without much benefit -- saving few lines of > logic during early boot doesn't look as huge win to me. Also giving kthreads a different VM would prevent lazy VM switching when switching from/to

RE: [PATCH v3 2/2] dt-bindings: net: Add Cortina device tree bindings

> -Original Message- > From: Andrew Lunn [mailto:and...@lunn.ch] > Sent: Friday, May 26, 2017 4:36 PM > To: Bogdan Purcareata > Cc: f.faine...@gmail.com; net...@vger.kernel.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org > Subject: Re: [PATCH v3

Re: [PATCH 1/3] [media] si2157: get chip id during probing

>> ep: 81 l:9 08260080ff5901 >> >> here you see all the from the device. You need to be able to see the traffic on the physical I2C bus in order to help diagnose issues like this. You're going to want to see ACKS/NAKS, clocks and other I2C bus activity. You'll need to solder down

Re: [Patch 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

On Fri, May 26, 2017 at 01:46:58PM +1000, Michael Ellerman wrote: Reza Arbab writes: On Thu, May 25, 2017 at 04:19:53PM +1000, Michael Ellerman wrote: The commit message for 3af229f2071f says: In practice, we never see a system with 256 NUMA nodes, and in fact,

[PATCH] platform/x86: intel_cht_int33fe: Set supplied-from property on max17047 dev

Devices with the intel_cht_int33fe ACPI device use a max17047 fuel-gauge combined with a bq24272i charger, in order for the fuel-gauge driver to correctly display charging / discharging status it needs to know which charger is supplying the battery. This commit sets the supplied-from device

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

[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 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 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 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[] = {

[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

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 V2 2/2]: powerpc/hotplug/mm: Fix hot-add memory node assoc

>> arch/powerpc/mm/numa.c |7 --- >> 1 file changed, 7 deletions(-) >> >> diff --git a/arch/powerpc/mm/numa.c b/arch/powerpc/mm/numa.c >> index 15c2dd5..18f3038 100644 >> --- a/arch/powerpc/mm/numa.c >> +++ b/arch/powerpc/mm/numa.c >> @@ -907,13 +907,6 @@ void __init initmem_init(void) >>

[PATCH v2 1/2] doc,xen: document hypervisor sysfs nodes for xen

Today only a few sysfs nodes under /sys/hypervisor/ are documented for Xen in Documentation/ABI/testing/sysfs-hypervisor-pmu. Add the remaining Xen sysfs nodes under /sys/hypervisor/ in a new file Documentation/ABI/stable/sysfs-hypervisor-xen and add the Xen specific sysfs docs to the MAINTAINERS

Re: [PATCH v3 1/1] partitions/msdos: FreeBSD UFS2 file systems are not recognized

On 05/26/2017 04:48 AM, Richard Narron wrote: > The code in block/partitions/msdos.c recognizes FreeBSD, OpenBSD > and NetBSD partitions and does a reasonable job picking out OpenBSD > and NetBSD UFS subpartitions. > > But for FreeBSD the subpartitions are always "bad". > > Kernel: >

Re: [Xen-devel] [PATCH v2 1/2] doc, xen: document hypervisor sysfs nodes for xen

On 26/05/17 13:56, Juergen Gross wrote: > Today only a few sysfs nodes under /sys/hypervisor/ are documented > for Xen in Documentation/ABI/testing/sysfs-hypervisor-pmu. > > Add the remaining Xen sysfs nodes under /sys/hypervisor/ in a new > file Documentation/ABI/stable/sysfs-hypervisor-xen and

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

On Fri, 26 May 2017, Steven Rostedt wrote: > On Thu, 25 May 2017 10:57:51 +0200 (CEST) > Thomas Gleixner wrote: > > > ftrace use module_alloc() to allocate trampoline pages. The mapping of > > module_alloc() is RWX, which makes sense as the memory is written to right > >

[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

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

Commit-ID: 82def146e8f511c37d8d8934202491483dd09ca9 Gitweb: http://git.kernel.org/tip/82def146e8f511c37d8d8934202491483dd09ca9 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: d346807445883732d530a62ebadb69af2f017e28 Gitweb: http://git.kernel.org/tip/d346807445883732d530a62ebadb69af2f017e28 Author: Christoph Hellwig AuthorDate: Fri, 26 May 2017 12:03:11 +0300 Committer: Thomas Gleixner CommitDate: Fri, 26 May 2017

Re: [PATCH 1/8] serial: exar: Preconfigure xr17v35x MPIOs as output

Greg, On 2017-05-13 09:28, Jan Kiszka wrote: > This is the safe default for GPIOs with unknown external wiring. > > Signed-off-by: Jan Kiszka > --- > drivers/tty/serial/8250/8250_exar.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git

Re: status of the Altix mmtimer driver

Note that the mmtimer struct can probably be removed from the k_itimer struct in include/linux/posix-timers.h, just for completeness. --- a/include/linux/posix-timers.h +++ b/include/linux/posix-timers.h @@ -73,12 +73,6 @@ struct k_itimer { } real; struct

[PATCH 0/2] leds: trigger: gpio: Add update point / use threaded IRQ

See patches for details. Jan Kiszka (2): leds: trigger: gpio: Refresh LED state after GPIO change leds: trigger: gpio: Use threaded IRQ drivers/leds/trigger/ledtrig-gpio.c | 29 +++-- 1 file changed, 7 insertions(+), 22 deletions(-) -- 2.12.0

[PATCH 1/2] leds: trigger: gpio: Refresh LED state after GPIO change

The new GPIO may have a different state than the old one. Signed-off-by: Jan Kiszka --- drivers/leds/trigger/ledtrig-gpio.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/leds/trigger/ledtrig-gpio.c b/drivers/leds/trigger/ledtrig-gpio.c index

[PATCH 2/2] leds: trigger: gpio: Use threaded IRQ

This both simplifies the code because we can drop the workqueue indirection, and it enables using the trigger for GPIOs that work with threaded IRQs themselves. Signed-off-by: Jan Kiszka --- drivers/leds/trigger/ledtrig-gpio.c | 29 ++--- 1 file

[PATCH] genirq: Check irq disabled & masked states in irq_shutdown

If irq is already disabled and masked, we would hit a unbalanced irq shutdown/disable/mask when freeing it. Add a state check in irq_shutdown to prevent this. Signed-off-by: Jeffy Chen --- kernel/irq/chip.c | 8 +++- 1 file changed, 7 insertions(+), 1

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

On Fri, 26 May 2017 15:50:38 +0200 (CEST) Thomas Gleixner wrote: > That's very early boot, right? So interrupts have to be disabled. > > So this wants to be: > >BUG_ON(irqs_disabled() && !early_boot_irqs_disabled); > I was thinking the same thing. I'll add a patch

Re: [PATCH 1/8] serial: exar: Preconfigure xr17v35x MPIOs as output

On Fri, May 26, 2017 at 4:04 PM, Jan Kiszka wrote: > Greg, > Please drop from this tty-next, it may break Commtech adapters. I have > an update ready. > > I may also send a fix on top if that is preferred, just let me know. AFAIK what is in tty-next is left there, so,

Re: [PATCH] fork: fix kmemleak false positive due to thread stacks caching

On Fri, May 26, 2017 at 02:49:49PM +0100, Luis Henriques wrote: > kmemleak has been reporting memory leaks since commit ac496bf48d97 ("fork: > Optimize task creation by caching two thread stacks per CPU if > CONFIG_VMAP_STACK=y"): > > unreferenced object 0xc92b (size 16384): > comm

Re: [PATCH v3 1/2] net: phy: Add Cortina CS4340 driver (fwd)

@vger.kernel.org CC: Hi Bogdan, [auto build test WARNING on net-next/master] [also build test WARNING on v4.12-rc2 next-20170526] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Bogdan-Purcareata/ne

Re: [PATCH v3 1/1] partitions/msdos: FreeBSD UFS2 file systems are not recognized

On Fri, 2017-05-26 at 03:48 -0700, Richard Narron wrote: > The code in block/partitions/msdos.c recognizes FreeBSD, OpenBSD > and NetBSD partitions and does a reasonable job picking out OpenBSD > and NetBSD UFS subpartitions. > > But for FreeBSD the subpartitions are always "bad". > >

[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 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: [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 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

Re: [RESEND: PATCH v4 2/4] remoteproc: qcom: refactor mss fw image loading sequence

On 5/26/2017 12:43 AM, Bjorn Andersson wrote: On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote: This patch refactor code to first load all firmware blobs and then update modem proc to authenticate and boot fw. Nice, I like this! Just some style details below. Thanks. Sure will

Re: [RESEND: PATCH v4 4/4] remoteproc: qcom: Add support for mss boot on msm8996

On 5/26/2017 11:39 AM, Bjorn Andersson wrote: On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote: diff --git a/Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt b/Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt index 92347fe..f9dfb6c 100644 ---

Re: [PATCH] genirq: Check irq disabled & masked states in irq_shutdown

On Fri, 26 May 2017, Jeffy Chen wrote: > If irq is already disabled and masked, we would hit a unbalanced irq > shutdown/disable/mask when freeing it. Errr? What exactly is unbalanced? None of the called functions has any counter or whatever. Can you please explain what you are trying to fix?

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 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

[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 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] 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 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

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

Re: [-next] memory hotplug regression

On Wed, May 24, 2017 at 10:39:57AM +0200, Michal Hocko wrote: > On Wed 24-05-17 10:20:22, Heiko Carstens wrote: > > Having the ZONE_MOVABLE default was actually the only point why s390's > > arch_add_memory() was rather complex compared to other architectures. > > > > We always had this

[PATCH V3 2/2] powerpc/hotplug/mm: Fix hot-add memory node assoc

Removing or adding memory via the PowerPC hotplug interface currently dumps newly added processors or memory into default node 0, instead of into the node that would be calculated based upon the VPHN affinity tables. The code was updated to ensure that all nodes found at boot are still available

Re: [PATCH 1/5][v2] staging: fsl-mc: fix several checkpath.pl warnings

Hi Greg, On 05/25/2017 07:58 PM, Greg KH wrote: > On Mon, May 22, 2017 at 03:09:31PM +0300, laurentiu.tu...@nxp.com wrote: >> From: Laurentiu Tudor > > Your subject line is very odd, please use the 'v2' marking properly... > >> >> Remove several unneeded #includes,

Re: [RESEND: PATCH v4 3/4] remoteproc: qcom: Make secure world call for mem ownership switch

On 5/26/2017 7:46 AM, Bjorn Andersson wrote: On Tue 16 May 11:02 PDT 2017, Avaneesh Kumar Dwivedi wrote: +static int q6v5_assign_mem_to_subsys(struct q6v5 *qproc, + phys_addr_t addr, size_t size) +{ + struct qcom_scm_destVmPerm next[] = {{ QCOM_SCM_VMID_MSS_MSA, +

Re: [PATCH v5 6/6] kernel.h: handle pointers to arrays better in container_of()

On 25/05/17 19:35, Kees Cook wrote: On Thu, May 25, 2017 at 5:03 AM, Ian Abbott wrote: If the first parameter of container_of() is a pointer to a non-const-qualified array type (and the third parameter names a non-const-qualified array member), the local variable __mptr will

Re: [PATCH 2/2] crypto: mediatek - update DT binding documentation

On 26/05/17 11:43, Ryder Lee wrote: This patch removes unnecessary clock in binding file. Signed-off-by: Ryder Lee --- In the driver clocks are get by name, so this change does not break backwards compatibility. Reviewed-by: Matthias Brugger

Re: [PATCH 4/4] watchdog: provide watchdog_reconfigure() for arch watchdogs

On Fri, May 26, 2017 at 10:39:09AM +1000, Nicholas Piggin wrote: > On Thu, 25 May 2017 10:08:33 -0400 > Don Zickus wrote: > > > On Thu, May 25, 2017 at 06:28:56PM +1000, Nicholas Piggin wrote: > > > After reconfiguring watchdog sysctls etc., architecture specific > > >

RE: [PATCH v3 1/2] net: phy: Add Cortina CS4340 driver (fwd)

> -Original Message- > From: Julia Lawall [mailto:julia.law...@lip6.fr] > Sent: Friday, May 26, 2017 5:32 PM > To: Bogdan Purcareata > Cc: and...@lunn.ch; f.faine...@gmail.com; net...@vger.kernel.org; > devicet...@vger.kernel.org; linux-kernel@vger.kernel.org;

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: [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] 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] s390: provide default ioremap and iounmap declaration

On Thu, May 25, 2017 at 09:43:48AM -0600, Logan Gunthorpe wrote: > Add a default ioremap function which was not provided in all > circumstances. (Only when CONFIG_PCI was set). > > I have designs to use them in scatterlist.c where they'd likely never > be called without CONFIG_PCI set, but it is

[tip:irq/core] genirq: Make early_irq_init() print out more informative

Commit-ID: 5a29ef22098874db79af7bf92a247a0f503bfa6e Gitweb: http://git.kernel.org/tip/5a29ef22098874db79af7bf92a247a0f503bfa6e Author: Vincent Legoll AuthorDate: Tue, 9 May 2017 10:34:09 +0200 Committer: Thomas Gleixner CommitDate: Fri, 26

[PATCH v2] ktime: Simplify ktime_compare implementation

ktime_sub can be used here instread of two conditional checks. Signed-off-by: Mariusz Skamra Acked-by: Kuppuswamy Sathyanarayanan --- include/linux/ktime.h | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git

[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 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 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

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

Dear Andrey

Dear Andrey.docx Description: MS-Word 2007 document

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

  1   2   3   4   5   6   7   8   9   10   >