Linus,
The following changes since commit b41dae061bbd722b9d7fa828f35d22035b218e18:
Merge tag 'xfs-5.4-merge-7' of git://git.kernel.org/pub/scm/fs/xfs/xfs-linux
(2019-09-18 18:32:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
Quoting Geert Uytterhoeven (2019-09-26 06:07:13)
> Hi Stephen,
>
> On Fri, Sep 20, 2019 at 11:06 PM Stephen Boyd wrote:
> > Quoting Arnd Bergmann (2019-09-20 12:27:50)
> > > On Fri, Sep 20, 2019 at 6:45 PM Stephen Boyd wrote:
> > > > > @@ -54,11 +60,6 @@ static int qcom_apcs_ipc_probe(struct
>
On Wed, Sep 25, 2019 at 03:34:47AM +, Leo Li wrote:
>
>
> > -Original Message-
> > From: Biwen Li
> > Sent: Tuesday, September 24, 2019 10:30 PM
> > To: Leo Li ; shawn...@kernel.org;
> > robh...@kernel.org; mark.rutl...@arm.com; Ran Wang
> >
> > Cc: linuxppc-...@lists.ozlabs.org; lin
From: Kunihiko Hayashi
Date: Thu, 26 Sep 2019 15:35:10 +0900
> Until calling register_netdev(), ndev->dev_name isn't specified, and
> netdev_err() displays "(unnamed net_device)".
>
> ave 6500.ethernet (unnamed net_device) (uninitialized): invalid
> phy-mode setting
> ave: probe of
From: Hans Andersson
Date: Thu, 26 Sep 2019 09:54:37 +0200
> From: Hans Andersson
>
> The Micrel KSZ9031 PHY may fail to establish a link when the Asymmetric
> Pause capability is set. This issue is described in a Silicon Errata
> (DS8691D or DS8692D), which advises to always disable th
From: Colin King
Date: Thu, 26 Sep 2019 12:13:06 +0100
> From: Colin Ian King
>
> The return statement is indented incorrectly, add in a missing
> tab and remove an extraneous space after the return
>
> Signed-off-by: Colin Ian King
Applied.
On Tue, 24 Sep 2019 15:43:00 +0800, Xia Jiang wrote:
> Add jpeg enc device tree node document.
>
> Signed-off-by: Xia Jiang
> ---
> v3: change compatible to SoC specific compatible
>
> v2: no changes
> ---
> .../bindings/media/mediatek-jpeg-encoder.txt | 37 +++
> 1 file change
From: Colin King
Date: Thu, 26 Sep 2019 12:22:52 +0100
> From: Colin Ian King
>
> There memset is indented incorrectly, remove the extraneous tabs.
>
> Signed-off-by: Colin Ian King
Applied.
From: Nikhil Devshatwar
SEQ_BT indicates the buffer for bottom field needs to be processed
before the top field.
Simplify the field selection logic to support SEQ_BT as well.
Modify the interlace flags to include any of alternate, SEQ_TB, SEQ_BT.
Update other format error checking to consider S
A few NULL pointer checks were missing.
Add check with appropriate return code.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/vpe.c | 13 -
1 file changed, 12 insertions(+), 1 deletion(-)
diff --git a/drivers/media/platform/ti-vpe/vpe.c
b/drivers/media/platform/ti-
Instead of saving a pointer to the 'fh' member of struct vpe_ctx to
later have to use container_of to retrieve the actual pointer to the
context structure, which seems to confuse static code analysis tool
anyways, just save the pointer to the actual structure and then retrieve
it directly.
Signed-
v4l2-compliance warns with this message:
warn: v4l2-test-formats.cpp(717): \
TRY_FMT cannot handle an invalid pixelformat.
warn: v4l2-test-formats.cpp(718): \
This may or may not be a problem. For more information see:
warn: v4l2-test-formats.cpp(719): \
http://www
Up to now VPE was relying on the colorspace value of struct v4l2_format
as an indication to perform color space conversion from YUV to RGB or
not.
Instead we should used the source/destination fourcc codes as a more
reliable indication to perform color space conversion or not.
Signed-off-by: Beno
All 4 of the "colorspace" components were not originally handled.
Causing issue related to xfer_func not being initialized properly.
This was found with v4l2-compliance test.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/vpe.c | 12
1 file changed, 12 insertions(+)
commit 52831a418fa6 ("[media] media: ti-vpe: vpe: allow use of user
specified stride") and commit 8c1e4fa17e92 ("[media] media: ti-vpe: vpdma:
add support for user specified stride") resulted in the Motion Vector
stride to be the same as the image stride.
This caused memory corruption in the outpu
v4l2-compliance fails with this message:
fail: v4l2-test-buffers.cpp(691): ret == 0
fail: v4l2-test-buffers.cpp(974): captureBufs(node, q, m2m_q,
frame_count, true)
test MMAP: FAIL
This caused the following Kernel Warning:
WARNING: CPU: 0 PID: 961 at
drivers/media/v4l2-core/videobuf2-co
VPE uses VPDMA (built-in dma engine) to transfer data to and from the IP
and memory. VPDMA expect 32 bits addresses. To make sure that is always
the case set the DMA mask and coherent mask for the device.
Signed-off-by: Benoit Parrot
---
drivers/media/platform/ti-vpe/vpe.c | 7 +++
1 file ch
From: Nikhil Devshatwar
In NV21 format, the chroma plane is written to memory such that the U
and V components are swapped for NV12.
Create a new entry in the VPDMA formats to describe the correct data
types used in the data descriptors.
Update all checks for NV12 and add NV21 there as well.
A
Using dma_addr_t as the type to hold address inside of a fix sized
descriptor used by the vpdma firmware is prone to fail when the expected
width is 32 bits and suddenly when CONFIG_LPAE is enabled the data size
is now 64 bits shifted the remaining members of the descriptor in memory
which confuses
v4l2-compliance fails with this message:
fail: v4l2-test-formats.cpp(463): !pfmt.sizeimage
fail: v4l2-test-formats.cpp(736): \
Video Capture Multiplanar is valid, \
but TRY_FMT failed to return a format
test VIDIOC_TRY_FMT: FAIL
This failure is causd by the driver failing
On Fri, Sep 27, 2019 at 6:08 AM Zhang Rui wrote:
>
> One thing to mention is that, all the patches have been tested in
> linux-next for weeks, but there is a conflict detected, because
> upstream has took commit eaf7b46083a7e34 ("docs: thermal: add it to the
> driver API") from jc-docs tree while
v4l2-compliance fails with this message:
warn: v4l2-test-formats.cpp(717): \
TRY_FMT cannot handle an invalid pixelformat.
test VIDIOC_TRY_FMT: FAIL
This causes the following kernel panic:
Unable to handle kernel paging request at virtual address 56595561
pgd = ecd80e00
*pgd=00
v4l2-compliance fails with this message:
fail: v4l2-test-buffers.cpp(294): \
(int)g_sequence() < seq.last_seq + 1
fail: v4l2-test-buffers.cpp(740): \
buf.check(m2m_q, last_m2m_seq)
fail: v4l2-test-buffers.cpp(974): \
captureBufs(node, q, m2m_q, frame_count, true)
From: Ram Prasad
VPE's max height supported MAX_H is set to 1184 which is the
padded height from VC1 decoder output.
In case of 90, 270 degree rotated video processing, input to
VPE will be 1080x1920, 720x1280 etc and MAX_H needs to be set
correct value. Setting MAX_H to 2048 as worst case heigh
v4l2-compliance fails with this message:
fail: v4l2-test-formats.cpp(672): \
Video Capture Multiplanar: TRY_FMT(G_FMT) != G_FMT
fail: v4l2-test-formats.cpp(672): \
Video Output Multiplanar: TRY_FMT(G_FMT) != G_FMT
...
test VIDIOC_TRY_FMT: FAIL
Fixes: 94ed726e8e01
This a collection of backlog patches I have been carrying for the VPE
driver.
It adds supports for SEQ_BT as well as NV21.
And fixes a number of issues both through v4l2-compliance and normal
usage.
==
v4l2-compliance SHA: 5b168dc8473911227890526bad26553d9e8ff8
The pull request you sent on Fri, 27 Sep 2019 09:15:27 +0200:
> git://www.linux-watchdog.org/linux-watchdog.git tags/linux-watchdog-5.4-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/7bccb9f10c8f36ee791769b531ed4d28f6379aae
Thank you!
--
Deet-doot-dot, I am a bo
The pull request you sent on Thu, 26 Sep 2019 13:35:22 -0400:
> git://github.com/jonmason/ntb tags/ntb-5.4
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/0cd81d77d0569f1dc1e39abeea93c6184e9b5b54
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/u
On Tue, 24 Sep 2019 11:44:11 -0500, Benoit Parrot wrote:
> Add powerdown-gpios and reset-gpios to the list of optional properties
> for the OV2659 camera sensor.
>
> Signed-off-by: Benoit Parrot
> ---
> Documentation/devicetree/bindings/media/i2c/ov2659.txt | 9 +
> 1 file changed, 9 ins
This patchs series add support of New Amlogic temperature sensor and minimal
thermal zone for SEI510 and ODROID-N2 boards.
First implementation was doing on IIO[1] but after comments i move on thermal
framework.
Formulas and calibration values come from amlogic.
Changes since v5:
- fix patch 5
Add missing #colling-cells field for G12A SoC
Add cooling-map for passive and hot trip point
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La Roque
---
arch/arm64/boot/dts/amlogic/meson-g12a.dtsi | 24 +
1 file changed, 24 insertions(+)
diff
Add minimal thermal zone for two temperature sensor
One is located close to the DDR and the other one is
located close to the PLLs (between the CPU and GPU)
Acked-by: Martin Blumenstingl
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La Roque
---
.../boot/dts/aml
Add myself as maintainer for Amlogic Thermal driver.
Reviewed-by: Neil Armstrong
Signed-off-by: Guillaume La Roque
---
MAINTAINERS | 9 +
1 file changed, 9 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 390c3194ee93..bdc30d740342 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@
On Thu, Sep 26, 2019 at 6:14 PM Shuah Khan wrote:
>
> make TARGETS=bpf kselftest fails with:
>
> Makefile:127: tools/build/Makefile.include: No such file or directory
>
> When the bpf tool make is invoked from tools Makefile, srctree is
> cleared and the current logic check for srctree equals to e
Add missing #colling-cells field for G12B SoC
Add cooling-map for passive and hot trip point
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La Roque
---
arch/arm64/boot/dts/amlogic/meson-g12b.dtsi | 29 +
1 file changed, 29 insertions(+)
diff
Add cpu and ddr temperature sensors for G12 Socs
Reviewed-by: Martin Blumenstingl
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La Roque
---
.../boot/dts/amlogic/meson-g12-common.dtsi| 20 +++
1 file changed, 20 insertions(+)
diff --git a/ar
Amlogic G12A and G12B SoCs integrate two thermal sensors
with the same design. One is located close to the DDR controller
and the other one is located close to the PLLs (between the CPU and GPU).
The calibration data for each of the thermal sensors instance is stored
in a different location within
Adding the devicetree binding documentation for the Amlogic temperature
sensor found in the Amlogic Meson G12A and G12B SoCs.
Reviewed-by: Rob Herring
Tested-by: Christian Hewitt
Tested-by: Kevin Hilman
Signed-off-by: Guillaume La Roque
---
.../bindings/thermal/amlogic,thermal.yaml | 54 +
The initial registers sequence is only loaded at probe
time. Afterward only the resolution and format specific
register are modified. Care must be taken to make sure
registers modified by one resolution setting are reverted
back when another resolution is programmed.
This was not done properly for
Several of include files listed are not explicitly needed.
If they are need then they are implicitly included.
Reduce the list of includes to an easier to manage list.
Signed-off-by: Benoit Parrot
---
drivers/media/i2c/ov2659.c | 14 --
1 file changed, 14 deletions(-)
diff --git a/
This patch series is a collection of patches we have been carrying for a
while.
It includes a few sensor register fixes which would cause visual
artifacts at lower resolution and also at 720p.
Also on some board the 'powerdown' and /or 'reset' pins are not tied so
we need to add support for optio
Add powerdown-gpios and reset-gpios to the list of optional properties
for the OV2659 camera sensor.
Signed-off-by: Benoit Parrot
---
Documentation/devicetree/bindings/media/i2c/ov2659.txt | 9 +
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/media/i2c/ov
In ov2659_s_stream() return value for invoked function should be checked
and propagated.
Signed-off-by: Benoit Parrot
---
drivers/media/i2c/ov2659.c | 11 +++
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/drivers/media/i2c/ov2659.c b/drivers/media/i2c/ov2659.c
index f7732
Based on recently found sensor configuration examples, it was
discovered that when scaling and binning are used for the lower
resolutions (i.e. 640x480, 320x240) the read offset has to be
increased otherwise the image appears to be wrapped around.
Signed-off-by: Benoit Parrot
Signed-off-by: Jyri
Make sure that if the expected sensor device id register
is not recognized properly the failure is propagated
up so devices are not left partially initialized.
Signed-off-by: Benoit Parrot
Signed-off-by: Jyri Sarha
---
drivers/media/i2c/ov2659.c | 5 +++--
1 file changed, 3 insertions(+), 2 del
Switch to SPDX licensing and drop the redundant GPL text.
Signed-off-by: Benoit Parrot
---
drivers/media/i2c/ov2659.c | 14 +-
1 file changed, 1 insertion(+), 13 deletions(-)
diff --git a/drivers/media/i2c/ov2659.c b/drivers/media/i2c/ov2659.c
index 720310e0725d..e6da23d3a555 100644
On some board it is possible that the sensor 'powerdown' and or 'reset'
pin might be controlled by gpio instead of being tied.
To implement we add pm_runtime support which will handle the power
up/down sequence when it is available otherwise the sensor will be
powered on at module insertion/probe
Quoting Baolin Wang (2019-09-26 20:50:53)
> The syscon_regmap_lookup_by_phandle() will never return NULL, thus use
> IS_ERR() to validate the return value instead of IS_ERR_OR_NULL().
>
> Signed-off-by: Baolin Wang
> ---
> drivers/clk/sprd/common.c |2 +-
> 1 file changed, 1 insertion(+), 1
On Mon, 23 Sep 2019 at 23:39, Michael K. Johnson wrote:
>
> On Wed, Sep 18, 2019 at 02:07:51PM +0300, Adrian Hunter wrote:
> > On 18/09/19 1:47 PM, Michael K. Johnson wrote:
> > > I see that the first four patches made it into Linus's kernel
> > > yesterday. Is there any chance of this final patch
Hello RT Folks!
I'm pleased to announce the 4.14.146-rt67 stable release.
This release is just an update to the new stable 4.14.146
version and no RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt
There are a few manually-calculated variable-length struct allocations
left, this converts them to use struct_size.
Signed-off-by: Stephen Kitt
---
drivers/clk/at91/sckc.c | 3 +--
drivers/clk/imgtec/clk-boston.c | 3 +--
drivers/clk/ingenic/tcu.c
From: Navid Emamdoost
Date: Thu, 26 Sep 2019 20:51:46 -0500
> In nfp_abm_u32_knode_replace if the allocation for match fails it should
> go to the error handling instead of returning. Updated other gotos to
> have correct errno returned, too.
>
> Signed-off-by: Navid Emamdoost
Applied.
From: Colin King
Date: Fri, 27 Sep 2019 10:40:39 +0100
> From: Colin Ian King
>
> There is a statement that is indented too deeply, remove
> the extraneous tab.
>
> Signed-off-by: Colin Ian King
Applied.
This is net-next material.
On 9/18/19 10:34 AM, Natarajan, Janakarajan wrote:
Modify cpupower to schedule itself on each of the cpus in the system and
then get the APERF/MPERF register values.
This is advantageous because an IPI is not generated when a read_msr() is
executed on the local logical CPU thereby reducing the c
> -Original Message-
> From: Intel-wired-lan [mailto:intel-wired-lan-boun...@osuosl.org] On
> Behalf Of Navid Emamdoost
> Sent: Wednesday, September 25, 2019 8:49 AM
> Cc: net...@vger.kernel.org; k...@umn.edu; linux-kernel@vger.kernel.org;
> emamd...@umn.edu; intel-wired-...@lists.osuosl.or
On 9/27/19 12:44 PM, Song Liu wrote:
On Thu, Sep 26, 2019 at 6:14 PM Shuah Khan wrote:
make TARGETS=bpf kselftest fails with:
Makefile:127: tools/build/Makefile.include: No such file or directory
When the bpf tool make is invoked from tools Makefile, srctree is
cleared and the current logic
Hi Tim,
Sorry for taking to so long to look at this.
On 2019-09-23 15:04:47 -0700, Tim Harvey wrote:
> On Thu, Aug 29, 2019 at 7:29 AM Niklas Söderlund
> wrote:
> >
> > Hi,
> >
> > On 2019-08-29 13:43:49 +0200, Hans Verkuil wrote:
> > > Adding Niklas.
> > >
> > > Niklas, can you take a look at t
Hi Marco,
On Fri, 27 Sep 2019 11:47:21 +0200
Marco Felsch wrote:
> Hi Andreas,
>
> thanks for the patch.
>
thanks for the quick review. Most of your comments are clear.
[...]
> > + wifi_pwrseq: wifi_pwrseq {
> > + compatible = "mmc-pwrseq-simple";
> > + post-power-on-del
Hi Stephen,
On Fri, Sep 27, 2019 at 8:26 PM Stephen Boyd wrote:
> Quoting Geert Uytterhoeven (2019-09-26 06:07:13)
> > On Fri, Sep 20, 2019 at 11:06 PM Stephen Boyd wrote:
> > > Quoting Arnd Bergmann (2019-09-20 12:27:50)
> > > > On Fri, Sep 20, 2019 at 6:45 PM Stephen Boyd wrote:
> > > > > > @
On 9/27/19 10:26 AM, Nathan Chancellor wrote:
When building cpupower with clang, the following warning appears:
utils/idle_monitor/hsw_ext_idle.c:42:16: warning: initializer overrides
prior initialization of this subobject [-Winitializer-overrides]
.desc =
Hi Tim,
On Wed, Sep 25, 2019 at 9:22 PM Tim Harvey wrote:
> Have you looked at this yet? Without this patch the ADV7280A does not
> output proper BT.656. We tested this on a Gateworks Ventana GW5404-G
> which uses the ADV7280A connected to the IMX6 CSI parallel bus. I'm
> hoping to see this get
The pull request you sent on Fri, 27 Sep 2019 18:31:04 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm.git
> tags/pwm/for-5.4-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/e37e3bc7e265d05d00f14079767537699cf6bd46
Thank you!
--
D
On Fri, Sep 27, 2019 at 12:04 PM Niklas Söderlund
wrote:
>
> Hi Tim,
>
> Sorry for taking to so long to look at this.
>
> On 2019-09-23 15:04:47 -0700, Tim Harvey wrote:
> > On Thu, Aug 29, 2019 at 7:29 AM Niklas Söderlund
> > wrote:
> > >
> > > Hi,
> > >
> > > On 2019-08-29 13:43:49 +0200, Hans
On Fri, 2019-09-27 at 11:34 -0700, Linus Torvalds wrote:
> On Fri, Sep 27, 2019 at 6:08 AM Zhang Rui wrote:
> > One thing to mention is that, all the patches have been tested in
> > linux-next for weeks, but there is a conflict detected, because
> > upstream has took commit eaf7b46083a7e34 ("docs:
On Fri, Sep 27, 2019 at 9:14 AM Kaitao Cheng wrote:
>
> There is no need to make the 'node_order' variable static
> since new value always be assigned before use it.
>
> Signed-off-by: Kaitao Cheng
> Signed-off-by: Muchun Song
> ---
> mm/page_alloc.c | 2 +-
> 1 file changed, 1 insertion(+), 1
ZynqMP firmware driver can be used for versal also.
Add versal compatible string to zynqmp firmware driver
doc.
Signed-off-by: Jolly Shah
---
.../bindings/firmware/xilinx/xlnx,zynqmp-firmware.txt| 16 +++-
1 file changed, 15 insertions(+), 1 deletion(-)
diff --git
a/Documentati
Versal is xilinx's next generation soc. This patch adds
driver support required to be compatible with versal device.
Signed-off-by: Jolly Shah
---
drivers/firmware/xilinx/zynqmp.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/drivers/firmware/xilinx/zynqmp.c b/drive
Versal is xilinx's next generation soc. This patch adds
driver support required to be compatible with versal device.
Jolly Shah (2):
dt-bindings: firmware: Add bindings for Versal firmware
drivers: firmware: xilinx: Add support for versal soc
.../bindings/firmware/xilinx/xlnx,zynqmp-firmware
On Fri, Sep 27, 2019 at 12:29 PM Doug Ledford wrote:
>
> Because there are literally thousands of developers working on kernel
> bits here and there, and you're swatting this particular fly one
> developer at a time.
Well, at least these days it's also very clearly spelled out in the
Documentatio
On Fri, Sep 27, 2019 at 4:22 PM Walter Wu wrote:
>
> On Fri, 2019-09-27 at 15:07 +0200, Dmitry Vyukov wrote:
> > On Fri, Sep 27, 2019 at 5:43 AM Walter Wu wrote:
> > >
> > > memmove() and memcpy() have missing underflow issues.
> > > When -7 <= size < 0, then KASAN will miss to catch the underflo
On architectures like s390, arch_free_page() could mark the page unused
(set_page_unused()) and any access later would trigger a kernel panic.
Fix it by moving arch_free_page() after all possible accessing calls.
Hardware name: IBM 2964 N96 400 (z/VM 6.4.0)
Krnl PSW : 0404e0018000 26
On Fri, Sep 27, 2019 at 2:19 PM Greg Kroah-Hartman
wrote:
>
> On Fri, Sep 27, 2019 at 09:04:02AM -0400, Dan Streetman wrote:
> > The dummy vio_bus_device creates the /sys/devices/vio directory, which
> > contains real vio devices under it; since it represents itself as having
> > a bus = &vio_bus_
On Fri, Sep 27, 2019 at 9:30 PM Doug Ledford wrote:
> Because there are literally thousands of developers working on kernel
> bits here and there, and you're swatting this particular fly one
> developer at a time.
I strongly disagree. One of the golden rules of kernel development is,
read what Li
On Fri, 2019-09-27 at 12:41 -0700, Linus Torvalds wrote:
> On Fri, Sep 27, 2019 at 12:29 PM Doug Ledford
> wrote:
> > Because there are literally thousands of developers working on
> > kernel
> > bits here and there, and you're swatting this particular fly one
> > developer at a time.
>
> Well, a
Hi Dave,
On 27/09/2019 17:15, Dave Martin wrote:
> On Fri, Sep 27, 2019 at 11:39:49AM -0400, Masayoshi Mizuma wrote:
>> From: Masayoshi Mizuma
>>
>> The system which has SVE feature crashed because of
>> the memory pointed by task->thread.sve_state was destroyed
>> by someone.
>>
>> That is becau
On Fri, 2019-09-27 at 21:52 +0200, Richard Weinberger wrote:
> On Fri, Sep 27, 2019 at 9:30 PM Doug Ledford
> wrote:
> > Because there are literally thousands of developers working on
> > kernel
> > bits here and there, and you're swatting this particular fly one
> > developer at a time.
>
> I st
Hello.
On 18.09.19 00:47, Navid Emamdoost wrote:
In ca8210_probe the allocated pdata needs to be assigned to
spi_device->dev.platform_data before calling ca8210_get_platform_data.
Othrwise when ca8210_get_platform_data fails pdata cannot be released.
Signed-off-by: Navid Emamdoost
---
driver
On Fri, 2019-09-27 at 14:19 +0200, Sebastian Andrzej Siewior wrote:
> On 2019-09-26 11:52:42 [-0500], Scott Wood wrote:
> > Looks good, thanks!
>
> Thanks, just released.
> Moving forward. It would be nice to have some DL-dev feedback on DL
> patch. For the remaining once, could please throw Steve
Please pull nfsd changes from:
git://linux-nfs.org/~bfields/linux.git tags/nfsd-5.4
--b.
Highlights:
- add a new knfsd file cache, so that we don't have to open and
close on each (NFSv2/v3) READ or WRITE. This
On Wed, Sep 25, 2019 at 6:45 AM Jian Hu wrote:
>
> Add the documentation to support Amlogic A1 clock driver,
> and add A1 clock controller bindings.
>
> Signed-off-by: Jian Hu
> Signed-off-by: Jianxin Pan
> ---
> .../devicetree/bindings/clock/amlogic,a1-clkc.yaml | 65 +
> include/
The pull request you sent on Fri, 27 Sep 2019 11:25:13 -0700 (PDT):
> git://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
> tags/riscv/for-v5.4-rc1-b
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/568d850e3c6015acec8f854f5be97766497a676b
Thank you!
--
Dee
The pull request you sent on Fri, 27 Sep 2019 14:08:02 +0200:
> https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/8bbe0dec38e147a50e9dd5f585295f7e68e0f2d0
Thank you!
--
Deet-doot-dot, I am a bot.
https://ko
The pull request you sent on Fri, 27 Sep 2019 16:50:52 +0800:
> (unable to parse the git remote)
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/70570a6418be2bd28be30fda700e57a81df7282b
Thank you!
--
Deet-doot-dot, I am a bot.
https://korg.wiki.kernel.org/userdoc/prt
On 9/27/19 4:15 AM, Paolo Bonzini wrote:
> Shadow paging is fundamentally incompatible with the page-modification
> log, because the GPAs in the log come from the wrong memory map.
> In particular, for the EPT page-modification log, the GPAs in the log come
> from L2 rather than L1. (If there was
On Thu, Jul 18, 2019 at 3:26 PM Nick Desaulniers
wrote:
>
> On Tue, Jul 16, 2019 at 4:17 PM Josh Poimboeuf wrote:
> >
> > > > > 2) There's also an issue in clang where a large switch table had a
> > > > > bunch
> > > > >of unused (bad) entries. It's not a code correctness issue, but
> > > >
On Thu, Sep 26, 2019 at 02:19:52PM +0300, Peter Ujfalusi wrote:
> Make the dma-channel-mask to be usable for controllers with more than 32
> channels.
>
> Signed-off-by: Peter Ujfalusi
> ---
> Documentation/devicetree/bindings/dma/dma-common.yaml | 9 -
> 1 file changed, 8 insertions(+),
Hi Benoit,
thank you for the patch.
On Fri, Sep 27, 2019 at 7:46 PM Benoit Parrot wrote:
>
> In ov2659_s_stream() return value for invoked function should be checked
> and propagated.
>
> Signed-off-by: Benoit Parrot
> ---
> drivers/media/i2c/ov2659.c | 11 +++
> 1 file changed, 7 inse
On Fri, Sep 27, 2019 at 7:47 PM Benoit Parrot wrote:
>
> Based on recently found sensor configuration examples, it was
> discovered that when scaling and binning are used for the lower
> resolutions (i.e. 640x480, 320x240) the read offset has to be
> increased otherwise the image appears to be wra
On Fri, Sep 27, 2019 at 7:47 PM Benoit Parrot wrote:
>
> Make sure that if the expected sensor device id register
> is not recognized properly the failure is propagated
> up so devices are not left partially initialized.
>
> Signed-off-by: Benoit Parrot
> Signed-off-by: Jyri Sarha
> ---
> drive
On Fri, Sep 27, 2019 at 7:47 PM Benoit Parrot wrote:
>
> Several of include files listed are not explicitly needed.
> If they are need then they are implicitly included.
>
> Reduce the list of includes to an easier to manage list.
>
> Signed-off-by: Benoit Parrot
> ---
> drivers/media/i2c/ov2659
On Fri, Sep 27, 2019 at 7:47 PM Benoit Parrot wrote:
>
> The initial registers sequence is only loaded at probe
> time. Afterward only the resolution and format specific
> register are modified. Care must be taken to make sure
> registers modified by one resolution setting are reverted
> back when
On Fri, Sep 27, 2019 at 7:47 PM Benoit Parrot wrote:
>
> Add powerdown-gpios and reset-gpios to the list of optional properties
> for the OV2659 camera sensor.
>
> Signed-off-by: Benoit Parrot
> ---
> Documentation/devicetree/bindings/media/i2c/ov2659.txt | 9 +
> 1 file changed, 9 inser
Thiago Jung Bauermann writes:
> Thiago Jung Bauermann writes:
>
>> The ultravisor will do an integrity check of the kernel image but we
>> relocated it so the check will fail. Restore the original image by
>> relocating it back to the kernel virtual base address.
>>
>> This works because durin
On Fri, Sep 27, 2019 at 7:39 PM Pierre-Louis Bossart
wrote:
> > The problem with solution #1 is freeing orphaned pointer. It will work,
> > but it's simple is not okay from object life time prospective.
>
> ?? I don't get your point at all Andy.
> Two allocations happens in a loop and if the secon
On Fri, Sep 27, 2019 at 5:49 AM Peter Zijlstra wrote:
>
> On Fri, Sep 27, 2019 at 11:51:07AM +0200, Andrea Parri wrote:
>
> > For the record, the LKMM doesn't currently model "order" derived from
> > control dependencies to a _plain_ access (even if the plain access is
> > a write): in particular,
Hi Tim,
On 2019-09-27 12:26:40 -0700, Tim Harvey wrote:
> On Fri, Sep 27, 2019 at 12:04 PM Niklas Söderlund
> wrote:
> >
> > Hi Tim,
> >
> > Sorry for taking to so long to look at this.
> >
> > On 2019-09-23 15:04:47 -0700, Tim Harvey wrote:
> > > On Thu, Aug 29, 2019 at 7:29 AM Niklas Söderlund
On Thu, Sep 26, 2019 at 02:19:53PM +0300, Peter Ujfalusi wrote:
> Similarly to paRAM slots, channels can be used by other cores.
>
> The common dma-channel-mask property can be used for specifying the
> available channels.
>
> Signed-off-by: Peter Ujfalusi
> ---
> Documentation/devicetree/bindi
Hello,
syzbot found the following crash on:
HEAD commit:2994c077 usb-fuzzer: main usb gadget fuzzer driver
git tree: https://github.com/google/kasan.git usb-fuzzer
console output: https://syzkaller.appspot.com/x/log.txt?x=171c4be360
kernel config: https://syzkaller.appspot.com/x/.
On Fri, 27 Sep 2019 15:47:03 -0400 Qian Cai wrote:
> On architectures like s390, arch_free_page() could mark the page unused
> (set_page_unused()) and any access later would trigger a kernel panic.
> Fix it by moving arch_free_page() after all possible accessing calls.
>
> Hardware name: IBM 29
1 - 100 of 646 matches
Mail list logo
