Re: [PATCH v3 1/3] pinctrl/broxton: enable platform device in the absent of ACPI enumeration

On Tue, Jun 7, 2016 at 8:55 AM, Tan Jui Nee wrote: > This is to cater the need for non-ACPI system whereby > a platform device has to be created in order to bind > with the Apollo Lake Pinctrl GPIO platform driver. > > Signed-off-by: Tan Jui Nee

Re: [PATCH] sched: unlikely corrupted stack end

* WANG Chao wrote: > unlikely() was dropped in commit ce03e41 ("sched/core: Drop unlikely > behind BUG_ON()"), but commit 29d6455 ("sched: panic on corrupted stack > end") dropped BUG_ON() and called panic directly. > > Now we should bring unlikely() back for branch

Re: [PATCH v6 3/6] crypto: AF_ALG -- add asymmetric cipher interface

Hi Stephan, On 14 June 2016 at 07:12, Stephan Mueller wrote: > Am Dienstag, 14. Juni 2016, 00:16:11 schrieb Andrew Zaborowski: >> On 8 June 2016 at 21:14, Mat Martineau >> >> wrote: >> > On Wed, 8 Jun 2016, Stephan Mueller wrote: >> >>

[PATCH] [RESEND] drivers/base dmam_declare_coherent_memory leaks

dmam_declare_coherent_memory doesn't take into account the return value of dma_declare_coherent_memory, which leads to incorrect resource handling Signed-off-by: Vyacheslav V. Yurkov --- drivers/base/dma-mapping.c | 7 +-- 1 file changed, 5 insertions(+), 2 deletions(-)

[rfc patch] sched/fair: Use instantaneous load for fork/exec balancing

SUSE's regression testing noticed that... 0905f04eb21f sched/fair: Fix new task's load avg removed from source CPU in wake_up_new_task() ...introduced a hackbench regression, and indeed it does. I think this regression has more to do with randomness than anything else, but in general... While

Re: [patch 13/20] timer: Switch to a non cascading wheel

Nice cleanup! I think I see a buglet in your level-5 cascading. Suppose a timer is requested far in the future for a time that is an exact multiple of 32768 jiffies. collect_expired_timers() scans level 5 after all the previous ones, and will cascade it to level 0, in a level-0 bucket which

Re: [PATCH v10 01/14] usb: hcd: Initialize hcd->flags to 0

+Alan, On 10/06/16 16:07, Roger Quadros wrote: > When using the OTG/DRD library we can call hcd_add/remove > consecutively without calling usb_put_hcd/usb_create_hcd in between > so hcd->flags can be stale. > > If the HC dies due to whatever reason then without this > patch we get the below

Re: [PATCH] sched: unlikely corrupted stack end

On Tue, Jun 14, 2016 at 02:43:06PM +0800, WANG Chao wrote: > unlikely() was dropped in commit ce03e41 ("sched/core: Drop unlikely > behind BUG_ON()"), but commit 29d6455 ("sched: panic on corrupted stack > end") dropped BUG_ON() and called panic directly. Please use git config core.abbrev=12 and

[PATCH 1/2] Revert "mm: make faultaround produce old ptes"

This reverts commit 5c0a85fad949212b3e059692deecdeed74ae7ec7. The commit causes ~6% regression in unixbench. Let's revert it for now and consider other solution for reclaim problem later. Signed-off-by: Kirill A. Shutemov Reported-by: "Huang, Ying"

[PATCH 0/2] Reverts to address unixbench regression

Faultaround changes cause regression in unixbench, let's revert them. Kirill A. Shutemov (2): Revert "mm: make faultaround produce old ptes" Revert "mm: disable fault around on emulated access bit architecture" include/linux/mm.h | 2 +- mm/filemap.c | 2 +- mm/memory.c| 31

[PATCH] [ACPI] Change structure initialisation to C99 style

Replace the in order struct initialisation style with explicit field style. The Coccinelle semantic patch used to make this change is as follows: @decl@ identifier i1,fld; type T; field list[n] fs; @@ struct i1 { fs T fld; ...}; @@ identifier decl.i1,i2,decl.fld; expression e; position

[PATCH 2/2] Revert "mm: disable fault around on emulated access bit architecture"

This reverts commit d0834a6c2c5b0c76cfb806bd7dba6556d8b4edbb. After revert of 5c0a85fad949 ("mm: make faultaround produce old ptes") faultaround doesn't have dependencies on hardware accessed bit, so let's revert this one too. Signed-off-by: Kirill A. Shutemov

Re: [PATCH v2 4/5]nbd: make nbd device wait for its users.

