[PATCH] net: dccp: Add handling of IPV6_PKTOPTIONS to dccp_v6_do_rcv()

Add handling of IPV6_PKTOPTIONS to dccp_v6_do_rcv() in net/dccp/ipv6.c, similar to the handling in net/ipv6/tcp_ipv6.c Signed-off-by: Andrii Vladyka diff --git a/net/dccp/ipv6.c b/net/dccp/ipv6.c index 1b58eac..fdff10b 100644 --- a/net/dccp/ipv6.c +++ b/net/dccp/ipv6.c @@ -16,6

[lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to drivers/staging/irda/net/") url: https://github.com/0day-ci/linux/commits/Greg-Kroah-Hartman/irda-move-it-to-drivers-staging-so-we-can-delete-it/20170829-090816 in testcase: trinity

Re: [PATCH v2 3/3] livepatch: force transition process to finish

On Thu 2017-08-10 12:48:15, Miroslav Benes wrote: > If a task sleeps in a set of patched functions uninterruptibly, it could > block the whole transition process indefinitely. Thus it may be useful > to clear its TIF_PATCH_PENDING to allow the process to finish. > > Admin can do that now by

[PATCH 6/6] [media] cx24116: Delete jump targets in cx24116_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:44:29 +0200 * Return directly after a call of the function "kzalloc" failed at the beginning. * Move a bit of exception handling code into an if branch. * Delete two jump targets which became unnecessary with this

Re: [PATCH net-next v2 00/10] net: dsa: add generic debugfs interface

Tue, Aug 29, 2017 at 05:57:54PM CEST, vivien.dide...@savoirfairelinux.com wrote: >Hi David, Jiri, > >Jiri Pirko writes: > >> Tue, Aug 29, 2017 at 06:38:37AM CEST, da...@davemloft.net wrote: >>>From: Vivien Didelot >>>Date: Mon, 28 Aug 2017

Re: [PATCH] MAINTAINERS: Update Cavium ThunderX2 entry

On Tue, Aug 08, 2017 at 11:29:13AM +0200, Robert Richter wrote: > On 08.08.17 01:07:04, Jayachandran C wrote: > > Add Robert Richter as the primary maintainer for this platform. > > > > Signed-off-by: Jayachandran C > > --- > > MAINTAINERS | 1 + > > 1 file changed, 1

Re: [GIT PULL] ARM: at91: DT for 4.14

On Tue, Aug 29, 2017 at 10:52:34PM +0200, Alexandre Belloni wrote: > Arnd, Olof, > > I understand this is very late in the cycle but I completely forgot to > send that pull request alongside the 4.13 fixes. > Most of the patches have been included in linux-next for a while so I > don't this it is

Re: [GIT PULL] ARM: dts: uniphier: UniPhier DT updates for v4.14

On Tue, Aug 29, 2017 at 12:23:32AM +0900, Masahiro Yamada wrote: > Hi Arnd, Olof, > > Sorry for my last-minute pull request. > Please pull a little more for the upcoming merge window. > Here are some trivial UniPhier DT (32bit) updates. Please pull! > > > > The following changes since commit

Re: [GIT PULL] arm64: dts: uniphier: UniPhier DT updates (64bit) for v4.14 (2nd)

On Tue, Aug 29, 2017 at 12:28:21AM +0900, Masahiro Yamada wrote: > Hi Arnd, Olof, > > > Sorry for my last-minute pull request. > Please pull a little more for the upcoming merge window. > Here are some trivial + new SoC support for UniPhier DT (64bit). > Please pull! > > > The following

Re: [PATCH v2 14/20] mm: Provide speculative fault infrastructure

On Wed, Aug 30, 2017 at 07:19:30AM +1000, Benjamin Herrenschmidt wrote: > On Tue, 2017-08-29 at 13:27 +0200, Peter Zijlstra wrote: > > mpe helped me out and explained that is the PWC hint to TBLIE. > > > > So, you set need_flush_all when you unhook pud/pmd/pte which you then > > use to set PWC.

Re: [PATCH 05/13] IB/umem: update to new mmu_notifier semantic

On Tue, Aug 29, 2017 at 07:54:39PM -0400, Jérôme Glisse wrote: > Call to mmu_notifier_invalidate_page() are replaced by call to > mmu_notifier_invalidate_range() and thus call are bracketed by > call to mmu_notifier_invalidate_range_start()/end() > > Remove now useless invalidate_page callback. >

Re: I/O hangs after resuming from suspend-to-ram

Hello. Addressing your questions below. Can't reproduce even with putting dmcypt on raid10 after applying my patch. Just a side note, that dm-crypt is not necessary here — I am able to trigger hang with RAID10 and LVM only. BTW, could you share us which blk-mq scheduler you are using on

Re: [RFC] block: deprecate choosing elevator via boot param

Jens, any thoughts about this? On Mon, Aug 14, 2017 at 11:27 AM, Oleksandr Natalenko wrote: > Setting I/O scheduler via kernel command line is not flexible enough > anymore. Different schedulers might be desirable for different types > of devices (SSDs and HDDs, for

Re: [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

On 08/30, Greg Kroah-Hartman wrote: >On Wed, Aug 30, 2017 at 02:04:11PM +0800, kernel test robot wrote: >> FYI, we noticed the following commit: >> >> commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to >> drivers/staging/irda/net/") >> url: >>

Re: [PATCH net-next v3 02/13] phy: add the mvebu cp110 comphy driver

Hi Kishon, On Wed, Aug 30, 2017 at 11:01:56AM +0530, Kishon Vijay Abraham I wrote: > > I think we should just select the mode that a particular lane has been > configured here instead of populating all the modes. But I think that doesn't > make sense since the mode is set by the consumer and the

[PATCH 3/6] [media] cx24116: Delete an unnecessary variable initialisation in cx24116_writeregN()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:10:38 +0200 The variable "ret" will eventually be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 4/6] [media] cx24116: Improve a size determination in cx24116_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:15:33 +0200 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [PATCH v2] mm/hugetlb.c: make huge_pte_offset() consistent and document behaviour

On Fri 18-08-17 15:54:15, Punit Agrawal wrote: > When walking the page tables to resolve an address that points to > !p*d_present() entry, huge_pte_offset() returns inconsistent values > depending on the level of page table (PUD or PMD). > > It returns NULL in the case of a PUD entry while in the

[PATCH] Input: synaptics - Lenovo Thinkpad X1 Carbon G5 (2017) with Elantech trackpoints should use RMI.

From: Edvard Holst Lenovo use two different trackpoints in the fifth generation Thinkpad X1 Carbon. Both are accessible over SMBUS/RMI but the pnpIDs are missing. This patch is for the Elantech trackpoint specifically which also reports SMB version 3 so rmi_smbus needs

(Kernel Bug report) Make kaby lake cpu crash Ethernet

Hello Sir, i am using cpu i7 7700k kaby lake, i have no overclock the CPU but i think i7 7700k come across with Ethernet crash issue. Don't know why it will keeping crash. I tested the kernel since 4.8 - 4.12 almost 2-3months and i can see that the issue is still exist. Kernel error then the

Re: [RFC v1] sched/fair: search a task from the tail of the queue

On Mon, Aug 28, 2017 at 10:41 AM, Peter Zijlstra wrote: > On Fri, Aug 25, 2017 at 12:11:31AM +0200, Uladzislau Rezki (Sony) wrote: >> From: Uladzislau Rezki >> >> As a first step this patch makes cfs_tasks list as MRU one. >> It means, that when a next

Re: [PATCH 04/13] drm/amdgpu: update to new mmu_notifier semantic

Am 30.08.2017 um 01:54 schrieb Jérôme Glisse: Call to mmu_notifier_invalidate_page() are replaced by call to mmu_notifier_invalidate_range() and thus call are bracketed by call to mmu_notifier_invalidate_range_start()/end() Remove now useless invalidate_page callback. Signed-off-by: Jérôme

Re: [PATCH net-next v3 02/13] phy: add the mvebu cp110 comphy driver

Hi Kishon, On Wed, Aug 30, 2017 at 10:49:13AM +0530, Kishon Vijay Abraham I wrote: > On Monday 28 August 2017 08:27 PM, Antoine Tenart wrote: > > + > > +static int mvebu_comphy_set_mode_sgmii(struct phy *phy, enum phy_mode mode) > > the mode need not be passed as argument here since this

[PATCH 2/6] [media] cx24116: Return directly after a failed kmalloc() in cx24116_writeregN()

From: Markus Elfring Date: Wed, 30 Aug 2017 07:55:49 +0200 * Return directly after a call of the function "kmalloc" failed at the beginning. * Delete the jump target "error" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring

Re: [PATCH v2] USB: serial: option: add support for D-Link DWM-157 C1

On Tue, Aug 29, 2017 at 09:50:03PM +0200, Maciej S. Szmigiero wrote: > This commit adds support (an ID, really) for D-Link DWM-157 hardware > version C1 USB modem to option driver. > > According to manufacturer-provided Windows INF file the device has four > serial ports: > "D-Link HSPA+DataCard

Re: [PATCH] USB: serial: option: simplify 3 D-Link device entries

On Tue, Aug 29, 2017 at 04:41:21PM +0200, Johan Hovold wrote: > On Tue, Aug 29, 2017 at 10:45:13AM +0200, Bjørn Mork wrote: > > All the vendor specific interfaces on these devices are serial > > functions handled by this driver, so we can use a single class > > match entry for each. > > > > P:

Re: [PATCH v3 2/5] dmaengine: Add STM32 DMAMUX driver

On 08/28/2017 01:48 PM, Peter Ujfalusi wrote: > > Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. > Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki > Thanks for your invaluable inputs. This is more clear now and revise my driver > > I would not bother with

Re: (Kernel Bug report) Make kaby lake cpu crash Ethernet

On Wed, Aug 30, 2017 at 04:16:54PM +0800, Chiwu Yung wrote: > Hello Sir, i am using cpu i7 7700k kaby lake, i have no overclock the > CPU but i think i7 7700k come across with Ethernet crash issue. Don't > know why it will keeping crash. > I tested the kernel since 4.8 - 4.12 almost 2-3months

[PATCH v4] provide rule for finding refcounters

changes in v4: Removed unnessesary "()" around expression in rule 4. changes in v3: Removed unnessesary rule 4 conditions pointed by Julia. changes in v2: Following the suggestion from Julia the first rule is split into 2. The output does not differ that much between these two versions, but rule

[PATCH] Coccinelle: add atomic_as_refcounter script

atomic_as_refcounter.cocci script allows detecting cases when refcount_t type and API should be used instead of atomic_t. Signed-off-by: Elena Reshetova --- scripts/coccinelle/api/atomic_as_refcounter.cocci | 131 ++ 1 file changed, 131

Re: [RFC] workqueue: remove manual lockdep uses to detect deadlocks

On Wed, Aug 30, 2017 at 10:53:39AM +0900, Byungchul Park wrote: > On Tue, Aug 29, 2017 at 08:57:27PM +0200, Peter Zijlstra wrote: > > On Sat, Aug 26, 2017 at 12:49:26AM +0900, Byungchul Park wrote: > > > > However, how would it distinguish things like flushing another work > > > > > > I think it

Re: [PATCH v2 15/30] xfs: Define usercopy region in xfs_inode slab cache

On Wed, Aug 30, 2017 at 07:51:57AM +1000, Dave Chinner wrote: > Right, I've looked at btrees, too, but it's more complex than just > using an rbtree. I originally looked at using Peter Z's old > RCU-aware btree code, but it doesn't hold data in the tree leaves. > So that needed significant

[PATCH 5/6] [media] cx24116: Delete an unnecessary variable initialisation in cx24116_attach()

From: Markus Elfring Date: Wed, 30 Aug 2017 08:30:12 +0200 The variable "state" will be set to an appropriate pointer a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 1/2] arm64: stacktrace: avoid listing stacktrace functions in stacktrace

The stacktraces always begin as follows: [] save_stack_trace_tsk+0x0/0x98 [] save_stack_trace+0x24/0x28 ... This is because the stack trace code includes the stack frames for itself. This is incorrect behaviour, and also leads to "skip" doing the wrong thing (which is the number of stack

[PATCH 2/2] mm, page_owner: Skip unnecessary stack_trace entries

The page_owner stacktrace always begin as follows: [] save_stack+0x40/0xc8 [] __set_page_owner+0x3c/0x6c These two entries do not provide any useful information and limits the available stacktrace depth. The page_owner stacktrace was skipping caller function from stack entries but this was

Re: [RFC PATCH v2 1/7] x86/paravirt: Add pv_idle_ops to paravirt ops

On 29/08/17 15:55, Konrad Rzeszutek Wilk wrote: > On Tue, Aug 29, 2017 at 11:46:35AM +, Yang Zhang wrote: >> So far, pv_idle_ops.poll is the only ops for pv_idle. .poll is called in >> idle path which will polling for a while before we enter the real idle >> state. >> >> In virtualization,

Re: d82fed7529 ("locking/lockdep/selftests: Fix mixed read-write .."): BUG: -1 unexpected failures (out of 262) - debugging disabled! |

On Wed, Aug 30, 2017 at 08:29:47AM +0200, Peter Zijlstra wrote: > On Wed, Aug 30, 2017 at 11:37:21AM +0800, kernel test robot wrote: > > > [0.004000] > > - > > [0.004000] BUG: -1 unexpected failures (out of 262) - debugging

Re: [PATCH net-next v2 00/10] net: dsa: add generic debugfs interface

Tue, Aug 29, 2017 at 02:50:04PM CEST, and...@lunn.ch wrote: >On Tue, Aug 29, 2017 at 08:25:23AM +0200, Jiri Pirko wrote: >> Mon, Aug 28, 2017 at 10:08:34PM CEST, and...@lunn.ch wrote: >> >> I see this overlaps a lot with DPIPE. Why won't you use that to expose >> >> your hw state? >> > >> >We took

Re: possible circular locking dependency detected [was: linux-next: Tree for Aug 22]

Hi, On (08/30/17 14:43), Byungchul Park wrote: [..] > > notably slower than earlier 4.13 linux-next. (e.g. scrolling in vim > > is irritatingly slow) > > To Ingo, > > I cannot decide if we have to roll back CONFIG_LOCKDEP_CROSSRELEASE > dependency on CONFIG_PROVE_LOCKING in Kconfig. With them

Re: [lkp-robot] [irda] 66d98e78e4: BUG:unable_to_handle_kernel

On Wed, Aug 30, 2017 at 02:04:11PM +0800, kernel test robot wrote: > FYI, we noticed the following commit: > > commit: 66d98e78e44ccb969cb3196995759d200e64b49b ("irda: move net/irda/ to > drivers/staging/irda/net/") > url: >

Re: [PATCH v3 3/3] eeprom: at24: enable runtime pm support

Hi Divagar, Thanks for the update. A few more comments below. On Wed, Aug 30, 2017 at 09:41:06AM +0530, Divagar Mohandass wrote: > Currently the device is kept in D0, there is an opportunity > to save power by enabling runtime pm. > > Device can be daisy chained from PMIC and we can't rely on

Re: kvm splat in mmu_spte_clear_track_bits

On Tue 29-08-17 16:09:24, Andrea Arcangeli wrote: [...] > The other bug where you can reproduce the same corruption with OOM is > unrelated and caused by the OOM reaper. OOM reaper was even corrupting > data if a task was writing to disk and stuck in OOM in write() syscall > or async io write. >

Re: [PATCH 4/4] lockdep: Fix workqueue crossrelease annotation

On Wed, Aug 30, 2017 at 11:09:53AM +0900, Byungchul Park wrote: > On Tue, Aug 29, 2017 at 10:59:39AM +0200, Peter Zijlstra wrote: > > Subject: lockdep: Untangle xhlock history save/restore from task > > independence > > > > Where XHLOCK_{SOFT,HARD} are save/restore points in the xhlocks[] to > >

Re: I/O hangs after resuming from suspend-to-ram

Hi, On Wed, Aug 30, 2017 at 08:15:02AM +0200, oleksa...@natalenko.name wrote: > Hello. > > Addressing your questions below. > > > Can't reproduce even with putting dmcypt on raid10 after applying my > > patch. > > Just a side note, that dm-crypt is not necessary here — I am able to trigger >

linux-next: no release today

Hi all, There will be no linux-next release today, sorry. -- Cheers, Stephen Rothwell

Re: [PATCH v3 1/6] android: binder: Refactor prev and next buffer into a helper function

On Tue, Aug 29, 2017 at 05:46:57PM -0700, Sherry Yang wrote: > Use helper functions buffer_next and buffer_prev instead > of list_entry to get the next and previous buffers. > > Signed-off-by: Sherry Yang > --- > drivers/android/binder_alloc.c | 24 +++-

Re: [PATCH] drm: vmwgfx: constify vmw_fence_ops

On 08/30/2017 07:47 AM, Arvind Yadav wrote: vmw_fence_ops are not supposed to change at runtime. Functions "dma_fence_init" working with const vmw_fence_ops provided by . So mark the non-const structs as const. Signed-off-by: Arvind Yadav ---

Re: d82fed7529 ("locking/lockdep/selftests: Fix mixed read-write .."): BUG: -1 unexpected failures (out of 262) - debugging disabled! |

On Wed, Aug 30, 2017 at 11:37:21AM +0800, kernel test robot wrote: > [0.004000] > - > [0.004000] BUG: -1 unexpected failures (out of 262) - debugging > disabled! | > [0.004000] >

[PATCH 0/6] [media] cx24116: Adjustments for two function implementations

From: Markus Elfring Date: Wed, 30 Aug 2017 09:05:04 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (6): Delete an error message for a failed memory allocation in cx24116_writeregN() Return directly

[PATCH 1/6] [media] cx24116: Delete an error message for a failed memory allocation in cx24116_writeregN()

From: Markus Elfring Date: Tue, 29 Aug 2017 22:56:29 +0200 Omit an extra message for a memory allocation failure in this function. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

Re: [PATCH v2 15/30] xfs: Define usercopy region in xfs_inode slab cache

On Wed, Aug 30, 2017 at 12:14:03AM -0700, Christoph Hellwig wrote: > On Wed, Aug 30, 2017 at 07:51:57AM +1000, Dave Chinner wrote: > > Right, I've looked at btrees, too, but it's more complex than just > > using an rbtree. I originally looked at using Peter Z's old > > RCU-aware btree code, but it

Re: [PATCH v3] mfd: tps65217: Introduce dependency on CONFIG_OF

Hello Keerthy, On Wed, Aug 30, 2017 at 7:50 AM, Keerthy wrote: > Currently the driver boots only via device tree hence add a > dependency on CONFIG_OF. This leaves with a bunch of unused code > so clean that up. This patch also makes use of probe_new function > in place of the

Re: possible circular locking dependency mmap_sem/cpu_hotplug_lock.rw_sem

The previous patch is insufficient. drain_all_stock can still race with the memory offline callback and the underlying memcg disappear. So we need to be more careful and pin the css on the memcg. This patch instead... --- >From 70a5acf9bbe76d183e81a1a6b57dd5b9edc677c6 Mon Sep 17 00:00:00 2001

Re: [PATCH] intel-iommu: Don't be too aggressive when clearing one context entry

On Mon, 28 Aug 2017 16:16:29 +0200 Filippo Sironi via iommu wrote: > Previously, we were invalidating context cache and IOTLB globally when > clearing one context entry. This is a tad too aggressive. > Invalidate the context cache and IOTLB for the interested

[PATCH v2 2/3] regulator: Add support for stm32-vrefbuf

Add regulator driver for STM32 voltage reference buffer which can be used as voltage reference for ADCs, DACs and external components through dedicated VREF+ pin. Signed-off-by: Fabrice Gasnier --- Changes in v2: - Remarks from Mark: include error codes when printing

[PATCH v2 1/3] dt-bindings: regulator: Add STM32 Voltage Reference Buffer

Document STM32 VREFBUF (voltage reference buffer) which can be used as voltage reference for ADCs, DACs and external components. Signed-off-by: Fabrice Gasnier Acked-by: Rob Herring --- .../bindings/regulator/st,stm32-vrefbuf.txt | 20

[PATCH v2 0/3] Add support for STM32 vrefbuf regulator

Some STM32 devices embed a voltage reference buffer which can be used as voltage reference for ADCs, DACs and also as voltage reference for external components through the dedicated VREF+ pin. This patchset adds vrefbuf regulator driver, device tree bindings and vrefbuf device tree node for

[PATCH v2 3/3] ARM: dts: stm32: add vrefbuf to stm32h743

Add STM32H743 VREFBUF (Voltage Reference Buffer) definition. Signed-off-by: Fabrice Gasnier --- arch/arm/boot/dts/stm32h743.dtsi | 9 + 1 file changed, 9 insertions(+) diff --git a/arch/arm/boot/dts/stm32h743.dtsi b/arch/arm/boot/dts/stm32h743.dtsi index

Re: [PATCH v3 56/59] KVM: arm/arm64: GICv4: Prevent heterogenous systems from using GICv4

On 28/08/17 19:35, Christoffer Dall wrote: > On Mon, Jul 31, 2017 at 06:26:34PM +0100, Marc Zyngier wrote: >> The GICv4 architecture doesn't prevent CPUs implementing GICv4 to >> cohabit with CPUs limited to GICv3 in the same system. >> >> This is mad (the sheduler would have to be made aware of

[GIT PULL] ARM: at91: DT for 4.14#2

Hi Olof, As discussed, this replaces the previous pull request. The only change is the fixed up SoB. The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877: Linux v4.13-rc1 (2017-07-15 15:22:10 -0700) are available in the git repository at:

Re: [PATCH] acpi: apei: call into AER handling regardless of severity

On Wed, Aug 30, 2017 at 09:42:08AM -0600, Baicar, Tyler wrote: > I think with my two patches we will have the desired functionality: > > GHES_SEV_CORRECTABLE -> AER_CORRECTABLE -> Print AER info, but do not call > do_recovery > > GHES_SEV_RECOVERABLE -> AER_NONFATAL -> Print AER info and

linux-next: Signed-off-by missing for commits in the mailbox tree

Hi Jassi, Commits da91001cab90 ("mailbox: bcm-flexrm-mailbox: Set IRQ affinity hint for FlexRM ring IRQs") 6bee3ba26d4d ("mailbox: bcm-flexrm-mailbox: Add debugfs support") 73c28265c82b ("mailbox: bcm-flexrm-mailbox: Fix mask used in CMPL_START_ADDR_VALUE()") 33001f4ee950 ("mailbox:

Re: [PATCH] qla2xxx: add missing includes for qla_isr

> On Aug 30, 2017, at 6:12 AM, Johannes Thumshirn wrote: > > Since commit 7401bc18d1ee ("scsi: qla2xxx: Add FC-NVMe command handling") > we make use of 'struct nvmefc_fcp_req' in qla24xx_nvme_iocb_entry() without > including linux/nvme-fc-driver.h where it is defined. > >

Re: iov_iter_pipe warning.

On Wed, Aug 30, 2017 at 10:13:43AM -0700, Darrick J. Wong wrote: > > I reverted the debug patches mentioned above, and ran trinity for a while > > again, > > and got this which smells really suspiciously related > > > > WARNING: CPU: 1 PID: 10380 at fs/iomap.c:993 iomap_dio_rw+0x825/0x840

Re: [RFC PATCH v9 1/7] edac: thunderx: Remove suspend/resume support

On Tue, Aug 29, 2017 at 03:12:32PM +0200, Jan Glauber wrote: > The memory controller on ThunderX/OcteonTX systems does not > support power management. Therefore remove the suspend/resume > callbacks. > > Signed-off-by: Jan Glauber > --- > drivers/edac/thunderx_edac.c | 21

Re: [GIT] Networking

From: Kalle Valo Date: Wed, 30 Aug 2017 20:31:31 +0300 > AFAICS the bug was introduced by 9df86e2e702c6 back in 2010. If the bug > has been there for 7 years so waiting for a few more weeks should not > hurt. As a maintainer you have a right to handle bug fixing in that

Re: [RFC PATCH 2/2] membarrier: provide register sync core cmd

On Wed, Aug 30, 2017 at 05:53:53PM +, Mathieu Desnoyers wrote: > - On Aug 28, 2017, at 1:49 PM, Paul E. McKenney > paul...@linux.vnet.ibm.com wrote: > > > On Sun, Aug 27, 2017 at 09:39:54PM +, Mathieu Desnoyers wrote: > >> - On Aug 27, 2017, at 2:00 PM, Paul E. McKenney > >>

Re: [PATCH] acpi: apei: call into AER handling regardless of severity

On 8/30/2017 11:14 AM, Borislav Petkov wrote: On Wed, Aug 30, 2017 at 09:42:08AM -0600, Baicar, Tyler wrote: I think with my two patches we will have the desired functionality: GHES_SEV_CORRECTABLE -> AER_CORRECTABLE -> Print AER info, but do not call do_recovery GHES_SEV_RECOVERABLE ->

[PATCH 2/5] lmp92001: mfd: iio: adc: Add support LMP92001

From: Abhisit Sangjan TI LMP92001 Analog System Monitor and Controller 8-bit GPIOs. 12 DACs with 12-bit resolution. The GPIOs and DACs are shared port function with Cy function pin to take control the pin suddenly from external hardware. DAC's referance voltage selectable

Re: [PATCH] drm: vmwgfx: constify vmw_fence_ops

On Wed, Aug 30, 2017 at 10:30:24AM +0200, Daniel Vetter wrote: > On Wed, Aug 30, 2017 at 08:21:46AM +0200, Thomas Hellstrom wrote: > > On 08/30/2017 07:47 AM, Arvind Yadav wrote: > > > vmw_fence_ops are not supposed to change at runtime. Functions > > > "dma_fence_init" working with const

Re: [PATCH] acpi: apei: call into AER handling regardless of severity

On 8/30/2017 9:31 AM, Sinan Kaya wrote: On 8/30/2017 11:16 AM, Borislav Petkov wrote: On Wed, Aug 30, 2017 at 10:05:44AM -0400, Sinan Kaya wrote: Link reset is not the only recovery mechanism. In the case of nonfatal errors, it is assumed that the endpoint CSR is still reachable. Error is

Re: linux-next: Signed-off-by missing for commit in the arm-soc tree

On Wed, Aug 30, 2017 at 6:19 AM, Alexandre Belloni wrote: > On 30/08/2017 at 23:07:12 +1000, Stephen Rothwell wrote: >> Hi all, >> >> Commit >> >> 1a9f9af07e80 ("ARM: dts: at91: at91sam9g45: add AC97") >> >> is missing a Signed-off-by from its author. >> >

Re: [PATCH] PCI: tegra: Use PTR_ERR_OR_ZERO

On Wed, Aug 30, 2017 at 04:25:47PM +0200, Thierry Reding wrote: > On Wed, Aug 30, 2017 at 08:59:31AM -0500, Bjorn Helgaas wrote: > > On Tue, Aug 29, 2017 at 03:55:17PM +0200, Thierry Reding wrote: > > > On Tue, Aug 29, 2017 at 07:09:00PM +0530, Himanshu Jha wrote: > > > > Use PTR_ERR_OR_ZERO

Re: linux-next: Signed-off-by missing for commit in the arm-soc tree

On 30/08/2017 at 09:21:47 -0700, Olof Johansson wrote: > On Wed, Aug 30, 2017 at 6:19 AM, Alexandre Belloni > wrote: > > On 30/08/2017 at 23:07:12 +1000, Stephen Rothwell wrote: > >> Hi all, > >> > >> Commit > >> > >> 1a9f9af07e80 ("ARM: dts: at91:

[PATCH] ARM: mxs: constify platform_suspend_ops

platform_suspend_ops are not supposed to change at runtime. Functions suspend_set_ops working with const platform_suspend_ops. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- arch/arm/mach-mxs/pm.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] powerpc: 4xx: constify platform_suspend_ops

platform_suspend_ops are not supposed to change at runtime. Functions suspend_set_ops working with const platform_suspend_ops. So mark the non-const structs as const. Signed-off-by: Arvind Yadav --- arch/powerpc/sysdev/ppc4xx_cpm.c | 2 +- 1 file changed, 1

Re: [PATCH 02/13] mm/rmap: update to new mmu_notifier semantic

Hello Jerome, On Tue, Aug 29, 2017 at 07:54:36PM -0400, Jerome Glisse wrote: > Replacing all mmu_notifier_invalidate_page() by mmu_notifier_invalidat_range() > and making sure it is bracketed by call to > mmu_notifier_invalidate_range_start/ > end. > > Note that because we can not presume the

Re: [PATCH 1/2] iommu/tegra: Add support for struct iommu_device

On 30/08/17 16:30, Joerg Roedel wrote: > Hi Jon, > > On Wed, Aug 30, 2017 at 03:22:05PM +0100, Jon Hunter wrote: >> Yes I can confirm that this fixes the crash. I assume that you will fix >> the error path for bus_set_iommu() above as I believe now it needs to >> call

[PATCH v4 2/3] eeprom: at24: add support to fetch eeprom device property "size"

Obtain the size of the EEPROM chip from DT if the "size" property is specified for the device. Signed-off-by: Divagar Mohandass --- drivers/misc/eeprom/at24.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/misc/eeprom/at24.c

Re: iov_iter_pipe warning.

On Mon, Aug 28, 2017 at 09:25:42PM -0700, Darrick J. Wong wrote: > On Mon, Aug 28, 2017 at 04:31:30PM -0400, Dave Jones wrote: > > On Mon, Aug 07, 2017 at 04:18:18PM -0400, Dave Jones wrote: > > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > > > On Fri, Apr 28, 2017 at

[PATCH v4 3/3] eeprom: at24: enable runtime pm support

Currently the device is kept in D0, there is an opportunity to save power by enabling runtime pm. Device can be daisy chained from PMIC and we can't rely on I2C core for auto resume/suspend. Driver will decide when to resume/suspend. Signed-off-by: Divagar Mohandass

best price, best quality,solar hot water heating system

New product--How to connect the solar thermal collectors with the existing tank Hi, We have invented the circulation pump with 4 ways valve integrated to make all the family have the solar water heating. Just to connect the valve with the existing tank which has the circulation connection to

Re: [PATCH v2] membarrier: provide register sync core cmd

- On Aug 30, 2017, at 12:01 AM, Boqun Feng boqun.f...@gmail.com wrote: > Hi Mathieu, > > On Sun, Aug 27, 2017 at 01:50:35PM -0700, Mathieu Desnoyers wrote: >> Add a new MEMBARRIER_CMD_REGISTER_SYNC_CORE command to the membarrier >> system call. It allows processes to register their intent to

[PATCH] drivers/fmc: make structure fmc_dbgfs_sdb_dump static and include fmc-private.h

From: Colin Ian King The structure fmc_dbgfs_sdb_dump is local to the source and does not need to be in global scope, so make it static. Also, fmc-private.h should be included to fix up two sparse warnings on fmc_debug_init and fmc_debug_exit. Cleans up sparse

Re: [RFC Part1 PATCH v3 16/17] X86/KVM: Provide support to create Guest and HV shared per-CPU variables

On Wed, Aug 30, 2017 at 11:18:42AM -0500, Brijesh Singh wrote: > I was trying to avoid mixing early and no-early set_memory_decrypted() but if > feedback is: use early_set_memory_decrypted() only if its required otherwise > use set_memory_decrypted() then I can improve the logic in next rev.

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Wed, 2017-08-30 at 10:32 -0700, Kees Cook wrote: > On Wed, Aug 30, 2017 at 10:13 AM, Mike Galbraith wrote: > > On Wed, 2017-08-30 at 09:35 -0700, Kees Cook wrote: > >> On Tue, Aug 29, 2017 at 10:02 PM, Mike Galbraith wrote: > >> > On Tue, 2017-08-29 at 11:41

Re: [PATCH] compiler: Don't perform compiletime_assert with -O0.

On 30 August 2017 at 03:26, Michal Nazarewicz wrote: > On Tue, Aug 29 2017, Joe Stringer wrote: >> Recent changes[0] to make use of __compiletime_assert() from >> container_of() increased the usage of this macro, allowing developers to >> notice type conflicts in usage of

Re: linux-next: Signed-off-bys missing for commits in the block tree

On Thu, Aug 31, 2017 at 03:38:03AM +1000, Stephen Rothwell wrote: > > I would say that if you rebase someone's commit(s), then you are on the > > "patch's delivery path" and so should add a Signed-off-by tag. > > Yeah, I agree. Rebasing really is pretty much the exact same thing as > applying a

Re: [PATCH 06/16] fs: fix kernel_write prototype

On Wed, Aug 30, 2017 at 04:59:57PM +0200, Christoph Hellwig wrote: > for (prot = 0; prot < prot_length;) { > sector_t len = min_t(sector_t, bufsize, prot_length - prot); > - ssize_t ret = kernel_write(prot_fd, buf, len, pos + prot); > + ssize_t ret =

Re: tip -ENOBOOT - bisected to locking/refcounts, x86/asm: Implement fast refcount overflow protection

On Wed, Aug 30, 2017 at 10:13 AM, Mike Galbraith wrote: > On Wed, 2017-08-30 at 09:35 -0700, Kees Cook wrote: >> On Tue, Aug 29, 2017 at 10:02 PM, Mike Galbraith wrote: >> > On Tue, 2017-08-29 at 11:41 -0700, Kees Cook wrote: >> >> Can you also test with

Re: [PATCH][net-next][V3] bpf: test_maps: fix typos, "conenct" and "listeen"

On 08/30/2017 10:15 AM, Colin King wrote: > From: Colin Ian King > > Trivial fix to typos in printf error messages: > "conenct" -> "connect" > "listeen" -> "listen" > > thanks to Daniel Borkmann for spotting one of these mistakes > > Signed-off-by: Colin Ian King

Re: [PATCH v7 07/11] sparc64: optimized struct page zeroing

From: Pasha Tatashin Date: Wed, 30 Aug 2017 09:19:58 -0400 > The reason I am not doing initializing stores is because they require > a membar, even if only regular stores are following (I hoped to do a > membar before first load). This is something I was thinking was

[PATCH v3 2/2] media:imx274 V4l2 driver for Sony imx274 CMOS sensor

The imx274 is a Sony CMOS image sensor that has 1/2.5 image size. It supports up to 3840x2160 (4K) 60fps, 1080p 120fps. The interface is 4-lane MIPI CSI-2 running at 1.44Gbps each. This driver has been tested on Xilinx ZCU102 platform with a Leopard LI-IMX274MIPI-FMC camera board. Support for

Applied "regulator: Add support for stm32-vrefbuf" to the regulator tree

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

[PATCH v3 1/2] media:imx274 device tree binding file

The binding file for imx274 CMOS sensor V4l2 driver Signed-off-by: Leon Luo Acked-by: Sören Brinkmann --- v3: - remove redundant properties and references - document 'reg' property v2: - no changes ---

ATENÇÃO

ATENÇÃO; Sua caixa de correio excedeu o limite de armazenamento, que é de 5 GB como definido pelo administrador, que está atualmente em execução no 10.9GB, você pode não ser capaz de enviar ou receber novas mensagens até que você re-validar a sua caixa de correio. Para revalidar sua caixa de

Re: [PATCH v3 5/5] kernel: tracepoints: add support for relative references

On Sat, 19 Aug 2017 19:10:35 +0100 Ard Biesheuvel wrote: > To avoid the need for relocating absolute references to tracepoint > structures at boot time when running relocatable kernels (which may > take a disproportionate amount of space), add the option to emit >

Re: linux-next: Signed-off-by missing for commit in the arc-current tree

On 08/30/2017 05:59 AM, Stephen Rothwell wrote: Hi Vineet, On Mon, 28 Aug 2017 15:28:32 -0700 Vineet Gupta wrote: On 08/28/2017 03:23 PM, Stephen Rothwell wrote: Commit 279921e080b9 ("ARCv2: SLC: provide a line based flush routine for debugging") is

[PATCH 2/3] Makefile: support flag -fsanitizer-coverage=trace-cmp

From: Victor Chibotaru The flag enables Clang instrumentation of comparison operations (currently not supported by GCC). This instrumentation is needed by the new KCOV device to collect comparison operands. Signed-off-by: Victor Chibotaru Cc: Andrew Morton

[PATCH 3/3] kcov: update documentation

From: Victor Chibotaru The updated documentation describes new KCOV mode for collecting comparison operands. Signed-off-by: Victor Chibotaru Cc: Andrew Morton Cc: Mark Rutland Cc: Alexander Popov

  1   2   3   4   5   6   7   8   9   10   >