Re: [PATCH] ASoC: omap: constify snd_soc_ops structures

On Mon, Mar 20, 2017 at 01:53:26AM +0100, Sebastian Reichel wrote: > Hi, > > On Sat, Mar 18, 2017 at 07:34:11PM +0530, Bhumika Goyal wrote: > > Declare snd_soc_ops structures as const as they are only stored > > in the ops field of a snd_soc_dai_link structure. This field is > > of type const, so

Re: [PATCH] backlight: Add TI LMU backlight driver

Hi, On Mon, Mar 20, 2017 at 11:21:04AM +0900, Milo Kim wrote: > This is consolidated driver which supports backlight devices below. > LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. > > Structure > - > It consists of two parts - core and data. > > Core part supports features bel

[PATCH] stm class: Document the stm_ftrace

This patch adds a description of the stm_ftrace device source, an interface for collecting Function trace information via STM devices. Signed-off-by: Chunyan Zhang --- Documentation/trace/stm.txt | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/Documentation/trace/st

[PATCH v6 3/4] leds: Add LED support for MT6323 PMIC

From: Sean Wang MT6323 PMIC is a multi-function device that includes LED function. It allows attaching up to 4 LEDs which can either be on, off or dimmed and/or blinked with the controller. Signed-off-by: Sean Wang Reviewed-by: Jacek Anaszewski --- drivers/leds/Kconfig | 8 + drivers/

[PATCH v6 4/4] mfd: mt6397: Align the placement at which the mfd_cell of LED is defined

From: Sean Wang Align the placement as which the mfd_cell of LED is defined as the other members done on the structure. Signed-off-by: Sean Wang Acked-by: Lee Jones --- drivers/mfd/mt6397-core.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/mfd/mt6397-core.c b/

[PATCH v6 2/4] dt-bindings: mfd: Add the description for LED as the sub module

From: Sean Wang This patch adds description for LED as the sub-module on MT6397/MT6323 multifunction device. Signed-off-by: Sean Wang --- Documentation/devicetree/bindings/mfd/mt6397.txt | 1 + 1 file changed, 1 insertion(+) diff --git a/Documentation/devicetree/bindings/mfd/mt6397.txt b/Doc

[PATCH v6 1/4] dt-bindings: leds: Add document bindings for leds-mt6323

From: Sean Wang This patch adds documentation for devicetree bindings for LED support on MT6323 PMIC. Signed-off-by: Sean Wang --- .../devicetree/bindings/leds/leds-mt6323.txt | 60 ++ 1 file changed, 60 insertions(+) create mode 100644 Documentation/devicetree/bindi

[PATCH v6 0/4] leds: add leds-mt6323 support on MT7623 SoC

From: Sean Wang MT7623 SoC uses MT6323 PMIC as the default power supply which has LED function insides. The patchset introduces the LED support for MT6323 with on, off and hardware dimmed and blinked and it should work on other similar SoCs if also using MT6323. Changes since v1: - fixed typo in

Re: [PATCH 11/11] net: usb: usb: remove old api ethtool_{get|set}_settings

Am Donnerstag, den 16.03.2017, 23:18 +0100 schrieb Philippe Reynes: > The function usbnet_{get|set}_settings is no longer used, > so we remove it. > > Signed-off-by: Philippe Reynes Acked-by: Oliver Neukum

Re: [PATCH 01/11] net: usb: usbnet: add new api ethtool_{get|set}_link_ksettings

Am Donnerstag, den 16.03.2017, 23:18 +0100 schrieb Philippe Reynes: > The ethtool api {get|set}_settings is deprecated. > We add the new api {get|set}_link_ksettings to this driver. > > As I don't have the hardware, I'd be very pleased if > someone may test this patch. > > Signed-off-by: Philippe

Re: [PATCH v6 5/8] dt-bindings: input: touchscreen: Add max11801-ts binding

On Mon, Mar 20, 2017 at 8:06 AM, Shawn Guo wrote: > On Thu, Mar 16, 2017 at 12:35:38PM +0530, Jagan Teki wrote: >> From: Jagan Teki >> >> Add missing documentation of max11801-ts dt-binding details. >> >> Cc: Mark Rutland >> Cc: Rob Herring >> Cc: Shawn Guo >> Cc: Michael Trimarchi >> Signed-

Re: ZONE_NORMAL vs. ZONE_MOVABLE

2017-03-17 4:01 GMT+09:00 Andrea Arcangeli : > Hello Joonsoo, Hello, Andrea. > On Thu, Mar 16, 2017 at 02:31:22PM +0900, Joonsoo Kim wrote: >> I don't follow up previous discussion so please let me know if I miss >> something. I'd just like to mention about sticky pageblocks. > > The interesting

Re: [PATCH v6 05/15] mlx4: Replace PCI pool old API

