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

Hi all, After merging the akpm tree, today's linux-next build (x86_64 allmodconfig) failed like this: In file included from include/linux/bitmap.h:8:0, from include/linux/cpumask.h:11, from include/linux/mm_types_task.h:13, from

[PATCH] crypto: ccp-platform: print error message on platform_get_irq failure

Print error message on platform_get_irq failure before return. Signed-off-by: Gustavo A. R. Silva --- drivers/crypto/ccp/ccp-platform.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/crypto/ccp/ccp-platform.c

[PATCH 2/6] Staging: rtl8712 : os_intfs.c: use octal permission representation

Fix checkpatch.pl Warning: Symbolic permissions 'S_IRUGO | S_IWUSR' are not preferred. Consider using octal permissions '0644'. Signed-off-by: Jaya Durga --- drivers/staging/rtl8712/os_intfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v1 0/4] media: rc: add support for IR receiver on MT7622 SoC

From: Sean Wang This patchset introduces Consumer IR (CIR) support for MT7622 SoC implements raw mode for more compatibility with different protocols as previously SoC did. Before adding support to MT7622 SoC, extra code refactor is done since there're major differences

[PATCH v1 3/4] media: rc: mtk-cir: add support for MediaTek MT7622 SoC

From: Sean Wang This patch adds driver for CIR controller on MT7622 SoC. It has similar handling logic as the previously MT7623 does, but there are some differences in the register and field definition. So for ease portability and maintenance, those differences all are

Re: [kernel-hardening] Re: [PATCH v4 06/13] iscsi: ensure RNG is seeded before use

