Fixes the following W=1 kernel build warning(s):
drivers/crypto/hisilicon/sec/sec_drv.c:843: warning: Function parameter or
member 'queue' not described in 'sec_queue_empty'
Cc: Herbert Xu
Cc: "David S. Miller"
Cc: Zaibo Xu
Cc: Jonathan Cameron
Cc: linux-cry...@vger.kernel.org
Signed-off-by
On 3/2/21 7:35 PM, Mathieu Poirier wrote:
> On Fri, Feb 19, 2021 at 12:14:51PM +0100, Arnaud Pouliquen wrote:
>> Move the code related to the rpmsg_ctrl char device to the new
>> rpmsg_ctrl.c module.
>> Manage the dependency in the kconfig.
>>
>> Signed-off-by: Arnaud Pouliquen
>> ---
>> drive
On Wed, 3 Mar 2021 11:25:58 +0100
Petr Mladek wrote:
> Alternative solution would be to minimize the information, for
> example, by printing only the modules that appear in the backtrace.
> But this might be complicated to implement.
It could be a list after the backtrace perhaps, and not part o
On Wed, Mar 03, 2021 at 11:46:55AM +0800, Chengming Zhou wrote:
> This patch series is RESEND of the previous patches on psi subsystem. A few
> weeks passed since the last review, so I put them together and resend for
> more convenient review and merge.
>
> Patch 1 add PSI_CPU_FULL state means all
Applied. Thanks!
Alex
On Wed, Mar 3, 2021 at 2:42 AM Christian König wrote:
>
> Am 03.03.21 um 01:27 schrieb Colin King:
> > From: Colin Ian King
> >
> > Currently the ioctl command RADEON_INFO_SI_BACKEND_ENABLED_MASK can
> > copy back uninitialised data in value_tmp that pointer *value points
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
This is set 1 of 2 sets required to fully clean Crypto.
No functional changes since v1.
Lee Jones (10):
crypto: hisilicon: sec_drv: Supply missi
Fixes the following W=1 kernel build warning(s):
drivers/scsi/lpfc/lpfc_hbadisc.c:1505: warning: expecting prototype for
lpfc_update_fcf_record(). Prototype was for __lpfc_update_fcf_record() instead
Cc: James Smart
Cc: Dick Kennedy
Cc: "James E.J. Bottomley"
Cc: "Martin K. Petersen"
Cc: li
Build a local laundry list in sgx_init(), and transfer its ownsership to
ksgxd for sanitization, thus getting rid of useless member in struct
sgx_epc_section.
Signed-off-by: Jarkko Sakkinen
---
arch/x86/kernel/cpu/sgx/main.c | 64 ++
arch/x86/kernel/cpu/sgx/sgx.h
If sgx_page_cache_init() fails in the middle, a trivial return statement
causes unused memory and virtual address space reserved for the EPC
section, not freed. Fix this by using the same rollback, as when
sgx_page_reclaimer_init() fails.
Cc: sta...@vger.kernel.org # 5.11
Fixes: e7e0545299d8 ("x86
Replace the ad-hoc code with a sgx_free_epc_page(), in order to make sure
that all the relevant checks and book keeping is done, while freeing a
borrowed EPC page.
Signed-off-by: Jarkko Sakkinen
---
arch/x86/kernel/cpu/sgx/main.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff
Background
==
EPC section is covered by one or more SRAT entries that are associated with
one and only one PXM (NUMA node). The motivation behind this patch is to
provide basic elements of building allocation scheme based on this premise.
Solution
Use phys_to_target_node() to as
On 2021-03-03 01:48, Nitin Gupta wrote:
-Original Message-
From: pintu=codeaurora@mg.codeaurora.org
On Behalf Of Pintu Kumar
Sent: Tuesday, March 2, 2021 9:56 AM
To: linux-kernel@vger.kernel.org; a...@linux-foundation.org; linux-
m...@kvack.org; linux-fsde...@vger.kernel.org; pi...@c
Background
==
EPC section is covered by one or more SRAT entries that are associated with
one and only one PXM (NUMA node). The current implementation overheats a
single NUMA node, because sgx_alloc_epc_page() always starts looking for
pages from the same EPC section everytime.
Only withi
Fixes the following W=1 kernel build warning(s):
drivers/scsi/megaraid/megaraid_mbox.c:1438: warning: expecting prototype for
megaraid_queue_command(). Prototype was for megaraid_queue_command_lck() instead
Cc: Kashyap Desai
Cc: Sumit Saxena
Cc: Shivasharan S
Cc: "James E.J. Bottomley"
Cc:
Christian Brauner wrote:
> In order to answer this more confidently I need to know a bit more about
> how cachefiles are supposed to work.
>
> From what I gather here it seemed what this code is trying to set here
> is an internal "CacheFiles.cache" extended attribute on the indode. This
> exten
Fixes the following W=1 kernel build warning(s):
drivers/scsi/megaraid/megaraid_mm.c:505: warning: expecting prototype for
mraid_mm_attch_buf(). Prototype was for mraid_mm_attach_buf() instead
Cc: Kashyap Desai
Cc: Sumit Saxena
Cc: Shivasharan S
Cc: "James E.J. Bottomley"
Cc: "Martin K. Pet
-randconfig-s031-20210303 (attached as .config)
compiler: riscv32-linux-gcc (GCC) 9.3.0
reproduce:
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
# apt-get install sparse
# sparse version
Linus,
The following changes since commit 2df8d3807ce7f75bb975f1aeae8fc6757527c62d:
KVM: SVM: Fix nested VM-Exit on #GP interception handling (2021-02-25
05:13:05 -0500)
are available in the Git repository at:
https://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
for you to fetch
This set is part of a larger effort attempting to clean-up W=1
kernel builds, which are currently overwhelmingly riddled with
niggly little warnings.
Lee Jones (30):
scsi: megaraid: megaraid_mm: Fix incorrect function name in header
scsi: megaraid: megaraid_sas_base: Fix a bunch of misnamed fu
On Tue, Feb 23, 2021 at 3:36 AM Jian Cai wrote:
> This patch adds CONFIG_HARDEN_SLS_ALL that can be used to turn on
> -mharden-sls=all, which mitigates the straight-line speculation
> vulnerability, speculative execution of the instruction following some
> unconditional jumps. Notice -mharden-sls
Hi Suzuki,
On Wed, 3 Mar 2021 at 10:09, Suzuki K Poulose wrote:
>
> On 1/28/21 5:09 PM, Mike Leach wrote:
> > Creates an system management API to allow complex configurations and
> > features to be programmed into a CoreSight infrastructure.
> >
> > A feature is defined as a programming set for a
On 2/17/21 10:40 PM, Lizhi Hou wrote:
> Add ICAP driver. ICAP is a hardware function discovered by walking
What does ICAP stand for ?
> firmware metadata. A platform device node will be created for it.
> FPGA bitstream is written to hardware through ICAP.
>
> Signed-off-by: Sonal Santan
> Signed
Hi Minchan,
I love your patch! Yet something to improve:
[auto build test ERROR on block/for-next]
[also build test ERROR on linux/master linus/master v5.12-rc1 next-20210303]
[cannot apply to hnaz-linux-mm/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
On Thu, Feb 18, 2021 at 11:16:49AM +0800, qiang.zh...@windriver.com wrote:
> From: Zqiang
>
> The debug_work_activate() is called on the premise that
> the work can be inserted, because if wq be in WQ_DRAINING
> status, insert work may be failed.
>
> Fixes: e41e704bc4f4 ("workqueue: improve dest
On Wed, Mar 03, 2021 at 05:39:56PM +0800, Muchun Song wrote:
> For simplification 991e7673859e ("mm: memcontrol: account kernel stack
> per node") has changed the per zone vmalloc backed stack pages
> accounting to per node. By doing that we have lost a certain precision
> because those pages might
On Tue, Feb 23, 2021 at 11:05 AM Will Deacon wrote:
> On Mon, Feb 22, 2021 at 01:50:06PM -0800, Jian Cai wrote:
> > I am not sure if there are any plans to protect assembly code and I
> > will leave it to the Arm folks since they know a whole lot better. But
> > even without that part, we should s
On Wed, 03 Mar 2021 14:22:02 +,
Pali Rohár wrote:
>
> IRQ domain alloc function should return zero on success. Non-zero value
> indicates failure.
>
> Signed-off-by: Pali Rohár
> Fixes: fc54bae28818 ("PCI: iproc: Allow allocation of multiple MSIs")
> ---
> drivers/pci/controller/pcie-iproc
On Wed, 3 Mar 2021 at 00:58, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.178 release.
> There are 246 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.
>
> Re
Fixes the following W=1 kernel build warning(s):
drivers/scsi/aic94xx/aic94xx_dump.c:731: warning: expecting prototype for
asd_dump_ddb_site(). Prototype was for asd_dump_target_ddb() instead
drivers/scsi/aic94xx/aic94xx_dump.c:875: warning: expecting prototype for
ads_dump_seq_state(). Protot
Le 03/03/2021 à 15:17, Philipp Zabel a écrit :
Hi Benjamin,
On Mon, 2021-03-01 at 16:17 +0100, Benjamin Gaignard wrote:
The two VPUs inside IMX8MQ share the same control block which can be see
as a reset hardware block.
This isn't a reset controller though. The control block also contains
cl
On Wed, Mar 03, 2021 at 06:56:38AM -0800, Guenter Roeck wrote:
> On 3/3/21 6:05 AM, Greg Kroah-Hartman wrote:
> [ ... ]
> >> Anyway, that's the convention or consensus so far for entire SoC. If we
> >> want to change it - sure, but let's make it for everyone, not for just
> >> this one USB driver.
On Wed, Mar 03, 2021 at 03:52PM +0100, Christophe Leroy wrote:
> Le 03/03/2021 à 15:38, Marco Elver a écrit :
> > On Wed, 3 Mar 2021 at 15:09, Christophe Leroy
> > wrote:
> > >
> > > It seems like all other sane architectures, namely x86 and arm64
> > > at least, include the running function as t
For simplification 991e7673859e ("mm: memcontrol: account kernel stack
per node") has changed the per zone vmalloc backed stack pages
accounting to per node. By doing that we have lost a certain precision
because those pages might live in different NUMA nodes. In the end
NR_KERNEL_STACK_KB exported
On Wed, Mar 3, 2021 at 8:43 AM Lee Jones wrote:
>
> None of the surrounding code was removed just in case even a small
> fraction of it was functional.
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/../display/dc/bios/command_table.c: In function
> ‘adjust_di
On Wed, Mar 3, 2021 at 8:43 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> drivers/gpu/drm/amd/amdgpu/../display/dc/bios/command_table.c: In function
> ‘adjust_display_pll_v2’:
> drivers/gpu/drm/amd/amdgpu/../display/dc/bios/command_table.c:1462:11:
> warning: unu
On Wed 2021-03-03 15:34:09, Petr Mladek wrote:
> Hi,
>
> the following warning is filling my kernel log buffer
> with 5.12-rc1+ kernels:
>
> [ 941.070598] WARNING: CPU: 0 PID: 11 at drivers/gpu/drm/ttm/ttm_bo.c:139
> ttm_bo_move_to_lru_tail+0x1ba/0x210
> [ 941.070601] Modules linked in:
> [ 9
On Wed, Mar 3, 2021 at 8:44 AM Lee Jones wrote:
>
> Fixes the following W=1 kernel build warning(s):
>
> In file included from
> drivers/gpu/drm/amd/amdgpu/../display/dc/dce112/dce112_resource.c:59:
>
> drivers/gpu/drm/amd/amdgpu/../include/asic_reg/dce/dce_11_2_sh_mask.h:10014:58:
> warning:
On Mon, 2021-03-01 at 16:17 +0100, Benjamin Gaignard wrote:
> IMX8MQ SoC got a dedicated hardware block to reset the video processor
> units (G1 and G2).
>
> Signed-off-by: Benjamin Gaignard
> ---
> drivers/reset/Kconfig| 8 ++
> drivers/reset/Makefile | 1 +
> drivers/
This series contains support to get basic metricgroups working for
arm64 CPUs.
Initial support is added for HiSilicon hip08 platform.
Some sample usage on Huawei D06 board:
$ ./perf list metric
List of pre-defined events (to be used in -e):
Metrics:
bp_misp_flush
[BP misp
On Tue, 2 Mar 2021 15:43:22 -0500
Tony Krowiak wrote:
> This patch fixes a lockdep splat introduced by commit f21916ec4826
> ("s390/vfio-ap: clean up vfio_ap resources when KVM pointer invalidated").
> The lockdep splat only occurs when starting a Secure Execution guest.
> Crypto virtualization
through power supply property
> > POWER_SUPPLY_PROP_INPUT_CURRENT_LIMIT.
> >
> > Ray Chi (2):
> > usb: dwc3: add a power supply for current control
> > usb: dwc3: add an alternate path in vbus_draw callback
>
> While using next-20210303 this patchset leads to the following kernel crash
> on
On Wed, Mar 3, 2021 at 3:23 PM Álvaro Fernández Rojas wrote:
> v3: introduce new files for shared code and add more changes suggested by
> Linus Walleij. Also add a new patch needed for properly parsing gpio-ranges.
This looks very appetizing, I am ready to merge this once we cut some
slack for
Making it possible for the drivers to assign complete
software fwnodes to the devices instead of only the device
properties in those nodes.
Signed-off-by: Heikki Krogerus
---
drivers/spi/spi.c | 13 +++--
include/linux/spi/spi.h | 5 -
2 files changed, 15 insertions(+), 3 dele
On Wed, 3 Mar 2021 at 00:58, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.223 release.
> There are 175 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.
>
> Re
On Wed, 3 Mar 2021 at 14:55, 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 operations are common. The RPMB partition
> cannot be accessed via standard block
When device properties are supplied to the devices, in
reality a software fwnode that holds those properties is
created which is then assigned to the device. If the device
properties are constant the software node can also be
constant.
Signed-off-by: Heikki Krogerus
Cc: Daniel Mack
Cc: Haojian Z
From: Linus Walleij
> Sent: 03 March 2021 15:19
>
> On Tue, Feb 23, 2021 at 11:05 AM Will Deacon wrote:
> > On Mon, Feb 22, 2021 at 01:50:06PM -0800, Jian Cai wrote:
> > > I am not sure if there are any plans to protect assembly code and I
> > > will leave it to the Arm folks since they know a wh
On Wed, Mar 3, 2021 at 4:29 PM David Laight wrote:
> > On Tue, Feb 23, 2021 at 11:05 AM Will Deacon wrote:
> > I wrote some suggestions on follow-ups in my reply, and I can
> > help out doing some of the patches, I think.
> >
> > Since ARM32 RET is mov pc, <>
> > git grep 'mov.*pc,' | wc -l give
Hi,
The older API used to supply additional device properties for the
devices - so mainly the function device_add_properties() - is going to
be removed. The reason why the API will be removed is because it gives
false impression that the properties are assigned directly to the
devices, which has a
From: "Wong, Vee Khee"
For interrupt mode INTM=0, TX/RX transfer complete will trigger signal
not only on sbd_perch_[tx|rx]_intr_o (Transmit/Receive Per Channel) but
also on the sbd_intr_o (Common).
As for multi-MSI implementation, setting interrupt mode INTM=1 is more
efficient as each TX intr
It was discovered that find_autofs_mount() function
in autofs not support cases when autofs mount
parent is overmounted. In this case this function will
always return -ENOENT.
Real-life reproducer is fairly simple.
Consider the following mounts on root mntns:
--
35 24 0:36 / /proc/sys/fs/binfmt_mi
From: Ong Boon Leong
Now we introduce MSI interrupt service routines and hook these routines
up if stmmac_open() sees valid irq line being requested:-
stmmac_mac_interrupt():- MAC (dev->irq), WOL (wol_irq), LPI (lpi_irq)
stmmac_safety_interrupt() :- Safety Feat Correctible Error (sfty_ce_irq
From: Ong Boon Leong
Intel mgbe controller supports multi-vector interrupts:
msi_rx_vec 0,2,4,6,8,10,12,14
msi_tx_vec 1,3,5,7,9,11,13,15
msi_sfty_ue_vec 26
msi_sfty_ce_vec 27
msi_lpi_vec 28
msi_mac_vec 29
During probe(), the driver will starts with request allocation for
multi-
On Wed, Mar 03, 2021 at 09:59:11AM -0500, Johannes Weiner wrote:
> On Wed, Mar 03, 2021 at 11:46:55AM +0800, Chengming Zhou wrote:
> > This patch series is RESEND of the previous patches on psi subsystem. A few
> > weeks passed since the last review, so I put them together and resend for
> > more c
Use find_cpumap() to get the cpumap for the common CPU PMU, if one exists.
Signed-off-by: John Garry
---
tools/perf/util/metricgroup.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/tools/perf/util/metricgroup.c b/tools/perf/util/metricgroup.c
index 9a2a23093961..c7c9ee9c0
Add L3 metrics.
Signed-off-by: John Garry
---
.../arch/arm64/hisilicon/hip08/metrics.json | 161 ++
1 file changed, 161 insertions(+)
diff --git a/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/metrics.json
b/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/metrics.json
ind
Calling perf_pmu__find_map(NULL) returns the cpumap for the common CPU
PMU. However arm64 supports heterogeneous-CPU based systems, and so there
may be no common CPU PMU. As such, perf_pmu__find_map(NULL) returns NULL
for arm64.
To support printing metrics for arm64, iterate through all PMUs, look
On Wed, Mar 03, 2021 at 07:43:57AM +0100, Jiri Slaby wrote:
> Commit 8382c668ce4f ("x86/vdso: Add support for exception fixup in vDSO
> functions") added a printf of len which is size_t. Compilers now
> complain on 32b:
> In file included from arch/x86/entry/vdso/vdso2c.c:162:
> arch/x86/entry/vdso
Add L2 metrics.
Signed-off-by: John Garry
---
.../arch/arm64/hisilicon/hip08/metrics.json | 42 +++
1 file changed, 42 insertions(+)
diff --git a/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/metrics.json
b/tools/perf/pmu-events/arch/arm64/hisilicon/hip08/metrics.json
inde
When device properties are supplied to the devices, in
reality a software fwnode that holds those properties is
created which is then assigned to the device. If the device
properties are constant the software node can also be
constant.
Signed-off-by: Heikki Krogerus
Cc: Daniel Mack
Cc: Haojian Z
>From now on only accepting complete software nodes.
Signed-off-by: Heikki Krogerus
---
drivers/spi/spi.c | 24 +++-
include/linux/spi/spi.h | 4
2 files changed, 3 insertions(+), 25 deletions(-)
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
index 9b46998ae2
On Wed, 3 Mar 2021 at 08:23, Liu Ying wrote:
>
> Hi Robert,
>
> On Tue, 2021-03-02 at 15:22 +0100, Robert Foss wrote:
> > Hey Liu,
> >
> > Thanks for submitting this patch.
>
> Thanks for reviewing this patch.
>
> >
> > On Thu, 18 Feb 2021 at 04:59, Liu Ying wrote:
> > > This patch adds a helper
Add L1 metrics. Formula is as consistent as possible with standard.
Signed-off-by: John Garry
---
.../arch/arm64/hisilicon/hip08/metrics.json | 30 +++
1 file changed, 30 insertions(+)
create mode 100644
tools/perf/pmu-events/arch/arm64/hisilicon/hip08/metrics.json
diff --gi
On Wed 2021-03-03 11:15:13, John Ogness wrote:
> Hello,
>
> Here is v4 of a series to remove @logbuf_lock, exposing the
> ringbuffer locklessly to both readers and writers. v3 is
> here [0].
The series look ready. I am going to push it into printk/linux.git
the following week unless anyone speaks
This patchset adds support for multi MSI interrupts in addition to
current single common interrupt implementation. Each MSI interrupt is tied
to a newly introduce interrupt service routine(ISR). Hence, each interrupt
will only go through the corresponding ISR.
In order to increase the efficiency,
From: Ong Boon Leong
Refactor stmmac_interrupt() by introducing stmmac_common_interrupt()
so that we prepare the ISR operation to be friendly to MSI later.
Signed-off-by: Ong Boon Leong
Signed-off-by: Voon Weifeng
---
.../net/ethernet/stmicro/stmmac/stmmac_main.c | 59 +++
1 f
From: Ong Boon Leong
In preparation to make stmmac support multi-vector MSI, we introduce the
interrupt status masking according to RX, TX or RXTX. Default to use RXTX
inside stmmac_dma_interrupt(), so there is no run-time logic difference
now.
Signed-off-by: Ong Boon Leong
Signed-off-by: Voon
On Wed, Mar 3, 2021 at 3:23 PM Álvaro Fernández Rojas wrote:
> This is needed for properly registering gpio regmap as a child of a regmap
> pin controller.
>
> Signed-off-by: Álvaro Fernández Rojas
> ---
> v3: introduce patch needed for properly parsing gpio-ranges.
Oops a little bug. I sugges
On 2021-02-22 10:15 a.m., syzbot wrote:
Hello,
syzbot found the following issue on:
HEAD commit:29ad81a1 arch/x86: add missing include to sparsemem.h
git tree: https://github.com/google/kmsan.git master
console output: https://syzkaller.appspot.com/x/log.txt?x=111e6312d0
kernel co
On 03/03, Sebastian Andrzej Siewior wrote:
>
> +static struct sigqueue *sigqueue_from_cache(struct task_struct *t)
> +{
> + struct sigqueue *q = t->sigqueue_cache;
> +
> + if (q && cmpxchg(&t->sigqueue_cache, q, NULL) == q)
> + return q;
> + return NULL;
> +}
> +
> +static b
On Tue, Mar 2, 2021 at 5:26 PM Vivek Goyal wrote:
> > I still feel that it should probably be fixed in virtiofsd, given fuse
> > client
> > is expecting file server to take care of any change of mode (file
> > permission bits).
>
> Havid said that, there is one disadvantage of relying on server
Am 2021-03-03 16:27, schrieb Linus Walleij:
On Wed, Mar 3, 2021 at 3:23 PM Álvaro Fernández Rojas
wrote:
This is needed for properly registering gpio regmap as a child of a
regmap
pin controller.
Signed-off-by: Álvaro Fernández Rojas
---
v3: introduce patch needed for properly parsing gpi
On 03/03/2021 15:05, Greg Kroah-Hartman wrote:
On Wed, Mar 03, 2021 at 11:38:39AM +0100, Krzysztof Kozlowski wrote:
This is so far component of a SoC, so it cannot be re-used outside of
SoC. Unless it appears in a new SoC (just like recent re-use of Samsung
serial driver for Apple M1). Because o
On Mon 2021-02-22 13:39:56, Matthew Wilcox wrote:
> On Mon, Feb 22, 2021 at 01:38:17PM +0100, Petr Mladek wrote:
> > Another question where to push this change. It is pity the we
> > finalized it in the middle of the merge window. It has to spend
> > at least few days in linux-next.
> >
> > I woul
Em Sun, Jan 31, 2021 at 11:27:08PM +0100, Jiri Olsa escreveu:
> On Thu, Jan 28, 2021 at 09:34:17AM +0800, Jin Yao wrote:
> > Uncore becomes die-scope on Xeon Cascade Lake-AP and perf has supported
> > --per-die aggregation yet.
> >
> > One issue is found in check_per_pkg() for uncore events runnin
On 03/03/2021 16:09, Greg Kroah-Hartman wrote:
On Wed, Mar 03, 2021 at 06:56:38AM -0800, Guenter Roeck wrote:
On 3/3/21 6:05 AM, Greg Kroah-Hartman wrote:
[ ... ]
Anyway, that's the convention or consensus so far for entire SoC. If we
want to change it - sure, but let's make it for everyone, no
> For error address with sigbus, i think this is not an issue resulted by the
> patch i post, before my patch, the issue is already there.
> I don't find a realizable way to get the correct address for same reason ---
> we don't know whether the page mapping is there or not when
> we got to kill_
According to the revised binding, the devicetree needs a board-specific
compatible string.
Signed-off-by: Jonathan Neuschäfer
---
v2:
- no changes
---
arch/arm/boot/dts/nuvoton-npcm750-evb.dts | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/nuvoton-npcm750-
Ilya Lipnitskiy writes:
> On Tue, Mar 2, 2021 at 11:37 AM Eric W. Biederman
> wrote:
>>
>> Ilya Lipnitskiy writes:
>>
>> > On Mon, Mar 1, 2021 at 12:43 PM Eric W. Biederman
>> > wrote:
>> >>
>> >> Ilya Lipnitskiy writes:
>> >>
>> >> > Eric, All,
>> >> >
>> >> > The following error appears w
Hi Abhishek,
> During suspend, there are a few scan enable and set event filter
> commands that don't need to be sent unless there are actual BR/EDR
> devices capable of waking the system. Check the HCI_PSCAN bit before
> writing scan enable and use a new dev flag, HCI_EVENT_FILTER_CONFIGURED
> to
Em Tue, Mar 02, 2021 at 02:03:05PM +0100, Jiri Olsa escreveu:
> On Tue, Mar 02, 2021 at 10:50:15AM +0900, Namhyung Kim wrote:
>
> SNIP
>
> > > > err = -ENOMEM;
> > > > pr_debug("Not enough memory to create thread/cpu maps\n");
> > > > - goto out_free_maps;
On Tue, Mar 02 2021 at 20:06, Feng Tang wrote:
> On Tue, Mar 02, 2021 at 10:16:37AM +0100, Peter Zijlstra wrote:
>> On Tue, Mar 02, 2021 at 10:54:24AM +0800, Feng Tang wrote:
>> > clocksource watchdog runs every 500ms, which creates some OS noise.
>> > As the clocksource wreckage (especially for th
- Original Message -
> This patch removes unneeded return variables, using only
> '0' instead.
> It fixes the following warning detected by coccinelle:
> ./fs/gfs2/super.c:592:5-10: Unneeded variable: "error". Return "0" on
> line 628
>
> Reported-by: Abaci Robot
> Signed-off-by: Yang Li
Hello,
On Tue, Mar 02, 2021 at 12:17:04AM -0800, Vipin Sharma wrote:
> +/**
> + * struct misc_res: Per cgroup per misc type resource
> + * @max: Maximum count of the resource.
> + * @usage: Current usage of the resource.
> + */
> +struct misc_res {
> + unsigned int max;
> + atomic_t usage;
-Original Message-
From: Sergei Trofimovich [mailto:sly...@gmail.com]
Sent: Tuesday, March 2, 2021 6:23 PM
To: John Paul Adrian Glaubitz ; Don Brace -
C33706
Cc: linux-i...@vger.kernel.org; linux-kernel@vger.kernel.org; Joe Szczypek
; Scott Benesh - C33703 ;
Scott Teel - C33730 ; Tomas
Em Thu, Feb 25, 2021 at 05:12:37PM +0100, Jiri Olsa escreveu:
> On Thu, Feb 25, 2021 at 12:51:47PM +0900, Namhyung Kim wrote:
> > Add the perf_evlist__reset_id_hash() function as an internal function
> > so that it can be called by perf to reset the hash table. This is
> > necessary for perf stat
Em Thu, Feb 25, 2021 at 02:07:00PM +0800, Jiapeng Chong escreveu:
> Fix the following coccicheck warnings:
>
> ./tools/perf/tests/parse-metric.c:101:2-3: Unneeded semicolon.
Thanks, applied.
- Arnaldo
> Reported-by: Abaci Robot
> Signed-off-by: Jiapeng Chong
> ---
> tools/perf/tests/parse-
Hi Linus,
Three urgent fixes for rc2.
/Jarkko
The following changes since commit c03c21ba6f4e95e406a1a7b4c34ef334b977c194:
Merge tag 'keys-misc-20210126' of
git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs (2021-02-23
16:09:23 -0800)
are available in the Git repository at:
Hello,
syzbot found the following issue on:
HEAD commit:7a7fd0de Merge branch 'kmap-conversion-for-5.12' of git://..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=164a74dad0
kernel config: https://syzkaller.appspot.com/x/.config?x=779a2568b654c1c6
das
Em Wed, Feb 24, 2021 at 12:06:46PM +0100, Jiri Olsa escreveu:
> On Wed, Feb 24, 2021 at 04:14:38PM +0900, Namhyung Kim wrote:
> > I'm seeing a build failure when build with address sanitizer.
> > It seems we could write to the name[100] if the var is longer.
> >
> > $ make EXTRA_CFLAGS=-fsanitiz
Commit 5ee759cda51b ("l2tp: use standard API for warning log messages")
changed a number of warnings about invalid packets in the receive path
so that they are always shown, instead of only when a special L2TP debug
flag is set. Even with rate limiting these warnings can easily cause
significant lo
On Wed, Mar 3, 2021 at 7:50 AM Eric W. Biederman wrote:
>
> Ilya Lipnitskiy writes:
>
> > On Tue, Mar 2, 2021 at 11:37 AM Eric W. Biederman
> > wrote:
> >>
> >> Ilya Lipnitskiy writes:
> >>
> >> > On Mon, Mar 1, 2021 at 12:43 PM Eric W. Biederman
> >> > wrote:
> >> >>
> >> >> Ilya Lipnitskiy
Em Wed, Feb 24, 2021 at 02:50:20PM +0100, Jiri Olsa escreveu:
> On Fri, Feb 19, 2021 at 11:09:32AM -0500, Nicholas Fraser wrote:
> > A non-existent build-id used to be treated as all-zero SHA-1 hash.
> > Build-ids are now variable width. A non-existent build-id is an empty
> > string and "perf buil
Hi Minchan,
I love your patch! Yet something to improve:
[auto build test ERROR on block/for-next]
[also build test ERROR on linux/master linus/master v5.12-rc1 next-20210303]
[cannot apply to hnaz-linux-mm/master]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when
Changeset f546ff0c0c07 ("Move our minimum Sphinx version to 1.7")
cleaned up some compatibility issues with previous Sphinx
versions, but it also dropped the PDF margin sets.
Without that, the media documentation won't build fine, as
the margins are too wide to display texts with monospaced
fonts.
On Sat, Feb 27, 2021 at 02:01:23PM -0800, Jacob Pan wrote:
> IOASIDs are used to associate DMA requests with virtual address spaces.
> They are a system-wide limited resource made available to the userspace
> applications. Let it be VMs or user-space device drivers.
>
> This RFC patch introduces a
Pierre-Louis Bossart wrote:
> An unsigned long variable should rely on '%lu' format strings, not '%zd'
>
> Fixes: a1a6a4cf49ece ("iwlwifi: pnvm: implement reading PNVM from UEFI")
> Signed-off-by: Pierre-Louis Bossart
> Acked-by: Luca Coelho
Patch applied to wireless-drivers.git, thanks.
436
On Wed, Mar 3, 2021 at 11:53 PM Peter Zijlstra wrote:
>
> On Wed, Mar 03, 2021 at 11:46:59AM +0800, Chengming Zhou wrote:
> > The commit 36b238d57172 ("psi: Optimize switching tasks inside shared
> > cgroups") only update cgroups whose state actually changes during a
> > task switch only in task p
On Wed, 3 Mar 2021 at 00:58, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.259 release.
> There are 134 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.
>
> Res
Jiri Kosina wrote:
> From: Jiri Kosina
>
> We can't call netif_napi_add() with rxq-lock held, as there is a potential
> for deadlock as spotted by lockdep (see below). rxq->lock is not
> protecting anything over the netif_napi_add() codepath anyway, so let's
> drop it just before calling into N
901 - 1000 of 1879 matches
Mail list logo
