On Fri, Sep 4, 2020 at 8:49 PM syzbot
wrote:
>
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:0f091e43 netlabel: remove unused param from audit_log_form..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=14551a7190
> kernel config:
* Grygorii Strashko [210304 20:58]:
> On 04/03/2021 09:21, Tony Lindgren wrote:
> > When the timer is configured in posted mode, we need to check the write-
> > posted status register (TWPS) before writing to the register.
...
> > --- a/drivers/clocksource/timer-ti-dm-systimer.c
> > +++
On Thu, Mar 04, 2021 at 09:56:24PM +0100, Arnd Bergmann wrote:
> On Wed, Mar 3, 2021 at 2:54 PM Alex Bennée wrote:
> >
> > A number of storage technologies support a specialised hardware
> > partition designed to be resistant to replay attacks. The underlying
> > HW protocols differ but the
On Fri, Mar 05, 2021 at 04:01PM +1100, Michael Ellerman wrote:
> Marco Elver writes:
> > On Thu, Mar 04, 2021 at 12:48PM +0100, Christophe Leroy wrote:
> >> Le 04/03/2021 à 12:31, Marco Elver a écrit :
> >> > On Thu, 4 Mar 2021 at 12:23, Christophe Leroy
> >> > wrote:
> >> > > Le 03/03/2021 à
* Grygorii Strashko [210304 20:56]:
>
>
> On 04/03/2021 09:21, Tony Lindgren wrote:
> > We have of_translate_address() already do of_node_put() as needed.
> > I probably looked at __of_translate_address() earlier by accident
> > that of_translate_address() uses.
>
> I do not see of_node_put()
In preparation to enable -Wimplicit-fallthrough for Clang, fix multiple
warnings by explicitly adding multiple break statements instead of
letting the code fall through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
On Thu, Mar 04, 2021 at 05:26:42PM -0700, Jens Axboe wrote:
> Christoph, since there's multiple commits with issues, mind resending
> a fixed branch? Then I'll drop the one I pulled today.
I've fixed the commit id and dropped the patch without the author
signoff, but your branch still has the
Hi Andy,
> El 4 mar 2021, a las 17:33, Andy Shevchenko
> escribió:
>
> On Thu, Mar 4, 2021 at 5:44 PM Álvaro Fernández Rojas
> wrote:
>>> El 4 mar 2021, a las 16:28, Andy Shevchenko
>>> escribió:
>>> On Thu, Mar 4, 2021 at 5:24 PM Álvaro Fernández Rojas
>>> wrote:
> El 4 mar 2021, a
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 280d542f6ffac0e6d65dc267f92191d509b13b64
commit: cf59eb13e151ef42c37ae31864046c17e481ed8f KVM: PPC: Book3S: Fix symbol
undeclared warnings
date: 5 months ago
config: powerpc-randconfig-r006-20210305
In preparation to enable -Wimplicit-fallthrough for Clang, fix multiple
warnings by explicitly adding multiple break statements instead of
letting the code fall through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
net/rose/rose_route.c
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of letting the code fall
through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
net/core/dev.c | 1 +
1 file changed,
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a fallthrough pseudo-keyword.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
drivers/firewire/core-topology.c | 1 +
1 file changed, 1 insertion(+)
diff --git
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of letting the code fall
through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Acked-by: Nikolay Aleksandrov
Signed-off-by: Gustavo A. R. Silva
---
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of letting the code fall
through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
net/ax25/af_ax25.c | 1 +
1 file
Hi,
On 3/5/21 8:51 AM, Stefan Berger wrote:
From: Stefan Berger
Detect whether a key is an sm2 type of key by its OID in the parameters
array rather than assuming that everything under OID_id_ecPublicKey
is sm2, which is not the case.
Cc: David Howells
Cc: keyri...@vger.kernel.org
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of letting the code fall
through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
net/decnet/dn_route.c | 2 +-
1 file
On Fri, Mar 05, 2021 at 03:17:37PM +0800, Chien Kun Niu wrote:
> Greg KH 於 2021年3月3日 週三 下午5:10寫道:
> >
> > On Wed, Mar 03, 2021 at 05:03:25PM +0800, Chien Kun Niu wrote:
> > > Hi , Greg
> > >
> > > What tool will "catch" this? Where is that code located at?
> > > => I prepare merge the code to
Hi,
On 3/4/21 7:46 AM, Stefan Berger wrote:
Tianjia,
can you say whether SM2 support works for you before and after
applying this patch? I cannot verify it with an sm2 key I have created
using a sequence of commands like this:
> modprobe sm2_generic
> id=$(keyctl newring test @u)
>
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of just letting the code
fall through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of just letting the code
fall through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
---
drivers/net/ethernet/3com/3c509.c
In preparation to enable -Wimplicit-fallthrough for Clang, fix a warning
by explicitly adding a break statement instead of just letting the code
fall through to the next case.
Link: https://github.com/KSPP/linux/issues/115
Signed-off-by: Gustavo A. R. Silva
Reviewed-by: Vladimir Oltean
---
On 05-03-21, 15:00, Jie Deng wrote:
> On 2021/3/5 11:09, Viresh Kumar wrote:
> > On 05-03-21, 09:46, Jie Deng wrote:
> > > On 2021/3/4 14:06, Viresh Kumar wrote:
> > > > > + mutex_lock(>i2c_lock);
> > > > I have never worked with i2c stuff earlier, but I don't think you need
> > > > a lock
>
Hi Coly,
Thanks a lot for your detailed explanation :)
Best wishes,
Jia-Ju Bai
On 2021/3/5 12:05, Coly Li wrote:
On 3/5/21 10:46 AM, Jia-Ju Bai wrote:
When bch_bio_alloc_pages() fails, no error return code of
cached_dev_cache_miss() is assigned.
To fix this bug, ret is assigned with -ENOMEN
On Thu, Mar 04, 2021 at 03:44:37PM +0900, Naoya Horiguchi wrote:
> From: Naoya Horiguchi
Hi Naoya,
good catch!
> Currently me_huge_page() temporary unlocks page to perform some actions
> then locks it again later. My testcase (which calls hard-offline on some
> tail page in a hugetlb, then
On 2021/3/5 1:47 下午, Jie Deng wrote:
On 2021/3/4 17:15, Jason Wang wrote:
On 2021/3/4 9:59 上午, Jie Deng wrote:
Add an I2C bus driver for virtio para-virtualization.
The controller can be emulated by the backend driver in
any device model software by following the virtio protocol.
The
End users frequently want to know what features their processor
supports, independent of what the kernel supports.
/proc/cpuinfo is great. It is omnipresent and since it is provided by
the kernel it is always as up to date as the kernel. But, it could be
ambiguous about processor features which
On Thu, 2021-03-04 at 20:42 -0800, Roderick Colenbrander wrote:
> (resend in plain text)
> +benjamin in a more explicit way
>
> Hi Chris,
>
> I see the need for the Record button. I wonder what makes sense from
> the Linux kernel perspective. For DualShock 4 and DualSense there is a
> Share
Greg KH 於 2021年3月3日 週三 下午5:10寫道:
>
> On Wed, Mar 03, 2021 at 05:03:25PM +0800, Chien Kun Niu wrote:
> > Hi , Greg
> >
> > What tool will "catch" this? Where is that code located at?
> > => I prepare merge the code to Android phone , so I used Android HLOS
> > to catch this uevent.
>
> Very odd
On 04.03.2021 07:46, 'Wei Yongjun wrote:
From: Wei Yongjun
The sparse tool complains as follows:
drivers/mtd/parsers/ofpart_core.c:25:32: warning:
symbol 'bcm4908_partitions_quirks' was not declared. Should it be static?
This symbol is not used outside of ofpart_core.c, so this
commit
On Fri, 5 Mar 2021 06:49:14 +0100
Christophe Leroy wrote:
> Le 05/03/2021 ?? 02:43, angkery a ??crit?0?2:
> > From: Junlin Yang
> >
> > ibmvnic_remove locks multiple spinlocks while disabling interrupts:
> > spin_lock_irqsave(>state_lock, flags);
> > spin_lock_irqsave(>rwi_lock, flags);
> >
>
Add support for STMicroelectronics digital magnetic sensors,
LSM303AH,LSM303AGR,LIS2MDL,ISM303DAC,IIS2MDC.
The patch tested with IIS2MDC instrument.
Signed-off-by: LI Qingwu
---
drivers/iio/magnetometer/Kconfig | 23 ++
drivers/iio/magnetometer/Makefile | 4 +
Add support for ST magnetometer lsm303ah,sm303dac and iis2mdc.
The patch tested with IIS2MDC instrument.
Signed-off-by: LI Qingwu
---
Documentation/devicetree/bindings/iio/st,st-sensors.yaml | 5 +
1 file changed, 5 insertions(+)
diff --git
Hi John,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v5.12-rc1]
[cannot apply to linux/master drm-intel/for-linux-next drm-tip/drm-tip
next-20210305]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And
BCM6368 devices need to reset the IPSEC controller in order to generate true
random numbers.
This is what BCM6368 produces without a reset:
root@OpenWrt:/# cat /dev/hwrng | rngtest -c 1000
rngtest 6.10
Copyright (c) 2004 by Henrique de Moraes Holschuh
This is free software; see the source for
brcm,bcm6368-rng controllers require resetting the IPSEC clock in order to get
a functional RNG.
Signed-off-by: Álvaro Fernández Rojas
---
v6: fix dt-bindings warnings.
v5: no changes.
v4: pass dt_binding_check.
v3: make resets required if brcm,bcm6368-rng.
v2: document reset support.
brcm,bcm6368-rng controllers require enabling the IPSEC clock in order to get
a functional RNG.
Signed-off-by: Álvaro Fernández Rojas
---
v6: add new patch making clocks mandatory for BCM6368.
.../devicetree/bindings/rng/brcm,bcm2835.yaml | 10 ++
1 file changed, 10
Some devices may need to perform a reset before using the RNG, such as the
BCM6368.
v6: fix dt-bindings documentation, add patch makings clocks mandatory for
BCM6368.
v5: remove reset_control_rearm() and apply on latest herbert/cryptodev-2.6.git.
v4: fix documentation, add reset_control_rearm().
On 2021/3/5 11:09, Viresh Kumar wrote:
On 05-03-21, 09:46, Jie Deng wrote:
On 2021/3/4 14:06, Viresh Kumar wrote:
depends on I2C as well ?
No need that. The dependency of I2C is included in the Kconfig in its parent
directory.
Sorry about that, I must have figured that out myself.
(Though
在 2021/3/5 11:12, HongJieDeng 写道:
From: Hongjie Deng
We need more stack space, xori/ori no longer apply when
_THREAD_MASK exceeds 16 bits
Signed-off-by: Hongjie Deng
---
arch/mips/include/asm/stackframe.h | 8
arch/mips/kernel/genex.S | 6 ++
2 files changed,
Hi Sebastian,
Thanks a lot for your input, I changed according your input in PATCH V5, please
review.
About "why 0x instead of just '0' like in the other entries?", since I
got an error from checkpatch.pl.
ERROR: space prohibited before that ',' (ctx:WxW)
#100: FILE:
Fix the following coccicheck warnings:
./drivers/power/supply/cpcap-charger.c:468:31-36: WARNING: conversion to
bool not needed here.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
drivers/power/supply/cpcap-charger.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Add support for TI BQ78Z100, I2C interface gas gauge.
It provides a fully integrated safety protection
and authentication for 1 to 2-series cell Li-Ion and
Li-Polymer battery packs.
The patch was tested with BQ78Z100 equipment.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: LI Qingwu
---
Changes in V5:
1. Change [BQ27XXX_REG_TTES] from INVALID_REG_ADDR to 0x1c,
the StandbyTimeToEmpty command of bq78z100.
2. Add [BQ27XXX_REG_RC] = 0x10. the RemainingCapacity command of
bq78z100.
3. Set [BQ27XXX_REG_AE] to INVALID_REG_ADDR, support by bq78z100.
4. Delete property
Add bindings for TI BQ78Z100. An I2C interface gas gauge.
It provides a fully integrated safety protection
and authentication for 1 to 2-series cell Li-Ion and
Li-Polymer battery packs.
Acked-by: Rob Herring
Signed-off-by: LI Qingwu
---
On Fri, Mar 05, 2021 at 02:22:18PM +0800, Huang Jianan via Linux-erofs wrote:
> It should be better to ensure memory allocation during rolling
> decompression to avoid io error.
Currently, err would be treated as io error. Therefore, it'd be
better to ensure memory allocation during rolling
On Fri, Mar 5, 2021 at 7:10 AM Nicolas Pitre wrote:
>
> On Thu, 4 Mar 2021, Masahiro Yamada wrote:
>
> > The kernel build uses various tools, many of which are provided by the
> > same software suite, for example, LLVM and Binutils.
> >
> > When we raise the minimal version of Clang/LLVM, we need
On Thu, 2021-03-04 at 19:47 +0100, Thomas Gleixner wrote:
> On Thu, Mar 04 2021 at 10:12, Mike Galbraith wrote:
> > On Mon, 2021-03-01 at 18:29 +0100, Ben Hutchings wrote:
> >
> > --- a/kernel/futex.c
> > +++ b/kernel/futex.c
> > @@ -874,8 +874,12 @@ static void free_pi_state(struct futex_p
> >
On Thu, Mar 4, 2021 at 9:11 AM Nathan Chancellor wrote:
>
> On Thu, Mar 04, 2021 at 03:33:31AM +0900, Masahiro Yamada wrote:
> > The kernel build uses various tools, many of which are provided by the
> > same software suite, for example, LLVM and Binutils.
> >
> > When we raise the minimal
On Fri, Mar 05, 2021 at 02:22:19PM +0800, Huang Jianan via Linux-erofs wrote:
> z_erofs_decompressqueue_endio may not be executed in the interrupt
> context, for example, when dm-verity is turned on. In this scenario,
> io should be decompressed directly to avoid additional scheduling
> overhead.
Fix the following coccicheck warnings:
./drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c:8257:16-21: WARNING:
conversion to bool not needed here.
Reported-by: Abaci Robot
Signed-off-by: Jiapeng Chong
---
drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm.c | 3 +--
1 file changed, 1
Le 04/03/2021 à 20:24, Segher Boessenkool a écrit :
On Thu, Mar 04, 2021 at 09:54:44AM -0800, Nick Desaulniers wrote:
On Thu, Mar 4, 2021 at 9:42 AM Marco Elver wrote:
include/linux/compiler.h:246:
prevent_tail_call_optimization
commit a9a3ed1eff36 ("x86: Fix early boot crash on gcc-10,
On 3/4/2021 1:16 AM, Vitaly Kuznetsov wrote:
Tianyu Lan writes:
From: Tianyu Lan
Hyper-V provides GHCB protocol to write Synthetic Interrupt
Controller MSR registers and these registers are emulated by
Hypervisor rather than paravisor.
Hyper-V requests to write SINTx MSR registers
This patchset fix bugs related to 'dma_map_single' use:
Hui Tang (2):
crypto: qat - fix 'dma_unmap_single' invalid address
crypto: qat - fix use of 'dma_map_single'
v1 -> v2:
1.fix build warning reported by kernel test rebot
2.add patch #1
DMA_TO_DEVICE synchronisation must be done after the last modification
of the memory region by the software and before it is handed off to
the device.
Signed-off-by: Hui Tang
Reported-by: kernel test robot
Reported-by: Dan Carpenter
---
drivers/crypto/qat/qat_common/qat_algs.c | 27
'dma_mapping_error' return a negative value if 'dma_addr' is equal to
'DMA_MAPPING_ERROR' not zero, so fix initialization of 'dma_addr'.
Signed-off-by: Hui Tang
---
drivers/crypto/qat/qat_common/qat_algs.c | 11 +--
1 file changed, 9 insertions(+), 2 deletions(-)
diff --git
: f5427c24 Add linux-next specific files for 20210304
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=120b11b0d0
console output: https://syzkaller.appspot.com/x/log.txt?x=140b11b0d0
kernel config: https://syzkaller.appspot.com/x/.config?x
On 2021/3/5 1:23, Sean Christopherson wrote:
On Thu, Mar 04, 2021, Xu, Like wrote:
On 2021/3/4 1:26, Sean Christopherson wrote:
On Wed, Mar 03, 2021, Like Xu wrote:
New VMX controls bits for Arch LBR are added. When bit 21 in vmentry_ctrl
is set, VM entry will write the value from the "Guest
> On Thu, Mar 4, 2021 at 8:54 PM Winkler, Tomas
> wrote:
> > > Winkler, Tomas writes:
> > > >> "Winkler, Tomas" writes:
> > > >>
> > > >> >> The user space API is achieved via a number of synchronous
> IOCTLs.
> > > >> >>
> > > >> >> * RPMB_IOC_VER_CMD - simple versioning API
> > > >> >> *
Add compatibles for PM7325, PM8350C, PMK8350 and PMR735A GPIO support to the
Qualcomm technologies Inc PMIC GPIO binding.
Signed-off-by: satya priya
---
Documentation/devicetree/bindings/pinctrl/qcom,pmic-gpio.yaml | 8
1 file changed, 8 insertions(+)
diff --git
Add PM7325, PM8350c, PMK8350 and PMR735A compatibles for GPIO
support.
Signed-off-by: satya priya
---
drivers/pinctrl/qcom/pinctrl-spmi-gpio.c | 4
1 file changed, 4 insertions(+)
diff --git a/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
b/drivers/pinctrl/qcom/pinctrl-spmi-gpio.c
index
Convert Qualcomm PMIC GPIO bindings from .txt to .yaml format.
Signed-off-by: satya priya
---
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 272
.../bindings/pinctrl/qcom,pmic-gpio.yaml | 273 +
2 files changed, 273 insertions(+), 272
On Fri, Mar 05, 2021 at 12:05:23PM +1100, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the tty tree got a conflict in:
>
> drivers/tty/hvc/hvcs.c
>
> between commit:
>
> 386a966f5ce7 ("vio: make remove callback return void")
>
> from the powerpc-fixes tree and commit:
satya priya (3):
pinctrl: qcom: spmi-gpio: Add support for four variants
dt-bindings: pinctrl: qcom-pmic-gpio: Convert pmic gpio bindings to
YAML
dt-bindings: pinctrl: qcom-pmic-gpio: Add pmic gpio support
.../devicetree/bindings/pinctrl/qcom,pmic-gpio.txt | 272
Hi Florian,
> El 4 mar 2021, a las 23:28, Florian Fainelli escribió:
>
> On 3/4/21 7:11 AM, Nicolas Saenz Julienne wrote:
>> On Wed, 2021-03-03 at 10:29 +0100, Álvaro Fernández Rojas wrote:
>>> Hi Herbert,
>>>
El 3 mar 2021, a las 10:20, Herbert Xu
escribió:
On Sat, Feb
On 3/4/2021 12:58 AM, Vitaly Kuznetsov wrote:
Tianyu Lan writes:
From: Tianyu Lan
Add new hvcall guest address host visibility support. Mark vmbus
ring buffer visible to host when create gpadl buffer and mark back
to not visible when tear down gpadl buffer.
Signed-off-by: Sunil
Laurent Dufour writes:
> This is helpful to read the security flavor from inside the LPAR.
We already have /sys/kernel/debug/powerpc/security_features.
Is that not sufficient?
> Export it like this in /proc/powerpc/lparcfg:
>
> $ grep security_flavor /proc/powerpc/lparcfg
> security_flavor=1
>
z_erofs_decompressqueue_endio may not be executed in the interrupt
context, for example, when dm-verity is turned on. In this scenario,
io should be decompressed directly to avoid additional scheduling
overhead. Also there is no need to wait for endio to execute
synchronous decompression.
It should be better to ensure memory allocation during rolling
decompression to avoid io error.
Signed-off-by: Huang Jianan
Signed-off-by: Guo Weichao
---
fs/erofs/decompressor.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/erofs/decompressor.c
Hi Bjorn,
Do you have any comments on this patch? If need any changes, please let me
know.
Thanks!
-Qiuxu
> -Original Message-
> From: Zhuo, Qiuxu
> Sent: Monday, February 22, 2021 9:17 AM
> To: Bjorn Helgaas
> Cc: Zhuo, Qiuxu ; Lorenzo Pieralisi
> ; Krzysztof Wilczyński ; Kelley,
>
On Thu, Mar 04, 2021 at 02:42:50PM -0800, Darrick J. Wong wrote:
> My vision here, however, is to establish upcalls for /both/ types of
> stroage.
I already have patches for doing these kinds of callbacks properly
for the block layer. They will be posted shortly.
On Thu, Mar 4, 2021 at 5:47 AM 'Nick Desaulniers' via Clang Built
Linux wrote:
>
> + Sami
>
> On Wed, Mar 3, 2021 at 10:34 AM Masahiro Yamada wrote:
> >
> > This guarding is wrong. As Documentation/kbuild/llvm.rst notes, LLVM=1
> > switches the default of tools, but you can still override CC,
Hi Vitaly:
Thanks for your review.
On 3/4/2021 12:27 AM, Vitaly Kuznetsov wrote:
Tianyu Lan writes:
From: Tianyu Lan
Add visibility parameter for vmbus_establish_gpadl() and prepare
to change host visibility when create gpadl for buffer.
"No functional change" as you don't actually
> On Mar 4, 2021, at 11:49 PM, Christophe Leroy
> wrote:
>
>
>
> Le 05/03/2021 à 02:43, angkery a écrit :
>> From: Junlin Yang
>> ibmvnic_remove locks multiple spinlocks while disabling interrupts:
>> spin_lock_irqsave(>state_lock, flags);
>> spin_lock_irqsave(>rwi_lock, flags);
>> there
On Wed, Feb 24, 2021 at 7:53 PM Rasmus Villemoes
wrote:
>
> It can be quite useful to have ld emit a link map file, in order to
> debug or verify that special sections end up where they are supposed
> to, and to see what LD_DEAD_CODE_DATA_ELIMINATION manages to get rid
> of.
>
> The only reason
From: Wong Vee Khee
Issue seen when enumerating multiple Intel mGbE interfaces in EHL.
[6.898141] intel-eth-pci :00:1d.2: enabling device ( -> 0002)
[6.900971] intel-eth-pci :00:1d.2: Fail to register stmmac-clk
[6.906434] intel-eth-pci :00:1d.2: User ID: 0x51,
From: Rafał Miłecki
1. Use meaningful variable names (e.g. "flash_start", "res_size" instead
of e.g. "iobase", "end")
2. Always operate on "offset" instead of mix of start, end, size, etc.
3. Add helper checking for NVRAM to avoid duplicating code
4. Use "found" variable instead of goto
5.
> On 24-Feb-2021, at 5:51 PM, Thadeu Lima de Souza Cascardo
> wrote:
>
> EBB events must be under exclusive groups, so there is no mix of EBB and
> non-EBB events on the same PMU. This requirement worked fine as perf core
> would not allow other pinned events to be scheduled together with
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 280d542f6ffac0e6d65dc267f92191d509b13b64
commit: 7dffe01765d9309b8bd5505503933ec0ec53d192 rcu: Add
lockdep_assert_irqs_disabled() to raw_spin_unlock_rcu_node() macros
date: 8 weeks ago
config:
Le 05/03/2021 à 02:43, angkery a écrit :
From: Junlin Yang
ibmvnic_remove locks multiple spinlocks while disabling interrupts:
spin_lock_irqsave(>state_lock, flags);
spin_lock_irqsave(>rwi_lock, flags);
there is no need for the second irqsave,since interrupts are disabled
at that point, so
On 2021/3/4 17:15, Jason Wang wrote:
On 2021/3/4 9:59 上午, Jie Deng wrote:
Add an I2C bus driver for virtio para-virtualization.
The controller can be emulated by the backend driver in
any device model software by following the virtio protocol.
The device specification can be found on
From: Junlin Yang
ibmvnic_remove locks multiple spinlocks while disabling interrupts:
spin_lock_irqsave(>state_lock, flags);
spin_lock_irqsave(>rwi_lock, flags);
there is no need for the second irqsave,since interrupts are disabled
at that point, so remove the second irqsave:
On 2/23/2021 1:09 PM, Stephen Boyd wrote:
Quoting Rajendra Nayak (2021-02-11 23:28:41)
Add the compatible string for sc7180 SoC from Qualcomm
Signed-off-by: Rajendra Nayak
---
Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.txt | 1 +
Is this being YAML-ified at some
For Intel mGbE controller, MAC VLAN filter delete operation will time-out
if serdes power-down sequence happened first during driver remove() with
below message.
[82294.764958] intel-eth-pci :00:1e.4 eth2: stmmac_dvr_remove: removing
driver
[82294.778677] intel-eth-pci :00:1e.4 eth2:
On 3/4/2021 5:43 AM, Stephen Boyd wrote:
Quoting Rajendra Nayak (2021-03-03 04:17:57)
From: Maulik Shah
Add cpuidle states for little and big cpus.
Please also say "The latency values are preliminary placeholders and will be
updated
once testing provides the real numbers".
will do
On 3/4/2021 5:42 AM, Stephen Boyd wrote:
Quoting Rajendra Nayak (2021-03-03 04:17:56)
diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi
b/arch/arm64/boot/dts/qcom/sc7280.dtsi
index fe4fdb9..aa6f847 100644
--- a/arch/arm64/boot/dts/qcom/sc7280.dtsi
+++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi
X.25 Layer 3 (the Packet Layer) expects layer 2 to provide a reliable
datalink service such that no packets are reordered or dropped. And
X.25 Layer 2 (the LAPB layer) is indeed designed to provide such service.
However, this reliability is not preserved when a driver calls "netif_rx"
to deliver
On 3/4/2021 5:34 AM, Stephen Boyd wrote:
Quoting Rajendra Nayak (2021-03-03 04:17:49)
diff --git a/arch/arm64/boot/dts/qcom/sc7280.dtsi
b/arch/arm64/boot/dts/qcom/sc7280.dtsi
index 4a56d9c..21c2399 100644
--- a/arch/arm64/boot/dts/qcom/sc7280.dtsi
+++ b/arch/arm64/boot/dts/qcom/sc7280.dtsi
According to latest errata of J721e [1], HS400 mode is not supported
in MMCSD0 subsystem (i2024) and SDR104 mode is not supported in MMCSD1/2
subsystems (i2090). Therefore, replace mmc-hs400-1_8v with mmc-hs200-1_8v
in MMCSD0 subsystem and add a sdhci mask to disable SDR104 speed mode.
Also,
On Thu, Mar 04, 2021 at 09:40:49AM -0500, Steven Rostedt wrote:
> On Thu, 4 Mar 2021 15:15:24 +0530
> Vamshi K Sthambamkadi wrote:
>
> Not anything to do with you. I have a set of fixes that I have queued that
> requires a ~13 hour test to run before I push off to Linus. When it was
> almost
On Fri, Mar 5, 2021 at 1:58 AM Josh Triplett wrote:
> On Wed, Mar 03, 2021 at 12:53:18PM -0800, Linus Torvalds wrote:
> > One additional reason for this note is that I want to not just warn
> > people to not run this if you have a swapfile - even if you are
> > personally not impacted (like I
Convert power key bindings from .txt to .yaml format.
Signed-off-by: satya priya
---
.../bindings/input/qcom,pm8941-pwrkey.txt | 53 ---
.../bindings/input/qcom,pm8941-pwrkey.yaml | 76 ++
2 files changed, 76 insertions(+), 53 deletions(-)
From: David Collins
On Qualcomm Technologies, Inc. PMIC PMK8350, the PON peripheral
is split into two peripherals: PON_HLOS and PON_PBS. The
application processor only has write access to PON_HLOS which
limits it to only receiving PON interrupts.
Add support for the PMK8350 PON_HLOS peripheral
From: David Collins
Add power key and resin compatible strings for the PMK8350 PMIC.
These are needed to distinguish key PON_HLOS register differences
between PMK8350 and previous PMIC PON modules.
Signed-off-by: David Collins
Signed-off-by: satya priya
---
David Collins (2):
input: pm8941-pwrkey: add support for PMK8350 PON_HLOS PMIC peripheral
dt-bindings: input: pm8941-pwrkey: Add pmk8350 compatible strings
satya priya (1):
dt-bindings: input: pm8941-pwrkey: Convert power key bindings to yaml
.../bindings/input/qcom,pm8941-pwrkey.txt
On 3/5/21 10:54 AM, Anshuman Khandual wrote:
> This series fixes pfn_valid() for ZONE_DEVICE based memory and also improves
> its performance for normal hotplug memory. While here, it also reorganizes
> pfn_valid() on CONFIG_SPARSEMEM. This series is based on v5.12-rc1.
>
> Cc: Catalin Marinas
Hi Nishanth,
On 05/03/21 10:44 am, Nishanth Menon wrote:
> On 10:59-20210301, Kishon Vijay Abraham I wrote:
>> On 25/02/21 6:57 pm, Aswath Govindraju wrote:
>>> According to latest errata of J721e [1], HS400 mode is not supported
>>> in MMCSD0 subsystem (i2024) and SDR104 mode is not supported in
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 280d542f6ffac0e6d65dc267f92191d509b13b64
commit: 2f78788b55baa3410b1ec91a576286abe1ad4d6a ilog2: improve ilog2 for
constant arguments
date: 3 months ago
config: mips-randconfig-m031-20210305 (attached as
On Thu 04 Mar 16:34 CST 2021, Alex Elder wrote:
> Replace the use of C bit-fields in the rmnet_map_ul_csum_header
> structure with a single two-byte (big endian) structure member,
> and use field masks to encode or get values within it.
>
> Previously rmnet_map_ipv4_ul_csum_header() would update
There are multiple instances of pfn_to_section_nr() and __pfn_to_section()
when CONFIG_SPARSEMEM is enabled. This can be optimized if memory section
is fetched earlier. This replaces the open coded PFN and ADDR conversion
with PFN_PHYS() and PHYS_PFN() helpers. While there, also add a comment.
pfn_valid() validates a pfn but basically it checks for a valid struct page
backing for that pfn. It should always return positive for memory ranges
backed with struct page mapping. But currently pfn_valid() fails for all
ZONE_DEVICE based memory types even though they have struct page mapping.
1 - 100 of 1321 matches
Mail list logo