On Sun, Mar 19, 2017 at 06:03:54PM +0100, Romain Perier wrote: > The PCI pool API is deprecated. This commit replaces the PCI pool old > API by the appropriate function with the DMA pool API. > > Signed-off-by: Romain Perier > Acked-by: Peter Senna Tschudin > Tested-by: Peter Senna Tschudin > --

Re: [PATCH v6 06/15] mlx5: Replace PCI pool old API

On Sun, Mar 19, 2017 at 06:03:55PM +0100, Romain Perier wrote: > The PCI pool API is deprecated. This commit replaces the PCI pool old > API by the appropriate function with the DMA pool API. > > Signed-off-by: Romain Perier > Reviewed-by: Peter Senna Tschudin > --- > drivers/net/ethernet/mellan

[PATCH] mm, swap: Remove WARN_ON_ONCE() in free_swap_slot()

From: Huang Ying Before commit 452b94b8c8c7 ("mm/swap: don't BUG_ON() due to uninitialized swap slot cache"), the following bug is reported, [ cut here ] kernel BUG at mm/swap_slots.c:270! invalid opcode: [#1] SMP CPU: 5 PID: 1745 Comm: (sd-pam) Not tainted 4

[PATCH] staging: wilc1000: Fix sparse warning in wilc_wfi_cfgoperations.c

Fix the following warning reported by sparse: drivers/staging/wilc1000/wilc_wfi_cfgoperations.c:2006:51: warning: incorrect type in assignment (different base types) drivers/staging/wilc1000/wilc_wfi_cfgoperations.c:2006:51:expected unsigned short [unsigned] [assigned] [usertype] ht_capa_inf

Re: [PATCH v7 3/3] printk: fix double printing with earlycon

Hello, On (03/17/17 16:43), Aleksey Makarov wrote: [..] > +static void ensure_preferred_is_last(int i) > +{ > + int last; > + > + for (last = MAX_CMDLINECONSOLES - 1; > + last >= 0 && !console_cmdline[last].name[0]; > + last--) > + ; > + > + BUG_ON(last <

[RFC PATCH] x86_64/mm/boot: Fix kernel_ident_mapping_init() failure for kexec

I found that the kdump is broken on linux-4.11.0-rc2+, probably due to the 5level-paging feature that "#define p4d_present(p4d) 1", as a result in ident_p4d_init(), it will go into ident_pud_init() directly without allocating the new pud. Looks like this patch can make it work again. Cc: Kirill A

[PATCH] drm: bridge: dw-hdmi: add HDMI vendor specific infoframe config

Vendor specific infoframe is mandatory for 4K2K resolution. Without this, the HDMI protocol compliance fails. Signed-off-by: Nickey Yang --- drivers/gpu/drm/bridge/dw-hdmi.c | 50 drivers/gpu/drm/bridge/dw-hdmi.h | 4 2 files changed, 54 insertions(

linux-next: build warnings after merge of the net-next tree

Hi all, After merging the net-next tree, today's linux-next build (powerpc allyesconfig) produced thie warnings: In file included from include/linux/byteorder/big_endian.h:4:0, from arch/powerpc/include/uapi/asm/byteorder.h:13, from include/linux/qed/common_hsi.h

linux-next: Tree for Mar 20

Hi all, Changes since 20170310: Changed trees: kbuild-currrent, kbuild (new maintainer) The renesas tree gained a conflict against the arm tree. The fscrypt tree gained a conflict against Linus' tree. The net-next tree gained a conflict against the net tree. The tty tree gained a conflict aga

Re: [PATCH] scsi: sr: fix oob access in get_capabilities

On 2017/3/18 7:29, Martin K. Petersen wrote: > Kefeng Wang writes: > > Kefeng, > >> root@localhost ~]# sg_modes -p 0x2a /dev/sr0 >> QEMU QEMU DVD-ROM 0.15 peripheral_type: cd/dvd [0x5] >> Mode parameter header from MODE SENSE(10): >> Invalid block descriptor length=512, ignore

Re: [RFC 0/1] add support for reclaiming priorities per mem cgroup

Hello, On Fri, Mar 17, 2017 at 04:16:35PM -0700, Tim Murray wrote: > Hi all, > > I've been working to improve Android's memory management and drop > lowmemorykiller from the kernel, and I'd like to get some feedback on a small > patch with a lot of side effects. > > Currently, when an Android

Re: [PATCH] power: supply: Add driver for TI BQ2416X battery charger

Hi, On Tue, Feb 07, 2017 at 01:09:09AM +, Wojciech Ziemba wrote: > There is interest in adding a Linux driver for TI BQ2416X battery > charger. This is a strange sentence to introduce a patch. If there wasn't you wouldn't have sent a patch... > The driver supports BQ24160 chip, thus can be e

[PATCH v3 2/3] powerpc/fadump: Use the correct VMCOREINFO_NOTE_SIZE for phdr

vmcoreinfo_max_size stands for the vmcoreinfo_data, the correct one we should use is vmcoreinfo_note whose total size is VMCOREINFO_NOTE_SIZE. Like explained in commit 77019967f06b ("kdump: fix exported size of vmcoreinfo note"), it does not affect the actual function, we better fix it, also this

[PATCH v3 3/3] kdump: Relocate vmcoreinfo to the crash memory range

Currently vmcoreinfo data is updated at boot time subsys_initcall(), it has the risk of being modified by some wrong code during system is running. As a result, vmcore dumped may contain the wrong vmcoreinfo. Later on, when using "crash", "makedumpfile", etc utility to parse this vmcore, we probab

[PATCH v3 1/3] kexec: Move vmcoreinfo out of the kernel's .bss section

As Eric said, "what we need to do is move the variable vmcoreinfo_note out of the kernel's .bss section. And modify the code to regenerate and keep this information in something like the control page. Definitely something like this needs a page all to itself, and ideally far away from any other k

linux-next: build failure after merge of the akpm tree

Hi Andrew, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: fs/f2fs/node.c: In function 'init_free_nid_cache': fs/f2fs/node.c:2634:25: error: implicit declaration of function 'f2fs_kvzalloc' [-Werror=implicit-function-declaration] nm_i->free_nid_cou

[PATCH v2] xfs: Honor FALLOC_FL_KEEP_SIZE when punching ends of files

When punching past EOF on XFS, fallocate(mode=PUNCH_HOLE|KEEP_SIZE) will round the file size up to the nearest multiple of PAGE_SIZE: calvinow@vm-disks/generic-xfs-1 ~$ dd if=/dev/urandom of=test bs=2048 count=1 calvinow@vm-disks/generic-xfs-1 ~$ stat test Size: 2048Blocks: 8

Re: [Patch v2 02/11] s5p-mfc: Adding initial support for MFC v10.10

On Wed, 2017-03-15 at 14:52 -0500, Rob Herring wrote: > On Fri, Mar 03, 2017 at 02:37:07PM +0530, Smitha T Murthy wrote: > > Adding the support for MFC v10.10, with new register file and > > necessary hw control, decoder, encoder and structural changes. > > > > Signed-off-by: Smitha T Murthy > >

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

Hi Andrew, After merging the akpm-current tree, today's linux-next build (x86_64 allmodconfig) produced these warnings: drivers/crypto/cavium/zip/zip_main.c: In function 'zip_show_stats': drivers/crypto/cavium/zip/zip_main.c:489:18: warning: format '%ld' expects argument of type 'long int', but

Re: [PATCH 09/15] power: supply: bq24190_charger: Add voltage_max_design prop to battery

Hi, On Fri, Mar 17, 2017 at 10:55:21AM +0100, Hans de Goede wrote: > When combined with an external fuel-gauge, upower needs voltage_max_design > as it internally does all its calculations in Watts and converts the > charge_foo properties from A to Watts by using voltage_max_design. > > Signed-of

linux-next: manual merge of the akpm tree with the net-next tree

Hi Andrew, Today's linux-next merge of the akpm tree got a conflict in: Documentation/devicetree/bindings/net/brcm,unimac-mdio.txt between commit: 0ce5aa1d6c97 ("dt-bindings: net: update bcmgenet binding for GENETv5") from the net-next tree and patch: "scripts/spelling.txt: Add regsiter

Re: [PATCH 26/26] x86/mm: allow to have userspace mappings above 47-bits

"Kirill A. Shutemov" writes: @@ -168,6 +182,10 @@ arch_get_unmapped_area_topdown(struct file *filp, const unsigned long addr0, > unsigned long addr = addr0; > struct vm_unmapped_area_info info; > > + addr = mpx_unmapped_area_check(addr, len, flags); > + if (IS_ERR_VALUE(add

Re: [PATCH v21 00/13] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

Hi Mark, On 18 March 2017 at 04:03, Mark Rutland wrote: > On Thu, Mar 09, 2017 at 11:47:16PM +0100, Fu Wei wrote: >> Hi Mark, Marc, > > Hi, > >> I have tried to rebase all the 19(6+13) patches on 4.11-rc1, >> all the patchse can directly apply on 4.11-rc1, >> >> Could you help to review the pat

Re: [PATCH 14/15] power: supply: Add driver for Cherry Trail Whiskey Cove PMIC Fuel Gauge

Hi, On Fri, Mar 17, 2017 at 10:55:26AM +0100, Hans de Goede wrote: > Add a driver for the Cherry Trail Whiskey Cove PMIC Fuel Gauge, note > the Cherry Trail Whiskey Cove PMIC Fuel Gauge block is purely a fuel gauge > and not a full battery controller. As such it offers a platform_data > callback f

Re: [PATCH] Input: synaptics-rmi4 - Report slot as inactive when contact is a palm

On Thu, Mar 16, 2017 at 05:52:07PM -0700, Andrew Duggan wrote: > On 03/16/2017 05:04 PM, Dmitry Torokhov wrote: > > On Thu, Mar 16, 2017 at 04:56:31PM -0700, Andrew Duggan wrote: > > > When the firmware identifies a contact as a palm the driver sets the tool > > > type to MT_TOOL_PALM, but sets the

Re: Synaptics RMI4 touchpad regression in 4.11-rc1

On Fri, Mar 17, 2017 at 12:23:36PM -0700, Andrew Duggan wrote: > On 03/17/2017 09:57 AM, Benjamin Tissoires wrote: > > On Wed, Mar 15, 2017 at 2:19 AM, Andrew Duggan > > wrote: > > > On 03/13/2017 10:10 PM, Cameron Gutman wrote: > > > > > > > > On 03/13/2017 06:35 PM, Andrew Duggan wrote: > > >

Re: [PATCH 10/15] power: supply: bq24190_charger: Use extcon to determine ilimit, 5v boost

Hi, On Fri, Mar 17, 2017 at 10:55:22AM +0100, Hans de Goede wrote: > Add support for monitoring an extcon device with SDP/CDP/DCP and HOST > cables and adjust ilimit and enable/disable the 5v boost converter > accordingly. This is necessary on systems where the PSEL pin is hardwired > high and ILI

Re: [PATCH v2] kexec: Introduce vmcoreinfo signature verification

On 03/20/2017 at 11:55 AM, Baoquan He wrote: > On 03/20/17 at 10:39am, Xunlei Pang wrote: >> On 03/20/2017 at 10:13 AM, Baoquan He wrote: >>> On 03/17/17 at 12:22pm, Eric W. Biederman wrote: Xunlei Pang writes: > Currently vmcoreinfo data is updated at boot time subsys_initcall(), >>

Re: [PATCH 06/15] power: supply: bq24190_charger: Use i2c-core irq-mapping code

Hi, On Fri, Mar 17, 2017 at 07:24:14PM +0200, Andy Shevchenko wrote: > On Fri, 2017-03-17 at 10:55 +0100, Hans de Goede wrote: > > The i2c-core already maps of irqs before calling the driver's probe > > function and there are no in tree users of > > bq24190_platform_data->gpio_int. > > > > Remove

linux-next: manual merge of the gpio tree with the input tree

Hi Linus, Today's linux-next merge of the gpio tree got a conflict in: drivers/input/misc/soc_button_array.c between commit: a01cd17000a4 ("Input: soc_button_array - use NULL for GPIO connection ID") from the input tree and commit: c5097538c86a ("Input: soc_button_array - Propagate erro

Re: [PATCH v2] kexec: Introduce vmcoreinfo signature verification

On 03/20/17 at 10:39am, Xunlei Pang wrote: > On 03/20/2017 at 10:13 AM, Baoquan He wrote: > > On 03/17/17 at 12:22pm, Eric W. Biederman wrote: > >> Xunlei Pang writes: > >> > >>> Currently vmcoreinfo data is updated at boot time subsys_initcall(), > >>> it has the risk of being modified by some wr

[PATCH v3] ASoC: rt286: fix headphone click/crack noise on Dell XPS 9343 I2S mode

HDA mode fixed the issue by these two commits: '9476d369d7b3 ALSA: hda - Mute headphone pin on suspend on XPS13 9333' '3e1b0c4a9d56 ALSA: hda - Fix click noise at start on Dell XPS13' Apply the same workarounds to rt286 can solve the issue. When jack is plugged, it rapidly generates I2C interrup

Re: [RFC][PATCH 2/2] cpufreq: schedutil: Force max frequency on busy CPUs

On 19-03-17, 14:34, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > The PELT metric used by the schedutil governor underestimates the > CPU utilization in some cases. The reason for that may be time spent > in interrupt handlers and similar which is not accounted for by PELT. > > That ca

Re: [PATCH v5 3/7] perf/sdt: Directly record SDT events with 'perf record'

Thanks Masami for detailed review. Please see my comments below. On Friday 17 March 2017 02:35 PM, Masami Hiramatsu wrote: > Hi Ravi, > > (I avoided to review parser part since it may go to yacc in next version) > > On Tue, 14 Mar 2017 20:36:54 +0530 > Ravi Bangoria wrote: > > [SNIP] >> @@ -151

[PATCH v6] drm/rockchip: Refactor the component match logic.

Currently we are adding all components from the dts, if one of their drivers been disabled, we would not be able to bring up others. Refactor component match logic, follow exynos drm. Signed-off-by: Jeffy Chen Reviewed-by: Andrzej Hajda Acked-by: Mark Yao --- Changes in v6: Add Mark Yao 's A

Re: [PATCH 1/2] cpufreq: schedutil: Fix per-CPU structure initialization in sugov_start()

On 19-03-17, 14:30, Rafael J. Wysocki wrote: > From: Rafael J. Wysocki > > sugov_start() only initializes struct sugov_cpu per-CPU structures > for shared policies, but it should do that for single-CPU policies too. > > That in particular makes the IO-wait boost mechanism work in the > cases whe

Re: [PATCH] cpufreq: Restore policy min/max limits on CPU online

On 17-03-17, 18:40, Rafael J. Wysocki wrote: > On Fri, Mar 17, 2017 at 5:43 PM, Viresh Kumar wrote: > > On 17 March 2017 at 22:01, Rafael J. Wysocki wrote: > > > >> IMO if we are not going to restore the governor, we also should not > >> restore the limits as those things are related. Now, the g

Re: Still OOM problems with 4.9er/4.10er kernels

On Sun, 2017-03-19 at 17:02 +0100, Gerhard Wiesinger wrote: > mount | grep cgroup Just because controllers are mounted doesn't mean they're populated. To check that, you want to look for directories under the mount points with a non-empty 'tasks'. You will find some, but memory cgroup assignment

[PATCH v2] drm/bridge: dw_hdmi: support i2c extended read mode

"I2C Master Interface Extended Read Mode" implements a segment pointer-based read operation using the Special Register configuration. This patch fix https://patchwork.kernel.org/patch/7098101/ mentioned "The current implementation does not support "I2C Master Interface Extended Read Mode" to read

[PATCH 2/4] perf annotate: Avoid division by zero when calculating percent

Currently perf-annotate with --print-line can print -nan(0x8) because of division by zero when calculating percent. So if a sum of samples is zero, skip calculating percent. Before: $ perf annotate --stdio -l Sorted summary for file /home/taeung/workspace/a.out -

[PATCH 3/4] perf annotate: Fix missing setting nr samples on source_line

If using --show-total-period with -l, disasm__calc_percent() use a 'samples' array of source_line. But samples[evidx].nr is always zero so print 0 values as below. Before: $ perf annotate --stdio -l --show-total-period ... 0 :400816: push %rbp 0 :400817:

[PATCH 1/4] perf annotate: Use build-id dir when reading link name

In dso__disassemble_filename() when reading link name from a build-id file, it is failed each time because a build-id file gotten from dso__build_id_filename() is not symbolic link. So use build-id directory path instead of a build-id file name. For example, if build-id file name gotten from dso_

[PATCH 0/4] perf annotate: Bugfixes

Hi, perf-annotate has little bugs so I fix them. I'd appreciate some feedback on this patchset. :) Thanks, Taeung Taeung Song (4): perf annotate: Use build-id dir when reading link name perf annotate: Avoid division by zero when calculating percent perf annotate: Fix missing setting nr sam

[PATCH 4/4] perf annotate: More exactly grep -v of the objdump command

grep -v "file name" in the objdump command cause a side effect eliminating filename:linenr of output of 'objdump -l' if the object file name and source file name are about the same so fix it. The objdump command in symbol__disassemble() can be as below $ objdump -l -d -S -C /home/taeung/hello

Re: [PATCH v2 3/4] watchdog: iTCO_wdt: Fix PMC GCR memory mapping failure

Hi Kuppuswamy, [auto build test ERROR on linus/master] [also build test ERROR on v4.11-rc3 next-20170310] [cannot apply to platform-drivers-x86/for-next tip/x86/core] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0d

[PATCH 2/2 v2] clk: qoriq: Separate root input clock for core PLLs on ls1012a

From: Scott Wood ls1012a has separate input root clocks for core PLLs versus the platform PLL, with the latter described as sysclk in the hw docs. If a second input clock, named "coreclk", is present, this clock will be used for the core PLLs. Signed-off-by: Scott Wood Signed-off-by: Tang Yuant

[PATCH 1/2 v2] dt-bindings: qoriq-clock: Add coreclk

From: Scott Wood ls1012a has separate input root clocks for core PLLs versus the platform PLL, with the latter described as sysclk in the hw docs. Update the qoriq-clock binding to allow a second input clock, named "coreclk". If present, this clock will be used for the core PLLs. Signed-off-by:

RE: [PATCH] HV: properly delay KVP packets when negotiation is in progress

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Friday, March 17, 2017 9:16 AM > To: Long Li > Cc: KY Srinivasan ; Haiyang Zhang > ; Stephen Hemminger > ; de...@linuxdriverproject.org; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH] HV: properly

linux-next: build failure after merge of the char-misc tree

Hi all, After merging the char-misc tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/misc/aspeed-lpc-ctrl.c: In function 'aspeed_lpc_ctrl_mmap': drivers/misc/aspeed-lpc-ctrl.c:51:9: error: implicit declaration of function 'pgprot_dmacoherent' [-Werror=implicit-funct

[PATCH] kvmgt: Hold struct kvm reference

The kvmgt code keeps a pointer to the struct kvm associated with the device, but doesn't actually hold a reference to it. If we do unclean shutdown testing (ie. killing the user process), then we can see the kvm association to the device unset, which causes kvmgt to trigger a device release via a

Re: [PATCH v2] kexec: Introduce vmcoreinfo signature verification

On 03/20/2017 at 10:13 AM, Baoquan He wrote: > On 03/17/17 at 12:22pm, Eric W. Biederman wrote: >> Xunlei Pang writes: >> >>> Currently vmcoreinfo data is updated at boot time subsys_initcall(), >>> it has the risk of being modified by some wrong code during system >>> is running. >>> >>> As a res

[PATCH] vfio: Rework group release notifier warning

The intent of the original warning is make sure that the mdev vendor driver has removed any group notifiers at the point where the group is closed by the user. Theoretically this would be through an orderly shutdown where any devices are release prior to the group release. We can't always count o

Re: [PATCH v6 5/8] dt-bindings: input: touchscreen: Add max11801-ts binding

On Thu, Mar 16, 2017 at 12:35:38PM +0530, Jagan Teki wrote: > From: Jagan Teki > > Add missing documentation of max11801-ts dt-binding details. > > Cc: Mark Rutland > Cc: Rob Herring > Cc: Shawn Guo > Cc: Michael Trimarchi > Signed-off-by: Jagan Teki > --- > Changes for v6: > - Replace the

Linux 4.11-rc3

Another week, another rc. As is our usual pattern after the merge window, rc3 is larger than rc2, but this is hopefully the point where things start to shrink and calm down. We had a late typo in rc2 that affected arm and powerpc (the prep code for the 5-level page tables), and hopefully there are

linux-next: manual merge of the tty tree with the tty.current tree

Hi Greg, Today's linux-next merge of the tty tree got a conflict in: drivers/tty/tty_ldisc.c between commit: 5362544bebe8 ("tty: don't panic on OOM in tty_set_ldisc()") from the tty.current tree and commit: 71472fa9c52b ("tty: Fix ldisc crash on reopened tty") from the tty tree. I fix

Re: [PATCH] x86/mm: trivial code cleanup for memory_map_top_doown()

Hi, Borislav Do you still have some concern on this change? On Tue, Mar 14, 2017 at 11:56:39AM +0800, Wei Yang wrote: >On Mon, Mar 13, 2017 at 07:50:21PM +0100, Borislav Petkov wrote: >>On Fri, Feb 17, 2017 at 10:30:33PM +0800, Wei Yang wrote: >>> In case (last_start <= step_size), start is for s

[PATCH] backlight: Add TI LMU backlight driver

This is consolidated driver which supports backlight devices below. LM3532, LM3631, LM3632, LM3633, LM3695 and LM3697. Structure - It consists of two parts - core and data. Core part supports features below. - Backlight subsystem control - Channel configuration from DT prope

Re: [PATCH v2] kexec: Introduce vmcoreinfo signature verification

On 03/17/17 at 12:22pm, Eric W. Biederman wrote: > Xunlei Pang writes: > > > Currently vmcoreinfo data is updated at boot time subsys_initcall(), > > it has the risk of being modified by some wrong code during system > > is running. > > > > As a result, vmcore dumped may contain the wrong vmcorei

Re: [PATCH] x86_64, kexec: Avoid unnecessary identity mappings for kdump

On 03/18/2017 at 01:38 AM, Eric W. Biederman wrote: > Xunlei Pang writes: > >> kexec setups identity mappings for all the memory mapped in 1st kernel, >> this is not necessary for the kdump case. Actually it can cause extra >> memory consumption for paging structures, which is quite considerable >

Re: [PATCH] kexec: Update vmcoreinfo after crash happened

On 03/19/2017 at 02:23 AM, Petr Tesarik wrote: > On Thu, 16 Mar 2017 21:40:58 +0800 > Xunlei Pang wrote: > >> On 03/16/2017 at 09:18 PM, Baoquan He wrote: >>> On 03/16/17 at 08:36pm, Xunlei Pang wrote: On 03/16/2017 at 08:27 PM, Baoquan He wrote: > Hi Xunlei, > > Did you really se

Re: kexec regression since 4.9 caused by efi

On 03/17/17 at 01:32pm, Matt Fleming wrote: > On Fri, 17 Mar, at 10:09:51AM, Dave Young wrote: > > > > Matt, I think it should be fine although I think the md type checking in > > efi_mem_desc_lookup() is causing confusion and not easy to understand.. > > Could you make that a separate patch if

Re: [PATCH 1/5] mm, swap: Fix comment in __read_swap_cache_async

Hi, Rafeal, Rafael Aquini writes: > On Fri, Mar 17, 2017 at 02:46:19PM +0800, Huang, Ying wrote: >> From: Huang Ying >> >> The commit cbab0e4eec29 ("swap: avoid read_swap_cache_async() race to >> deadlock while waiting on discard I/O completion") fixed a deadlock in >> read_swap_cache_async().

Re: [PATCH v2] kexec: Introduce vmcoreinfo signature verification

On 03/18/2017 at 01:22 AM, Eric W. Biederman wrote: > Xunlei Pang writes: > >> Currently vmcoreinfo data is updated at boot time subsys_initcall(), >> it has the risk of being modified by some wrong code during system >> is running. >> >> As a result, vmcore dumped may contain the wrong vmcoreinfo

Re: [GIT PULL] target fixes for v4.11-rc3

On Sat, Mar 18, 2017 at 7:08 PM, Nicholas A. Bellinger wrote: > > Here are the target-pending fixes for v4.11-rc3 code. So I'm very unhappy with how these patches were rebased or applied just before the pull request. I did my usual build test, but didn't notice how recent it all was until after

[PATCH] rapidio: tsi721: make module parameter variable name unique

From: Randy Dunlap kbuild test robot reported a non-static variable name collision between a staging driver and a RapidIO driver, with a generic variable name of 'dbg_level'. Both drivers should be changed so that they don't use this generic public variable name. This patch fixes the RapidIO dri

Re: Still OOM problems with 4.9er/4.10er kernels

On 2017/03/19 17:17, Gerhard Wiesinger wrote: > On 17.03.2017 21:08, Gerhard Wiesinger wrote: >> On 17.03.2017 18:13, Michal Hocko wrote: >>> On Fri 17-03-17 17:37:48, Gerhard Wiesinger wrote: >>> [...] > > 4.11.0-0.rc2.git4.1.fc27.x86_64 > > There are also lockups after some runtime hours to 1

Re: [RFC] AT_NO_JUMPS/LOOKUP_NO_JUMPS

On Sun, Mar 19, 2017 at 10:24 AM, Al Viro wrote: > Bringing back an old conversation - what do you think about the > potential usefulness of the following ...at() option: > * no mountpoint crossings allowed (mount --bind included) > * only relative symlinks traversals are a

Re: [PATCH 03/15] extcon: cht-wc: Add Intel Cherry Trail Whiskey Cove PMIC extcon driver

Hi, On 2017년 03월 17일 18:55, Hans de Goede wrote: > Add a driver for charger detection / control on the Intel Cherrytrail > Whiskey Cove PMIC. > > Signed-off-by: Hans de Goede > --- > drivers/extcon/Kconfig | 7 + > drivers/extcon/Makefile| 1 + > drivers/extcon/extcon-cht-wc

Re: [x86] 45fc8757d1: BUG:unable_to_handle_kernel

On 03/17, Thomas Garnier wrote: >I tried multiple things to repro this crash without success: > - Used the config on my existing qemu setup (boot fine) > - Add most of the command-line (boot fine) > - Try to run the script on a dedicated machine and it seems it is >really tailored for your setup. I

[PATCH] staging: speakup: Fix alignment with parenthesis.

This patch fixes the warnings reported by checkpatch.pl for please use a blank line after function/struct/union/enum declarations. Signed-off-by: Arushi Singhal --- drivers/staging/speakup/speakup_apollo.c | 2 +- drivers/staging/speakup/speakup_decext.c | 4 ++-- 2 files changed, 3 insertions(+

Re: [PATCH 0/2] Hi all,

Hi, On Thu, Mar 16, 2017 at 11:05:28AM -0500, Andrew F. Davis wrote: > To finish the work started in this patch[0] we needed to reorganize > the 1-wire subsystem a bit, this is done here[1]. After that is taken > this series can remove the need for a platform driver for supporting > 1-wire connect

Re: kernel BUG at mm/swap_slots.c:270

Hi, Michal Hocko writes: > On Sat 18-03-17 09:57:18, Linus Torvalds wrote: >> Tim at al, >> I got this on my desktop at shutdown: >> >> [ cut here ] >> kernel BUG at mm/swap_slots.c:270! >> invalid opcode: [#1] SMP >> CPU: 5 PID: 1745 Comm: (sd-pam) Not tai

Re: [PATCH tip] x86/mm: Correct fixmap header usage on adaptable MODULES_END

On Sun, Mar 19, 2017 at 09:25:00AM -0700, Thomas Garnier wrote: >On Sun, Mar 19, 2017 at 9:03 AM, Wei Yang wrote: >> On Fri, Mar 17, 2017 at 10:50:34AM -0700, Thomas Garnier wrote: >>>This patch remove fixmap header usage on non-x86 code that was >>>introduced by the adaptable MODULE_END change. >

Re: [PATCH] mm, swap: VMA based swap readahead

On Tue, Mar 14, 2017 at 05:25:29PM +0800, Huang, Ying wrote: > +struct page *do_swap_page_readahead(struct vm_fault *vmf, > + struct vma_swap_readahead *swap_ra, > + swp_entry_t fentry, > + struct page *

[PATCH] staging: speakup: Match alignment with open parenthesis.

Fix checkpatch issues: "CHECK: Alignment should match open parenthesis". Signed-off-by: Arushi Singhal --- drivers/staging/speakup/main.c | 2 +- drivers/staging/speakup/selection.c | 2 +- drivers/staging/speakup/serialio.c | 2 +- drivers/staging/speakup/speakup_acntpc.c |

Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver

Em Sun, 19 Mar 2017 10:04:28 -0700 Michael Zoran escreveu: > On Sun, 2017-03-19 at 13:58 -0300, Mauro Carvalho Chehab wrote: > > Em Fri, 17 Mar 2017 17:34:36 -0700 > > Eric Anholt escreveu: > > > > > Mauro Carvalho Chehab writes: > > > > > > > Em Wed, 15 Mar 2017 18:46:24 -0700 > > > > Mi

Re: [PATCH v2] extcon: Allow registering a single notifier for all cables on an extcon_dev

Hi, On 2017년 03월 20일 03:23, Hans de Goede wrote: > In some cases a driver may want to monitor multiple cables on a single > extcon. For example a charger driver will typically want to monitor all > of EXTCON_CHG_USB_SDP, EXTCON_CHG_USB_CDP, EXTCON_CHG_USB_DCP to configure > the max. current it can

Re: [PATCH] ASoC: omap: constify snd_soc_ops structures

Hi, On Sat, Mar 18, 2017 at 07:34:11PM +0530, Bhumika Goyal wrote: > Declare snd_soc_ops structures as const as they are only stored > in the ops field of a snd_soc_dai_link structure. This field is > of type const, so snd_soc_ops structures having this property > can be made const too. > > Cross

linux-next: build failure after merge of the drm tree

Hi Dave, After merging the drm tree, today's linux-next build (x86_64 allmodconfig) failed like this: drivers/gpu/drm/i915/i915_irq.c: In function 'gen6_rps_reset_ei': drivers/gpu/drm/i915/i915_irq.c:1115:38: error: 'struct intel_gen6_power_mgmt' has no member named 'down_ei' vlv_c0_read(dev_p

[PATCH trivial] drivers: Clean up duplicated email address

My email address may be found in the git commit logs and in MAINTAINERS. Remove duplicate addresses so they won't have to be kept up-to-date. Signed-off-by: Finn Thain diff --git a/drivers/macintosh/via-macii.c b/drivers/macintosh/via-macii.c index 3725f08..415c145 100644 --- a/drivers/macintos

[PATCH] ASoC: Add support for Maxim Integrated MAX98927 Amplifier

Signed-off-by: Ryan Lee --- Resubmit the intial version of MAX98927 driver. Added all fixes into the initial patch. .../devicetree/bindings/sound/max98927.txt | 39 + sound/soc/codecs/Kconfig |5 + sound/soc/codecs/Makefile |2

[PATCH v3 1/9] i2c: export i2c_client_type structure

i2c bus has 2 different types of device belonging to the same bus and bus notifiers use device type to distinguish between adapters and clients. Previously we only had i2c_adapter_type exported, which made code wanting to work with i2c_client devices test for type not equal to adapter type. This un

[PATCH v3 6/9] Input: psmouse - add support for SMBus companions

From: Benjamin Tissoires This provides glue between PS/2 devices that enumerate the RMI4 devices and Elan touchpads to the RMI4 (or Elan) SMBus driver. The SMBus devices keep their PS/2 connection alive. If the initialization process goes too far (psmouse_activate called), the device disconnects

[PATCH v3 5/9] Input: psmouse - introduce notion of SMBus companions

Prepare PS/2 mouse drivers to work with devices that are accessible both via PS/2 and SMBus, which provides higher bandwidth, and thus suits better for modern multi-touch devices. We expect that SMBus drivers will take control over the device, so when we detect SMBus "protocol" we forego registeri

[PATCH v3 9/9] [NEEDS F21] Input: synaptics - switch forcepad devices over to SMbus access

Synaptics "forcedpad" devices use address 0x20 instead of 0x2c. Unfortunately the fact that the device is a forcepad is not exported through PS/2 interface, so we need a bit of DMI magic to switch over to the correct address. Reviewed-by: Benjamin Tissoires Signed-off-by: Dmitry Torokhov --- dr

[PATCH v3 8/9] Input: synaptics - add support for Intertouch devices

From: Benjamin Tissoires Most of the Synaptics devices are connected through PS/2 and a different bus (SMBus or HID over I2C). The secondary bus capability is indicated by the InterTouch bit in extended capability 0x0C. We only enable the InterTouch device to be created for the laptops registere

[PATCH v3 7/9] Input: synaptics - split device info into a separate structure

In preparation for SMBus/Intertouch device support, move static device information that we query form the touchpad upon initialization into separate structure. This will allow us to query the device without allocating memory first. Also stop using "unsigned long", everything fits into 32 bit chunk

[PATCH v3 2/9] Input: serio - add fast reconnect option

Devices connected to serio bus are quite slow, and to improve apparent speed of resume process, serio core resumes (reconnects) its devices asynchronously, by posting port reconnect requests to a workqueue. Unfortunately this means that if there is a dependent device of a given serio port (for exam

  1   2   3   4   >