On Mon, Dec 21, 2020 at 07:27:31PM +0800, Dinghao Liu wrote:
> When mlx5_create_flow_group() fails, ft->g should be
> freed just like when kvzalloc() fails. The caller of
> mlx5e_create_l2_table_groups() does not catch this
> issue on failure, which leads to memleak.
>
> Signed-off-by: Dinghao Liu
On Wed, Dec 23, 2020 at 11:30:41AM -0800, t...@redhat.com wrote:
> From: Tom Rix
>
> This change fixes the checkpatch warning described in this commit
> commit cbacb5ab0aa0 ("docs: printk-formats: Stop encouraging use of
> unnecessary %h[xudi] and %hh[xudi]")
>
> Standard integer promotion is
On Mon, Dec 21, 2020 at 04:50:31PM +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
Hi Hsin-Hsiung,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on next-20201223]
[cannot apply to regulator/for-next robh/for-next v5.10 v5.10-rc7 v5.10-rc6
v5.10]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
[Why]
Similar to commit<0fa375e6>. If the set_state/can_switch code access the
drm_device when dev is not bound,
a null pointer dereference can happen.
[How]
Add sanity checks to prevent it.
Signed-off-by: Defang Bo
---
drivers/gpu/drm/radeon/radeon_device.c | 6 ++
1 file changed, 6
Currently openrisc will print a message and then hang in an infinite
loop when rebooting.
This patch adopts some code from ARM, which calls the common restart
infrastructure and hangs after a small delay if the restart infra
doesn't do anything.
Signed-off-by: Joel Stanley
---
Geert has a
Linus,
Please pull the latest sched/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
sched-urgent-2020-12-27
# HEAD: ae7927023243dcc7389b2d59b16c09cbbeaecc36 sched: Optimize
finish_lock_switch()
Fix a context switch performance regression.
Thanks,
Linus,
Please pull the latest timers/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-2020-12-27
# HEAD: f6f5cd840ae782680c5e94048c72420e4e6857f9 timekeeping: Fix spelling
mistake in Kconfig "fullfill" -> "fulfill"
Update/fix two CPU sanity
Linus,
Please pull the latest objtool/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
objtool-urgent-2020-12-27
# HEAD: 44f6a7c0755d8dd453c70557e11687bb080a6f21 objtool: Fix seg fault with
Clang non-section symbols
Fix a segfault that occurs when built
Linus,
Please pull the latest locking/urgent git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
locking-urgent-2020-12-27
# HEAD: 91ea62d58bd661827c328a2c6c02a87fa4aae88b softirq: Avoid bad tracing
/ lockdep interaction
Misc fixes/updates:
- Fix static keys usage
Em Sat, 26 Dec 2020 13:18:58 +
Nícolas F. R. A. Prado escreveu:
> During the process of converting the documentation to reST, some links
> were converted using the following wrong syntax (and sometimes using %20
> instead of spaces):
>
The patch itself looks ok, although the description
Hi all!
On Sat, 2020-12-26 at 14:30 -0800, Theodore Dubois wrote:
[...]
> thing on macOS (please don't question my sanity :), and I've run
> into various issues stemming from macOS having a case-insensitive
> filesystem.
Case-insensitive filesystems are broken by design.
Kind regards,
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: 9b80e4c4ddaca3501177ed41e49d0928ba2122a8 overflow: Add __must_check
attribute to check_*() helpers
date: 3 months ago
config: arm-randconfig-r031-20201226
add compitable/reg/irq/clock/efuse/reset setting in svs node
Signed-off-by: Roger Lu
---
arch/arm64/boot/dts/mediatek/mt8192.dtsi | 34
1 file changed, 34 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8192.dtsi
b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
add compitable/reg/irq/clock/efuse setting in svs node
Signed-off-by: Roger Lu
---
arch/arm64/boot/dts/mediatek/mt8183.dtsi | 20
1 file changed, 20 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8183.dtsi
b/arch/arm64/boot/dts/mediatek/mt8183.dtsi
index
1. SVS driver uses OPP adjust event in [1] to update OPP table voltage part.
2. SVS driver gets thermal/GPU device by node [2][3] and do device_link_add()
to make sure probe/suspend callback priority.
3. SVS driver gets CPU device by get_cpu_device() and do device_link_add()
to make sure
The purpose of SVS is to help find the suitable voltages
for DVFS. Therefore, if SVS bank voltages are concerned
to be wrong, we can adjust SVS bank voltages by this patch.
Signed-off-by: Roger Lu
---
drivers/soc/mediatek/mtk-svs.c | 324 +
1 file changed, 324
Signed-off-by: Roger Lu
---
drivers/soc/mediatek/mtk-svs.c | 494 -
1 file changed, 488 insertions(+), 6 deletions(-)
diff --git a/drivers/soc/mediatek/mtk-svs.c b/drivers/soc/mediatek/mtk-svs.c
index ef3aeb4b7dbd..9201e5480c6c 100644
---
The Smart Voltage Scaling(SVS) engine is a piece of hardware
which calculats suitable SVS bank voltages to OPP voltage table.
Then, DVFS driver could apply those SVS bank voltages to PMIC/Buck
when receiving OPP_EVENT_ADJUST_VOLTAGE.
Signed-off-by: Roger Lu
---
drivers/soc/mediatek/Kconfig |
Signed-off-by: Roger Lu
---
.../bindings/soc/mediatek/mtk-svs.yaml| 26 +++
1 file changed, 26 insertions(+)
diff --git a/Documentation/devicetree/bindings/soc/mediatek/mtk-svs.yaml
b/Documentation/devicetree/bindings/soc/mediatek/mtk-svs.yaml
index
Document the binding for enabling mtk svs on MediaTek SoC.
Signed-off-by: Roger Lu
---
.../bindings/soc/mediatek/mtk-svs.yaml| 75 +++
1 file changed, 75 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/mediatek/mtk-svs.yaml
diff --git
Hi Nathan,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: afe956c577b2d5a3d9834e4424587c1ebcf90c4c kbuild: Enable
-Wtautological-compare
date: 9 months ago
On 23.12.20 02:20, Tony Krowiak wrote:
> The vfio_ap device driver registers a group notifier with VFIO when the
> file descriptor for a VFIO mediated device for a KVM guest is opened to
> receive notification that the KVM pointer is set (VFIO_GROUP_NOTIFY_SET_KVM
> event). When the KVM pointer
Hi,
On Fri 11 Sep 20, 09:25, Hamish Martin wrote:
> Some integrated OHCI controller hubs do not expose all ports of the hub
> to pins on the SoC. In some cases the unconnected ports generate
> spurious over-current events. For example the Broadcom 56060/Ranger 2 SoC
> contains a nominally 3 port
Warning found by checkpatch.pl script.
Signed-off-by: Angshuman Sengupta
---
drivers/staging/android/ashmem.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/android/ashmem.c b/drivers/staging/android/ashmem.c
index 4789d36ddfd3..2cb665e0228c 100644
---
Bert,
On Sat, 26 Dec 2020 15:02:21 +,
Bert Vermeulen wrote:
>
> On 12/23/20 5:18 PM, Marc Zyngier wrote:
> >> + /* Set up interrupt routing */
> >> + writel(RTL8380_IRR0_SETTING, REG(RTL8380_IRR0));
> >> + writel(RTL8380_IRR1_SETTING, REG(RTL8380_IRR1));
> >> +
Hi Linus:
This push fixes a number of autobuild failures due to missing
Kconfig dependencies.
The following changes since commit 93cebeb1c21a65b92636aaa278a32fbc0415ec67:
crypto: qat - add capability detection logic in qat_4xxx (2020-12-11 21:54:16
+1100)
are available in the Git repository
On Sun, Dec 27, 2020 at 04:56:45PM +0530, Angshuman Sengupta wrote:
> Warning found by checkpatch.pl script.
>
> Signed-off-by: Angshuman Sengupta
> ---
> drivers/staging/android/ashmem.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/android/ashmem.c
Hi YANG,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on song-md/md-next]
[also build test WARNING on v5.10 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
Hi,
I love your patch! Yet something to improve:
[auto build test ERROR on soc/for-next]
[also build test ERROR on next-20201223]
[cannot apply to robh/for-next arm/for-next keystone/next rockchip/for-next
arm64/for-next/core shawnguo/for-next xlnx/master kvmarm/next mediatek/for-next
v5.10]
On Fri, Dec 25, 2020 at 04:51:13PM +0300, Konstantin Komarov wrote:
> +static int ntfs_readdir(struct file *file, struct dir_context *ctx)
> +{
> + const struct INDEX_ROOT *root;
> + u64 vbo;
> + size_t bit;
> + loff_t eod;
> + int err = 0;
> + struct inode *dir =
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 a large amount of IO. Current approach is to limit
> the max amount of tags a disk can get equally to the average of total
>
Hi Markus
> This should be caused by
> commit <9b947a13e7f6> ("")
> I suggest to omit angle brackets from such information.
> * Will another imperative wording become helpful for the commit description?
> * How do you think about to add the tag “Fixes”?
Do you mean so?
commit:
[Why]
Similar to commit<0fa375e6>. If amdgpu_switcheroo_can_switch access
the drm_device when dev is not bound, a null pointer dereference can happen.
[How]
Add sanity checks to prevent it.
Signed-off-by: Defang Bo
---
drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 3 +++
1 file changed, 3
Hi Mauro,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: 5b552b198c2557295becd471bff53bb520fefee5 media: atomisp: re-enable
warnings again
date: 7 months ago
CC Arnd
On Sun, Dec 27, 2020 at 3:48 AM Randy Dunlap wrote:
>
> Make mandatory in include/asm-generic/Kbuild
> and remove all arch/*/include/asm/local64.h arch-specific files since
> they only #include .
>
> This fixes build errors on arch/c6x/ and arch/nios2/ for
> block/blk-iocost.c.
>
>
From: Tho Vu
Define the Falcon board dependent part of the Ethernet-AVB device nodes.
Only AVB0 was tested because it was the only port with a PHY on current
hardware.
Signed-off-by: Tho Vu
[wsa: rebased]
Signed-off-by: Wolfram Sang
---
.../boot/dts/renesas/r8a779a0-falcon.dts | 195
From: Tho Vu
Define the generic parts of Ethernet-AVB device nodes. Only AVB0 was
tested because it was the only port with a PHY on current hardware.
Signed-off-by: Tho Vu
[wsa: double checked & rebased]
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0.dtsi | 270
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/r8a779a0-cpg-mssr.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/drivers/clk/renesas/r8a779a0-cpg-mssr.c
b/drivers/clk/renesas/r8a779a0-cpg-mssr.c
index 04514140e615..5be70a6a7904 100644
---
Document the compatible value for the RAVB block in the Renesas R-Car
V3U (R8A779A0) SoC. This variant has no stream buffer, so we only need
to add the new compatible.
Signed-off-by: Wolfram Sang
---
Documentation/devicetree/bindings/net/renesas,etheravb.yaml | 1 +
1 file changed, 1
Retrieving a GPIO currently fails, so probing the whole driver fails
then. Remove them for now to get a working AVB device for testing.
Signed-off-by: Wolfram Sang
---
arch/arm64/boot/dts/renesas/r8a779a0-falcon.dts | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git
Here is the series to enable RAVB on V3U. I took the DTS patches
from the BSP, the rest was developed on mainline tree. Note that only
RAVB0 could be tested because the other ones did not have PHYs attached.
Also, the last patch is a workaround. 'reset-gpios' cannot be obtained
currently which
From: Hongtao Wu
This series adds PCIe controller driver for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Changes from v1:
1) Test this patch on top of Rob Herring's 40 part series of DWC clean-ups:
https://lore.kernel.org/linux-pci/20200821035420.380495-1-r...@kernel.org/
From: Hongtao Wu
This series adds PCIe bindings for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Signed-off-by: Hongtao Wu
---
.../devicetree/bindings/pci/sprd-pcie.yaml | 91 ++
1 file changed, 91 insertions(+)
create mode 100644
From: Hongtao Wu
This series adds PCIe controller driver for Unisoc SoCs.
This controller is based on DesignWare PCIe IP.
Signed-off-by: Hongtao Wu
---
drivers/pci/controller/dwc/Kconfig | 12 ++
drivers/pci/controller/dwc/Makefile| 1 +
drivers/pci/controller/dwc/pcie-sprd.c | 293
Dear Linux folks,
Using an initrd created by tiny-initramfs [1], the boot stalls for two
minutes *after* the initrd has run and systemd has already started. An
F2FS root partition is used.
```
[0.00] microcode: microcode updated early to revision 0xa0b,
date = 2010-09-28
[
Similar to commit<1bd54d85>,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 insertions(+)
diff --git a/drivers/misc/kgdbts.c
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f838f8d2b694cf9d524dc4423e9dd2db13892f3f
commit: 18c07d23da5a48525b2955aa269b8bb108c19300 csky: Fixup calltrace panic
date: 8 months ago
config: csky-randconfig-r004-20201227 (attached as .config)
compiler
Paging Hartley who I think uses this chip.
On Thu, Dec 24, 2020 at 12:22 PM Nikita Shubin
wrote:
> I was lucky enough to became an owner of some splendid piece's of
> antiques called ts7250 based on the top of Cirrus Logic EP9302.
>
> I don't know what fate expects this hardware (it's not EOL
On Sun Dec 27, 2020 at 6:59 AM -03, Mauro Carvalho Chehab wrote:
> Well, docutils define two types of references at:
>
> https://docutils.sourceforge.io/docs/ref/rst/restructuredtext.html#reference-names
>
> The first one are "simple reference names", defined as:
>
> ``Simple reference names are
On Sat, Dec 26, 2020 at 6:34 PM Andy Shevchenko
wrote:
> I personally consider it quite nice to have support even for outdated
> hardware (reminds me about a recent LWN article about 32-bit
> architectures and a comment there how it could affect the environment
> if we drop them from being
On Sat, Dec 26, 2020 at 6:16 PM Hillf Danton wrote:
>
> Sat, 26 Dec 2020 10:51:13 +0800
> > From: Lai Jiangshan
> >
> > There is possible that a per-node pool/woker's affinity is a single
> > CPU. It can happen when the workqueue user changes the cpumask of the
> > workqueue or when
Move the pm_power_off callback into one global place and also add an
function for conditionally calling it (when not NULL), in order to remove
code duplication in all individual archs.
Reported-by: kernel test robot
Signed-off-by: Enrico Weigelt, metux IT consult
changes v2:
* fix
On Sat, Dec 26, 2020 at 10:52 PM Paul E. McKenney wrote:
> >
> > Can you please specify a bit what you encountered in rcutorture
> > before this patchset? You know we cant have a correct estimation
> > of the fix diameter without your help.
>
> It triggers the following in sched_cpu_dying() in
Hello Linus,
Here are a few NTB bug fixes for v5.11. Please consider pulling them.
Thanks,
Jon
The following changes since commit 3650b228f83adda7e5ee532e2b90429c03f7b9ec:
Linux 5.10-rc1 (2020-10-25 15:14:11 -0700)
are available in the Git repository at:
git://github.com/jonmason/ntb
After commit 72cdab808714 ("ath9k: Do not select MAC80211_LEDS by
default") a configuration like:
- MAC80211_LEDS=y
- LEDS_CLASS=m
- NEW_LEDS=y
- ATH9K=y
leads to a build failure:
/usr/bin/ld: drivers/net/wireless/ath/ath9k/gpio.o: in function
`ath_deinit_leds':
From: Dylan Van Assche
GPIO LEDs only know 2 states: ON or OFF and do not have PWM capabilities.
However, the max brightness is reported as 255.
This patch sets the max brightness value of a GPIO controlled LED to 1.
Tested on my PinePhone 1.2.
Signed-off-by: Dylan Van Assche
---
Significant time was spent on synchronize_rcu in evdev_detach_client
when applications closed evdev devices. Switching VT away from a
graphical environment commonly leads to mass input device closures,
which could lead to noticable delays on systems with many input devices.
Replace
Hi Geert,
Thanks for your patch.
On 2020-12-10 20:46:48 +0100, Geert Uytterhoeven wrote:
> The Renesas Compare Match Timer 0 and 1 (CMT0/1) variants have a
> register to control the clock supply to the individual channels.
> Currently the driver does not touch this register, and relies on the
>
On Sun, Dec 27, 2020 at 09:43:05PM +0800, Defang Bo wrote:
> Similar to commit<1bd54d85>,kgdbts_option_setup does not check input argument
> before passing it to strlen. The argument would be a NULL pointer.
>
As per the documentation, you should write commits out as 1bd54d851f50
("kgdboc:
On Sun, Dec 27, 2020 at 11:45 AM Randy Dunlap wrote:
>
> Make mandatory in include/asm-generic/Kbuild
> and remove all arch/*/include/asm/local64.h arch-specific files since
> they only #include .
>
> This fixes build errors on arch/c6x/ and arch/nios2/ for
> block/blk-iocost.c.
>
> Build-tested
There should be a check for clk to prevent NULL pointer dereference.
Signed-off-by: Defang Bo
---
arch/m68k/coldfire/clk.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/m68k/coldfire/clk.c b/arch/m68k/coldfire/clk.c
index 7bc666e..cf1ed97 100644
--- a/arch/m68k/coldfire/clk.c
+++
On 12/23/20 11:42 AM, Borislav Petkov wrote:
From: Borislav Petkov
Hi,
here's v1 with the requested change to return -ENODATA on short input to
the decoder. The rest is as in the previous submission.
Only lightly tested.
Thx.
changelog:
==
That is, provided this is how we want to
On Dez 27 2020, Defang Bo wrote:
> diff --git a/arch/m68k/coldfire/clk.c b/arch/m68k/coldfire/clk.c
> index 7bc666e..cf1ed97 100644
> --- a/arch/m68k/coldfire/clk.c
> +++ b/arch/m68k/coldfire/clk.c
> @@ -90,6 +90,9 @@ EXPORT_SYMBOL(clk_get);
> int clk_enable(struct clk *clk)
> {
>
On Sat, 2020-12-26 at 16:06 +0100, Greg Kroah-Hartman wrote:
> On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
> > On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
> > > This is the start of the stable review cycle for the 5.10.3
> > > release.
> > > There are 40
On Sun, Dec 27, 2020 at 10:08:51PM +0800, Lai Jiangshan wrote:
> On Sat, Dec 26, 2020 at 10:52 PM Paul E. McKenney wrote:
>
> > >
> > > Can you please specify a bit what you encountered in rcutorture
> > > before this patchset? You know we cant have a correct estimation
> > > of the fix diameter
On Sun, Dec 27, 2020 at 09:20:07PM +0530, Jeffrin Jose T wrote:
> On Sat, 2020-12-26 at 16:06 +0100, Greg Kroah-Hartman wrote:
> > On Thu, Dec 24, 2020 at 03:13:38PM +0530, Jeffrin Jose T wrote:
> > > On Wed, 2020-12-23 at 16:33 +0100, Greg Kroah-Hartman wrote:
> > > > This is the start of the
The kernel test robot reports the following warning in [1]:
drivers/gpio/gpiolib-cdev.c: In function 'gpio_ioctl':
>>drivers/gpio/gpiolib-cdev.c:1437:1: warning: the frame size of 1040 bytes is
>>larger than 1024 bytes [-Wframe-larger-than=]
Refactor gpio_ioctl() to handle each ioctl in its
Similar to commit<124751d5e>, there should be a check for urb before kill it.
Signed-off-by: Defang Bo
---
sound/usb/mixer.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/sound/usb/mixer.c b/sound/usb/mixer.c
index 81e987e..0223ef3 100644
--- a/sound/usb/mixer.c
+++
Move generic LiteX CSR (MMIO) register accessors to litex.h and
declare them as "static inline", in preparation for supporting
32-bit CSR subregisters and 64-bit CPUs.
NOTE: this is a non-functional change.
Signed-off-by: Gabriel Somlo
---
drivers/soc/litex/litex_soc_ctrl.c | 73
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 and sizeof(u64), which SHOULD be checked at runtime
if these methods are
Upstream LiteX now defaults to using 32-bit CSR subregisters
(see https://github.com/enjoy-digital/litex/commit/a2b71fde).
This patch expands on commit 22447a99c97e ("drivers/soc/litex: add
LiteX SoC Controller driver"), adding support for handling both 8-
and 32-bit LiteX CSR (MMIO)
Separate MMIO (read/write) access into _[read|write]_litex_subregister()
static inline functions, leaving existing "READ|WRITE" macros to handle
calculation of the subregister offset only.
NOTE: this is a non-functional change.
Signed-off-by: Gabriel Somlo
---
include/linux/litex.h | 16
This series expands on commit 22447a99c97e ("drivers/soc/litex: add LiteX
SoC Controller driver"), adding support for handling both 8- and 32-bit
LiteX CSR (MMIO) subregisters, on both 32- and 64-bit CPUs.
Notes v5:
- added patch (4/4) taking 'litex_[set|get]_reg()' private
-
Hello,
Now that 5.9 series is EOL, I tried to move to 5.10.3. I ran in to regression
where LXC containers do not start with newer kernel. I found that issue had
been reported (bisected + with reduced test case) in bugzilla at:
https://bugzilla.kernel.org/show_bug.cgi?id=209971
Has this been
On Wed, Dec 16, 2020 at 08:48:29AM -0800, Paul E. McKenney wrote:
> On Wed, Dec 16, 2020 at 10:31:16AM +0100, Geert Uytterhoeven wrote:
> > Hi Paul,
> >
> > On Tue, Dec 15, 2020 at 7:24 PM Paul E. McKenney wrote:
> > > On Tue, Dec 15, 2020 at 09:40:26AM +0100, Geert Uytterhoeven wrote:
> > > >
On Sun, Dec 27, 2020 at 06:32:41PM +0200, Jussi Kivilinna wrote:
> Hello,
>
> Now that 5.9 series is EOL, I tried to move to 5.10.3. I ran in to regression
> where LXC containers do not start with newer kernel. I found that issue had
> been reported (bisected + with reduced test case) in
On Thu, 24 Dec 2020 16:42:08 +0530, Roja Rani Yarubandi wrote:
> While most devices within power-domains which support performance states,
> scale the performance state dynamically, some devices might want to
> set a static/default performance state while the device is active.
> These devices
On Fri, 25 Dec 2020 19:01:09 +0800, Xin Ji wrote:
> Add DPI flag for distinguish MIPI input signal type, DSI or DPI. Add
> swing setting for adjusting DP tx PHY swing
>
> Signed-off-by: Xin Ji
> ---
> .../bindings/display/bridge/analogix,anx7625.yaml | 19
> +++
> 1 file
On Sun, 27 Dec 2020 18:54:43 +0800, Roger Lu wrote:
> Document the binding for enabling mtk svs on MediaTek SoC.
>
> Signed-off-by: Roger Lu
> ---
> .../bindings/soc/mediatek/mtk-svs.yaml| 75 +++
> 1 file changed, 75 insertions(+)
> create mode 100644
>
On Sun, 27 Dec 2020 21:12:13 +0800, Hongtao Wu wrote:
> From: Hongtao Wu
>
> This series adds PCIe bindings for Unisoc SoCs.
> This controller is based on DesignWare PCIe IP.
>
> Signed-off-by: Hongtao Wu
> ---
> .../devicetree/bindings/pci/sprd-pcie.yaml | 91
>
On Thu, 24 Dec 2020 20:31:18 +0800, Nick Fan wrote:
> Convert the Arm Valhall GPU binding to DT schema format.
>
> Define a compatible string for the Mali Valhall GPU
> for Mediatek's SoC platform.
>
> Signed-off-by: Nick Fan
> ---
> .../bindings/gpu/arm,mali-valhall.yaml| 252
On Sun, 27 Dec 2020 at 21:39, Mikhail Gavrilov
wrote:
> I suppose the root of cause my problem here:
>
> [3.961326] amdgpu :0b:00.0: Direct firmware load for
> amdgpu/sienna_cichlid_sos.bin failed with error -2
> [3.961359] amdgpu :0b:00.0: amdgpu: failed to init sos firmware
> [
This started with 5.5 and hasn't gotten better since then, despite some reports
I tried to send.
As per my previous message:
I have a Thinkpad P70 with hybrid graphics.
01:00.0 VGA compatible controller: NVIDIA Corporation GM107GLM [Quadro M600M]
(rev a2)
that one works fine, I can use i915 for
Oops, missed removing this deleted file from the Makefile.
make[3]: *** No rule to make target 'lib/zlib_dfltcc/dfltcc_syms.o', needed by
'lib/zlib_dfltcc/built-in.a'.
Signed-off-by: Randy Dunlap
Reported-by: kernel test robot
Cc: Zaslonko Mikhail
Cc: Andrew Morton
Cc: Heiko Carstens
Cc:
Similar to commit<2423496af35>, the fragmentation code tries to parse the
header options in order
to figure out where to insert the fragment option. Since nexthdr points
to an invalid option, the calculation of the size of the network header
can made to be much larger than the linear section of
On Sun, Dec 27, 2020 at 8:32 AM Jussi Kivilinna wrote:
>
> Has this been fixed in 5.11-rc? Is there any patch that I could backport and
> test with 5.10?
Here's a patch to test. Entirely untested by me. I'm surprised at how
people use sendfile() on random files. Oh well..
Linus
This adds audio playback to the first generation Amazon Echo
Signed-off-by: André Hentschel
---
It took me by far too long to get this working as the codec sets one important
bit based on the
combination of provided supplies. That was just too hidden for me.
The first generation Amazon Echo
On 21.12.20 13:22, Donald Buczek wrote:
On 18.12.20 22:49, Dave Chinner wrote:
On Thu, Dec 17, 2020 at 06:44:51PM +0100, Donald Buczek wrote:
Dear xfs developer,
I was doing some testing on a Linux 5.10.1 system with two 100 TB xfs
filesystems on md raid6 raids.
The stress test was
Le 22/12/2020 à 05:35, Viresh Kumar a écrit :
On 19-12-20, 11:17, Christophe JAILLET wrote:
If 'cpufreq_register_driver()' fails, we must release the resources
allocated in 'brcm_avs_prepare_init()' as already done in the remove
function.
To do that, introduce a new function
The pull request you sent on Sun, 27 Dec 2020 10:31:05 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> objtool-urgent-2020-12-27
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/cce622ab9284a27257dd75bb35eccdd619bf96d1
Thank you!
--
The pull request you sent on Sun, 27 Dec 2020 10:26:58 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers-urgent-2020-12-27
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/2eeefc60ad70ffb7a5daf9f47aef5b1ebd1f39ad
Thank you!
--
The pull request you sent on Sun, 27 Dec 2020 22:32:21 +1100:
> git://git.kernel.org/pub/scm/linux/kernel/git/herbert/crypto-2.6.git linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/33c148a4ae7dc3cd440f6c0d746ac7f0ff320682
Thank you!
--
Deet-doot-dot, I am a
The pull request you sent on Sun, 27 Dec 2020 10:50:44 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> locking-urgent-2020-12-27
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/6be5f58215f1dcbd697a695ad5db9986c28c50c3
Thank you!
--
The pull request you sent on Sun, 27 Dec 2020 09:16:38 -0500:
> git://github.com/jonmason/ntb tags/ntb-5.11
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/52cd5f9c22eeef26d05f9d9338ba4eb38f14dd3a
Thank you!
--
Deet-doot-dot, I am a bot.
From: Jia Qingtong
Supply little-endian address bit definitions as well as
set proper endian swapping modes.
Signed-off-by: Jia Qingtong
---
fix pcie setup error when Octeon in little-endian mode
[] octeon_pcie_setup+0x264/0x4e8
[] do_one_initcall+0x54/0x190
[]
The pull request you sent on Sun, 27 Dec 2020 10:16:01 +0100:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> sched-urgent-2020-12-27
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/3b80dee70eaa5f9a120db058c30cc8e63c443571
Thank you!
--
Deet-doot-dot,
On 18.12.20 19:35, Donald Buczek wrote:
On 18.12.20 16:35, Brian Foster wrote:
On Thu, Dec 17, 2020 at 10:30:37PM +0100, Donald Buczek wrote:
On 17.12.20 20:43, Brian Foster wrote:
On Thu, Dec 17, 2020 at 06:44:51PM +0100, Donald Buczek wrote:
Dear xfs developer,
I was doing some testing on
On Sun, Dec 27, 2020 at 6:16 AM Jon Mason wrote:
>
> Wang Qing (1):
> ntb: idt: fix error check in ntb_hw_idt.c
So this patch seems to be at least partially triggered by a smatch
warning that is a bit questionable.
This part:
if (IS_ERR_OR_NULL(dbgfs_topdir)) {
We want to reuse SD clock handling for other SoCs and, thus, need to
generalize it. So, don't access cpg_quirks in that realm.
Signed-off-by: Wolfram Sang
---
drivers/clk/renesas/rcar-gen3-cpg.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git
1 - 100 of 249 matches
Mail list logo