On Mon, 2017-06-26 at 19:38 +0200, Stephan Müller wrote: > Am Montag, 26. Juni 2017, 03:23:09 CEST schrieb Nicholas A. Bellinger: > > Hi Nicholas, > > > Hi Stephan, Lee & Jason, > > > > (Adding target-devel CC') > > > > Apologies for coming late to the discussion. Comments below. > > > > On

Re: [PATCH v3] staging: lustre: lnet: remove dead code and crc32_le() wrapper

On Fri, Jun 30, 2017 at 03:52:46AM +, Dmitriy Cherkasov wrote: > After removing code which was premanently disabled with ifdefs, the > function ksocknal_csum() becomes just a wrapper for crc32_le(). Remove > this useless wrapper and instead call crc32_le() directly. > > This also resolves the

arm64: dts: rockchip: add SdioAudio pd control for rk3399

The SdioAudio power domain includes the i2s/spdif/spi5/sdio. So this patch adds the pd control for rk3399 i2s/spdif/spi5/sdio, in order to save more power consumption. Signed-off-by: Caesar Wang --- Changes note: - As the Jeffy fixes the spi'cs issue recently as follows:

Re: [patch 1/5] pinctrl: samsung: Remove bogus irq_[un]mask from resource management

On Fri, Jun 30, 2017 at 4:47 AM, Tomasz Figa wrote: > Hi Thomas, > > 2017-06-30 6:33 GMT+09:00 Thomas Gleixner : >> The irq chip callbacks irq_request/release_resources() have absolutely no >> business with masking and unmasking the irq. >> >> The core

[PATCH v1 4/4] MAINTAINERS: add entry for MediaTek CIR driver

From: Sean Wang I work for MediaTek on maintaining the MediaTek CIR driver for the existing SoCs and adding support for the following SoCs. Signed-off-by: Sean Wang --- MAINTAINERS | 5 + 1 file changed, 5 insertions(+) diff --git

Re: [PATCH 00/37] fine-grained locking in binder driver

On Thu, Jun 29, 2017 at 12:01:34PM -0700, Todd Kjos wrote: > The binder driver uses a global mutex to serialize access to state in a > multi-threaded environment. This global lock has been increasingly > problematic as Android devices have scaled to more cores. The problem is > not so much

[PATCH v1 2/4] media: rc: mtk-cir: add platform data to adapt into various hardware

From: Sean Wang This patch is the preparation patch in order to adapt into various hardware through adding platform data which holds specific characteristics and differences among MediaTek supported CIR devices instead of the old way defining those data in the static way

[PATCH v1 1/4] dt-bindings: media: mtk-cir: Add support for MT7622 SoC

From: Sean Wang Document the devicetree bindings for CIR on MediaTek MT7622 SoC. Signed-off-by: Sean Wang --- Documentation/devicetree/bindings/media/mtk-cir.txt | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git

Re: [PATCH 36/37] binder: fix death race conditions

On Thu, Jun 29, 2017 at 12:02:10PM -0700, Todd Kjos wrote: > From: Martijn Coenen > > A race existed where one thread could register > a death notification for a node, while another > thread was cleaning up that node and sending > out death notifications for its references, >

[PATCH v3 5/6] pwm: mediatek: add PWM_CLK_DIV_MAX

1. Replace "7" with "PWM_CLK_DIV_MAX" in function:mtk_pwm_config() to improve the code readablity. 2. add pwm clk disable in function:mtk_pwm_config() for error parameter checking case. Signed-off-by: Zhi Mao --- drivers/pwm/pwm-mediatek.c |7 ++- 1 file changed, 6

[PATCH v3 2/6] pwm: mediatek: fix pwm source clock selection

In original code, the pwm output frequency is not correct when set bit<3>=1 to PWMCON register. Signed-off-by: Zhi Mao --- drivers/pwm/pwm-mediatek.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pwm/pwm-mediatek.c

[PATCH v3 6/6] pwm: mediatek: add MT2712/MT7622 support

1. support multiple chip(MT2712, MT7622, MT7623) 2. add mtk_pwm_com_reg for match the registers of MT2712 pwm8 the register offset address of pwm8 for MT2712 is not fixed 0x40 and they are not the same as pwm0~6. Signed-off-by: Zhi Mao --- drivers/pwm/pwm-mediatek.c

[PATCH v3 4/6] pwm: bindings: add MT2712/MT7622 information

add MT2712/MT7622 pwm information Acked-by: Rob Herring Signed-off-by: Zhi Mao --- .../devicetree/bindings/pwm/pwm-mediatek.txt |6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

[PATCH v3 1/6] pwm: kconfig: modify mediatek information

modify mediatek information Signed-off-by: Zhi Mao --- drivers/pwm/Kconfig |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig index 313c107..45cdf2a 100644 --- a/drivers/pwm/Kconfig +++ b/drivers/pwm/Kconfig @@

[PATCH v3 3/6] pwm: mediatek: fix clock control issue

1. prepare top/main clk in mtk_pwm_probe() function, it will increase power consumption and in original code these clocks is only prepeare but never enabled. 2. pwm clock should be enabled before setting pwm registers in function: mtk_pwm_config(). 3. delete "pwm_disable" in

[PATCH v3 0/6] mediatek: pwm driver add MT2712/MT7622 support

change in v3: 1. add pwm clk disable in function:mtk_pwm_config() for error parameter checking case Zhi Mao (6): pwm: kconfig: modify mediatek information pwm: mediatek: fix pwm source clock selection pwm: mediatek: fix clock control issue pwm: bindings: add MT2712/MT7622 information

Re: [PATCH NET V7 0/2] Add loopback support in phy_driver and hns ethtool fix

Hi, David I will send out a patch based on net-next, and I will continue to address the problem andrew pointed out. If I come out with a doable solution, I will send out the new patch. Best Regards Yunsheng Lin On 2017/6/30 4:08, David Miller wrote: > From: Andrew Lunn > Date:

Re: [PATCH v2 0/2] x86/boot/KASLR: Code bug fix about kernel virtual address randomization

On 06/27/17 at 08:39pm, Baoquan He wrote: > People complained that crashkernel high doesn't work when kaslr code > compiled in but add 'nokaslr' to diable it. Kexec has the same > phenomenon. This is a regression, with 4.12* kernel kexec reboot fails always on my desktop pc now without kaslr

pull-request: wireless-drivers-next 2017-06-30

Hi Dave, here's a pull request to net-next for 4.13. Actually not really that big this time, more info in the signed tag below. Please let me know if you have any problems. Intel has new hardware coming up and they just submitted patches to iwlwifi supporting that, but because the patches were

Re: [patch 1/5] pinctrl: samsung: Remove bogus irq_[un]mask from resource management

2017-06-30 15:02 GMT+09:00 Krzysztof Kozlowski : > On Fri, Jun 30, 2017 at 4:47 AM, Tomasz Figa wrote: >> Hi Thomas, >> >> 2017-06-30 6:33 GMT+09:00 Thomas Gleixner : >>> The irq chip callbacks irq_request/release_resources() have

Re: [PATCH v3 4/4] crypto: caam: cleanup CONFIG_64BIT ifdefs when using io{read|write}64

On 6/29/2017 7:10 PM, Logan Gunthorpe wrote: > From: Horia Geantă > > We can now make use of the io-64-nonatomic-hi-lo header to always Typo: we are using io-64-nonatomic-lo-hi, not hi-lo. Thanks, Horia

Re: [PATCH] vmalloc: respect the GFP_NOIO and GFP_NOFS flags

On 06/29/2017 07:25 PM, Mikulas Patocka wrote: > The __vmalloc function has a parameter gfp_mask with the allocation flags, > however it doesn't fully respect the GFP_NOIO and GFP_NOFS flags. The > pages are allocated with the specified gfp flags, but the pagetables are > always allocated with

[PATCH] crypto: mediatek: fix error return code in mtk_crypto_probe()

Propagate the return value of platform_get_irq on failure. Signed-off-by: Gustavo A. R. Silva --- drivers/crypto/mediatek/mtk-platform.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/crypto/mediatek/mtk-platform.c

Question regarding MAX_ARG_STRLEN with execve()

Hello, execve() system call should support argument length of MAX_ARG_STRLEN (PAGE_SIZE * 32). On 64K page size systems, we are not able to pass 32 * PAGE_SIZE arguments into the execve() system call because of the following reasons. * struct linux_binprm's vma starts with a size of PAGE_SIZE

Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900

On 29/06/17 21:50, Aaro Koskinen wrote: > Hi, > > On Thu, Jun 15, 2017 at 09:51:06AM +0300, Tomi Valkeinen wrote: >> On 15/06/17 01:11, Aaro Koskinen wrote: >>> When booting v4.12-rc5 on Nokia N900, omapdrm fails to probe and there >>> is no display. >> >> Are you sure it doesn't probe? It fails

[PATCH] crypto: mxc-scc: fix error code in mxc_scc_probe()

Print and propagate the return value of platform_get_irq on failure. Signed-off-by: Gustavo A. R. Silva --- drivers/crypto/mxc-scc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/crypto/mxc-scc.c b/drivers/crypto/mxc-scc.c index

Re: [PATCH] PM / sleep: constify attribute_group structures.

On Fri 2017-06-30 10:22:14, Arvind Yadav wrote: > attribute_groups are not supposed to change at runtime. All functions > working with attribute_groups provided by work with const > attribute_group. So mark the non-const structs as const. > > File size before: >text data bss

Re: [RFC 0/5] drivers: Add boot constraints core

= On Fri, Jun 30, 2017 at 1:12 PM, Viresh Kumar wrote: > On 30-06-17, 12:22, Chen-Yu Tsai wrote: >> On Fri, Jun 30, 2017 at 12:12 PM, Viresh Kumar >> wrote: >> > On 30-06-17, 12:05, Chen-Yu Tsai wrote: > >> >> I also want to mention that for DT

[PATCH v3] acpi: handle the acpi hotplug schedule error

Kernel should decrements the reference count of acpi device when the scheduling of acpi hotplug work failed, and evaluates _OST to notify BIOS the failure. v3: More simplify the code. (Rafael J. Wysocki) v2: To simplify the code. (Andy Shevchenko) Cc: "Rafael J. Wysocki"

Re: [PATCH v2 04/20] gcc-plugins: Add the randstruct plugin

On Fri, Jun 30, 2017 at 12:53 AM, Kees Cook wrote: > On Thu, Jun 29, 2017 at 3:08 PM, Arnd Bergmann wrote: >> On Fri, May 26, 2017 at 10:17 PM, Kees Cook wrote: >> I noticed new build errors that bisected back to this patch, which has

[PATCH] dmaengine: zx: add check on platform_get_irq return value

Check return value from call to platform_get_irq(), so in case of failure print error message and propagate the return value. Signed-off-by: Gustavo A. R. Silva --- drivers/dma/zx_dma.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/dma/zx_dma.c

Re: [PATCH 5/6] i2c: pca-platform: use device_property_read_u32

On Fri, Jun 30, 2017 at 3:54 AM, Chris Packham wrote: > Use device_property_read_u32 instead of of_property_read_u32_index to > lookup the "clock-frequency" property. My comments below. > > Signed-off-by: Chris Packham > ---

Re: Regarding your thread on LKML - drm_radeon spamming alloc_contig_range [WAS: Re: PROBLEM-PERSISTS: dmesg spam: alloc_contig_range: [XX, YY) PFNs busy]

[CC Vlastimil, Joonsoo] On Thu 29-06-17 17:47:05, Robin H. Johnson wrote: > CC'd back to LKML. > > On Thu, Jun 29, 2017 at 06:11:00PM +0530, Kumar Abhishek wrote: > > Hi Robin, > > > > I am an independent developer who stumbled upon your thread on the LKML > > after facing a similar issue - my

Re: [PATCH v2] PCI / PM: Avoid using device_may_wakeup() for runtime PM

On Fri, Jun 30, 2017 at 12:37:00AM +0200, Rafael J. Wysocki wrote: > On Friday, June 23, 2017 02:58:11 PM Rafael J. Wysocki wrote: > > From: Rafael J. Wysocki > > > > pci_target_state() calls device_may_wakeup() which checks whether > > or not the device may wake up

Re: [PATCH 5/6] i2c: pca-platform: use device_property_read_u32

> > - i2c->algo_data.i2c_clock = 59000; > > + ret = device_property_read_u32(>dev, > > "clock-frequency", > > + >algo_data.i2c_clock); > > + if (ret) > > + i2c->algo_data.i2c_clock =

Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900

On 30/06/17 11:58, Aaro Koskinen wrote: > Hi, > > On Fri, Jun 30, 2017 at 09:41:35AM +0300, Tomi Valkeinen wrote: >> On 29/06/17 21:50, Aaro Koskinen wrote: >>> On Thu, Jun 15, 2017 at 09:51:06AM +0300, Tomi Valkeinen wrote: On 15/06/17 01:11, Aaro Koskinen wrote: > When booting

[PATCH] crypto: mxs-dcp: print error message on platform_get_irq failure

Print error message on platform_get_irq failure before return. Signed-off-by: Gustavo A. R. Silva --- drivers/crypto/mxs-dcp.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/crypto/mxs-dcp.c b/drivers/crypto/mxs-dcp.c index

[PATCH v2] clocksource: em_sti: fix error return codes in em_sti_probe()

Propagate the return values of platform_get_irq and devm_request_irq on failure. Cc: Frans Klaver Signed-off-by: Gustavo A. R. Silva --- Changes in v2: Use 'ret' instead of 'irq' for taking the result of devm_request_irq.

Re: [PATCH v2 04/19] media: camss: Add CSIPHY files

Hi Sakari, On 06/30/2017 02:53 AM, Sakari Ailus wrote: > Hi Todor, > > On Thu, Jun 29, 2017 at 07:36:47PM +0300, Todor Tomov wrote: +/* + * csiphy_link_setup - Setup CSIPHY connections + * @entity: Pointer to media entity structure + * @local: Pointer to local pad + *

Re: [PATCH] mm: convert three more cases to kvmalloc

On Thu 29-06-17 22:13:26, Mikulas Patocka wrote: > > > On Thu, 29 Jun 2017, Michal Hocko wrote: [...] > > > Index: linux-2.6/kernel/bpf/syscall.c > > > === > > > --- linux-2.6.orig/kernel/bpf/syscall.c > > > +++

[PATCH] devfreq: tegra: fix error code in tegra_devfreq_probe()

Print and propagate the return value of platform_get_irq on failure. Signed-off-by: Gustavo A. R. Silva --- drivers/devfreq/tegra-devfreq.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/devfreq/tegra-devfreq.c

[PATCH] dt-bindings: nvmem: mediatek: add support for MediaTek MT7623 and MT7622 SoC

From: Sean Wang This updates dt-binding documentation for MediaTek MT7622 and MT7623 SoC. For the both SoCs supported all rely on the fallback binding of the generic case with "mediatek,efuse". Signed-off-by: Sean Wang Signed-off-by: Andrew-CT

[PATCH] nvmem: core: remove unneeded NULL check

"p" is the list iterator so it can't be NULL. Static checkers complain about this unnecessary check because we dereference the list iterator to get the next item in the list so we'd be in trouble if it really was NULL. I have removed the check. Signed-off-by: Dan Carpenter

[PATCH] fs: 9p: v9fs: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 2739 80 282847 b1f

[GIT PULL] overlayfs fixes for 4.12-final

Hi Linus, Please pull from: git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git overlayfs-linus Fix two bugs in copy-up code. One introduced in 4.11 and one in 4.12-rc. Thanks, Miklos --- Miklos Szeredi (2): ovl: copy-up: don't unlock between lookup and link ovl:

Re: [PATCH] vmalloc: respect the GFP_NOIO and GFP_NOFS flags

On Thu 29-06-17 22:25:09, Mikulas Patocka wrote: > The __vmalloc function has a parameter gfp_mask with the allocation flags, > however it doesn't fully respect the GFP_NOIO and GFP_NOFS flags. The > pages are allocated with the specified gfp flags, but the pagetables are > always allocated with

Re: [PATCH v2 04/20] gcc-plugins: Add the randstruct plugin

On Fri, Jun 30, 2017 at 9:55 AM, Ard Biesheuvel wrote: > On 30 June 2017 at 07:35, Arnd Bergmann wrote: >> On Fri, Jun 30, 2017 at 12:53 AM, Kees Cook wrote: >>> The first obviously won't fly. The second just bypasses the problem

Re: [v3 5/6] mm, oom: don't mark all oom victims tasks with TIF_MEMDIE

On Thu 29-06-17 14:45:13, Roman Gushchin wrote: > On Thu, Jun 29, 2017 at 10:53:57AM +0200, Michal Hocko wrote: > > On Wed 21-06-17 22:19:15, Roman Gushchin wrote: > > > We want to limit the number of tasks which are having an access > > > to the memory reserves. To ensure the progress it's enough

Re: [PATCH 3/6] i2c: pca-platform: propagate error from i2c_pca_add_numbered_bus

On Fri, Jun 30, 2017 at 3:54 AM, Chris Packham wrote: > Rather than returning -ENODEV if i2c_pca_add_numbered_bus() fails, > propagate the error to aid debugging. > + Suggested-by ? You or Wolfram can use below if you agree on it (I'm fine either way):

Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900

On 30/06/17 09:41, Tomi Valkeinen wrote: > So, I don't know... I guess I need to try to invent some horrible hacks > around the driver to somehow manage the omap3 problems. Perhaps > disabling/enabling the outputs when sync lost happens... Well, I tried that (attached), but it didn't work

Re: [PATCH 3/6] i2c: pca-platform: propagate error from i2c_pca_add_numbered_bus

On Fri, Jun 30, 2017 at 11:40:51AM +0300, Andy Shevchenko wrote: > On Fri, Jun 30, 2017 at 3:54 AM, Chris Packham > wrote: > > Rather than returning -ENODEV if i2c_pca_add_numbered_bus() fails, > > propagate the error to aid debugging. > > > > + Suggested-by ?

[PATCH] ASoC: ak4642: make arrays fs_list and ps_list static const

From: Colin Ian King Don't populate the arrays fs_list and ps_list on the stack but make them static const. Makes the object code smaller: Before: textdata bss dec hex filename 120844888 64 17036428c sound/soc/codecs/ak4642.o

Re: [PATCH RFC 12/26] arm64: Remove spin_unlock_wait() arch-specific definitions

On Thu, Jun 29, 2017 at 05:01:20PM -0700, Paul E. McKenney wrote: > There is no agreed-upon definition of spin_unlock_wait()'s semantics, > and it appears that all callers could do just as well with a lock/unlock > pair. This commit therefore removes the underlying arch-specific >

[PATCH] eCryptfs: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 6122 636 2467821a7e

[PATCH] mfd: rtsx: make arrays depth and cd_mask static const

From: Colin Ian King Don't populate the arrays depath and cd_mask on the stack but make them static const. Makes the object code smaller: textdata bss dec hex filename 254137216 448 330778135 drivers/mfd/rtsx_pcr.o textdata

Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900

Hi, On Fri, Jun 30, 2017 at 11:47:55AM +0300, Tomi Valkeinen wrote: > > So, I don't know... I guess I need to try to invent some horrible hacks > > around the driver to somehow manage the omap3 problems. Perhaps > > disabling/enabling the outputs when sync lost happens... > > Well, I tried that

Re: [PATCH] [media] davinci/dm644x: work around ccdc_update_raw_params trainwreck

Hi Arnd, On Tue, Jun 27, 2017 at 12:08 PM, Arnd Bergmann wrote: > On Tue, Jun 27, 2017 at 12:13 PM, Sekhar Nori wrote: >> On Tuesday 20 June 2017 06:36 PM, Lad, Prabhakar wrote: >>> Hi Arnd, >>> >>> Thanks for the patch. >>> >>> On Fri, Jun 9, 2017 at 10:36 PM,

Re: [PATCH v4 6/6] ARM: sun4i: Convert to CCU

Hi, On Sun, Jun 25, 2017 at 11:45:47PM +0300, Priit Laes wrote: > osc24M: clk@01c20050 { > #clock-cells = <0>; > compatible = "allwinner,sun4i-a10-osc-clk"; > @@ -187,487 +176,12 @@ > clock-output-names = "osc24M"; >

Re: [PATCH] mm: Fix overflow check in expand_upwards()

On 30.06.2017 01:02, Jörn Engel wrote: > I believe the overflow check was correct, then got subtly broken by > commit bd726c90b6b8 > Author: Helge Deller > Date: Mon Jun 19 17:34:05 2017 +0200 > > Allow stack to grow up to address space limit > > The

linux-next: Tree for Jun 30

Hi all, Changes since 20170629: The net-next tree gained a conflict against Linus' tree. The sound-asoc tree still had its build failure so I applied a supplied patch. The block tree gained a conflict against Linus' tree. The akpm tree gained a build failure due to an interaction with the

Re: [RFC][PATCHv3 2/5] printk: introduce printing kernel thread

Hello, On (06/29/17 16:33), Sergey Senozhatsky wrote: [..] > On (06/28/17 14:19), Petr Mladek wrote: > [..] > > > so I try to minimize the negative impact of RT prio here. printk_kthread > > > is not special any more. it's an auxiliary kthread that we sometimes > > > wake_up. the thing is that

[PATCH] crypto: omap-aes: fix error return code in omap_aes_probe()

Propagate the return value of platform_get_irq on failure. Signed-off-by: Gustavo A. R. Silva --- drivers/crypto/omap-aes.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/crypto/omap-aes.c b/drivers/crypto/omap-aes.c index 5120a17..c376a3e 100644 ---

Re: git send-email (w/o Cc: stable)

On Thu, Jun 29, 2017 at 03:11:37PM -0700, Luck, Tony wrote: > So there is a "--cc-cmd" option that can do the same as those "-cc" arguments. > Combine that with --suppress-cc=bodycc and things get a bit more automated. Yeah, whatever works for you. I did play with cc-cmd somewhat but can't be

Re: [PATCH] mm: Fix overflow check in expand_upwards()

* Helge Deller : > On 30.06.2017 01:02, Jörn Engel wrote: > > I believe the overflow check was correct, then got subtly broken by > > commit bd726c90b6b8 > > Author: Helge Deller > > Date: Mon Jun 19 17:34:05 2017 +0200 > > > > Allow stack to

[PATCH] dmaengine: idma64: print error message on platform_get_irq failure

Print error message on platform_get_irq failure before return. Signed-off-by: Gustavo A. R. Silva --- drivers/dma/idma64.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/dma/idma64.c b/drivers/dma/idma64.c index 1953e57..08ade66 100644

RFC: changed error code when binding unix socket twice

Hello, commit 0fb44559ffd6 ("af_unix: move unix_mknod() out of bindlock") moves the special file creation in unix_bind() before u->bindlock is taken in order to avoid an ABBA deadlock with do_splice(). As a side effect, it also moves the check for existence of the special file (which would result

[PATCH] dmaengine: zynqmp_dma: fix error return code in zynqmp_dma_chan_probe()

Print error message and propagate the return value of platform_get_irq on failure. Signed-off-by: Gustavo A. R. Silva --- drivers/dma/xilinx/zynqmp_dma.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/dma/xilinx/zynqmp_dma.c

[PATCH 1/2] scsi: lpfc: spin_lock_irq() is not nestable

We're calling spin_lock_irq() multiple times, the problem is that on the first spin_unlock_irq() then we will re-enable IRQs and we don't want that. Fixes: 966bb5b71196 ("scsi: lpfc: Break up IO ctx list into a separate get and put list") Signed-off-by: Dan Carpenter

Re: [PATCH v2 2/2] thermal: core: Allow to disable polling when disabling thermal zone.

Hi Rui, 2017-06-30 7:05 GMT+02:00 Zhang Rui : > On Thu, 2017-06-29 at 18:50 +0200, Enric Balletbo i Serra wrote: >> Under each thermal zone there is a optional file called "mode". >> Writing >> enabled or disabled to this file allows a given thermal zone to be >> enabled >>

Re: [RFC 0/5] drivers: Add boot constraints core

On 30-06-17, 14:36, Chen-Yu Tsai wrote: > = On Fri, Jun 30, 2017 at 1:12 PM, Viresh Kumar > wrote: > > Right, but someone needs to get the regulator first to have that > > considered by the regulator core while deciding the final range. > > AFAIK the regulator core

[PATCH V3 25/37] perf script: Add synthesized Intel PT power and ptwrite events

Add definitions for synthesized Intel PT events for power and ptwrite. Signed-off-by: Adrian Hunter --- Changes in V3: Avoid using __packed tools/perf/builtin-script.c | 114 +- tools/perf/util/event.h | 118

[PATCH V3 33/37] perf intel-pt: Synthesize new power and ptwrite events

Synthesize new power and ptwrite events. Signed-off-by: Adrian Hunter --- Changes in V3: Use perf_synth__raw_size() and perf_synth__raw_data() as a result of avoiding __packed tools/perf/util/intel-pt.c | 283

Re: [PATCH 6/8] drm: Allow DSI devices to be registered before the host registers.

On 29.06.2017 17:22, Eric Anholt wrote: > Andrzej Hajda writes: > >> On 29.06.2017 07:03, Archit Taneja wrote: >>> On 06/28/2017 01:28 AM, Eric Anholt wrote: When a mipi_dsi_host is registered, the DT is walked to find any child nodes with compatible strings. Those

Re: [PATCH v5] drm/sun4i: hdmi: Implement I2C adapter for A10s DDC bus

Hi, On Fri, Jun 30, 2017 at 08:22:13AM +1000, Jonathan Liu wrote: > Hi Maxime, > > On 30 June 2017 at 01:56, Maxime Ripard > wrote: > > On Wed, Jun 28, 2017 at 08:39:33PM +1000, Jonathan Liu wrote: > >> >> + u32 int_status; > >> >> + u32 fifo_status; >

Re: [PATCH] sata_rcar: fix error return code in sata_rcar_probe()

Hello! On 6/30/2017 8:22 AM, Gustavo A. R. Silva wrote: Print error message and propagate the return value of platform_get_irq on failure. You should have probably mentioned that this function no longer returns 0 on error. Signed-off-by: Gustavo A. R. Silva

Re: [PATCH 2/2] mm, memory_hotplug: remove zone restrictions

On Fri 30-06-17 17:39:56, Wei Yang wrote: > On Fri, Jun 30, 2017 at 4:39 PM, Michal Hocko wrote: [...] > > yes and to be honest I do not plan to fix it unless somebody has a real > > life usecase for it. Now that we allow explicit onlininig type anywhere > > it seems like a

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

Hi Stephen, On Fri, Jun 30, 2017 at 6:56 AM, Stephen Rothwell wrote: > After merging the pinctrl tree, today's linux-next build (x86_64 > allmodconfig) produced this warning: > > drivers/pinctrl/pinctrl-rza1.c: In function 'rza1_pinctrl_probe': >

Re: [PATCH 0/5] Last bits for initial 5-level paging enabling

* Kirill A. Shutemov wrote: > > > Can I apply them in this order cleanly, without breaking bisection: > > > > > > > x86/mm: Rename tasksize_32bit/64bit to task_size_32bit/64bit > > > > x86/mpx: Do not allow MPX if we have mappings above 47-bit > > > > x86/mm:

RE: [PATCH] staging: fsl-dpaa2/eth: Remove dead code

> -Original Message- > From: Ioana Radulescu [mailto:ruxandra.radule...@nxp.com] > Sent: Thursday, June 29, 2017 7:26 PM > To: gre...@linuxfoundation.org > Cc: de...@driverdev.osuosl.org; linux-kernel@vger.kernel.org; > ag...@suse.de; a...@arndb.de; linux-arm-ker...@lists.infradead.org;

Re: [PATCH 1/2] KVM: nVMX: Implement EPTP switching for the L1 hypervisor

- Original Message - > From: "Bandan Das" > To: k...@vger.kernel.org > Cc: pbonz...@redhat.com, linux-kernel@vger.kernel.org > Sent: Friday, June 30, 2017 1:29:55 AM > Subject: [PATCH 1/2] KVM: nVMX: Implement EPTP switching for the L1 hypervisor > > This is a mix of

Re: [PATCH v1] xen/input: add multi-touch support

Hi, Dmitry! On 06/29/2017 10:24 PM, Dmitry Torokhov wrote: On June 29, 2017 11:40:30 AM PDT, Oleksandr Andrushchenko wrote: Hi, Dmitry! First of all thank you for both the comments and the patch On 06/29/2017 11:17 AM, Dmitry Torokhov wrote: Hi Oleksandr, On Fri, Jun

Re: [PATCH RFC 2/2] dt-bindings: add binding documentation for Allwinner CSI

On Fri, 30 Jun 2017 11:41:50 +0800 Chen-Yu Tsai wrote: > On Fri, Jun 30, 2017 at 5:19 AM, Rob Herring wrote: > > On Tue, Jun 27, 2017 at 07:07:34PM +0800, Yong Deng wrote: > >> Add binding documentation for Allwinner CSI. > > > > For the subject: > > > >

Re: [PATCH v2 04/20] gcc-plugins: Add the randstruct plugin

On 30 June 2017 at 07:35, Arnd Bergmann wrote: > On Fri, Jun 30, 2017 at 12:53 AM, Kees Cook wrote: >> On Thu, Jun 29, 2017 at 3:08 PM, Arnd Bergmann wrote: >>> On Fri, May 26, 2017 at 10:17 PM, Kees Cook wrote: >>> I

Re: [PATCH V1 7/9] clk: sprd: add adjustable pll support

Hi Stephen, On 30 June 2017 at 09:44, Stephen Boyd wrote: > On 06/22, Chunyan Zhang wrote: >> On 20 June 2017 at 09:37, Stephen Boyd wrote: >> > On 06/18, Chunyan Zhang wrote: >> >> diff --git a/drivers/clk/sprd/Makefile b/drivers/clk/sprd/Makefile >>

[PATCH] powerpc/64s: watchdog false positive warning at CPU unplug

CPU unplug will call stop_wd_on_cpu regardless if the watchdog has been configured to be enabled on that CPU. Don't warn in the case it's not in our enabled mask, this is a valid case. Fixes: powerpc-64s-implement-arch-specific-hardlockup-watchdog.patch Reported-by: Santosh Sivaraj

Re: [PATCH RFC] x86/smpboot: Unbreak CPU0 hotplug

Vitaly Kuznetsov writes: > A hang on CPU0 onlining after a preceding offlining is observed. Trace > shows that CPU0 is stuck in check_tsc_sync_target() waiting for source > CPU to run check_tsc_sync_source() but this never happens. Source CPU, > in its turn, is stuck on

Re: [PATCH] cpuidle: menu: allow state 0 to be disabled

On Thu, 29 Jun 2017 22:57:33 +0200 "Rafael J. Wysocki" wrote: > On Mon, Jun 26, 2017 at 7:38 AM, Nicholas Piggin wrote: > > The menu driver does not allow state0 to be disabled completely. > > If it is disabled but other enabled states don't meet latency >

Re: [PATCH] irqchip: gicv3-its: Use NUMA aware memory allocation for ITS tables

On 30/06/17 04:01, Ganapatrao Kulkarni wrote: > On Fri, Jun 30, 2017 at 8:04 AM, Ganapatrao Kulkarni > wrote: >> Hi Shanker, >> >> On Sun, Jun 25, 2017 at 9:16 PM, Shanker Donthineni >> wrote: >>> The NUMA node information is visible to ITS driver

Re: [PATCH V2 2/2] rt: Increase/decrease the nr of migratory tasks when enabling/disabling migration

On 06/30/2017 09:30 AM, Ingo Molnar wrote: > > * Daniel Bristot de Oliveira wrote: > >> There is a problem in the migrate_disable()/enable() implementation >> regarding the number of migratory tasks in the rt/dl RQs. The problem >> is the following: >> >> When a task is

Re: [PATCH V2 25/37] perf script: Add synthesized Intel PT power and ptwrite events

On 06/30/2017 05:08 AM, Arnaldo Carvalho de Melo wrote: > Em Thu, Jun 29, 2017 at 05:13:54PM -0300, Arnaldo Carvalho de Melo escreveu: >> Em Thu, Jun 29, 2017 at 10:56:25PM +0300, Adrian Hunter escreveu: >>> On 06/28/2017 11:26 PM, Arnaldo Carvalho de Melo wrote: Right, and I've not been able

Re: [BISECTED, REGRESSION] v4.12-rc: omapdrm fails to probe on Nokia N900

Hi, On Fri, Jun 30, 2017 at 09:41:35AM +0300, Tomi Valkeinen wrote: > On 29/06/17 21:50, Aaro Koskinen wrote: > > On Thu, Jun 15, 2017 at 09:51:06AM +0300, Tomi Valkeinen wrote: > >> On 15/06/17 01:11, Aaro Koskinen wrote: > >>> When booting v4.12-rc5 on Nokia N900, omapdrm fails to probe and

Re: [Patch v5 12/12] Documention: v4l: Documentation for HEVC CIDs

On Wed, 2017-06-28 at 22:04 +0200, Kamil Debski wrote: > Hi, > > Please find my comments inline. > > On 19 June 2017 at 07:10, Smitha T Murthy wrote: > > Added V4l2 controls for HEVC encoder > > > > Signed-off-by: Smitha T Murthy > > --- > >

[PATCH net-next v8 2/2] net: hns: Use phy_driver to setup Phy loopback

Use function set_loopback in phy_driver to setup phy loopback when doing ethtool self test. Signed-off-by: Lin Yun Sheng --- drivers/net/ethernet/hisilicon/hns/hnae.h| 1 + drivers/net/ethernet/hisilicon/hns/hns_ethtool.c | 105 --- 2 files

[PATCH net-next v8 1/2] net: phy: Add phy loopback support in net phy framework

This patch add set_loopback in phy_driver, which is used by MAC driver to enable or disable phy loopback. it also add a generic genphy_loopback function, which use BMCR loopback bit to enable or disable loopback. Signed-off-by: Lin Yun Sheng Reviewed-by: Andrew Lunn

Re: [PATCH NET V5 2/2] net: hns: Use phy_driver to setup Phy loopback

Hi, Andrew On 2017/6/29 21:56, Andrew Lunn wrote: >>> You only call dev_close() if the device is running. What if somebody >>> runs the self test on an interface when it has never been opened? It >>> looks like you will call phy_resume(). But since it has never been >>> suspended, you could be in

  1   2   3   4   5   6   7   8   9   10   >