On Thursday 02 June 2016 13:25:00 Pranay Kr. Srivastava wrote: > When a timeout occurs or a recv fails, then > instead of abruplty killing nbd block device > wait for it's users to finish. > > This is more required when filesystem(s) like > ext2 or ext3 don't expect their buffer heads to >

Re: [RFC][PATCH 1/8] rtmutex: Deboost before waking up the top waiter

Hi, I've got only nitpicks for the changelog. Otherwise the patch looks good to me (and yes, without it bw inheritance would be a problem). On 07/06/16 21:56, Peter Zijlstra wrote: > From: Xunlei Pang > > We should deboost before waking the high-prio task, such that > we

[PATCH 3/5] gpio: of: move chip->of_gpio_n_cells checking to of_gpiochip_add()

Do this sanity check only once when the gpio_chip is added rather than every time gpio-hog is handled. Signed-off-by: Masahiro Yamada --- drivers/gpio/gpiolib-of.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpio/gpiolib-of.c

[PATCH 0/5] gpio: refactor of_parse_own_gpio() and of_get_named_gpiod_flags()

I found one bug in of_parse_own_gpio(); of_gpiochip_find_and_xlate() fills gg_data->out_gpio with an error pointer if the .of_xlate() callback fails, but of_parse_own_gpio() only checks whether the out_gpio is NULL. This is a problem because the error pointer might be passed to the

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Mon, Jun 13, 2016 at 09:43:13PM +0200, Geert Uytterhoeven wrote: > Hi Joonsoo, Hello, > > On Tue, Apr 12, 2016 at 6:51 AM, wrote: > > From: Joonsoo Kim > > > > To check whther free objects exist or not precisely, we need to grab a > > lock. But,

[v2 PATCH 2/2] scsi:stex.c Add S6 support

From: Charles 1.Add reboot notifier and register it in stex_probe for all supported device. 2.For all supported device in restart flow, we get a callback from notifier and set S6flag for stex_shutdown & stex_hba_stop to send restart command to FW. Signed-off-by:

[PATCH v2 1/2] nxp/dts: add pcie aer interrupt-name property in the dts

NXP some platforms aer interrupt was not MSI/MSI-X/INTx but using interrupt line independently. This patch add a "aer" interrupt-names for aer interrupt. Signed-off-by: Po Liu --- Changes for V2: - None. .../devicetree/bindings/pci/layerscape-pci.txt | 4 ++--

[PATCH v2] locking/qspinlock: Use __this_cpu_dec instead

queued_spin_lock_slowpath should not worry about another queued_spin_lock_slowpath which runs in interrupt changes node->count by accident because node->count keeps the same value everytime we enter/leave queued_spin_lock_slowpath. On some archs this_cpu_dec will save/restore irq flags, this will

linux-next: Tree for Jun 14

Hi all, Changes since 20160609: Undropped tree: amlogic My fixes tree is empty again. The amlogic tree lost its build failure. The nfs tree gained a build failure so I sed the version from next-20160609. The crypto tree gained a conflict against the amlogic tree. The drm tree gained a

Re: [PATCH 2/2] pinctrl: max77620: select PINMUX

On Mon, Jun 13, 2016 at 5:18 PM, Arnd Bergmann wrote: > The recently added max77620 driver fails to build when CONFIG_PINMUX > is not set: > > pinctrl/pinctrl-max77620.c:272:21: error: variable 'max77620_pinmux_ops' has > initializer but incomplete type > static const struct

Re: [PATCH 1/9] of: Add a new macro to declare_of for one parameter function returning a value

On 06/01/2016 10:34 AM, Daniel Lezcano wrote: The macro OF_DECLARE_1 expect a void (*func)(struct device_node *) while the OF_DECLARE_2 expect a int (*func)(struct device_node *, struct device_node *). The second one allows to pass an init function returning a value, which make possible to call

Re: [PATCH 5/7] ARM: OMAP: dmtimer: Do not call PM runtime functions when not needed.

* Ivaylo Dimitrov [160613 12:01]: > Hi, > > On 13.06.2016 10:10, Tony Lindgren wrote: > > * Ivaylo Dimitrov [160610 14:23]: > > > > > > On 10.06.2016 13:22, Tony Lindgren wrote: > > > > > > > > OK. And I just applied the related dts

Re: [PATCH 2/3] i2c: octeon: Add retry logic after receiving STAT_RXADDR_NAK

On Thu, Jun 09, 2016 at 10:11:51PM +0200, Wolfram Sang wrote: > On Wed, Jun 08, 2016 at 08:51:18AM +0200, Jan Glauber wrote: > > The controller specification states that when receiving STAT_RXADDR_NAK > > the START should be sent again. Retry several times before finally > > failing with -ENXIO. >

