Syzbot reported the following [1]:
BUG: kernel NULL pointer dereference, address: 0008
#PF: supervisor read access in kernel mode
#PF: error_code(0x) - not-present page
PGD 2d993067 P4D 2d993067 PUD 19a3c067 PMD 0
Oops: [#1] PREEMPT SMP KASAN
CPU: 1 PID: 3852 Comm:
On Mon, Dec 28, 2020 at 8:30 AM Sedat Dilek wrote:
>
> [ Please CC me I am not subscribed to LKML and linux-kbuild ML ]
>
> Hi Linus, Hi Mashiro,
>
> thanks for the Linux v5.11-rc1 release.
>
> With a new release I always do my first builds with my distro's
> default compiler and linker (GCC
Similar to commit<789d4c300e10>("drm/msm: don't deref error pointer in the
msm_fbdev_create error path"),
the error pointer returned by omap_framebuffer_init() gets passed to
drm_framebuffer_remove.
The latter handles only Null pointers,thus a nasty crash will occur.
Drop the unnecessary checks
On Thu, Dec 24, 2020 at 3:51 PM Krzysztof Kozlowski wrote:
>
> On Thu, 24 Dec 2020 at 11:08, Jagan Teki wrote:
> >
> > On Thu, Dec 24, 2020 at 2:48 PM Krzysztof Kozlowski wrote:
> > >
> > > On Wed, 23 Dec 2020 at 13:07, Jagan Teki
> > > wrote:
> > > >
> > > > On Wed, Dec 23, 2020 at 5:29 PM
On Mon, Dec 28, 2020 at 09:56:15AM +0800, yukuai (C) wrote:
> Hi,
>
> On 2020/12/27 19:58, Ming Lei wrote:
> > Hi Yu Kuai,
> >
> > On Sat, Dec 26, 2020 at 06:28:06PM +0800, Yu Kuai wrote:
> > > When sharing a tag set, if most disks are issuing small amount of IO, and
> > > only a few is issuing
On Wed, Dec 16, 2020 at 06:05:55PM +0900, Namhyung Kim wrote:
SNIP
> + *p++ = '\0';
>
> - while (token != NULL) {
> - if (subsys && !strcmp(token, subsys)) {
> - /* found */
> -
With C=1:
drivers/soc/renesas/rmobile-sysc.c:330:33: sparse: sparse: incorrect type
in argument 1 (different address spaces) @@ expected void *addr @@ got
void [noderef] __iomem *[assigned] base @@
drivers/soc/renesas/rmobile-sysc.c:330:33: sparse: expected void *addr
On Mon, 28 Dec 2020 at 09:21, Jagan Teki wrote:
> > > #include "imx8mm.dtsi"
> > > #include "imx8mm-beacon-som.dtsi"
> > > #include "imx8mm-beacon-baseboard.dtsi"
> > >
> > > (SoC dtsi, SoM dtsi, Carrier board dtsi)
> > >
> > > > design which makes any sense. We do not create empty DTS files
The following series are intended to prepare the mtk-mmsys driver to
allow different DDP (Data Display Path) function call per SoC.
base change:
https://patchwork.kernel.org/project/linux-mediatek/patch/20201006193320.405529-4-enric.balle...@collabora.com/
Change since v2:
- fix review issue in
This patch add component OVL_2L2
Signed-off-by: Yongqiang Niu
---
include/linux/soc/mediatek/mtk-mmsys.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/soc/mediatek/mtk-mmsys.h
b/include/linux/soc/mediatek/mtk-mmsys.h
index 4b6c514..42476c2 100644
---
the mmsys will more and more complicated after support
more and more SoCs, add an independent folder will be
more clear
Signed-off-by: Yongqiang Niu
---
drivers/soc/mediatek/Makefile | 2 +-
drivers/soc/mediatek/mmsys/Makefile| 2 +
drivers/soc/mediatek/mmsys/mtk-mmsys.c | 380
This patch add component POSTMASK
Signed-off-by: Yongqiang Niu
---
include/linux/soc/mediatek/mtk-mmsys.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/soc/mediatek/mtk-mmsys.h
b/include/linux/soc/mediatek/mtk-mmsys.h
index 42476c2..09ee424 100644
---
Actually, setting the registers for routing, use multiple 'if-else' for
different
routes, but this code would be more and more complicated while we
support more and more SoCs. Change that and use a function call per SoC so the
code will be more portable and clear.
Signed-off-by: Yongqiang Niu
Use function call for setting mmsys ovl mout register
Signed-off-by: Yongqiang Niu
---
drivers/soc/mediatek/mmsys/mtk-mmsys.c | 20
include/linux/soc/mediatek/mtk-mmsys.h | 3 +++
2 files changed, 23 insertions(+)
diff --git a/drivers/soc/mediatek/mmsys/mtk-mmsys.c
add mt8192 mmsys support
Signed-off-by: Yongqiang Niu
---
drivers/soc/mediatek/mmsys/Makefile | 1 +
drivers/soc/mediatek/mmsys/mt8192-mmsys.c | 119 ++
drivers/soc/mediatek/mmsys/mtk-mmsys.c| 9 +++
include/linux/soc/mediatek/mtk-mmsys.h| 1 +
4
This patch add component RDMA4
Signed-off-by: Yongqiang Niu
---
include/linux/soc/mediatek/mtk-mmsys.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/include/linux/soc/mediatek/mtk-mmsys.h
b/include/linux/soc/mediatek/mtk-mmsys.h
index 09ee424..aa4f60e 100644
---
add mt8183 function call for setting the routing registers
Signed-off-by: Yongqiang Niu
---
drivers/soc/mediatek/mmsys/Makefile | 1 +
drivers/soc/mediatek/mmsys/mt8183-mmsys.c | 90 +++
drivers/soc/mediatek/mmsys/mtk-mmsys.c| 1 +
Am 28.12.20 um 03:59 schrieb Qing Zhang:
> The SPI controller has the following characteristics:
>
> - Full-duplex synchronous serial data transmission
> - Support up to 4 variable length byte transmission
> - Main mode support
> - Mode failure generates an error flag and issues an interrupt
On Mon, Dec 28, 2020 at 2:04 PM Krzysztof Kozlowski wrote:
>
> On Mon, 28 Dec 2020 at 09:21, Jagan Teki wrote:
> > > > #include "imx8mm.dtsi"
> > > > #include "imx8mm-beacon-som.dtsi"
> > > > #include "imx8mm-beacon-baseboard.dtsi"
> > > >
> > > > (SoC dtsi, SoM dtsi, Carrier board dtsi)
> > > >
mlx5e_create_ttc_table_groups() frees ft->g on failure of
kvzalloc(), but such failure will be caught by its caller
in mlx5e_create_ttc_table() and ft->g will be freed again
in mlx5e_destroy_flow_table(). The same issue also occurs
in mlx5e_create_ttc_table_groups(). Set ft->g to NULL after
Hi
On 2020/12/28 16:28, Ming Lei wrote:
Another candidate solution may be to always return true from hctx_may_queue()
for this kind of queue because queue_depth has provided fair allocation for
each LUN, and looks not necessary to do that again.
If always return true from hctx_may_queue() in
Some SoCs, eg. mt8183, are using a pinconfig operation bias_set_combo.
The fallback path in mtk_pinconf_adv_pull_set() should also try this
operation.
Fixes: cafe19db7751 ("pinctrl: mediatek: Backward compatible to previous
Mediatek's bias-pull usage")
Signed-off-by: Hsin-Yi Wang
---
Below is the list of build error/warning regressions/improvements in
v5.11-rc1[1] compared to v5.10[2].
Summarized:
- build errors: +1/-3
- build warnings: +12/-132
Happy fixing! ;-)
Thanks to the linux-next team for providing the build service.
[1]
Hi,
I love your patch! Perhaps something to improve:
[auto build test WARNING on mkp-scsi/for-next]
[also build test WARNING on scsi/for-next v5.11-rc1 next-20201223]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as
On Mon, Dec 28, 2020 at 10:38 AM Geert Uytterhoeven
wrote:
> Below is the list of build error/warning regressions/improvements in
> v5.11-rc1[1] compared to v5.10[2].
>
> Summarized:
> - build errors: +1/-3
> - build warnings: +12/-132
>
> Happy fixing! ;-)
>
> Thanks to the linux-next team
From: Bongsu Jeon
A NCI virtual device can be made to simulate a NCI device in user space.
Using the virtual NCI device, The NCI module and application can be
validated. This driver supports to communicate between the virtual NCI
device and NCI module.
Signed-off-by: Bongsu Jeon
---
Hi!
> > > > > > https://www.kernel.org/pub/linux/kernel/v5.x/stable-review/patch-5.10.3-rc1.gz
> > > > > > or in the git tree and branch at:
> > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/stable/
> > > > > > linu
> > > > > > x-
> > > > > > stable-rc.git linux-5.10.y
> > > > > >
Similar to commit<1bd54d851f50>(("kgdboc: Passing ekgdboc to command line
causes panic"),
kgdbts_option_setup does not check input argument before passing it to strlen.
The argument would be a NULL pointer.
Signed-off-by: Defang Bo
---
drivers/misc/kgdbts.c | 5 +
1 file changed, 5
ChangeList:
RFC v1:
1. only upstream modeset and atomic at first commit.
2. remove some unused code;
3. use alpha and blend_mode properties;
3. add yaml support;
4. remove auto-adaptive panel driver;
5. bugfix
RFC v2:
1. add sprd crtc and plane module for KMS, preparing for multi crtc
2. remove
Adds drm support for the Unisoc's display subsystem.
This is drm kms driver, this driver provides support for the
application framework in Android, Yocto and more.
Application framework can access Unisoc's display internel
peripherals through libdrm or libkms, it's test ok by modetest
(DRM/KMS
From: Kevin Tang
DPU (Display Processor Unit) is the Display Controller for the Unisoc SoCs
which transfers the image data from a video memory buffer to an internal
LCD interface.
Cc: Orson Zhai
Cc: Chunyan Zhang
Signed-off-by: Kevin Tang
Reviewed-by: Rob Herring
---
Adds DPU(Display Processor Unit) support for the Unisoc's display subsystem.
It's support multi planes, scaler, rotation, PQ(Picture Quality) and more.
Cc: Orson Zhai
Cc: Chunyan Zhang
Signed-off-by: Kevin Tang
v2:
- Use drm_xxx to replace all DRM_XXX.
- Use kzalloc to replace
From: Kevin Tang
Adds MIPI DSI Controller
support for Unisoc's display subsystem.
Cc: Orson Zhai
Cc: Chunyan Zhang
Signed-off-by: Kevin Tang
Reviewed-by: Rob Herring
---
.../display/sprd/sprd,sharkl3-dsi-host.yaml| 107 +
1 file changed, 107 insertions(+)
Adds dsi host controller support for the Unisoc's display subsystem.
Adds dsi phy support for the Unisoc's display subsystem.
Only MIPI DSI Displays supported, DP/TV/HMDI will be support
in the feature.
v1:
- Remove dphy and dsi graph binding, merge the dphy driver into the dsi.
v2:
- Use
From: Kevin Tang
The Unisoc DRM master device is a virtual device needed to list all
DPU devices or other display interface nodes that comprise the
graphics subsystem
Unisoc's display pipeline have several components as below
description, multi display controllers and corresponding physical
Fri, Dec 18, 2020 at 08:30:33PM CET, ja...@redhat.com wrote:
>This comes from an end-user request, where they're running multiple VMs on
>hosts with bonded interfaces connected to some interest switch topologies,
>where 802.3ad isn't an option. They're currently running a proprietary
>solution
On Thu, Dec 24, 2020 at 06:36:10PM +, David Laight wrote:
> From: Daniel Scally
> > Sent: 24 December 2020 14:14
> ...
> > >> The array will be unwound in reverse order (i.e. last entry first). If
> > >> any member of the array is a child of another member then the child must
> > > children ?
On Mon, Dec 28, 2020 at 1:17 AM Hillf Danton wrote:
>
> On Sun, 27 Dec 2020 18:53:39 -0800 Xie He wrote:
> > ppp_cp_event is called directly or indirectly by ppp_rx with "ppp->lock"
> > held. It may call mod_timer to add a new timer. However, at the same time
> > ppp_timer may be already running
On Sun, Dec 27, 2020 at 01:36:13PM -0800, Andy Lutomirski wrote:
> On Sun, Dec 27, 2020 at 12:18 PM Mathieu Desnoyers
> wrote:
> >
> > - On Dec 27, 2020, at 1:28 PM, Andy Lutomirski l...@kernel.org wrote:
> >
>
> > >
> > > I admit that I'm rather surprised that the code worked at all on
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 5c8fe583cce542aa0b84adc939ce85293de36e5e
commit: c637693b20da8706b7f48d96882c9c80ae935151 ubsan: remove UBSAN_MISC in
favor of individual options
date: 12 days ago
config: mips-randconfig-r005-20201227
On 12/23/20 7:48 AM, Michael Kao wrote:
From: brian-sy yang
Slab OOB issue is scanned by KASAN in cpu_power_to_freq().
If power is limited below the power of OPP0 in EM table,
it will cause slab out-of-bound issue with negative array
index.
Return the lowest frequency if limited power
On Fri, Dec 25, 2020 at 11:33:21AM +, Timon Baetz wrote:
> On Thu, 24 Dec 2020 15:00:38 +0100, Krzysztof Kozlowski wrote:
> > On Thu, Dec 24, 2020 at 02:37:06PM +0100, Krzysztof Kozlowski wrote:
> > > On Thu, Dec 24, 2020 at 01:13:02PM +, Timon Baetz wrote:
> > > > On Thu, 24 Dec 2020
- Enable modular build of netfilter nf_tables netdev REJECT support,
- Enable modular build of the resource and cmdline API unit tests.
Signed-off-by: Geert Uytterhoeven
---
To be queued for v5.12.
arch/m68k/configs/amiga_defconfig| 3 +++
arch/m68k/configs/apollo_defconfig | 3 +++
On Sat, Dec 05, 2020 at 11:24:14AM +0530, Manivannan Sadhasivam wrote:
> On Mon, Nov 30, 2020 at 01:54:45AM +0100, Andreas Färber wrote:
> > On 29.11.20 20:48, Cristian Ciocaltea wrote:
> > > On Sat, Nov 28, 2020 at 01:13:50PM +0530, Manivannan Sadhasivam wrote:
> > >> On Fri, Nov 20, 2020 at
On Mon, Dec 28, 2020 at 12:43:07PM +0200, Cristian Ciocaltea wrote:
> On Sat, Dec 05, 2020 at 11:24:14AM +0530, Manivannan Sadhasivam wrote:
> > On Mon, Nov 30, 2020 at 01:54:45AM +0100, Andreas Färber wrote:
> > > On 29.11.20 20:48, Cristian Ciocaltea wrote:
> > > > On Sat, Nov 28, 2020 at
[Why]
Similar to commit <298360af3>("drivers/gpu/drm/ast: Fix infinite loop if read
fails"),
ast_init_dram_reg() configures a window in order to access BMC memory.
A BMC register can be configured to disallow this, and if so, causes
an infinite loop in the ast driver which renders the system
ufshcd_hba_exit() is always called after ufshcd_exit_clk_scaling() and
ufshcd_exit_clk_gating(), so move ufshcd_exit_clk_scaling/gating() to
ufshcd_hba_exit(). Meanwhile, add dedicated funcs to init and remove
sysfs nodes of clock scaling/gating to make the code more readable.
Overall
Commit 73cc291c27024 ("Make sure clk scaling happens only when HBA is
runtime ACTIVE") is no longer needed since commit f7a42540928a8 ("scsi:
ufs: Protect some contexts from unexpected clock scaling") is a more
mature fix to protect UFS LLD stability from clock scaling invoked through
sysfs nodes
In contexts like suspend, shutdown and error handling, we need to suspend
devfreq to make sure these contexts won't be disturbed by clock scaling.
However, suspending devfreq is not enough since users can still trigger a
clock scaling by manipulating the sysfs node clkscale_enable and devfreq
On Mon, Dec 28, 2020 at 04:48:40PM +0800, Dinghao Liu wrote:
> mlx5e_create_ttc_table_groups() frees ft->g on failure of
> kvzalloc(), but such failure will be caught by its caller
> in mlx5e_create_ttc_table() and ft->g will be freed again
> in mlx5e_destroy_flow_table(). The same issue also
date: 3 weeks ago
config: mips-randconfig-r012-20201228 (attached as .config)
compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
cee1e7d14f4628d6174b33640d502bff3b54ae45)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin
This is the result of multiple patches taken from the BSP, combined,
rebased, and properly sorted. SCIF0 gets DMA properties, other SCIFs are
entirely new.
Signed-off-by: Linh Phung
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 50 +++
1 file
From: Linh Phung
Define the generic parts of the HSCIF[0-3] device nodes.
Signed-off-by: Linh Phung
[wsa: double checked & rebased]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 64 +++
1 file changed, 64 insertions(+)
diff --git
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
b/drivers/clk/renesas/r8a779a0-cpg-mssr.c
index d85c31a465e1..f518c9e12a49 100644
--- a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
Mainly for testing the HSCIF0 node. We could make this switch permanent,
but we never did for any other SoC. So, I think this is not to be
applied.
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts | 14 +-
1 file changed, 9 insertions(+), 5
SCIF0 already worked because of firmware settings, but let's have a
proper node for it. Also add HSCIF0 because the last patch shows that it
also works. Because these blocks work in general, let's add the other
instances to the DTSI, too.
These additions make me a bit wonder about the 'reg'-based
Signed-off-by: Wolfram Sang
---
Documentation/devicetree/bindings/serial/renesas,hscif.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/serial/renesas,hscif.yaml
b/Documentation/devicetree/bindings/serial/renesas,hscif.yaml
index
SCIF0 has been enabled by the firmware, so it worked already. Still, add
the proper nodes to make it work in any case.
Signed-off-by: Wolfram Sang
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 25 +++
1 file changed, 25 insertions(+)
diff --git
On Thu, Dec 17, 2020 at 05:03:57PM +0100, SeongJae Park wrote:
> From: SeongJae Park
>
> Changes from v2
> (https://lore.kernel.org/stable/20201217130501.12702-1-sjp...@amazon.com/)
> - Move 'nr_pending' increase from 5th patch to 4th patch
>
> Changes from v1
>
This allows the MAX8997 charger to set the current limit depending on
the detected extcon charger type.
Signed-off-by: Timon Baetz
---
drivers/extcon/extcon-max8997.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/extcon/extcon-max8997.c b/drivers/extcon/extcon-max8997.c
index
Add maxim,max8997-battery and maxim,max8997-muic optional nodes.
Signed-off-by: Timon Baetz
Acked-by: Krzysztof Kozlowski
---
.../bindings/regulator/max8997-regulator.txt | 12
1 file changed, 12 insertions(+)
diff --git
Register for extcon notification and set charging current depending on
the detected cable type. Current values are taken from vendor kernel,
where most charger types end up setting 650mA [0].
Also enable and disable the CHARGER regulator based on extcon events.
[0]
muic node is only used for extcon consumers.
charger node is used to point to muic and regulator.
Signed-off-by: Timon Baetz
---
arch/arm/boot/dts/exynos4210-i9100.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4210-i9100.dts
muic node is only used for extcon consumers.
charger node is used to point to muic.
Note: charging control is not working as we don't have a charger-supply.
Signed-off-by: Timon Baetz
---
arch/arm/boot/dts/exynos4210-trats.dts | 9 +
1 file changed, 9 insertions(+)
diff --git
Value taken from Galaxy S2 Epic 4G Touch SPH-D710 Android vendor
kernel [0] which always sets 200mA.
Also rearrange regulators based on definition in max8997.h.
[0]
Set CHARGER current and CHARGER_CV voltage according to Galaxy S2 Epic
4G Touch SPH-D710 Android vendor sources [0,1].
Remove regulator-always-on. The regulator can be enabled and disabled
based on extcon events.
[0]
Both nodes are disabled as there is no battery and pins are not
connected.
Signed-off-by: Timon Baetz
---
arch/arm/boot/dts/exynos4210-origen.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/exynos4210-origen.dts
b/arch/arm/boot/dts/exynos4210-origen.dts
On Mon, Dec 21, 2020 at 04:00:28PM +0900, Namhyung Kim wrote:
> To synthesize information to resolve sample IPs, it needs to scan task
> and mmap info from the /proc filesystem. For each process, it
> opens (and reads) status and maps file respectively. But as kernel
> threads don't have memory
Not used anymore after refactoring:
arch/arm64/kernel/smp.c: In function ‘arch_show_interrupts’:
arch/arm64/kernel/smp.c:810:16: warning: unused variable ‘irq’
[-Wunused-variable]
810 | unsigned int irq = irq_desc_get_irq(ipi_desc[i]);
Fixes: 5089bc51f81f ("arm64/smp: Use
On Sat, Dec 26, 2020 at 12:15:20PM +0530, Syed Nayyar Waris wrote:
> Add extra check to see if sum of widths does not exceed 64. If it
> exceeds then return -EINVAL alongwith appropriate error message.
>
> Cc: Michal Simek
> Signed-off-by: Syed Nayyar Waris
Hello Syed,
This change is
On Sat, Dec 26, 2020 at 10:03 PM Vitaly Wool wrote:
>
> Sometimes, especially in a production system we may not want to
> use a "smart bootloader" like u-boot to load kernel, ramdisk and
> device tree from a filesystem on eMMC, but rather load the kernel
> from a NAND partition and just run it as
FYI, there is a regression in iwlwifi driver caused by commit
ba8f6f4ae254 ("iwlwifi: dbg: add dumping special device memory")
reported at
https://bugzilla.kernel.org/show_bug.cgi?id=210733
https://bugzilla.suse.com/show_bug.cgi?id=1180344
The problem seems to be an attempt to write
Not used anymore after refactoring:
arch/arm/kernel/smp.c: In function ‘show_ipi_list’:
arch/arm/kernel/smp.c:543:16: warning: variable ‘irq’ set but not used
[-Wunused-but-set-variable]
543 | unsigned int irq;
Fixes: 88c637748e31 ("ARM: smp: Use irq_desc_kstat_cpu() in show_ipi_list()")
On Fri, 2020-12-25 at 19:22 +, Marc Zyngier wrote:
> Hi Jianjun,
>
> On Fri, 25 Dec 2020 10:03:07 +,
> Jianjun Wang wrote:
> >
> > MediaTek's PCIe host controller has three generation HWs, the new
> > generation HW is an individual bridge, it supports Gen3 speed and
> > up to 256 MSI
Users can initiate resets to specific SCSI device/target/host through
IOCTL. When this happens, the SCSI cmd passed to eh_device/target/host
_reset_handler() callbacks is initialized with a request whose tag is -1.
So, in this case, it is not right for eh_device_reset_handler() callback
to count
On Sun, Dec 27, 2020 at 11:03:06PM +0100, Arnd Bergmann wrote:
> On Sat, Dec 26, 2020 at 7:42 AM Syed Nayyar Waris
> wrote:
> >
> > This macro iterates for each group of bits (clump) with set bits,
> > within a bitmap memory region. For each iteration, "start" is set to
> > the bit offset of the
Hi Pali and Miquel,
On Wed, 23 Dec 2020 17:24:03 +0100
Pali Rohár wrote:
> int xhci_mvebu_a3700_init_quirk(struct usb_hcd *hcd)
> {
> struct xhci_hcd *xhci = hcd_to_xhci(hcd);
> + struct device *dev = hcd->self.controller;
> + struct phy *phy;
> + int ret;
>
> /*
fwnode_handle_put() should be called after the fwnode
is last accessed. Fix it.
Fixes: b98158d837ef ("media: v4l2-async: Accept endpoints and devices for
fwnode matching")
Signed-off-by: Ezequiel Garcia
---
drivers/media/v4l2-core/v4l2-async.c | 6 --
1 file changed, 4 insertions(+), 2
9ce85293de36e5e
> commit: 518b466a21ad7fa1e338fa4ed9d180ef439d3bc0 pinctrl: ralink: add a
> pinctrl driver for the rt2880 family
> date: 3 weeks ago
> config: mips-randconfig-r012-20201228 (attached as .config)
> compiler: clang version 12.0.0 (https://github.com/llvm/llvm-project
> cee1e7d14f4
On Sun, Dec 27, 2020 at 10:12:19PM +0100, Hans de Goede wrote:
> The Linux Arizona driver uses the MFD framework to create several
> sub-devices for the Arizona codec and then uses a driver per function.
>
> The jack-detect support for the Arizona codec is handled by the
> extcon-arizona driver.
Hi Adam,
On Thu, Dec 24, 2020 at 2:53 PM Adam Ford wrote:
> On Tue, Dec 22, 2020 at 2:03 AM Geert Uytterhoeven
> wrote:
> > On Tue, Dec 22, 2020 at 2:39 AM Adam Ford wrote:
> > > On Fri, Dec 18, 2020 at 7:16 AM Geert Uytterhoeven
> > > wrote:
> > > > On Thu, Dec 17, 2020 at 12:52 PM Adam
On Mon, Dec 28, 2020 at 12:55 PM Wolfram Sang
wrote:
> Not used anymore after refactoring:
>
> arch/arm64/kernel/smp.c: In function ‘arch_show_interrupts’:
> arch/arm64/kernel/smp.c:810:16: warning: unused variable ‘irq’
> [-Wunused-variable]
> 810 | unsigned int irq =
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 2ca408d9c749c32288bc28725f9f12ba30299e8f
Gitweb:
https://git.kernel.org/tip/2ca408d9c749c32288bc28725f9f12ba30299e8f
Author:Brian Gerst
AuthorDate:Mon, 30 Nov 2020 17:30:59 -05:00
On Sun, Dec 27, 2020 at 11:13:20AM -0500, Gabriel Somlo wrote:
> The 'litex_[set|get]_reg()' methods use the 'reg_size' parameter to
> specify the width of the LiteX CSR (MMIO) register being accessed.
>
> Since 'u64' is the widest data being supported, the value of 'reg_size'
> MUST be between 1
From: Lukas Wunner
[ Upstream commit e13ee6cc4781edaf8c7321bee19217e3702ed481 ]
bcm2835aux_spi_remove() accesses the driver's private data after calling
spi_unregister_master() even though that function releases the last
reference on the spi_master and thereby frees the private data.
Fix by
From: Neal Cardwell
[ Upstream commit 299bcb55ecd1412f6df606e9dc0912d55610029e ]
When cwnd is not a multiple of the TSO skb size of N*MSS, we can get
into persistent scenarios where we have the following sequence:
(1) ACK for full-sized skb of N*MSS arrives
-> tcp_write_xmit() transmit
From: Zhang Changzhong
[ Upstream commit ee4f52a8de2c6f78b01f10b4c330867d88c1653a ]
Fix to return a negative error code from the error handling
case instead of 0, as done elsewhere in this function.
Fixes: f8ed289fab84 ("bridge: vlan: use br_vlan_(get|put)_master to deal with
refcounts")
From: Fugang Duan
[ Upstream commit 5f58591323bf3f342920179f24515935c4b5fd60 ]
There have chance to re-enable the eee_ctrl_timer and fire the timer
in napi callback after delete the timer in .stmmac_release(), which
introduces to access eee registers in the timer function after clocks
are
From: Bui Quang Minh
commit e90cfa813da7a527785033a0b247594c2de93dd8 upstream.
This error path
err_add_pdata:
for (i = 0; i < mod_data.num; i++)
kfree(dum[i]);
can be triggered when not all dum's elements are initialized.
Fix this by
From: Takashi Iwai
commit 43d5ca88dfcd35e43010fdd818e067aa9a55f5ba upstream.
syzbot spotted a potential out-of-bounds shift in the USB-audio format
parser that receives the arbitrary shift value from the USB
descriptor.
Add a range check for avoiding the undefined behavior.
Reported-by:
From: Li Jun
commit c1373f10479b624fb6dba0805d673e860f1b421d upstream.
If a USB2 device wakeup is not enabled/supported the link state may
still be in U0 in xhci_bus_suspend(), where it's then manually put
to suspended U3 state.
Just as with selective suspend the device needs time to enter U3
From: Nathan Chancellor
[ Upstream commit d853b3406903a7dc5b14eb5bada3e8cd677f66a2 ]
Clang warns:
drivers/spi/spi-bcm2835aux.c:532:50: warning: variable 'err' is
uninitialized when used here [-Wuninitialized]
dev_err(>dev, "could not get clk: %d\n", err);
From: Dmitry Torokhov
commit 82e06090473289ce63e23fdeb8737aad59b10645 upstream.
We need to make sure we are not stomping on the control URB that was
issued when opening the device when attempting to toggle buzzer.
To do that we need to mark it as pending in cm109_open().
From: Brant Merryman
commit 4387b3dbb079d482d3c2b43a703ceed4dd27ed28 upstream
Assign the .throttle and .unthrottle functions to be generic function
in the driver structure to prevent data loss that can otherwise occur
if the host does not enable USB throttling.
Signed-off-by: Brant Merryman
From: Cezary Rojewski
[ Upstream commit 4c22b80f61540ea99d9b4af0127315338755f05b ]
soc-pcm's dpcm_fe_dai_do_trigger() supported DRAIN commnad up to kernel
v5.4 where explicit switch(cmd) has been introduced which takes into
account all SNDRV_PCM_TRIGGER_xxx but SNDRV_PCM_TRIGGER_DRAIN. Update
From: Lukas Wunner
commit ddf75be47ca748f8b12d28ac64d624354fddf189 upstream
CONFIG_OF_DYNAMIC and CONFIG_ACPI allow adding SPI devices at runtime
using a DeviceTree overlay or DSDT patch. CONFIG_SPI_SLAVE allows the
same via sysfs.
But there are no precautions to prevent adding a device below
From: Leon Romanovsky
[ Upstream commit 340b940ea0ed12d9adbb8f72dea17d516b2019e8 ]
If cm_create_timewait_info() fails, the timewait_info pointer will contain
an error value and will be used in cm_remove_remote() later.
general protection fault, probably for non-canonical address
From: Necip Fazil Yildiran
[ Upstream commit 3a5fe2fb9635c43359c9729352f45044f3c8df6b ]
When BCM47XX_BCMA is enabled and BCMA_DRIVER_PCI is disabled, it results
in the following Kbuild warning:
WARNING: unmet direct dependencies detected for BCMA_DRIVER_PCI_HOSTMODE
Depends on [n]: MIPS [=y]
This is the start of the stable review cycle for the 4.4.249 release.
There are 132 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Wed, 30 Dec 2020 12:48:23 +.
Anything
From: Zhang Qilong
[ Upstream commit 4d1be581ec6b92a338bb7ed23e1381f45ddf336f ]
If softing_netdev_open() fails, we should call close_candev() to avoid
reference leak.
Fixes: 03fd3cf5a179d ("can: add driver for Softing card")
Signed-off-by: Zhang Qilong
Acked-by: Kurt Van Dijck
Link:
1 - 100 of 2629 matches
Mail list logo
