On Thu, May 08, 2025 at 09:48:34AM +0300, Dan Carpenter wrote:
> On Thu, May 08, 2025 at 08:46:04AM +0200, Greg Kroah-Hartman wrote:
> > On Thu, May 08, 2025 at 09:40:26AM +0300, Dan Carpenter wrote:
> > > Hi Greg,
> > >
> > > I'm sorry I forgot to add the:
> > >
> > > Cc: sta...@vger.kernel.org
On Thu, May 08, 2025 at 08:46:04AM +0200, Greg Kroah-Hartman wrote:
> On Thu, May 08, 2025 at 09:40:26AM +0300, Dan Carpenter wrote:
> > Hi Greg,
> >
> > I'm sorry I forgot to add the:
> >
> > Cc: sta...@vger.kernel.org
> >
> > to this patch. Could we backport it to stable, please?
>
> What is
On Thu, May 08, 2025 at 09:40:26AM +0300, Dan Carpenter wrote:
> Hi Greg,
>
> I'm sorry I forgot to add the:
>
> Cc: sta...@vger.kernel.org
>
> to this patch. Could we backport it to stable, please?
What is the git id of it in Linus's tree?
thanks,
greg k-h
On Thu, May 8, 2025 at 12:25 AM Frederic Weisbecker wrote:
>
> Le Wed, May 07, 2025 at 07:26:04PM +0800, Zqiang a écrit :
> > For built with CONFIG_PROVE_RCU=y and CONFIG_PREEMPT_RT=y kernels,
> > Disable BH does not change the SOFTIRQ corresponding bits in
> > preempt_count(), but change current-
Hi Greg,
I'm sorry I forgot to add the:
Cc: sta...@vger.kernel.org
to this patch. Could we backport it to stable, please?
regards,
dan carpenter
On Wed, Apr 23, 2025 at 08:22:05PM +0300, Dan Carpenter wrote:
> The "ret" variable isn't initialized if we don't enter the loop. For
> example, i
This commit introduces a new vmtest.sh runner for vsock.
It uses virtme-ng/qemu to run tests in a VM. The tests validate G2H,
H2G, and loopback. The testing tools from tools/testing/vsock/ are
reused. Currently, only vsock_test is used.
VMCI and hyperv support is automatically built, though not u
Document the "byte_size" and "type_string" kABI stability rules.
Signed-off-by: Sami Tolvanen
---
Documentation/kbuild/gendwarfksyms.rst | 97 --
1 file changed, 92 insertions(+), 5 deletions(-)
diff --git a/Documentation/kbuild/gendwarfksyms.rst
b/Documentation/kbuild/
A data structure can be partially opaque to modules if its
allocation is handled by the core kernel, and modules only need
to access some of its members. In this situation, it's possible
to append new members to the structure without breaking the ABI,
as long as the layout for the original members
Change the gendwarfksyms documentation to use proper chapter,
section, and subsection adornments instead of fragile section
numbers.
Suggested-by: Masahiro Yamada
Signed-off-by: Sami Tolvanen
---
Documentation/kbuild/gendwarfksyms.rst | 44 +-
1 file changed, 22 insertio
In rare situations where distributions must make significant
changes to otherwise opaque data structures that have
inadvertently been included in the published ABI, keeping
symbol versions stable using the existing kABI macros can
become tedious.
For example, Android decided to switch to a newer i
Reduce code duplication by moving kABI rule look-ups to separate
functions.
Signed-off-by: Sami Tolvanen
Reviewed-by: Petr Pavlu
---
scripts/gendwarfksyms/kabi.c | 101 +++
1 file changed, 44 insertions(+), 57 deletions(-)
diff --git a/scripts/gendwarfksyms/kabi
Hi,
While looking deeper into the genksyms hacks that have been
needed during Android's 5.10 and 5.15 GKI lifecycles so far,
we found a few instances that are not covered by the existing
gendwarfksyms kABI stability rules. The first case involved
appending new members to a partially opaque data st
Hi Masahiro,
On Wed, May 7, 2025 at 12:28 PM Masahiro Yamada wrote:
>
> Hmm, renumbering is annoying.
>
> Maybe, better to stop managing section numbers?
>
> For example, see this commit
> 1a4c1c9df72ec266f94631edc59f9f2a9dc5aa8c
Agreed, that looks much better. I'll send v3 that drops the sectio
On 5/7/25 16:21, Shuah Khan wrote:
On 5/7/25 01:23, Masahiro Yamada wrote:
On Wed, May 7, 2025 at 7:07 AM Shuah Khan wrote:
On 5/6/25 05:12, Nicolas Schier wrote:
On Fri, 02 May 2025, Shuah Khan wrote:
When make finds the source tree unclean, it prints a message to run
"make ARCH=x86_64 mr
On 5/7/25 01:23, Masahiro Yamada wrote:
On Wed, May 7, 2025 at 7:07 AM Shuah Khan wrote:
On 5/6/25 05:12, Nicolas Schier wrote:
On Fri, 02 May 2025, Shuah Khan wrote:
When make finds the source tree unclean, it prints a message to run
"make ARCH=x86_64 mrproper" message using the ARCH from
On 5/2/25 06:03, Thomas Weißschuh wrote:
The TAP specification requires that the output begins with a header line.
These headers lines are missing in the timens tests.
Print such a line.
There is no cover letter for this - so I will respond to the first
patch. The TAP information is added by t
On Wed, May 07, 2025 at 07:26:03PM +0800, Zqiang wrote:
> For built with CONFIG_PREEMPT_RT=y kernels, running rcutorture
> tests resulted in the following splat:
>
> [ 68.797425] rcutorture_one_extend_check during change: Current 0x1 To add
> 0x1 To remove 0x0 preempt_count() 0x0
> [ 68.79
On 10/17/24 10:47, John Hubbard wrote:
On 10/17/24 9:33 AM, Shuah Khan wrote:
On 10/16/24 20:01, John Hubbard wrote:
On 10/16/24 1:00 PM, Shuah Khan wrote:
On 10/16/24 04:20, Lorenzo Stoakes wrote:
...
The requirement to do "make headers" is not a keeper. Really.
The reason we added the re
On Sun, Apr 13, 2025 at 05:52:14PM -0500, Ira Weiny wrote:
> Endpoints can now support a single dynamic ram partition following the
> persistent memory partition.
>
> Expand the mode to allow a decoder to point to the first dynamic ram
> partition.
>
> Signed-off-by: Ira Weiny
>
Reviewed-by: F
On 5/6/25 15:34, John Hubbard wrote:
On 5/6/25 2:18 PM, Shuah Khan wrote:
On 5/1/25 05:42, Peter Zijlstra wrote:
On Wed, Oct 16, 2024 at 07:14:34PM -0700, John Hubbard wrote:
On 10/16/24 3:06 PM, Lorenzo Stoakes wrote:
On Wed, Oct 16, 2024 at 02:00:27PM -0600, Shuah Khan wrote:
On 10/16/24 0
On Wed, May 7, 2025 at 2:14 AM Lorenz Bauer wrote:
>
> On Tue, May 6, 2025 at 10:39 PM Andrii Nakryiko
> wrote:
>
> > > + raw_data = mmap(NULL, end, PROT_READ, MAP_PRIVATE, fd, 0);
> > > + if (!ASSERT_NEQ(raw_data, MAP_FAILED, "mmap_btf"))
> >
> > ASSERT_OK_PTR()?
>
> Don't think that
On Sun, Apr 13, 2025 at 05:52:10PM -0500, Ira Weiny wrote:
> Devices which optionally support Dynamic Capacity (DC) are configured
> via mailbox commands. CXL 3.2 section 9.13.3 requires the host to issue
> the Get DC Configuration command in order to properly configure DCDs.
> Without the Get DC
> On May 7, 2025, at 1:23 PM, Willem de Bruijn
> wrote:
>
> !---|
> CAUTION: External Email
>
> |---!
>
> Jon Kohler wrote:
>> Refactor variable names in vhost_net
Jon Kohler wrote:
> Refactor variable names in vhost_net_build_xdp to align with XDP
> terminology, enhancing code clarity and consistency. Additionally,
> reorder variables to follow a reverse Christmas tree structure,
> improving code organization and readability.
>
> This change introduces no f
On Fri, Apr 25, 2025 at 04:11:07PM +0530, Beleswar Padhi wrote:
> The ti_k3_r5_remoteproc.c driver previously hardcoded device memory
> region addresses and names. Change this to use the k3_r5_rproc_mem_data
> structure to store memory information. This aligns with K3 DSP and M4
> drivers, and can
On Fri, Apr 25, 2025 at 04:11:10PM +0530, Beleswar Padhi wrote:
> The ti_k3_m4_remoteproc.c driver previously hardcoded device memory
> region addresses and names. Change this to use the k3_rproc_mem_data
> structure to store memory information. This aligns with DSP and R5
> drivers, and can be ref
On Fri, Apr 25, 2025 at 04:11:10PM +0530, Beleswar Padhi wrote:
> The ti_k3_m4_remoteproc.c driver previously hardcoded device memory
> region addresses and names. Change this to use the k3_rproc_mem_data
> structure to store memory information. This aligns with DSP and R5
> drivers, and can be ref
On 5/7/2025 12:31 PM, Frederic Weisbecker wrote:
> Le Wed, May 07, 2025 at 12:06:29PM -0400, Joel Fernandes a écrit :
>>
>>
>> On 5/7/2025 7:26 AM, Zqiang wrote:
>>> For built with CONFIG_PROVE_RCU=y and CONFIG_PREEMPT_RT=y kernels,
>>> Disable BH does not change the SOFTIRQ corresponding bits i
Le Wed, May 07, 2025 at 12:06:29PM -0400, Joel Fernandes a écrit :
>
>
> On 5/7/2025 7:26 AM, Zqiang wrote:
> > For built with CONFIG_PROVE_RCU=y and CONFIG_PREEMPT_RT=y kernels,
> > Disable BH does not change the SOFTIRQ corresponding bits in
> > preempt_count(), but change current->softirq_disa
On Wed, 7 May 2025 at 18:01, Konstantin Shkolnyy wrote:
>
> On 07-May-25 10:41, Stefano Garzarella wrote:
> > On Wed, 7 May 2025 at 17:15, Konstantin Shkolnyy wrote:
> >>
> >> These tests:
> >> "SOCK_STREAM ioctl(SIOCOUTQ) 0 unsent bytes"
> >> "SOCK_SEQPACKET ioctl(SIOCOUTQ) 0 unsent by
Le Wed, May 07, 2025 at 07:26:04PM +0800, Zqiang a écrit :
> For built with CONFIG_PROVE_RCU=y and CONFIG_PREEMPT_RT=y kernels,
> Disable BH does not change the SOFTIRQ corresponding bits in
> preempt_count(), but change current->softirq_disable_cnt, this
> resulted in the following splat:
>
> WAR
On 5/7/25 04:14, Elena Reshetova wrote:
> In case an SGX vulnerability is discovered and TCB recovery
> for SGX is triggered, Intel specifies a process that must be
> followed for a given vulnerability. Steps to mitigate can vary
> based on vulnerability type, affected components, etc.
> In some ca
On 5/7/2025 7:26 AM, Zqiang wrote:
> For built with CONFIG_PROVE_RCU=y and CONFIG_PREEMPT_RT=y kernels,
> Disable BH does not change the SOFTIRQ corresponding bits in
> preempt_count(), but change current->softirq_disable_cnt, this
> resulted in the following splat:
>
> WARNING: suspicious RCU
From: Hiago De Franco
Move imx_sc_get_pd_power() from pmdomain/imx/scu-pd.c to
firmware/imx/misc.c and rename it to imx_sc_pm_get_resource_power_mode()
to maintain the same naming logic with other functions in misc.c.
This makes the API available for other use cases. For example,
remoteproc/imx_
From: Hiago De Franco
For the i.MX8X and i.MX8 family SoCs, currently when the remotecore is
started by the bootloader and the M core and A core are in the same
partition, the driver is not capable to detect the remote core and
report the correct state of it.
This series of patches implement an
From: Hiago De Franco
When the remote core is started before Linux boots (e.g., by the
bootloader), the driver currently is not able to attach because it only
checks for cores running in different partitions. If the core was kicked
by the bootloader, it is in the same partition as Linux and it is
From: Hiago De Franco
For the i.MX8X and i.MX8 family SoCs, when the M-core is powered up
by the bootloader, M-core and Linux are in same SCFW (System Controller
Firmware) partition, so linux has permission to control M-core.
But when M-core is started, the SCFW will automatically enable the clo
On 07-May-25 10:41, Stefano Garzarella wrote:
On Wed, 7 May 2025 at 17:15, Konstantin Shkolnyy wrote:
These tests:
"SOCK_STREAM ioctl(SIOCOUTQ) 0 unsent bytes"
"SOCK_SEQPACKET ioctl(SIOCOUTQ) 0 unsent bytes"
output: "Unexpected 'SIOCOUTQ' value, expected 0, got 64 (CLIENT)".
They te
Hi Peng,
On Tue, May 06, 2025 at 12:46:18PM +0800, Peng Fan wrote:
> On Mon, May 05, 2025 at 12:48:48PM -0300, Hiago De Franco wrote:
> >From: Hiago De Franco
> >
> >Move imx_sc_get_pd_power() from pmdomain/imx/scu-pd.c to
> >firmware/imx/misc.c and rename it to imx_sc_pm_get_resource_power_mode(
Use xdp_get_frame_len helper to ensure xdp frame size is calculated
correctly in both single buffer and multi buffer configurations.
Signed-off-by: Jon Kohler
---
drivers/vhost/net.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/vhost/net.c b/drivers/vhost/net.c
ind
On Wed, 7 May 2025 at 17:15, Konstantin Shkolnyy wrote:
>
> These tests:
> "SOCK_STREAM ioctl(SIOCOUTQ) 0 unsent bytes"
> "SOCK_SEQPACKET ioctl(SIOCOUTQ) 0 unsent bytes"
> output: "Unexpected 'SIOCOUTQ' value, expected 0, got 64 (CLIENT)".
>
> They test that the SIOCOUTQ ioctl reports 0 un
Refactor variable names in vhost_net_build_xdp to align with XDP
terminology, enhancing code clarity and consistency. Additionally,
reorder variables to follow a reverse Christmas tree structure,
improving code organization and readability.
This change introduces no functional modifications.
Sign
These tests:
"SOCK_STREAM ioctl(SIOCOUTQ) 0 unsent bytes"
"SOCK_SEQPACKET ioctl(SIOCOUTQ) 0 unsent bytes"
output: "Unexpected 'SIOCOUTQ' value, expected 0, got 64 (CLIENT)".
They test that the SIOCOUTQ ioctl reports 0 unsent bytes after the data
have been received by the other side. Howeve
On Mon, Apr 14 2025 at 14:31, Frank Li wrote:
> Some MSI controller change address/data pair when irq_set_affinity().
> Current PCI endpoint can't support this type MSI controller. So add flag
> MSI_FLAG_MUTABLE in include/linux/msi.h and check it when allocate
> doorbell.
This changelog has no re
Implement RPMSG_CREATE_EPT_FD_IOCTL, new uAPI for rpmsg ctrl, which
shares most of operations of RPMSG_CREATE_EPT_IOCTL except that it
returns fd representing eptdev to userspace directly.
Possible calling procedures for userspace are:
- fd = open("/dev/rpmsg_ctrlX")
- ioctl(fd, RPMSG_CREATE_EPT_F
Current uAPI implementation for rpmsg ctrl & char device manipulation is
abstracted in procedures below:
Current uAPI implementation for rpmsg ctrl & char device manipulation is
abstracted in procedures below:
- fd = open("/dev/rpmsg_ctrlX")
- ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info); /dev/rpmsgY
Introduce new eptdev abstraction based on anon inode. The new API is
exactly same with legacy one except:
- It's anonymous and devnode/path free.
- Its fops->open() is empty.
Signed-off-by: Dawei Li
---
drivers/rpmsg/rpmsg_char.c | 44 ++
drivers/rpmsg/rpmsg_
Hi,
This series introduce new uAPI(RPMSG_CREATE_EPT_FD_IOCTL) for rpmsg
subsystem.
Current uAPI implementation for rpmsg ctrl & char device manipulation is
abstracted in procedures below:
- fd = open("/dev/rpmsg_ctrlX")
- ioctl(fd, RPMSG_CREATE_EPT_IOCTL, &info); /dev/rpmsgY devnode is
generate
On Wed, May 07, 2025 at 06:48:33AM -0500, Konstantin Shkolnyy wrote:
These tests:
"SOCK_STREAM ioctl(SIOCOUTQ) 0 unsent bytes"
"SOCK_SEQPACKET ioctl(SIOCOUTQ) 0 unsent bytes"
output: "Unexpected 'SIOCOUTQ' value, expected 0, got 64 (CLIENT)".
They test that the SIOCOUTQ ioctl reports 0 uns
On Wed, May 07, 2025 at 09:18:29PM +1000, Alexey Kardashevskiy wrote:
> > We should not destroy the vdevice for something like that. In a CC
> > case that would unplug it from the VM which is not right.
>
> vdevice is not directly seen by the guest, is not it? The guest will
> see, for example, a
On Tue, May 6, 2025 at 6:24 AM Sami Tolvanen wrote:
>
> Document byte_size and type_string kABI stability rules. Also fix
> the section numbers while we're at it.
>
> Signed-off-by: Sami Tolvanen
> ---
> Documentation/kbuild/gendwarfksyms.rst | 103 +++--
> 1 file changed, 95
On Tue, May 06, 2025 at 12:55:02PM -0700, Nicolin Chen wrote:
> On Tue, May 06, 2025 at 09:58:47AM -0300, Jason Gunthorpe wrote:
> > On Mon, May 05, 2025 at 07:53:44PM -0700, Nicolin Chen wrote:
> > > On Mon, May 05, 2025 at 02:08:07PM -0300, Jason Gunthorpe wrote:
> > > > On Wed, Apr 30, 2025 at 1
On Wed, May 7, 2025 at 7:07 AM Shuah Khan wrote:
>
> On 5/6/25 05:12, Nicolas Schier wrote:
> > On Fri, 02 May 2025, Shuah Khan wrote:
> >
> >> When make finds the source tree unclean, it prints a message to run
> >> "make ARCH=x86_64 mrproper" message using the ARCH from the command
> >> line. Th
These tests:
"SOCK_STREAM ioctl(SIOCOUTQ) 0 unsent bytes"
"SOCK_SEQPACKET ioctl(SIOCOUTQ) 0 unsent bytes"
output: "Unexpected 'SIOCOUTQ' value, expected 0, got 64 (CLIENT)".
They test that the SIOCOUTQ ioctl reports 0 unsent bytes after the data
have been received by the other side. Howeve
For built with CONFIG_PROVE_RCU=y and CONFIG_PREEMPT_RT=y kernels,
Disable BH does not change the SOFTIRQ corresponding bits in
preempt_count(), but change current->softirq_disable_cnt, this
resulted in the following splat:
WARNING: suspicious RCU usage
kernel/rcu/tree_plugin.h:36 Unsafe read of R
On Wed May 7, 2025 at 11:15 AM CEST, Andreas Hindborg wrote:
> "Benno Lossin" writes:
>> On Tue May 6, 2025 at 3:02 PM CEST, Andreas Hindborg wrote:
>>> +pub trait ParseInt: private::FromStrRadix + TryFrom {
>>> +/// Parse a string according to the description in [`Self`].
>>> +
In the preparation stage of CPU online, if the corresponding
the rdp's->nocb_cb_kthread does not exist, will be created,
there is a situation where the rdp's rcuop kthreads creation fails,
and then de-offload this CPU's rdp, does not assign this CPU's
rdp->nocb_cb_kthread pointer, but this rdp's->n
For built with CONFIG_PREEMPT_RT=y kernels, running rcutorture
tests resulted in the following splat:
[ 68.797425] rcutorture_one_extend_check during change: Current 0x1 To add
0x1 To remove 0x0 preempt_count() 0x0
[ 68.797533] WARNING: CPU: 2 PID: 512 at kernel/rcu/rcutorture.c:1993
rcut
On Tue May 6, 2025 at 3:02 PM CEST, Andreas Hindborg wrote:
> Add support for module parameters to the `module!` macro. Implement read
> only support for integer types without `sysfs` support.
>
> Acked-by: Petr Pavlu # from modules perspective
> Tested-by: Daniel Gomez
> Reviewed-by: Greg Kroah-
On 6/5/25 22:58, Jason Gunthorpe wrote:
On Mon, May 05, 2025 at 07:53:44PM -0700, Nicolin Chen wrote:
On Mon, May 05, 2025 at 02:08:07PM -0300, Jason Gunthorpe wrote:
On Wed, Apr 30, 2025 at 12:58:47AM -0700, Nicolin Chen wrote:
... and I just hit a problem with it - this is basically gues
In case an SGX vulnerability is discovered and TCB recovery
for SGX is triggered, Intel specifies a process that must be
followed for a given vulnerability. Steps to mitigate can vary
based on vulnerability type, affected components, etc.
In some cases, a vulnerability can be mitigated via a runtim
Changes since v3 following reviews by Kai and Sean:
- Change the overall approach to the one suggested
by Sean and do the EUPDATESVN execution during
sgx_open() and sgx_vepc_open().
Note, I do not try to do EUPDATESVN during the release()
flows since it doesnt save any noticable amount
On Fri, Apr 25, 2025 at 10:27:29AM +0200, Vlastimil Babka wrote:
> Since we don't control the NUMA locality of objects in percpu sheaves,
> allocations with node restrictions bypass them. Allocations without
> restrictions may however still expect to get local objects with high
> probability, and t
Enable all remoteproc nodes on the qcs615-ride board and point to the
appropriate firmware files to allow proper functioning of the remote
processors.
Signed-off-by: Lijuan Gao
---
arch/arm64/boot/dts/qcom/qcs615-ride.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm
Add nodes for remoteprocs: ADSP and CDSP for QCS615 SoC to enable proper
remoteproc functionality.
Signed-off-by: Lijuan Gao
---
arch/arm64/boot/dts/qcom/qcs615.dtsi | 86
1 file changed, 86 insertions(+)
diff --git a/arch/arm64/boot/dts/qcom/qcs615.dtsi
b/
Add a simple-mfd representing IMEM on QCS615 and define the PIL
relocation info region as its child. The PIL region in IMEM is used to
communicate load addresses of remoteproc to post mortem debug tools, so
that these tools can collect ramdumps.
Signed-off-by: Lijuan Gao
---
arch/arm64/boot/dts/
From: Kyle Deng
The Shared Memory Point to Point (SMP2P) protocol facilitates
communication of a single 32-bit value between two processors.
Add these two nodes for remoteproc enablement on QCS615 SoC.
Signed-off-by: Kyle Deng
Signed-off-by: Lijuan Gao
---
arch/arm64/boot/dts/qcom/qcs615.dtsi
Document qcom,qcs615-imem compatible. It has a child node for debugging
purposes.
Acked-by: Krzysztof Kozlowski
Signed-off-by: Lijuan Gao
---
Documentation/devicetree/bindings/sram/qcom,imem.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/sram/qcom,ime
Document the components used to boot the ADSP and CDSP on the Qualcomm
QCS615 SoC. Use fallback to indicate the compatibility of the remoteproc
on the QCS615 with that on the SM8150.
Reviewed-by: Krzysztof Kozlowski
Signed-off-by: Lijuan Gao
---
.../bindings/remoteproc/qcom,sm8150-pas.yaml
/qcom/qcs615-ride.dts | 12 ++
arch/arm64/boot/dts/qcom/qcs615.dtsi | 143 +
4 files changed, 191 insertions(+), 24 deletions(-)
---
base-commit: 08710e696081d58163c8078e0e096be6d35c5fad
change-id: 20250507-add_qcs615_remoteproc_support-c82d30f9433d
Best
On Wed, May 07, 2025 at 06:15:34PM +0900, Harry Yoo wrote:
> On Fri, Apr 25, 2025 at 10:27:23AM +0200, Vlastimil Babka wrote:
> > Add functions for efficient guaranteed allocations e.g. in a critical
> > section that cannot sleep, when the exact number of allocations is not
> > known beforehand, bu
On Fri, Apr 25, 2025 at 10:27:23AM +0200, Vlastimil Babka wrote:
> Add functions for efficient guaranteed allocations e.g. in a critical
> section that cannot sleep, when the exact number of allocations is not
> known beforehand, but an upper limit can be calculated.
>
> kmem_cache_prefill_sheaf()
"Benno Lossin" writes:
> On Tue May 6, 2025 at 3:02 PM CEST, Andreas Hindborg wrote:
>> diff --git a/rust/kernel/str.rs b/rust/kernel/str.rs
>> index 878111cb77bc..174e70397305 100644
>> --- a/rust/kernel/str.rs
>> +++ b/rust/kernel/str.rs
>> @@ -573,7 +573,6 @@ macro_rules! c_str {
>> }
>>
>>
On Tue, May 6, 2025 at 10:39 PM Andrii Nakryiko
wrote:
> > + raw_data = mmap(NULL, end, PROT_READ, MAP_PRIVATE, fd, 0);
> > + if (!ASSERT_NEQ(raw_data, MAP_FAILED, "mmap_btf"))
>
> ASSERT_OK_PTR()?
Don't think that mmap follows libbpf_get_error conventions? I'd keep
it as it is.
> >
On Tue, May 6, 2025 at 10:39 PM Andrii Nakryiko
wrote:
>
> > + if (vma->vm_pgoff)
> > + return -EINVAL;
>
> any particular reason to not allow vm_pgoff?
Doesn't seem particularly useful because the header is at offset 0,
and I don't trust myself to get the overflow checks done
On Tue May 6, 2025 at 3:02 PM CEST, Andreas Hindborg wrote:
> diff --git a/rust/kernel/str.rs b/rust/kernel/str.rs
> index 878111cb77bc..174e70397305 100644
> --- a/rust/kernel/str.rs
> +++ b/rust/kernel/str.rs
> @@ -573,7 +573,6 @@ macro_rules! c_str {
> }
>
> #[cfg(test)]
> -#[expect(clippy::
On Wed, 7 May 2025 at 00:47, Michal Luczaj wrote:
>
> On 5/6/25 11:46, Stefano Garzarella wrote:
> > On Tue, 6 May 2025 at 11:43, Stefano Garzarella wrote:
> >>
> >> On Thu, May 01, 2025 at 10:05:24AM +0200, Michal Luczaj wrote:
> >>> There was an issue with SO_LINGER: instead of blocking until a
Add the necessary sound card bits and some dts additions to enable sound
over DisplayPort-over-USB-C, e.g. to a connected TV or monitor.
The UCM files can be found here:
https://gitlab.postmarketos.org/postmarketOS/pmaports/-/tree/master/device/testing/device-fairphone-fp5/ucm
This series - in sp
Sound machine drivers for Qualcomm SoCs can be reused across multiple
SoCs. But user space ALSA UCM files depend on the card driver name which
should be set per board/SoC.
Allow such customization by using driver match data as sound card driver
name. The QRB4210 RB2 gets its name set to "sm4250" a
Document the bindings for the sound card on Fairphone 5 which uses the
older non-audioreach audio architecture.
Acked-by: Rob Herring (Arm)
Signed-off-by: Luca Weiss
---
Documentation/devicetree/bindings/sound/qcom,sm8250.yaml | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/de
Add support for DisplayPort Jack events, so that user space can
configure the audio routing correctly.
Reviewed-by: Dmitry Baryshkov
Signed-off-by: Luca Weiss
---
sound/soc/qcom/sm8250.c | 17 ++---
1 file changed, 10 insertions(+), 7 deletions(-)
diff --git a/sound/soc/qcom/sm8250
Add the required nodes for sound playback via a connected external
display (DisplayPort over USB-C).
In user space just the following route needs to be set (e.g. using
ALSA UCM):
amixer -c0 cset name='DISPLAY_PORT_RX Audio Mixer MultiMedia1' 1
Afterwards one can play audio on the MultiMedia1 s
Add a compatible for the QCM6490-based Fairphone 5 which can use this
machine driver.
As a note, QCM6490 RB3 board is using audioreach architecture while
Fairphone 5 uses pre-audioreach.
Reviewed-by: Dmitry Baryshkov
Reviewed-by: Neil Armstrong
Signed-off-by: Luca Weiss
---
sound/soc/qcom/sm8
On Wed, May 7, 2025 at 7:07 AM Shuah Khan wrote:
>
> On 5/6/25 05:12, Nicolas Schier wrote:
> > On Fri, 02 May 2025, Shuah Khan wrote:
> >
> >> When make finds the source tree unclean, it prints a message to run
> >> "make ARCH=x86_64 mrproper" message using the ARCH from the command
> >> line. Th
84 matches
Mail list logo