Re: [PATCH v10 14/14] usb: host: xhci-plat: Add otg device to platform data

Mathias, On 10/06/16 16:07, Roger Quadros wrote: > Host controllers that are part of an OTG/dual-role instance > need to somehow pass the OTG controller device information > to the HCD core. > > We use platform data to pass the OTG controller device. > > Signed-off-by: Roger Quadros

[v3 PATCH 2/2] scsi:stex.c Add S6 support

From: Charles 1.Add reboot notifier and register it in stex_probe for all supported device. 2.For all supported device in restart flow, we get a callback from notifier and set S6flag for stex_shutdown & stex_hba_stop to send restart command to FW. Signed-off-by:

Re: [PATCH v2 1/1] Staging: comedi: dmm32at: fix BIT macro issue.

On 14/06/16 06:53, Ravishankar Karkala Mallikarjunayya wrote: This Replace all occurences of (1<

Re: [LKP] [lkp] [mm] 5c0a85fad9: unixbench.score -6.3% regression

On Wed, Jun 08, 2016 at 11:58:11AM +0300, Kirill A. Shutemov wrote: > On Wed, Jun 08, 2016 at 04:41:37PM +0800, Huang, Ying wrote: > > "Huang, Ying" writes: > > > > > "Kirill A. Shutemov" writes: > > > > > >> On Mon, Jun 06, 2016 at

Re: [PATCH] iommu/arm-smmu: request pcie devices to enable ACS

On Tue, Jun 14, 2016 at 11:11:36AM +0800, Wei Chen wrote: > On 13 June 2016 at 20:45, Will Deacon wrote: > > On Mon, Jun 13, 2016 at 05:20:17PM +0800, Wei Chen wrote: > >> The PCIe ACS capability will affect the layout of iommu groups. > >> Generally speaking, if the path

Re: [PATCH v3 4/6] drm/panel: simple: Add support for Samsung LSN122DL01-C01 2560x1600 panel

On Mon, Jun 13, 2016 at 10:00:45AM -0700, Doug Anderson wrote: > Yakir, > > On Sat, Jun 11, 2016 at 7:56 PM, Yakir Yang wrote: > > The Samsung LSN122DL01-C01 is an 12.2" 2560x1600 (WQXGA) TFT-LCD panel > > connected using eDP interfaces. > > > > Signed-off-by: Yakir Yang

Re: [PATCH 2/4] mtd: nand: implement two pairing scheme

Boris Brezillon wrote: > On 12 Jun 2016 16:24:53 George Spelvin wrote: >> Boris Brezillon wrote: >> My problem is that I don't really understand MLC programming. > I came to the same conclusion: we really have these 2 cases in the > wild, which makes it even more complicated to define a standard

Re: [PATCH v2] sched: unlikely corrupted stack end

Hi, [auto build test ERROR on tip/sched/core] [also build test ERROR on v4.7-rc3 next-20160614] [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/WANG-Chao/sched-unlikely-corrupted-stack-end

Re: [PATCH V9 09/11] ARM64/PCI: ACPI support for legacy IRQs parsing and consolidation with DT code

On Mon, Jun 13, 2016 at 01:01:35PM -0700, Duc Dang wrote: > On Mon, Jun 13, 2016 at 3:40 AM, Lorenzo Pieralisi > wrote: > > > > On Fri, Jun 10, 2016 at 06:36:12PM -0500, Bjorn Helgaas wrote: > > > On Fri, Jun 10, 2016 at 09:55:17PM +0200, Tomasz Nowicki wrote: > > > >

Re: [very-RFC 0/8] TSN driver for the kernel

On Mon, Jun 13, 2016 at 09:32:10PM +0200, Richard Cochran wrote: > On Mon, Jun 13, 2016 at 03:00:59PM +0200, Henrik Austad wrote: > > On Mon, Jun 13, 2016 at 01:47:13PM +0200, Richard Cochran wrote: > > > Which driver is that? > > > > drivers/net/ethernet/renesas/ > > That driver is merely a PTP

Re: [PATCH v2 1/2] clocksource: Add Oxford Semiconductor RPS Dual Timer

Hi Daniel, On 06/13/2016 04:35 PM, Daniel Lezcano wrote: > On Tue, Jun 07, 2016 at 06:04:11PM +0200, Neil Armstrong wrote: >> Add clocksource and clockevent driver from dual RPS timer. >> The HW provides a dual one-shot or periodic 24bit timers, >> the drivers set the first one as tick event

Re: [PATCH v8 2/3] CMDQ: Mediatek CMDQ driver

On 14/06/16 09:44, Horng-Shyang Liao wrote: Hi Matthias, On Wed, 2016-06-08 at 17:35 +0200, Matthias Brugger wrote: On 08/06/16 14:25, Horng-Shyang Liao wrote: Hi Matthias, On Wed, 2016-06-08 at 12:45 +0200, Matthias Brugger wrote: On 08/06/16 07:40, Horng-Shyang Liao wrote: Hi

Re: [PATCH v2] sched: unlikely corrupted stack end

> 在 2016年6月14日，下午4:56，Ingo Molnar 写道： > > > * WANG Chao wrote: > >> unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop >> unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on >> corrupted stack end") dropped BUG_ON() and

[PATCH 2/2] ASoC: nau8825: mark pm functions __maybe_unused

Subject: [PATCH] ASoC: nau8825: mark pm functions __maybe_unused The newly added nau8825_dai_is_active() function is only called from the PM logic that is build-time conditional in this driver, so we get a warning when CONFIG_PM is disabled: sound/soc/codecs/nau8825.c:229:13: error:

Re: [PATCH] phy: rockchip-dp: fix return value check in rockchip_dp_phy_probe()

Am Montag, 13. Juni 2016, 23:31:47 schrieb weiyj...@163.com: > From: Wei Yongjun > > In case of error, the function devm_kzalloc() returns NULL pointer > not ERR_PTR(). The IS_ERR() test in the return value check should > be replaced with NULL test. > >

Re: [RFC PATCH 2/3] mm, thp: convert from optimistic to conservative

On Sat 11-06-16 22:16:00, Ebru Akagunduz wrote: > Currently, khugepaged collapses pages saying only > a referenced page enough to create a THP. > > This patch changes the design from optimistic to conservative. > It gives a default threshold which is half of HPAGE_PMD_NR > for referenced pages,

RE: [PATCH v5 1/2] mm, kasan: improve double-free detection

> > Next time, when/if you send patch series, send patches in one thread, i.e. > > patches should be replies to the cover letter. > > Your patches are not linked together, which makes them harder to track. Thanks for the tip; but doesn't this conflict with the advice in

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Tue, Jun 14, 2016 at 09:31:23AM +0200, Geert Uytterhoeven wrote: > Hi Joonsoo, > > On Tue, Jun 14, 2016 at 8:24 AM, Joonsoo Kim wrote: > > On Mon, Jun 13, 2016 at 09:43:13PM +0200, Geert Uytterhoeven wrote: > >> On Tue, Apr 12, 2016 at 6:51 AM,

Re: linux-next: manual merge of the kvms390 tree with the s390 tree

On 06/14/2016 06:51 AM, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the kvms390 tree got a conflict in: > > arch/s390/hypfs/hypfs_diag.c > > between commit: > > 6c22c9863760 ("s390: avoid extable collisions") > > from the s390 tree and commit: > > e65f30e0cb29

[PATCH] more mapcount page as kpage could reduce total replacement times than fewer mapcount one in probability.

From: z00281421 more mapcount page as kpage could reduce total replacement times than fewer mapcount one when ksmd scan and replace among forked pages later. Signed-off-by: z00281421 --- mm/ksm.c | 15 +++ 1 file

Re: [PATCH v4 00/14] fix some type infos and bugs for arm64/of numa

On 2016/6/13 18:12, Will Deacon wrote: > On Sun, Jun 12, 2016 at 03:09:46PM +0800, Hanjun Guo wrote: >> On 2016/6/7 21:58, Will Deacon wrote: >>> On Tue, Jun 07, 2016 at 04:08:04PM +0800, Zhen Lei wrote: v3 -> v4: 1. Packed three patches of Kefeng Wang, patch6-8. 2. Add 6 new

Re: [patch 13/20] timer: Switch to a non cascading wheel

* Thomas Gleixner wrote: > On Mon, 13 Jun 2016, Peter Zijlstra wrote: > > On Mon, Jun 13, 2016 at 08:41:00AM -, Thomas Gleixner wrote: > > > + > > > + /* Cascading, sigh... */ > > > > So given that userspace has no influence on timer period; can't we > > simply fail to

Re: [PATCH 2/2] printk: Add kernel parameter to control writes to /dev/kmsg

* Borislav Petkov wrote: > From: Borislav Petkov > > Add a "printk.kmsg" kernel command line parameter which controls how > userspace writes into /dev/kmsg. It has two options: > > * on - unlimited logging from userspace > * off - logging from userspace gets

Re: [PATCH 1/2] pinctrl: fix incorrect inline keyword in multiple drivers

On Mon, Jun 13, 2016 at 5:18 PM, Arnd Bergmann wrote: > When building with 'make W=1', we get harmless warnings about > five drivers in drivers/pinctrl, which all contain a copy of > the same line: > > drivers/pinctrl/freescale/pinctrl-imx1-core.c:160:1: error: 'inline' is not >

Re: [RFC PATCH 1/3] mm, thp: revert allocstall comparing

On Sat 11-06-16 22:15:59, Ebru Akagunduz wrote: > This patch takes back allocstall comparing when deciding > whether swapin worthwhile because it does not work, > if vmevent disabled. > > Related commit: >

Re: [v2 PATCH 1/2] scsi:stex.c Support Pegasus 3 product

Hi, [auto build test WARNING on scsi/for-next] [also build test WARNING on v4.7-rc3 next-20160614] [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/Charles-Chiou/scsi-stex-c-Support-Pegasus-3

[PATCH 4/7] ubi: Rework Fastmap attach base code

Introduce a new list to the UBI attach information object to be able to deal better with old and corrupted Fastmap eraseblocks. Also move more Fastmap specific code into fastmap.c. Signed-off-by: Richard Weinberger --- drivers/mtd/ubi/attach.c | 99

[PATCH 6/7] ubi: Be more paranoid while seaching for the most recent Fastmap

Since PEB erasure is asynchornous it can happen that there is more than one Fastmap on the MTD. This is fine because the attach logic will pick the Fastmap data structure with the highest sequence number. On a not so well configured MTD stack spurious ECC errors are common. Causes can be

[PATCH 5/7] ubi: Check whether the Fastmap anchor matches the super block

This helps to detect cases where an user copies an UBI image to another target with different bad blocks. Signed-off-by: Richard Weinberger --- drivers/mtd/ubi/fastmap.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/mtd/ubi/fastmap.c

[PATCH 1/7] ubi: Fix scan_fast() comment

Signed-off-by: Richard Weinberger --- drivers/mtd/ubi/attach.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/mtd/ubi/attach.c b/drivers/mtd/ubi/attach.c index c1aaf03..cc04ca8 100644 --- a/drivers/mtd/ubi/attach.c +++ b/drivers/mtd/ubi/attach.c @@

[PATCH 7/7] ubi: Use bitmaps in Fastmap self-check code

...don't waste memory by allocating one sizeof(int) per PEB. Signed-off-by: Richard Weinberger --- drivers/mtd/ubi/fastmap.c | 20 +++- 1 file changed, 11 insertions(+), 9 deletions(-) diff --git a/drivers/mtd/ubi/fastmap.c b/drivers/mtd/ubi/fastmap.c index

Re: [PATCH RFC] slub: reap free slabs periodically

On Fri, Jun 10, 2016 at 04:32:26PM -0500, Christoph Lameter wrote: > One reason for SLUBs creation was the 2 second scans in SLAB which causes > significant disruption of latency sensitive tasksk. That's not good, indeed. > > You can simply implement a reaper in userspace by running > >

Re: [very-RFC 0/8] TSN driver for the kernel

On Mon, Jun 13, 2016 at 08:56:44AM -0700, John Fastabend wrote: > On 16-06-13 04:47 AM, Richard Cochran wrote: > > [...] > > Here is what is missing to support audio TSN: > > > > * User Space > > > > 1. A proper userland stack for AVDECC, MAAP, FQTSS, and so on. The > >OpenAVB project does

[PATCH] mmc: Change the enhanced area related sysfs output format

From: Chuanxiao Dong When the enhanced area feature was not enabled, the related sysfs will have -EINVAL(-22) value, so change the sysfs output format to display the correct value. Signed-off-by: Chuanxiao Dong --- drivers/mmc/core/mmc.c |

[PATCH v3 2/2] pci/aer: interrupt fixup in the quirk

On some platforms, root port doesn't support MSI/MSI-X/INTx in RC mode. When chip support the aer interrupt with none MSI/MSI-X/INTx mode, maybe there is interrupt line for aer pme etc. Search the interrupt number in the fdt file. Then fixup the dev->irq with it. Signed-off-by: Po Liu

[PATCH v3 1/2] nxp/dts: add pcie aer interrupt-name property in the dts

NXP some platforms aer interrupt was not MSI/MSI-X/INTx but using interrupt line independently. This patch add a "aer" interrupt-names for aer interrupt. Signed-off-by: Po Liu --- changes for v3: - None; .../devicetree/bindings/pci/layerscape-pci.txt | 4 ++--

[PATCH v3 06/14] pwm: rockchip: Add support for atomic update

Implement the ->apply() function to add support for atomic update. Signed-off-by: Boris Brezillon Tested-by: Heiko Stuebner Reviewed-by: Brian Norris Tested-by: Brian Norris ---

[PATCH v3 00/14] regulator: pwm: various improvements

Hello, This patch series series aims at adding two important features to the pwm-regulator driver. The first one is the support for 'smooth handover' between the bootloader and the kernel. This is mainly solving problems we have when the PWM is controlling a critical regulator (like the one

[PATCH v3 02/14] pwm: Add two helpers to ease relative duty cycle manipulation

The PWM framework expects PWM users to configure the duty cycle in nanoseconds, but most users just want to express this duty cycle relatively to the period value (i.e. duty_cycle = 33% of the period). Add the pwm_{get,set}_relative_duty_cycle() helpers to ease this kind of conversion.

[PATCH v3 03/14] pwm: rockchip: Fix period and duty_cycle approximation

The current implementation always round down the duty and period values, while it would be better to round them to the closest integer. These changes are needed in preparation of atomic update support to prevent a period/duty cycle drift when executing several time the 'pwm_get_state() / modify /

[PATCH v3 01/14] pwm: Add an helper to prepare a new PWM state

The pwm_init_state() helper prepares a new state object containing the current PWM state except for the polarity and period fields which are set to the reference values (those in pwm_args). This is particularly useful for PWM users who want to apply a new duty-cycle expressed relatively to the

[PATCH v3 04/14] pwm: rockchip: Add support for hardware readout

Implement the ->get_state() function to expose initial state. Signed-off-by: Boris Brezillon Reviewed-by: Brian Norris Tested-by: Brian Norris Tested-by: Heiko Stuebner ---

Re: [PATCH v2 4/5]nbd: make nbd device wait for its users.

Hi Markus, On Tue, Jun 14, 2016 at 2:29 PM, Markus Pargmann wrote: > > On Thursday 02 June 2016 13:25:00 Pranay Kr. Srivastava wrote: > > When a timeout occurs or a recv fails, then > > instead of abruplty killing nbd block device > > wait for it's users to finish. > > > >

[PATCH] mdio: mux: avoid 'maybe-uninitialized' warning

The latest changes to the MDIO code introduced a false-positive warning with gcc-6 (possibly others): drivers/net/phy/mdio-mux.c: In function 'mdio_mux_init': drivers/net/phy/mdio-mux.c:188:3: error: 'parent_bus_node' may be used uninitialized in this function [-Werror=maybe-uninitialized] It's

[PATCH 2/2] printk: Add kernel parameter to control writes to /dev/kmsg

From: Borislav Petkov Add a "printk.kmsg" kernel command line parameter which controls how userspace writes into /dev/kmsg. It has two options: * on - unlimited logging from userspace * off - logging from userspace gets ignored The default setting is to ratelimit the messages

[PATCH 1/2] ratelimit: Extend to print suppressed messages on release

From: Borislav Petkov Extend the ratelimiting facility to print the amount of suppressed lines when it is being released. Separated from a previous patch by Linus. Signed-off-by: Borislav Petkov Cc: Linus Torvalds ---

[PATCH 0/2] printk.kmsg: Ratelimit it by default

From: Borislav Petkov Ok, so how about these two? Rostedt is busy so I took Linus' old patch and Steven's last v2 and split and extended them with the comments people had on the last thread: https://lkml.kernel.org/r/20160425145606.59832...@gandalf.local.home I hope, at least.

Re: [PATCH 1/2] liblockdep: Fix compile errors

On Mon, Jun 13, 2016 at 04:38:01PM -0400, Sasha Levin wrote: > On 06/11/2016 04:36 AM, Vishal Thanki wrote: > > On Sat, Jun 11, 2016 at 5:53 AM, Sasha Levin wrote: > >> On 06/09/2016 09:34 AM, Vishal Thanki wrote: > >>> dfaaf3fa0: (Use __jhash_mix() for

Re: [PATCH] ibmvscsis: Initial commit of IBM VSCSI Tgt Driver

On Fri, 2016-06-10 at 12:03 -0700, Bart Van Assche wrote: > On 05/24/2016 01:00 PM, Bryant G Ly wrote: > > Quoting Bart Van Assche : > >> On 05/24/2016 06:52 AM, Bryant G. Ly wrote: > >>> +static uint64_t ibmvscsis_unpack_lun(const uint8_t *lun, int len) > >>> +{ > >>>

Re: [PATCH] clk: rockchip: add pclk_vio_grf to critical clock on the RK3399

Am Montag, 13. Juni 2016, 20:49:39 schrieb Doug Anderson: > Hi, > > On Mon, Jun 13, 2016 at 8:02 PM, Xing Zheng wrote: > > Hi Doug, > > > > On 2016年06月14日 07:46, Doug Anderson wrote: > >> Even if it's not much power, it seems like we should still turn it off > >> and

[PATCH] parisc: Change structure intialisation to C99 style

Replace the in order struct initialisation style with explicit field style. The Coccinelle semantic patch used to make this change is as follows: @decl@ identifier i1,fld; type T; field list[n] fs; @@ struct i1 { fs T fld; ...}; @@ identifier decl.i1,i2,decl.fld; expression e; position

[PATCH] sched: unlikely corrupted stack end

unlikely() was dropped in commit ce03e41 ("sched/core: Drop unlikely behind BUG_ON()"), but commit 29d6455 ("sched: panic on corrupted stack end") dropped BUG_ON() and called panic directly. Now we should bring unlikely() back for branch prediction. Signed-off-by: WANG Chao

Re: [PATCH 01/12] gpio: Only descend into gpio directory when CONFIG_GPIOLIB is set

On Mon, Jun 13, 2016 at 10:02 PM, Andrew F. Davis wrote: > When CONFIG_GPIOLIB is not set make will still descend into the gpio > directory but nothing will be built. This produces unneeded build > artifacts and messages in addition to slowing the build. Fix this here. > >

Re: [PATCH 2/2 v16] drm/bridge: Add I2C based driver for ps8640 bridge

Hi Jitao, On Thu, Jun 2, 2016 at 5:57 PM, Jitao Shi wrote: > > This patch adds drm_bridge driver for parade DSI to eDP bridge chip. > > Signed-off-by: Jitao Shi > Reviewed-by: Daniel Kurtz > --- > Changes since v15: > -

Re: [PATCH 1/3] net: Add MDIO bus driver for the Hisilicon FEMAC

On 2016/6/13 21:32, Andrew Lunn wrote: > On Mon, Jun 13, 2016 at 02:07:54PM +0800, Dongpo Li wrote: >> This patch adds a separate driver for the MDIO interface of the >> Hisilicon Fast Ethernet MAC. >> >> Reviewed-by: Jiancheng Xue >> Signed-off-by: Dongpo Li

[PATCH v2] sched: unlikely corrupted stack end

unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched: panic on corrupted stack end") dropped BUG_ON() and called panic directly. Now we should bring unlikely() back for branch prediction. While we're at it, it's better and

Re: [LKP] [lkp] [mm] 5c0a85fad9: unixbench.score -6.3% regression

On Mon, Jun 13, 2016 at 11:11:05PM -0700, Linus Torvalds wrote: > On Mon, Jun 13, 2016 at 5:52 AM, Kirill A. Shutemov > wrote: > > On Sat, Jun 11, 2016 at 06:02:57PM -0700, Linus Torvalds wrote: > >> > >> I've timed it at over a thousand cycles on at least some

[v3 PATCH 1/2] scsi:stex.c Support Pegasus 3 product

From: Charles Pegasus series is a RAID support product by using Thunderbolt technology. The newest product, Pegasus 3 is support Thunderbolt 3 technology with another chip. 1.Change driver version. 2.Add Pegasus 3 VID, DID and define it's device address.

Re: [PATCH v2 1/5] nbd: fix might_sleep warning on socket shutdown.

Hi, On Thursday 02 June 2016 13:24:57 Pranay Kr. Srivastava wrote: > spinlocked ranges should be small and not contain calls into huge > subfunctions. Fix my mistake and just get the pointer to the socket > instead of doing everything with spinlock held. > > Reported-by: Mikulas Patocka

[PATCH v3 10/14] regulator: pwm: Switch to the atomic PWM API

Use the atomic API wherever appropriate and get rid of pwm_apply_args() call (the reference period and polarity are now explicitly set when calling pwm_apply_state()). We also make use of the pwm_set_relative_duty_cycle() helper to ease relative to absolute duty_cycle conversion. Note that

[PATCH v3 11/14] regulator: pwm: Properly initialize the ->state field

The ->state field is currently initialized to 0, thus referencing the voltage selector at index 0, which might not reflect the current voltage value. If possible, retrieve the current voltage selector from the PWM state, else return -EINVAL. Signed-off-by: Boris Brezillon

Re: [RESEND PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version

On Tue, Jun 14, 2016 at 10:13:31AM +0100, Will Deacon wrote: > On Mon, Jun 13, 2016 at 03:41:54PM -0600, Al Stone wrote: > > This is a resend only: Ping? Last ping was 26 May; there has been zero > > response since then. Already have one ACK from Lorenzo; another from an > > arm64 maintainer

Re: [PATCH 2/4] mtd: nand: implement two pairing scheme

On 14 Jun 2016 05:07:26 -0400 "George Spelvin" wrote: > Boris Brezillon wrote: > > On 12 Jun 2016 16:24:53 George Spelvin wrote: > >> Boris Brezillon wrote: > >> My problem is that I don't really understand MLC programming. > > > I came to the same conclusion: we

Re: [PATCH v2 1/5] nbd: fix might_sleep warning on socket shutdown.

Hi On Tue, Jun 14, 2016 at 2:22 PM, Markus Pargmann wrote: > Hi, > > On Thursday 02 June 2016 13:24:57 Pranay Kr. Srivastava wrote: >> spinlocked ranges should be small and not contain calls into huge >> subfunctions. Fix my mistake and just get the pointer to the socket >>

[PATCH] mfd: qcom_rpm: fix offset error for msm8660

The RPM in MSM8660/APQ8060 has different offsets to the selector ACK and request context ACK registers. Make all these register offsets part of the per-SoC data and assign the right values. The bug was found by verifying backwards to the vendor tree in the out-of-tree files : all were using

Re: [PATCH v2] sched: unlikely corrupted stack end

* WANG Chao wrote: > > > 在 2016年6月14日，下午4:56，Ingo Molnar 写道： > > > > > > * WANG Chao wrote: > > > >> unlikely() was dropped in commit ce03e4137bb2 ("sched/core: Drop > >> unlikely behind BUG_ON()"), but commit 29d6455178a0 ("sched:

Re: [PATCH v2 0/3] hw_random: Add Amlogic Meson SoCs Random Generator driver

On Mon, Jun 13, 2016 at 03:10:28PM -0700, Kevin Hilman wrote: > Could you take just the driver please? > > Due to lots of other activity in the DT, I'd prefer to send the DT & > bindings though the arm-soc (via the amlogic tree.) OK I will back out these two patches. Cheers, -- Email: Herbert

[v2 PATCH 1/2] scsi:stex.c Support Pegasus 3 product

From: Charles Pegasus series is a RAID support product by using Thunderbolt technology. The newest product, Pegasus 3 is support Thunderbolt 3 technology with another chip. 1.Change driver version. 2.Add Pegasus 3 VID, DID and define it's device address.

Re: [PATCH v8 2/3] CMDQ: Mediatek CMDQ driver

Hi Matthias, On Wed, 2016-06-08 at 17:35 +0200, Matthias Brugger wrote: > > On 08/06/16 14:25, Horng-Shyang Liao wrote: > > Hi Matthias, > > > > On Wed, 2016-06-08 at 12:45 +0200, Matthias Brugger wrote: > >> > >> On 08/06/16 07:40, Horng-Shyang Liao wrote: > >>> Hi Matthias, > >>> > >>> On Tue,

Kconfig error: Missing dependency for MEMSTICK_UNSAFE_RESUME

Dear Kernel developers, we detected a missing dependency inside the Kconfig model, which allows to configure Memstick support for power management (MEMSTICK_UNSAFE_RESUME) even if Power Management (PM) was disabled. We suggest to add a "depends on" constraint to the Kconfig model for

Re: [PATCH v2 00/38] Documentation/sphinx

Hi Jon, On Fri, Jun 10, 2016 at 10:41 PM, Dave Airlie wrote: > On 11 June 2016 at 04:17, Daniel Vetter wrote: >> On Thu, Jun 9, 2016 at 9:55 PM, Jonathan Corbet wrote: >>> On Sat, 4 Jun 2016 14:37:01 +0300 >>> Jani Nikula

Re: [patch 13/20] timer: Switch to a non cascading wheel

On Tue, 14 Jun 2016, George Spelvin wrote: > I think I see a buglet in your level-5 cascading. > > Suppose a timer is requested far in the future for a time > that is an exact multiple of 32768 jiffies. > > collect_expired_timers() scans level 5 after all the previous ones, > and will cascade it

[PATCH v3 14/14] regulator: pwm: Document pwm-dutycycle-unit and pwm-dutycycle-range

Document the pwm-dutycycle-unit and pwm-dutycycle-range properties. Signed-off-by: Boris Brezillon Acked-by: Brian Norris --- .../devicetree/bindings/regulator/pwm-regulator.txt | 19 +++ 1 file changed, 19

[PATCH v3 12/14] regulator: pwm: Retrieve correct voltage

The continuous PWM voltage regulator is caching the voltage value in the ->volt_uV field. While most of the time this value should reflect the real voltage, sometime it can be sightly different if the PWM device rounded the set_duty_cycle request. Moreover, this value is not valid until someone

Re: [RESEND PATCH v5 0/1] ARM64: ACPI: Update documentation for latest specification version

On Mon, Jun 13, 2016 at 03:41:54PM -0600, Al Stone wrote: > This is a resend only: Ping? Last ping was 26 May; there has been zero > response since then. Already have one ACK from Lorenzo; another from an > arm64 maintainer would be really helpful. I thought there were outstanding comments on

  1   2   3   4   5   6   7   8   9   10   >