On 10/8/25 9:32 AM, Mukesh Ojha wrote:
> On Tue, Oct 07, 2025 at 02:55:04PM -0700, Manivannan Sadhasivam wrote:
>> On Tue, Oct 07, 2025 at 10:18:57PM +0530, Mukesh Ojha wrote:
>>> All the Lemans IOT variants boards are using Gunyah hypervisor which
>>> means that, so far, Linux-based OS could only
emory. It seems to be merged on linux-next and pushed for 6.18.
>>>>>
>>>>> https://lore.kernel.org/lkml/20250911-qcom-tee-using-tee-ss-without-mem-obj-v12-0-17f07a942...@oss.qualcomm.com/
>>>>>
>>>>> It is based on next-20250919 where above series i
On 08/10/2025 01:48, Mukesh Ojha wrote:
> Most Qualcomm platforms feature Gunyah hypervisor which handles IOMMU
> configuration for remote processor and when it is not present, the
> operating system must perform these configurations instead and for that
> firmware stream should be presented to the
On Tue, Oct 07, 2025 at 02:34:29PM -0700, Manivannan Sadhasivam wrote:
> On Tue, Oct 07, 2025 at 10:18:50PM +0530, Mukesh Ojha wrote:
> > As a superset of the existing metadata context, the PAS context
> > structure enables both remoteproc and non-remoteproc subsystems to
> > better support scenari
On Tue, Oct 07, 2025 at 02:55:04PM -0700, Manivannan Sadhasivam wrote:
> On Tue, Oct 07, 2025 at 10:18:57PM +0530, Mukesh Ojha wrote:
> > All the Lemans IOT variants boards are using Gunyah hypervisor which
> > means that, so far, Linux-based OS could only boot in EL1 on those
> > devices. However
On Tue, Oct 07, 2025 at 02:52:13PM -0700, Manivannan Sadhasivam wrote:
> On Tue, Oct 07, 2025 at 10:18:56PM +0530, Mukesh Ojha wrote:
> > Most Qualcomm platforms feature Gunyah hypervisor, which typically
> > handles IOMMU configuration. This includes mapping memory regions and
> > device memory re
for now, could add it in future
>or on a separate series.
> - Addressed most of the suggestion from Stephen and Bryan like some
>remoteproc code checking resource table presence or right error
>code propagation above the layer.
> - Added leman-el2 overlay f
Most Qualcomm platforms feature Gunyah hypervisor, which typically
handles IOMMU configuration. This includes mapping memory regions and
device memory resources for remote processors by intercepting
qcom_scm_pas_auth_and_reset() calls. These mappings are later removed
during teardown. Additionally,
On Tue, Oct 07, 2025 at 02:10:41PM +0200, Frederic Weisbecker wrote:
> Le Sat, Oct 04, 2025 at 02:47:08AM -0700, Paul E. McKenney a écrit :
> > On Thu, Oct 02, 2025 at 05:46:10PM +0200, Frederic Weisbecker wrote:
> > > Le Wed, Oct 01, 2025 at 07:48:13AM -0700, Paul E. McKenney a écrit :
> > > > Thi
On 10/7/25 08:34, Christoph Hellwig wrote:
> On Wed, Sep 10, 2025 at 10:01:02AM +0200, Vlastimil Babka wrote:
>> Hi,
>>
>> I'm sending full v8 due to more changes in the middle of the series that
>> resulted in later patches being fixed up due to conflicts (details in
>> the changelog below).
>> T
From: Alexandre Messier
Add the NFC chip used in the HTC One M8 to its device tree.
Signed-off-by: Alexandre Messier
---
arch/arm/boot/dts/qcom/qcom-msm8974pro-htc-m8.dts | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm/boot/dts/qcom/qcom-msm8974pro-htc-m8.dts
b/
Allow users of KHO to cancel the previous preservation by adding the
necessary interfaces to unpreserve folio and pages.
Signed-off-by: Pasha Tatashin
---
include/linux/kexec_handover.h | 12 +
kernel/kexec_handover.c| 85 --
2 files changed, 84 insert
On 10/7/25 8:29 AM, Eduard Zingerman wrote:
On Sat, 2025-10-04 at 22:47 +0800, Rong Tao wrote:
From: Rong Tao
Add tests for new kfuncs bpf_strcasestr() and bpf_strncasestr().
Signed-off-by: Rong Tao
---
Acked-by: Eduard Zingerman
[...]
diff --git a/tools/testing/selftests/bpf/progs/st
flict means the range is available for DAX, so register
it.
Here's what worked for me:
rc = add_soft_reserve_into_iomem(host, res);
/* The above add probably means patch 5 drops */
if (rc == -EBUSY) {
dev_dbg(host, "range already in iomem (CXL
rated by
> modpost if the module is built separately.
>
> To fix this it is necessary to generate the same modalias for vmlinux as
> for the individual modules. Fortunately '.vmlinux.export.o' is already
> generated from which '.modinfo' can be extracted in the
f event C, the
> >> oldest event
> >> that is not overwritten.
> >>
> >> 0 512 10241536 2048 2560 3072 3584
> >> 4096
> >>
> >> +--
ion related code from core/region.c
>>
>> We can minimize the churn in this patch by introduce the new
>> core/pmem_region.c and related bits in the beginning instead of introduce
>> new functions and then move them over from region.c.
>
> Hi Dave,
>
> As per
On 9/29/25 6:30 AM, Neeraj Kumar wrote:
> On 23/09/25 03:37PM, Dave Jiang wrote:
>>
>>
>> On 9/17/25 6:41 AM, Neeraj Kumar wrote:
>>> In 84ec985944ef3, devm_cxl_add_nvdimm() sequence was changed and called
>>> before devm_cxl_add_endpoint(). It's because cxl pmem region auto-assembly
>>> used to
Remove the arch specific variant of paravirt_steal_clock() and use
the common one instead.
Signed-off-by: Juergen Gross
Acked-by: Peter Zijlstra (Intel)
Reviewed-by: Andrew Jones
---
arch/riscv/Kconfig| 1 +
arch/riscv/include/asm/paravirt.h | 10 --
arch/riscv/kernel/
On Sun, Oct 05, 2025 at 03:35:56PM -0400, Chris Brown wrote:
> 850mA looks correct for the flash, whereas the flashlight/torch should
> be 100mA based on
> https://github.com/EmanuelCN/android_kernel_lge_sdm845/blob/U/arch/arm64/boot/dts/lge/sdm845-judy/sdm845-camera/sdm845-judy-camera.dtsi
> i.e.
virtio_vdpa_set_status() is declared as returning void, but it used
"return vdpa_set_status()" Since vdpa_set_status() also returns
void, the return statement is unnecessary and misleading.
Remove it.
Fixes: c043b4a8cf3b ("virtio: introduce a vDPA based transport")
Signed-off-by: Alok Tiwari
---
Reordered the header includes in drivers/remoteproc/remoteproc_core.c
to follow alphabetical order to simplify future maintenance.
No functional changes.
Signed-off-by: Peng Fan
---
drivers/remoteproc/remoteproc_core.c | 28 ++--
1 file changed, 14 insertions(+), 14 dele
Replace manual mutex_lock/unlock and error-handling patterns with cleanup.h
macros (ACQUIRE, ACQUIRE_ERR, and scoped_guard) to streamline lock
management. As a result, several goto labels and redundant error paths are
eliminated.
No functional changes.
Signed-off-by: Peng Fan
---
drivers/remote
From: Rong Tao
Add kfuncs bpf_strcasestr and bpf_strncasestr, which are extensions of
bpf_strstr and bpf_strnstr, suitable for more scenarios.
Rong Tao (2):
bpf: add bpf_strcasestr,bpf_strncasestr kfuncs
selftests/bpf: Test bpf_strcasestr,bpf_strncasestr kfuncs
kernel/bpf/helpers.c
From: Rong Tao
Add tests for new kfuncs bpf_strcasestr() and bpf_strncasestr().
Signed-off-by: Rong Tao
---
.../selftests/bpf/prog_tests/string_kfuncs.c| 2 ++
.../selftests/bpf/progs/string_kfuncs_failure1.c| 12
.../selftests/bpf/progs/string_kfuncs_failure2.c|
On 10/3/25 8:08 PM, Ihor Solodrai wrote:
>
>
> On 10/3/25 4:37 PM, Eduard Zingerman wrote:
>> On Fri, 2025-10-03 at 17:24 +0200, Matthieu Baerts (NGI0) wrote:
>> [...]
>>
>> Alan, Ihor, does this sound familiar?
>
> This is most likely the
dress-cells = <2>;
> #size-cells = <2>;
> ranges;
> +
> + stdout-path = "serial0:115200n8";
> };
>
> reserved-memory {
> @@ -595,3 +602,41 @@ &usb_1_qmpphy {
>
> status = "okay
On Sun, Sep 28, 2025 at 10:05:24PM -0700, Paul Sajna wrote:
> Improve adherance to style guidelines below:
> https://docs.kernel.org/devicetree/bindings/dts-coding-style.html
>
> Signed-off-by: Paul Sajna
> ---
> arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi | 124
> -
>
aul Sajna wrote:
> >
> > >
> > This patch will allow any values between 4.6 V and 6.0 V to
> > be set on your phone, with the kernel defaulting to 4.6 V at
> > boot and staying there until (if?) any driver requests that to
> > change.
> >
> >
October 3, 2025 at 7:36 PM, "Dmitry Baryshkov"
mailto:dmitry.barysh...@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E
> wrote:
>
> On Fri, Oct 03, 2025 at 06:52:03PM +, Paul Sajna wrote:
>
> >
> > October 3, 2025 at 5:13 PM, "Dmitry Baryshkov"
>
On Fri, Oct 03, 2025 at 06:52:03PM +, Paul Sajna wrote:
> October 3, 2025 at 5:13 PM, "Dmitry Baryshkov"
> mailto:dmitry.barysh...@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E
> > wrote:
>
>
>
> > Regarding the MDSS. Is it being solved by adding
dtsi
> @@ -484,7 +484,7 @@ zap-shader {
> };
>
> &ipa {
> - qcom,gsi-loader = "modem";
> + qcom,gsi-loader = "self";
The commit message might need to be improved. The patch itself LGTM.
> memory-region = <&ipa_fw_mem>;
>
> status = "okay";
>
> --
> 2.51.0
>
--
With best wishes
Dmitry
On Sun, Sep 28, 2025 at 10:05:33PM -0700, Paul Sajna wrote:
> These regulators seemingly help the lcd to work better
What does it mean? Also are they board-specific or should they be a part
of lg-common?
>
> Signed-off-by: Paul Sajna
> ---
> arch/arm64/boot/dts/qcom/sdm845-lg-judyln.dts | 17 +
On Sun, Sep 28, 2025 at 10:05:31PM -0700, Paul Sajna wrote:
> The sdm845-lg devices are all phones, therefore handset chassis
>
> Signed-off-by: Paul Sajna
> ---
> arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi | 2 ++
> 1 file changed, 2 insertions(+)
>
Reviewed-by: Dmitry Baryshkov
--
Wi
t; status = "okay";
> };
>
> +&cdsp_pas {
> + status = "okay";
> +};
Please move it down. Also please check the order of other nodes in the
patch.
> +
> @@ -137,9 +141,13 @@ sde_te_sleep: sde-te-sleep-state {
>
t6 is bluetooth
>
> Add bluetooth firmware path
>
> Signed-off-by: Paul Sajna
If the series get resent, could you please add the boot messages from
the bluetooth (hci0)?
The patch itself:
Reviewed-by: Dmitry Baryshkov
> ---
> arch/arm64/boot/dts/qcom/sdm845-lg-common.dtsi
October 3, 2025 at 5:13 PM, "Dmitry Baryshkov"
mailto:dmitry.barysh...@oss.qualcomm.com?to=%22Dmitry%20Baryshkov%22%20%3Cdmitry.baryshkov%40oss.qualcomm.com%3E
> wrote:
> Regarding the MDSS. Is it being solved by adding reset to the MDSS node?
> Or are there any other issues?
Yes I'm referrin
On Thu, Oct 02, 2025 at 07:26:16PM +, Paul Sajna wrote:
> October 2, 2025 at 9:37 AM, "Konrad Dybcio" mailto:konrad.dyb...@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E
> > wrote:
>
>
> >
> > On 10/2/25 6:51 AM, Paul Sajna wrote:
> >
> > >
> > > Octob
ly to be buggy.
Yes,But we aren't changing a buggy code. We are changing normal running
code for the sake of future code to not have those bugs which wouldn't
cause any issue (espacially when only changing variable types and not
casting like in my V3 of this patch[1]).
As a matter
This patch adds a selftest that verifies netconsole functionality
over bonded network interfaces using netdevsim. It sets up two bonded
interfaces acting as transmit (TX) and receive (RX) ends, placed in
separate network namespaces. The test sends kernel log messages and
verifies that they are
Create a netconsole test that puts a lot of pressure on the netconsole
list manipulation. Do it by creating dynamic targets and deleting
targets while messages are being sent. Also put interface down while the
messages are being sent, as creating parallel targets.
The code launches three backgroun
Extract the netconsole target creation from create_dynamic_target(), by
moving it from create_dynamic_target() into a new helper function. This
enables other tests to use the creation of netconsole targets with
arbitrary parameters and no sleep.
The new helper will be utilized by forthcoming tortu
commit efa95b01da18 ("netpoll: fix use after free") incorrectly
ignored the refcount and prematurely set dev->npinfo to NULL during
netpoll cleanup, leading to improper behavior and memory leaks.
Scenario causing lack of proper cleanup:
1) A netpoll is associated with a NIC (e.g., eth0) and netde
Fix a memory leak in netpoll and introduce netconsole selftests that
expose the issue when running with kmemleak detection enabled.
This patchset includes a selftest for netpoll with multiple concurrent
users (netconsole + bonding), which simulates the scenario from test[1]
that originally demonst
On Wed, Oct 01, 2025 at 12:16:50PM -0700, Alok Tiwari wrote:
> virtio_vdpa_set_status() is declared as returning void, but it used
> "return vdpa_set_status()" Since vdpa_set_status() also returns
> void, the return statement is unnecessary and misleading.
> Remove it.
>
> Signed-off-by: Alok Tiwa
Adding brcmstb-hwspinlock bindings.
Signed-off-by: Kamal Dasu
---
.../hwlock/brcm,brcmstb-hwspinlock.yaml | 36 +++
1 file changed, 36 insertions(+)
create mode 100644
Documentation/devicetree/bindings/hwlock/brcm,brcmstb-hwspinlock.yaml
diff --git
a/Documentation/devic
Add test to verify that unpinning hash tables containing internal timer
structures does not trigger context warnings.
Each subtest (timer_prealloc and timer_no_prealloc) can trigger the
context warning when unpinning, but the warning cannot be triggered
twice within a short time interval (a HZ), w
This small patchset is about avoid RCU context warning when unpinning
htab with internal structs (timer, workqueue, or task_work).
---
KaFai Wan (2):
bpf: Avoid RCU context warning when unpinning htab with internal
structs
selftests/bpf: Add test for unpinning htab with internal timer stru
When unpinning a BPF hash table (htab or htab_lru) that contains internal
structures (timer, workqueue, or task_work) in its values, a BUG warning
is triggered:
BUG: sleeping function called from invalid context at kernel/bpf/hashtab.c:244
in_atomic(): 1, irqs_disabled(): 0, non_block: 0, pid: 14
On Thu, Oct 02, 2025 at 08:26:24AM -0700, Breno Leitao wrote:
> Fix a memory leak in netpoll and introduce netconsole selftests that
> expose the issue when running with kmemleak detection enabled.
>
> This patchset includes a selftest for netpoll with multiple concurrent
> users (netconsole + bon
ass this pointer around from lock to unlock.
> > > We can add extra 8 bytes to struct bpf_tramp_run_ctx and save it there,
> > > but set/reset run_ctx operates on current anyway, so it's not clear
> > > which version will be faster. I suspect _trace()
Hello Shenwei,
On 9/22/25 22:04, Shenwei Wang wrote:
On i.MX SoCs, the system may include two processors:
- An MCU running an RTOS
- An MPU running Linux
These processors communicate via the RPMSG protocol.
The driver implements the standard GPIO interface, allowing
the Linux si
t be line wrapped.
> > Signed-off-by: Gopi Krishna Menon
> > ---
> > tools/testing/selftests/net/.gitignore | 1 +
> > 1 file changed, 1 insertion(+)
>
> Reviewed-by: Simon Horman
>
> I notice that tools/testing/selftests/kexec/test_kexec_jump
> is in a simil
On Mon, Sep 29, 2025 at 11:28 PM Willem de Bruijn
wrote:
>
> Reminder: use the net prefix: [PATCH net v2]
Oh I thought you meant me to change the subsytem in the subject.
Changing.
> My previous response accidentally left a state comment. The main
> feedback still held:
> This def
This allows the kernel to detect whether the userspace VDUSE device
supports the VQ group and ASID features. VDUSE devices that don't set
the V1 API will not receive the new messages, and vdpa device will be
created with only one vq group and asid.
The next patches implement the new feature incre
When query_virtqueues() fails, the error log prints the variable err
instead of cmd->err. Since err may still be zero at this point, the
log message can misleadingly report a success value 0 even though the
command actually failed.
Even worse, once err is set to the first failure, subsequent logs
On Fri, Sep 26, 2025 at 05:09:08PM +0100, Mark Brown wrote:
On Fri, Sep 26, 2025 at 03:46:26PM +, Edgecombe, Rick P wrote:
On Fri, 2025-09-26 at 01:44 +0100, Mark Brown wrote:
> I agree it seems clearly better from a security point of view to have
> writable shadow stacks than none at all
On Fri, Sep 26, 2025 at 5:27 PM Michael S. Tsirkin wrote:
>
> On Fri, Sep 26, 2025 at 12:14:29PM +0200, Eugenio Pérez wrote:
> > @@ -1859,6 +1894,7 @@ static int vduse_create_dev(struct vduse_dev_config
> > *config,
> > dev->device_features = config->features;
> > dev->device_id = con
On Mon, Sep 29, 2025 at 1:50 PM Dave Hansen wrote:
>
> On 9/29/25 13:33, Nataliia Bondarevska wrote:
> >> Could someone please spend a few minutes to explain what this tag means?
> > My apologies; I've clarified the details of the testing below.
> >
> > The verification was performed on a SPR mach
> On Fri, Sep 5, 2025 at 12:37 PM Dave Hansen wrote:
> >
> > On 8/18/25 00:11, Elena Reshetova wrote:
> > > Testing
> > > ---
> > >
> > > Tested on EMR machine using kernel 6.17.0_rc1 & sgx selftests.
> > > Also tested on a Kaby Lake machine without EUPDATESVN support.
> > > If Google folks
On Tue, Sep 30, 2025 at 10:12:27AM +0800, Jingyi Wang wrote:
>
>
> On 9/29/2025 8:22 PM, Dmitry Baryshkov wrote:
> > On Mon, Sep 29, 2025 at 06:11:23PM +0800, Jingyi Wang wrote:
> >>
> >>
> >> On 9/29/2025 5:39 PM, Dmitry Baryshkov wrote:
> >>> On Mon, Sep 29, 2025 at 02:06:11PM +0800, Jingyi Wan
Fix functions that return undefined values. These issues were caught by
running clang using LLVM=1 option.
Clang warnings are as follows:
ovpn-cli.c:1587:6: warning: variable 'ret' is used uninitialized whenever 'if'
condition is true [-Wsometimes-uninitialized]
1587 | if (!sock) {
On Mon, Sep 29, 2025 at 10:35 AM Dave Hansen wrote:
>
> On 9/29/25 10:12, Nataliia Bondarevska wrote:
> > Tested-by: Nataliia Bondarevska
>
> First, thanks for testing this.
>
> But I'd really, really appreciate if these tags (top posted and without
> any context trimmed no less) came with at _le
com,sm8750-cdsp-pas
> >>- const: qcom,sm8650-cdsp-pas
> >> + - items:
> >> + - const: qcom,kaanapali-cdsp-pas
> >> + - const: qcom,sm8550-cdsp-pas
> >
> >
> > This time maybe without HTML:
> >
> > T
On 9/27/25 1:19 PM, Alexei Starovoitov wrote:
On Fri, Sep 26, 2025 at 12:47 PM Maciej Fijalkowski
wrote:
On Fri, Sep 26, 2025 at 08:39:28AM +0200, Bastien Curutchet wrote:
Hi Maciej,
On 9/25/25 3:32 PM, Maciej Fijalkowski wrote:
On Wed, Sep 24, 2025 at 04:49:39PM +0200, Bastien Curutchet (e
check the state of the subsystem. This patch adds support to attach
>> to a subsystem by ensuring that the subsystem is in a sane state by
>> reading SMP2P bits and pinging the subsystem.
>>
>> Signed-off-by: Gokul krishna Krishnakumar
>> Co-developed-by: Jingyi Wang
From: Christopher Brown
Values based on lineageos kernel
https://github.com/LineageOS/android_kernel_lge_sdm845/blob/lineage-22.2/arch/arm64/boot/dts/lge/sdm845-battery/LGE_BLT39_LGC_3000mAh.dtsi
Signed-off-by: Christopher Brown
Signed-off-by: Paul Sajna
---
arch/arm64/boot/dts/qcom/sdm845-l
pe
> conversions and have predictable behavior.
>
> I have already compiled all bpf tests with no errors as well as the
> kernel and have ran all the selftests with no obvious side effects.
> I would like to know if it's more convinient to have all changes as
> a single patch lik
x27; the code is
still just as likely to be buggy.
>
> > As a matter of interest did you actually find any bugs?
>
> No,I have not found any bug related to the current state of code in bpf
> selftests but It works as a prevention mechanism for future bugs.Rather
> than wai
October 2, 2025 at 9:37 AM, "Konrad Dybcio" mailto:konrad.dyb...@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E
> wrote:
>
> On 10/2/25 6:51 AM, Paul Sajna wrote:
>
> >
> > October 1, 2025 at 9:14 AM, "Konrad Dybcio" > mailto:konrad.dyb...@oss.qualcomm.com
This commit saves more than 500 lines of RCU code by re-implementing
RCU Tasks Trace in terms of SRCU-fast. Follow-up work will remove
more code that does not cause problems by its presence, but that is no
longer required.
This variant places smp_mb() in rcu_read_{,un}lock_trace(), which will
be
On Wed, 24 Sept 2025 at 09:35, Peng Fan wrote:
>
> Hi Mathieu, Bjorn
>
> On Tue, Sep 23, 2025 at 01:16:32PM +0800, Peng Fan wrote:
> >This is the 2nd series to cleanup the driver.
> >
> >---
> >Changes in v2:
> >- Address a build warning in patch 4/6
&g
On Mon, Sep 29, 2025 at 10:52:45AM +0200, Eugenio Perez Martin wrote:
> On Mon, Sep 29, 2025 at 9:55 AM Michael S. Tsirkin wrote:
> >
> > On Mon, Sep 29, 2025 at 07:55:59AM +0200, Eugenio Perez Martin wrote:
> > > On Fri, Sep 26, 2025 at 5:27 PM Michael S. Tsirkin
> > > wrote:
> > > >
> > > > On
Alexey Gladkov.
RUKKIIEEE
(Rus)
On Mon, Aug 18, 2025 at 1:00 PM Alexey Gladkov wrote:
>
> Since .vmlinux.export.c is used to add generated by modpost modaliases
> for builtin modules the .vmlinux.export.o is no longer optional and
> should always be created. The generation of this file is
Indeed, it is so long. Sir Dong, of Meng.
On Tue, Aug 26, 2025 at 4:05 AM Menglong Dong wrote:
>
> Some functions is recursive for the kprobe_multi and impact the benchmark
> results. So just skip them.
>
> Signed-off-by: Menglong Dong
> ---
> v2:
> - introduce trace_blacklist instead of copy-pa
This patch adds a selftest that verifies netconsole functionality
over bonded network interfaces using netdevsim. It sets up two bonded
interfaces acting as transmit (TX) and receive (RX) ends, placed in
separate network namespaces. The test sends kernel log messages and
verifies that they are
ock.
> > We can add extra 8 bytes to struct bpf_tramp_run_ctx and save it there,
> > but set/reset run_ctx operates on current anyway, so it's not clear
> > which version will be faster. I suspect _trace() will be good enough.
> > Especially since trc_reader_nesting i
Le Wed, Oct 01, 2025 at 07:48:13AM -0700, Paul E. McKenney a écrit :
> This commit saves more than 500 lines of RCU code by re-implementing
> RCU Tasks Trace in terms of SRCU-fast. Follow-up work will remove
> more code that does not cause problems by its presence, but that is no
> longer required
Fix a memory leak in netpoll and introduce netconsole selftests that
expose the issue when running with kmemleak detection enabled.
This patchset includes a selftest for netpoll with multiple concurrent
users (netconsole + bonding), which simulates the scenario from test[1]
that originally demonst
boots and reports crash.
Signed-off-by: Tanmay Shah
---
Note: RFC patch for design discussion. Please do not merge.
drivers/remoteproc/remoteproc_core.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/remoteproc/remoteproc_core.c
b/drivers/remoteproc
Create a netconsole test that puts a lot of pressure on the netconsole
list manipulation. Do it by creating dynamic targets and deleting
targets while messages are being sent. Also put interface down while the
messages are being sent, as creating parallel targets.
The code launches three backgroun
Extract the netconsole target creation from create_dynamic_target(), by
moving it from create_dynamic_target() into a new helper function. This
enables other tests to use the creation of netconsole targets with
arbitrary parameters and no sleep.
The new helper will be utilized by forthcoming tortu
Comments in linux/device/driver.h say that the goal is to do async
probing on all devices. The current behavior unnecessarily slows down
the boot by synchronous probing dax_pmem devices, so let's change that.
Signed-off-by: Michal Clapinski
---
drivers/dax/pmem.c | 1 +
1 file changed, 1 inserti
extra 8 bytes to struct bpf_tramp_run_ctx and save it there,
> but set/reset run_ctx operates on current anyway, so it's not clear
> which version will be faster. I suspect _trace() will be good enough.
> Especially since trc_reader_nesting is kinda an optimization.
The i
Add some cleanups and fixes to shift-otter, and enable flash LED, RGB
LED and Venus.
Signed-off-by: Luca Weiss
---
Alexander Martinz (4):
arm64: dts: qcom: qcm6490-shift-otter: Fix sorting and indentation
arm64: dts: qcom: qcm6490-shift-otter: Remove thermal zone polling delays
On 10/2/25 6:51 AM, Paul Sajna wrote:
> October 1, 2025 at 9:14 AM, "Konrad Dybcio" mailto:konrad.dyb...@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E
> > wrote
>
>
>>
>> As the dt-checker points out, there is no such property
>>
>> If your wi-fi works regar
On Thu, Oct 02, 2025 at 12:53:13AM -0500, Andy Chiu wrote:
> Hi Yong-Xuan,
>
> I found some issues which deserve a re-roll:
>
> On Wed, Oct 1, 2025 at 6:15 AM Yong-Xuan Wang
> wrote:
> >
> > Add a test case that does some basic verification of the Vector ptrace
> > interface. This forks a child
On Thu, Oct 2, 2025 at 1:27 AM Si-Wei Liu wrote:
>
> Hi Eugenio,
>
> On 10/1/2025 6:26 AM, Eugenio Perez Martin wrote:
> > On Tue, Feb 7, 2023 at 12:15 AM Si-Wei Liu wrote:
> >> Today when device features are explicitly provisioned, the features
> >> user supplied may contain device class specifi
October 2, 2025 at 5:25 AM, "Paul Sajna" mailto:sajatt...@postmarketos.org?to=%22Paul%20Sajna%22%20%3Csajattack%40postmarketos.org%3E
> wrote:
>
> September 29, 2025 at 5:05 AM, "Paul Sajna" mailto:sajatt...@postmarketos.org?to=%22Paul%20Sajna%22%20%3Csajattack%40postmarketos.org%3E
> > wrote
Hi Yong-Xuan,
I found some issues which deserve a re-roll:
On Wed, Oct 1, 2025 at 6:15 AM Yong-Xuan Wang wrote:
>
> Add a test case that does some basic verification of the Vector ptrace
> interface. This forks a child process then using ptrace to inspect and
> manipulate the v31 register of the
October 1, 2025 at 9:01 AM, "Konrad Dybcio" mailto:konrad.dyb...@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E
> wrote:
>
> On 9/29/25 7:05 AM, Paul Sajna wrote:
>
> >
> > From: Amir Dahan
> >
> > Add the multicolor status led in the phone's notch
> >
October 1, 2025 at 9:14 AM, "Konrad Dybcio" mailto:konrad.dyb...@oss.qualcomm.com?to=%22Konrad%20Dybcio%22%20%3Ckonrad.dybcio%40oss.qualcomm.com%3E
> wrote
>
> As the dt-checker points out, there is no such property
>
> If your wi-fi works regardless of that, you probably don't need
> to set t
ipa_fws.mbn";
> > };
> >
> > +&lab {
> > + regulator-min-microvolt = <460>;
> > + regulator-max-microvolt = <600>;
> > + regulator-over-current-protection;
> > + regulator-pull-down;
> > + regulator-soft-s
On Tue, Sep 30, 2025 at 03:57:03PM +0200, Luca Weiss wrote:
> Use the correct compatible for this phone with standard Qualcomm
> firmware and remove references to power-domains from a 'reserved' node.
>
> Signed-off-by: Luca Weiss
> ---
> arch/arm64/boot/dts/qcom/qcm6490-fairphone-fp5.dts | 5 ++
On Tue, Sep 30, 2025 at 03:57:01PM +0200, Luca Weiss wrote:
> Add the OLED power supplies to the simple-framebuffer node, so that
> the regulators don't get turned off while the simple-fb is being used.
>
> Fixes: c365a026155c ("arm64: dts: qcom: qcm6490-fairphone-fp5: Enable
> display")
> Signed
On Thu, Sep 25, 2025 at 12:07:22AM +0530, Sibi Sankar wrote:
> Document the Inter-Processor Communication Controller on the Glymur SoCs.
That's obvious. Say something useful here like how the h/w compares to
existing documented h/w. Like perhaps the change from virtual ids to
physical ids, whate
Hi Eugenio,
On 10/1/2025 6:26 AM, Eugenio Perez Martin wrote:
On Tue, Feb 7, 2023 at 12:15 AM Si-Wei Liu wrote:
Today when device features are explicitly provisioned, the features
user supplied may contain device class specific features that are
not supported by the parent management device. O
Michał Cłapiński wrote:
> On Fri, Sep 26, 2025 at 8:45 PM wrote:
> >
> > Michał Cłapiński wrote:
> > [..]
> > > > As Mike says you would lose 128K at the end, but that indeed becomes
> > > > losing that 1GB given alignment constraints.
> > > >
> > > > However, I think that could be solved by just
Signed-off-by: Kamal Dasu
---
MAINTAINERS | 8
1 file changed, 8 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 97d958c945e4..21b78f468169 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -4972,6 +4972,14 @@ S: Supported
F: Documentation/devicetree/bindings/gpio/brcm
On Mon, Sep 22, 2025 at 03:04:10PM -0500, Shenwei Wang wrote:
> Remote processors may announce multiple devices (e.g., I2C, GPIO) over
> an RPMSG channel. These devices may require corresponding device tree
> nodes, especially when acting as providers, to supply phandles for their
> consumers.
>
>
1 - 100 of 531674 matches
Mail list logo
