Add device tree bindings documentation for Micron MT9T111/MT9T112 image
sensors.
Signed-off-by: Jacopo Mondi
---
Documentation/devicetree/bindings/mt9t112.txt | 41 +++
1 file changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mt9t112.txt
dif
On Wed, Apr 25, 2018 at 02:11:16AM +0200, Daniel Borkmann wrote:
> On 04/19/2018 05:54 PM, Wang YanQing wrote:
> > The JIT compiler emits ia32 bit instructions. Currently, It supports
> > eBPF only. Classic BPF is supported because of the conversion by BPF core.
> >
> > Almost all instructions fro
Hello,
this small series add device tree support for the MT9T112 image
sensor.
As in the device tree bindings I used 'semi-standard' name for the
'powerdown' GPIO, I have changed that for all other users of the mt9t112
driver (SH Ecovec only).
A note on clock: as the mt9t112 driver expects t
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hans de Goede
[ Upstream commit 54ddce7062242036402242242c07c60c0b505f84 ]
The battery code uses acpi_device->dep_unmet to check for unmet deps and
if there are unmet deps it does not bind to
2018-04-02 14:46 GMT+08:00 Geert Uytterhoeven :
> Hi Ganesh,
>
> On Mon, Apr 2, 2018 at 3:33 AM, Ganesh Mahendran
> wrote:
>> 2018-03-30 19:00 GMT+08:00 Geert Uytterhoeven :
>>> On Fri, Mar 30, 2018 at 12:25 PM, Rafael J. Wysocki
>>> wrote:
On Monday, March 5, 2018 9:47:46 AM CEST Ganesh Ma
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Yonghong Song
[ Upstream commit 09584b406742413ac4c8d7e030374d4daa045b69 ]
With CONFIG_BPF_JIT_ALWAYS_ON is defined in the config file,
tools/testing/selftests/bpf/test_kmod.sh failed like be
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
[ Upstream commit 9a9ab3078e2744a1a55163cfaec73a5798aae33e ]
We now have a platform (Ranchu) in the "generic" platform which matches
based on the FDT compatible string using mips_
OK. Patch was sent to linux.git as 1f5781725dcbb026.
#syz fix: commoncap: Handle memory allocation failure.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jean Delvare
[ Upstream commit a7770ae194569e96a93c48aceb304edded9cc648 ]
The handling of empty DMI strings looks quite broken to me:
* Strings from 1 to 7 spaces are not considered empty.
*
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
[ Upstream commit 328008a72d38b5bde6491e463405c34a81a65d3e ]
The declaration for swsusp_arch_resume marks it as 'asmlinkage', but the
definition in x86-32 does not, and it fails
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Subash Abhinov Kasiviswanathan
[ Upstream commit ea23d5e3bf340e413b8e05c13da233c99c64142b ]
Failures were seen in ICMPv6 fragmentation timeout tests if they were
run after the RFC2460 failure
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sebastian Ott
[ Upstream commit 366b77ae43c5a3bf1a367f15ec8bc16e05035f14 ]
Commit 2a842acab109 ("block: introduce new block status code type")
added blk_status_t usage to the eadm subchannel
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Estrin
[ Upstream commit 2b1e7fe16124e86ee9242a859c79a843e3a2 ]
The dd refcount is speculatively incremented prior to allocating
the fd memory with kzalloc(). If that kzalloc() faile
OK. Patch is in tty.git#tty-linus as 903f9db10f18f735.
#syz fix: tty: Don't call panic() at tty_ldisc_init()
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Don Hiatt
[ Upstream commit 87daac68f77a3e21a1113f816e6a7be0b38bdde8 ]
iWarp devices do not support the creation of address handles
so return AH_ATTR_TYPE_UNDEFINED for all iWarp devices.
Wh
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Estrin
[ Upstream commit 1029361084d18cc270f64dfd39529fafa10cfe01 ]
On reboot SM can program port pkey table before ipoib registered its
event handler, which could result in missing pkey
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "shidao.ytt"
[ Upstream commit a7ab400d6fe73d0119fdc234e9982a6f80faea9f ]
During our recent testing with fadvise(FADV_DONTNEED), we find that if
given offset/length is not page-aligned, the l
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jens Axboe
[ Upstream commit 445251d0f4d329aa061f323546cd6388a3bb7ab5 ]
I ran into an issue on my laptop that triggered a bug on the
discard path:
WARNING: CPU: 2 PID: 207 at drivers/nvme/ho
On Wed, Apr 25, 2018 at 11:00:31AM +0200, Greg Kroah-Hartman wrote:
> On Tue, Apr 24, 2018 at 06:34:54PM +0200, Johan Hovold wrote:
> > +static inline void *gnss_serial_get_drvdata(struct gnss_serial *gserial)
> > +{
> > + return &gserial[1];
> > +}
>
> Oh that's the best hack I have seen in a l
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mel Gorman
[ Upstream commit 69d763fc6d3aee787a3e8c8c35092b4f4960fa5d ]
Minchan Kim asked the following question -- what locks protects
address_space destroying when race happens between inod
OK. Patch is in vfs.git#for-next as 4fb48871409e2fcd.
#syz fix: restore cond_resched() in shrink_dcache_parent()
On Wed, Apr 25, 2018 at 01:44:20PM +0300, Jarkko Sakkinen wrote:
> "tpm: add retry logic" caused merge conflicts so I picked couple of
> other fixes in order to get it apply cleanly.
Are these only needed in 4.16.y? Nothing earlier?
thanks for the backports, I'll queue them up after this next 4.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
[ Upstream commit e58decc9c51eb61697aba35ba8eda33f4b80552d ]
Fix to return error code -EINVAL instead of 0 when num_vfs above
limit_vfs, as done elsewhere in this function.
Fixes
On 04/25/2018 08:57 AM, Cornelia Huck wrote:
AFAIU this will be the problem of the person implementing the clear
and the halt for vfio-ccw. I.e. it's a non-problem right now.
Well, that person is me:) I will post some RFC Real Soon Now if I stop
getting sidetracked...
Makes sense. It shoul
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Anand Jain
[ Upstream commit 6f794e3c5c8f8fdd3b5bb20d9ded894e685b5bbe ]
It appears from the original commit [1] that there isn't any design
specific reason not to fail the mount instead of ju
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
[ Upstream commit 96d5eaa9bb74d299508d811d865c2c41b38b0301 ]
While testing with the ARM specific memset() macro removed, I ran into a
compiler warning that shows an old bug:
dr
Armada 7K / 8K clock management has recently been reworked, see :
commit c7e92def1ef4 ("clk: mvebu: cp110: Fix clock tree representation")
I have been experiencing overall system hangs on MacchiatoBin when starting
the eth1 interface since then. It turns out some clocks dependencies were
missing
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Xose Vazquez Perez
[ Upstream commit 3f884a0a8bdf28cfd1e9987d54d83350096cdd46 ]
Replace "" with NULL for product revision level, and merge TEXEL
duplicate entries.
Cc: Hannes Reinecke
Cc: M
OK. Patch is in tty.git#tty-linus as 598c2d41ff44889d.
#syz fix: tty: Avoid possible error pointer dereference at tty_ldisc_restore().
Marvell's PPv2.2 IP needs an additional clock named "MG Core clock".
This is required on Armada 7K and 8K.
This commit adds the required clock, updates the devicetree and its
documentation accordingly, also fixing a small typo in the
marvell-mpp2.txt examples.
Fixes: c7e92def1ef4 ("clk: mvebu: cp
The Marvell XSMI controller needs 3 clocks to operate correctly :
- The MG clock (clk 5)
- The MG Core clock (clk 6)
- The GOP clock (clk 18)
This commit adds them, to avoid system hangs when using these
interfaces.
Fixes: c7e92def1ef4 ("clk: mvebu: cp110: Fix clock tree representation")
Sig
When clk_prepare_enable fails for the axi_clk, the mg_clk isn't properly
cleaned up. Add another jump label to handle that case, and make sure we
jump to it in the later error cases.
Fixes: 4792ea04bcd0 ("net: mvpp2: Fix clock resource by adding an optional bus
clock")
Signed-off-by: Maxime Cheva
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: "Gustavo A. R. Silva"
[ Upstream commit e4823fbd229bfbba368b40cdadb8f4eeb20604cc ]
Add suffix ULL to constant 8 in order to avoid a potential integer
overflow and give the compiler comple
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Vyukov
[ Upstream commit 1e98ffea5a8935ec040ab72299e349cb44b8defd ]
Several netfilter matches and targets put kernel pointers into
info objects, but don't set usersize in descriptors.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Logan Gunthorpe
[ Upstream commit cbd27448faff4843ac4b66cc71445a10623ff48d ]
When using the max_mw_size parameter of ntb_transport to limit the size of
the Memory windows, communication canno
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Leon Romanovsky
[ Upstream commit b081808a66345ba725b77ecd8d759bee874cd937 ]
Failure in XRCD FW deallocation command leaves memory leaked and
returns error to the user which he can't do anyth
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Parav Pandit
[ Upstream commit 00db63c128dd3daf38f481371976c24d32678142 ]
If valid netdevice is not found for RoCE, GID table should not be
searched with NULL netdevice.
Doing so causes the
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Michael Bringmann
[ Upstream commit a346137e9142b039fd13af2e59696e3d40c487ef ]
On powerpc systems which allow 'hot-add' of CPU or memory resources,
it may occur that the new resources are to
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jacob Keller
[ Upstream commit 02b4016bfe43d2d5ed043be7ffa56cda6a4d1100 ]
When implementing support for IP_USER_FLOW filters, we correctly
programmed a filter for both the non fragmented IPv4
The JIT compiler emits ia32 bit instructions. Currently, It supports eBPF
only. Classic BPF is supported because of the conversion by BPF core.
Almost all instructions from eBPF ISA supported except the following:
BPF_ALU64 | BPF_DIV | BPF_K
BPF_ALU64 | BPF_DIV | BPF_X
BPF_ALU64 | BPF_MOD | BPF_K
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Emil Tantilov
[ Upstream commit 2bafa8fac19a31ca72ae1a3e48df35f73661dbed ]
commit 2de6aa3a666e ("ixgbe: Add support for padding packet")
Uses RXDCTL.RLPML to limit the maximum frame size on
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ngai-Mint Kwan
[ Upstream commit cf315ea596ec26d7aa542a9ce354990875a920c0 ]
When a VF is under PF VLAN assignment:
ip link set vf <#> vlan
This will remove all previous entries in the VLA
>From 3606b60f60f5a2053290e7160a6fd3ee40f38a51 Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Wed, 25 Apr 2018 15:26:10 +0900
Subject: [PATCH] tty: Use __GFP_NOFAIL for tty_ldisc_get()
syzbot is reporting crashes triggered by memory allocation fault injection
at tty_ldisc_get() [1]. As an atte
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jake Daryll Obina
[ Upstream commit 5bdd0c6f89fba430e18d636493398389dadc3b17 ]
If jffs2_iget() fails for a newly-allocated inode, jffs2_do_clear_inode()
can get called twice in the error hand
On 2018-04-24 17:13, Jan Kiszka wrote:
> From: Jan Kiszka
>
> of_pci_get_host_bridge_resources allocates the resource structures it
> fills dynamically, but none of its callers care to release them so far.
> Rather than requiring everyone to do this explicitly, introduce a
> managed version of th
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Aaron Sierra
[ Upstream commit c7e1b4059075c9e8eed101d7cc5da43e95eb5e18 ]
Exar sleep wake-up handling has been done on a per-channel basis by
virtue of INT0 being accessible from each channel
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Andy Shevchenko
[ Upstream commit c505cbd45f6e9c539d57dd171d95ec7e5e9f9cd0 ]
Some of the drivers may use the macro at runtime flow, like
struct property_entry p[10];
...
p[index++] = PRO
On Wed, Apr 25, 2018 at 06:55:10PM +0800, Icenowy Zheng wrote:
> 于 2018年4月25日 GMT+08:00 下午6:53:09, Mark Brown 写到:
> >> SPDX identifier is special -- it should be in a seperated
> >> comment block.
> >No, it just needs to be a C++ comment on the first line to ease machine
> >parsing. The rest of
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Hua
[ Upstream commit 3a53285228165225a7f76c7d5ff1ddc0213ce0e4 ]
Problem description:
After ethernet cable connect and disconnect for several iterations on a
device with i210, tx times
vsprintf() must not change any data that parameters point to.
Let's add the missing const qualifier to ptr_to_id().
This patch does not change the existing behavior.
Signed-off-by: Petr Mladek
---
lib/vsprintf.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/vsprintf.
We are able to detect invalid values handled by %p[iI] printk specifier.
The current error message is "invalid address". It might cause confusion
against "(efault)" reported by the generic valid_pointer_address() check.
Let's unify the style and use the more appropriate error code description
"(ei
We are going to check the address using probe_kernel_address(). It will
be more expensive and it does not make sense for well known address.
This patch splits the string() function. The variant without the check
is then used on locations that handle string constants or strings defined
as local var
We already prevent crash when dereferencing some obviously broken
pointers. But the handling is not consistent. Sometimes we print "(null)"
only for pure NULL pointer, sometimes for pointers in the first
page and sometimes also for pointers in the last page (error codes).
Note that printk() call t
Crash in vsprintf() might be silent when it happens under logbuf_lock
in vprintk_emit(). This patch set prevents most of the crashes by probing
the address. The check is done only by %s and some %p* specifiers that need
to dereference the address.
Only the first byte of the address is checked to k
There are few printk formats that make sense only with two or more
specifiers. Also some specifiers make sense only when a kernel feature
is enabled.
The handling of unknown specifiers is strange, inconsistent, and
even leaking the address. For example, netdev_bits() prints the
non-hashed pointer
vsprintf puts "(efault)" into the output string when it is unable
to read information from the given address.
But "(efault)" might be hard to spot. And any invalid pointer is likely
to cause problems later. It is reasonable to WARN() about it.
The only problem might be a code that rely on the fac
Move code from the long pointer() function. We are going to add a check for
the access to the address that will make it even more complicated.
Also it is better to warn about unknown specifier instead of falling
back to the %p behavior. It will help people to understand what is
going wrong. They e
Move the non-trivial code from the long pointer() function. We are going
to add a check for the access to the address that will make it even more
complicated.
Also it is better to warn about unknown specifier instead of falling
back to the %p behavior. It will help people to understand what is
goi
Move the code from the long pointer() function. We are going to add a check
for the access to the address that will make it even more complicated.
This patch does not change the existing behavior.
Signed-off-by: Petr Mladek
---
lib/vsprintf.c | 22 +-
1 file changed, 13 inse
Enable CEU0 peripheral for Renesas R-Mobile A1 R8A7740.
Signed-off-by: Jacopo Mondi
---
arch/arm/boot/dts/r8a7740.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7740.dtsi b/arch/arm/boot/dts/r8a7740.dtsi
index afd3bc5..05ec41e 100644
--- a/arch/arm/boot
Hello,
this small series add R-Mobile A1 R8A7740 to the list of CEU supported
SoCs, and adds the CEU node to r8a7740.dtsi.
All the information on CEU clocks, power domains and memory regions have been
deducted from the now-deleted board file:
arch/arm/mach-shmobile/board-armadillo800eva.c
Than
Add R-Mobile A1 R8A7740 SoC to the list of compatible values for the CEU
unit.
Signed-off-by: Jacopo Mondi
---
Documentation/devicetree/bindings/media/renesas,ceu.txt | 7 ---
drivers/media/platform/renesas-ceu.c| 1 +
2 files changed, 5 insertions(+), 3 deletions(-)
dif
On Wed, Apr 25, 2018 at 9:21 AM, Christoph Hellwig wrote:
> On Wed, Apr 25, 2018 at 09:08:13AM +0200, Arnd Bergmann wrote:
>> > That probably also means it can use dma_mmap_coherent instead of the
>> > handcrafted remap_pfn_range loop and the PageReserved abuse.
>>
>> I'd rather not touch that cod
restricted_pointer() pretends that it prints the address when kptr_restrict
is set to zero. But it is never called in this situation. Instead,
pointer() falls back to ptr_to_id() and hashes the pointer.
This patch removes the potential confusion. klp_restrict is checked only
in restricted_pointer(
This is just a preparation step for further changes.
The patch does not change the code.
Signed-off-by: Petr Mladek
---
lib/vsprintf.c | 244 -
1 file changed, 122 insertions(+), 122 deletions(-)
diff --git a/lib/vsprintf.c b/lib/vsprintf
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Corinna Vinschen
[ Upstream commit 177132df5e45b134c147f419f567a3b56aafaf2b ]
Before libvirt modifies the MAC address and vlan tag for an SRIOV VF
for use by a virtual machine (either using v
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Jeffy Chen
[ Upstream commit fde7f9dbc71365230eeb8c8ea97ce9b552c8e5bd ]
The rt5514 dsp captures pcm data through spi directly, so we should not
use rockchip-i2s as it's cpu dai like other cod
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Vitaly Kuznetsov
[ Upstream commit 617ab45c9a8900e64a78b43696c02598b8cad68b ]
When hypercall-based TLB flush was enabled for Hyper-V guests PCID feature
was deliberately suppressed as a preca
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Herrmann
[ Upstream commit 587d8628fb71c3bfae29fb2bbe84c1478c59bac8 ]
This patch prevents the thinkpad_acpi driver from warning about 2 event
codes returned for keyboard palm-detection.
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Eryu Guan
[ Upstream commit 6b136a24b05c81a24e0b648a4bd938bcd0c4f69e ]
Attributes that only implement .seq_ops are read-only, any write to
them should be rejected. But currently kernel would
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Avinash Dayanand
[ Upstream commit 06aa040f039404a0039a5158cd12f41187487a1f ]
When a host disables and enables a PF device, all the associated
VFs are removed and added back in. It also gener
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: David Hildenbrand
[ Upstream commit b3ecd4aa8632a86428605ab73393d14779019d82 ]
Another VCPU might try to modify the SCB while we are creating the
shadow SCB. In general this is no problem - u
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Goldwyn Rodrigues
[ Upstream commit 20d59023c5ec4426284af492808bcea1f39787ef ]
We inadvertently set it again on the source bio, but we need
to set it on the new split bio instead.
Fixes: fbb
On 04/25/2018 04:43 AM, Dong Jia Shi wrote:
[Some procedural notes: I've created a new vfio-ccw-fixes branch based
on the s390 fixes branch for easier handling. Things targeted for the
next release will go on the vfio-ccw branch on top of the s390 features
branch, as before. Does that work for
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Dmitry Torokhov
[ Upstream commit 2bc4298f59d2f15175bb568e2d356b5912d0cdd9 ]
When Synaptics protocol is disabled, we still need to try and detect the
hardware, so we can switch to SMBus devic
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Hutterer
[ Upstream commit 19eb4ed1141bd1096b9bc84ba9c4d03d5830c143 ]
input_mt_init_slots() resets the ABS_X/Y fuzz to 0 and expects the driver
to call input_mt_report_pointer_emulation
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Mustafa Ismail
[ Upstream commit f20d429511affab6a2a9129f46042f43e6ffe396 ]
The iWARP Exception Queue (IEQ) resources are not freed when a QP is
destroyed. Fix this by freeing IEQ resources w
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
[ Upstream commit aa008206634363ef800fbd5f0262016c9ff81dea ]
The Marvell 9128 is the original device generating bug 42679, from which
many other Marvell DMA alias quirks have
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Liu Bo
[ Upstream commit 762221f095e3932669093466aaf4b85ed9ad2ac1 ]
The raid6 corruption is that,
suppose that all disks can be read without problems and if the content
that was read out does
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
[ Upstream commit e749d328b0b450aa78d562fa26a0cd8872325dd9 ]
Fix to return a negative error code from the request_irq() error
handling case instead of 0, as done elsewhere in this
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Borisov
[ Upstream commit 9ea2c7c9da13c9073e371c046cbbc45481ecb459 ]
When modifying a tree where the root is at BTRFS_MAX_LEVEL - 1 then
the level variable is going to be 7 (this is t
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Niklas Cassel
[ Upstream commit 80db6f08b7af93eddc9487535e6150b220262637 ]
Some hardware can operate in either "host" or "endpoint" mode, which means
there can be both a host bridge driver an
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ulf Magnusson
[ Upstream commit 0724a7c32a54e3e50d28e19e30c59014f61d4e2c ]
If a 'mainmenu' entry appeared in the Kconfig files, two things would
leak:
- The 'struct property' allocat
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ulf Magnusson
[ Upstream commit 5b1374b3b3c2fc4f63a398adfa446fb8eff791a4 ]
Only the E_NOT operand and not the E_NOT node itself was freed, due to
accidentally returning too early in expr_free
The function rds_ib_setup_qp is calling rds_ib_get_client_data and
should correspondingly call rds_ib_dev_put. This call was lost in
the non-error path with the introduction of error handling done in
commit 3b12f73a5c29 ("rds: ib: add error handle")
Signed-off-by: Dag Moxnes
---
net/rds/ib_cm.c
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Chuck Lever
[ Upstream commit d698c4a02ee02053bbebe051322ff427a2dad56a ]
The backchannel code uses rpcrdma_recv_buffer_put to add new reps
to the free rep list. This also decrements rb_recv_c
Hi Mark,
On Tue, Apr 17, 2018 at 07:37:31PM +0100, Mark Rutland wrote:
> diff --git a/arch/arm64/include/asm/mmu_context.h
> b/arch/arm64/include/asm/mmu_context.h
> index 39ec0b8a689e..caf0d3010112 100644
> --- a/arch/arm64/include/asm/mmu_context.h
> +++ b/arch/arm64/include/asm/mmu_context.h
>
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: James Hogan
[ Upstream commit 5f2483eb2423152445b39f2db59d372f523e664e ]
Make doesn't expand shell style "vmlinuz.{32,ecoff,bin,srec}" to the 4
separate files, so none of these files get clea
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Martin Blumenstingl
[ Upstream commit fb7d38a70e1d8ffd54f7a7464dcc4889d7e490ad ]
On Meson8b the only valid input clock is MPLL2. The bootloader
configures that to run at 52394Hz which can
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Sagi Grimberg
[ Upstream commit 246d8b184c100e8eb6b4e8c88f232c2ed2a4e672 ]
polling the completion queue directly does not interfere
with the existing polling logic, hence drop the requirement
This patch adds functionality to perform
flush from guest to hosy over VIRTIO
when 'ND_REGION_VIRTIO'flag is set on
nd_negion. Flag is set by 'virtio-pmem'
driver.
Signed-off-by: Pankaj Gupta
---
drivers/nvdimm/region_devs.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/n
This patch adds virtio-pmem Qemu device.
This device presents memory address range
information to guest which is backed by file
backend type. It acts like persistent memory
device for KVM guest. Guest can perform read
and persistent write operations on this memory
range with the help of DAX c
This patch adds virtio-pmem driver for KVM
guest.
Guest reads the persistent memory range
information from Qemu over VIRTIO and registers
it on nvdimm_bus. It also creates a nd_region
object with the persistent memory range
information so that existing 'nvdimm/pmem'
driver can reserve this
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: mulhern
[ Upstream commit 9b28a1102efc75d81298198166ead87d643a29ce ]
Fixes:
1. The use of "exceeds" when the opposite of exceeds, falls below,
was meant.
2. Properly speaking, a table can not
4.14-stable review patch. If anyone has any objections, please let me know.
--
From: Ming Lei
[ Upstream commit 7df938fbc4ee641e70e05002ac67c24b19e86e74 ]
We know this WARN_ON is harmless and in reality it may be trigged,
so convert it to printk() and dump_stack() to avoid to
On Wed, Apr 25, 2018 at 09:17:22AM +0200, Daniel Vetter wrote:
> On Tue, Apr 24, 2018 at 07:12:47PM +0100, Ayan Kumar Halder wrote:
> > malidp_pm_suspend_late checks if the runtime status is not suspended
> > and if so, invokes malidp_runtime_pm_suspend which disables the
> > display engine/core in
This is RFC V2 for 'fake DAX' flushing interface sharing
for review. This patchset has two main parts:
- Guest virtio-pmem driver
Guest driver reads persistent memory range from paravirt
device and registers with 'nvdimm_bus'. 'nvdimm/pmem'
driver uses this information to allocate persiste
On Wed, Apr 25, 2018 at 9:23 AM, Jaroslav Kysela wrote:
> Dne 24.4.2018 v 15:37 Arnd Bergmann napsal(a):
>> On Tue, Apr 24, 2018 at 3:29 PM, Jaroslav Kysela wrote:
>>> Dne 24.4.2018 v 14:06 Baolin Wang napsal(a):
Since many structures will use timespec type variables to record time stamp
>>>
On Wed, 25 Apr 2018 16:29:31 +0530
Shilpasri G Bhat wrote:
> gpstate_timer_handler() uses synchronous smp_call to set the pstate
> on the requested core. This causes the below hard lockup:
>
> [c03fe566b320] [c01d5340] smp_call_function_single+0x110/0x180
> (unreliable)
> [c03fe
Hi Christoph,
On Fri, 2018-04-20 at 10:02 +0200, Christoph Hellwig wrote:
> Switch to the generic noncoherent direct mapping implementation.
>
> Signed-off-by: Christoph Hellwig
> ---
> arch/arc/Kconfig | 4 +
> arch/arc/include/asm/Kbuild| 1 +
> arch/arc/include/
301 - 400 of 1348 matches
Mail list logo
