source large_stringclasses 2
values | subject large_stringclasses 112
values | code large_stringclasses 112
values | critique large_stringlengths 61 3.04M ⌀ | metadata dict |
|---|---|---|---|---|
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | On Thu 2025-11-27 00:16:23, Bird, Tim wrote:
I guess that it might break even basic tools, like dmesg, journalctl,
or crash.
A solution might be to pass it as an extra information to the official
timestamp, for example:
+ on console:
<level>[timestamp][callerid][cl cycles] message
<6>[ 0.000000][ ... | {
"author": "Petr Mladek <pmladek@suse.com>",
"date": "Thu, 27 Nov 2025 17:16:48 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | During early boot, printk timestamps are reported as zero before
kernel timekeeping starts (e.g. before time_init()). This
hinders boot-time optimization efforts. This period is about 400
milliseconds for many current desktop and embedded machines
running Linux.
Add support to save cycles during early boot, and outp... | {
"author": "Tim Bird <tim.bird@sony.com>",
"date": "Sat, 24 Jan 2026 12:40:27 -0700",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Hi Tim,
I tested this both on X86_64 QEMU and on a i.MX93 (ARM64) and can
confirm it is working as expected. Auto-calc of calibration data is far
better than the configuration parameters in v1.
It is slightly confusing to see a time value printed to serial output
and another one inside kmsg, but that's a human thing ... | {
"author": "Francesco Valla <francesco@valla.it>",
"date": "Sun, 25 Jan 2026 15:41:35 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Hi Tim,
On Sat, 24 Jan 2026 at 20:41, Tim Bird <tim.bird@sony.com> wrote:
Thanks for the update!
No need to cast to u64, as the second operand of the OR is u64 anyway.
BIT_ULL(63)
I think it would be good to have a #define for this at the top.
Please use the mul_u64_u32_shr() helper.
Please wrap this block in c... | {
"author": "Geert Uytterhoeven <geert@linux-m68k.org>",
"date": "Mon, 26 Jan 2026 11:12:42 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Agreed. I wasn't too worried about it, because most serious developers working
on boot-time will not be watching early messages over serial console. (Usually they
use 'quiet' or some lower log level). But on qemu, it does look strange to see 0s
on the first output sequence, and then non-zeroes when using dmesg la... | {
"author": "\"Bird, Tim\" <Tim.Bird@sony.com>",
"date": "Mon, 26 Jan 2026 16:52:57 +0000",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | I'll look at this. Is BIT_ULL(63) preferred over (1ULL << 63)?
Do you think something like "HIGH_BIT63" would be good enough?
OK. I did not know about that.
I can check, but do you know offhand if timestamps from local_clock() on 32-bit systems are
always 64-bit nanoseconds? I assume so looking at the prin... | {
"author": "\"Bird, Tim\" <Tim.Bird@sony.com>",
"date": "Mon, 26 Jan 2026 17:11:40 +0000",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | Hi Tim,
On Mon, 26 Jan 2026 at 18:11, Bird, Tim <Tim.Bird@sony.com> wrote:
When you refer to the bit value, yes: BIT() for unsigned long, BIT_ULL()
for unsigned long long; recently we got BIT_U{8,16,32,64}(), too).
I'd name it for what it means, not what it does, e.g. EARLY_TS_FLAG?
I am not 100% sure, but I thin... | {
"author": "Geert Uytterhoeven <geert@linux-m68k.org>",
"date": "Tue, 27 Jan 2026 09:10:31 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH] printk: add early_counter_ns routine for printk blind spot | From: Tim Bird <tim.bird@sony.com>
During early boot, printk timestamps are reported as zero,
which creates a blind spot in early boot timings. This blind
spot hinders timing and optimization efforts for code that
executes before time_init(), which is when local_clock() is
initialized sufficiently to start returning ... | On Mon 2026-01-26 16:52:57, Bird, Tim wrote:
I see the following in the serial console output:
[ 3.288049][ T1] Write protecting the kernel read-only data: 36864k
[ 3.298554][ T1] Freeing unused kernel image (text/rodata gap) memory: 1656K
[ 3.318942][ T1] Freeing unused kernel image (rodata/data ga... | {
"author": "Petr Mladek <pmladek@suse.com>",
"date": "Mon, 2 Feb 2026 17:23:59 +0100",
"thread_id": "39b09edb-8998-4ebd-a564-7d594434a981@bird.org.mbox.gz"
} |
lkml | [PATCH v4 0/2] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue | Hi,
=== Current situation: problems ===
Let's consider a nohz_full system with isolated CPUs: wq_unbound_cpumask is
set to the housekeeping CPUs, for !WQ_UNBOUND the local CPU is selected.
This leads to different scenarios if a work item is scheduled on an
isolated CPU where "delay" value is 0 or greater then 0:
... | This patch continues the effort to refactor workqueue APIs, which has begun
with the changes introducing new workqueues and a new alloc_workqueue flag:
commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
The point of the refactoring... | {
"author": "Marco Crivellari <marco.crivellari@suse.com>",
"date": "Mon, 2 Feb 2026 11:37:55 +0100",
"thread_id": "CAAofZF4oC+9ohHupkvmkR-967QEpSVdQoD5yHfLPcKzF4TnnXw@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v4 0/2] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue | Hi,
=== Current situation: problems ===
Let's consider a nohz_full system with isolated CPUs: wq_unbound_cpumask is
set to the housekeeping CPUs, for !WQ_UNBOUND the local CPU is selected.
This leads to different scenarios if a work item is scheduled on an
isolated CPU where "delay" value is 0 or greater then 0:
... | This continues the effort to refactor workqueue APIs, which began with
the introduction of new workqueues and a new alloc_workqueue flag in:
commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
The refactoring is going to alter the d... | {
"author": "Marco Crivellari <marco.crivellari@suse.com>",
"date": "Mon, 2 Feb 2026 11:37:56 +0100",
"thread_id": "CAAofZF4oC+9ohHupkvmkR-967QEpSVdQoD5yHfLPcKzF4TnnXw@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v4 0/2] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue | Hi,
=== Current situation: problems ===
Let's consider a nohz_full system with isolated CPUs: wq_unbound_cpumask is
set to the housekeeping CPUs, for !WQ_UNBOUND the local CPU is selected.
This leads to different scenarios if a work item is scheduled on an
isolated CPU where "delay" value is 0 or greater then 0:
... | On Mon, Feb 02, 2026 at 11:37:54AM +0100, Marco Crivellari wrote:
series is
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
I just resent it for CI and will push to drm-xe-next as soon as I get
the greenlight from CI.
Thanks,
Rodrigo. | {
"author": "Rodrigo Vivi <rodrigo.vivi@intel.com>",
"date": "Mon, 2 Feb 2026 11:20:55 -0500",
"thread_id": "CAAofZF4oC+9ohHupkvmkR-967QEpSVdQoD5yHfLPcKzF4TnnXw@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH v4 0/2] replace system_unbound_wq, add WQ_PERCPU to alloc_workqueue | Hi,
=== Current situation: problems ===
Let's consider a nohz_full system with isolated CPUs: wq_unbound_cpumask is
set to the housekeeping CPUs, for !WQ_UNBOUND the local CPU is selected.
This leads to different scenarios if a work item is scheduled on an
isolated CPU where "delay" value is 0 or greater then 0:
... | On Mon, Feb 2, 2026 at 5:21 PM Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
Many thanks Rodrigo!
--
Marco Crivellari
L3 Support Engineer | {
"author": "Marco Crivellari <marco.crivellari@suse.com>",
"date": "Mon, 2 Feb 2026 17:22:05 +0100",
"thread_id": "CAAofZF4oC+9ohHupkvmkR-967QEpSVdQoD5yHfLPcKzF4TnnXw@mail.gmail.com.mbox.gz"
} |
lkml | [PATCH] arm64: dts: mediatek: mt8365: fix infracfg_nao node | Use correct compatible string for the infracfg_nao: node and remove
the #clock-cells property.
Likely this was copied from the similar infracfg: node. However,
infracfg_nao: is just a syscon node with it's own register definitions
and is not a clock provider.
Fixes: 6ff945376556 ("arm64: dts: mediatek: Initial mt8365... | On 12/16/25 4:57 PM, David Lechner wrote:
Hmm... it looks like someone sent the same patch (actually better
because they fixed the node name too) quite a while ago [1], but that
patch didn't get picked up either. So I suggest to drop this patch
in favor of that one.
[1]: https://lore.kernel.org/linux-mediatek/2025050... | {
"author": "David Lechner <dlechner@baylibre.com>",
"date": "Mon, 2 Feb 2026 11:09:47 -0600",
"thread_id": "c616cc63-35fb-49a5-bd1a-ac559574c32d@baylibre.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | On Mon, Feb 02, 2026 at 12:03:11PM +0200, Bogdan Sandu wrote:
Was this an AI generated patch?
Either way, it needs to be properly broken up into "one logical change
per patch" like all others.
thanks,
greg k-h | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Mon, 2 Feb 2026 11:14:26 +0100",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | I can assure you, it is not AI-generated.
per patch" like all others.
Understood. I'll resend it afterwards.
Thank you for your patience. | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 12:18:43 +0200",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 12:18:44 +0200",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | On Mon, Feb 02, 2026 at 12:18:44PM +0200, Bogdan Sandu wrote:
You resent the same thing again?
confused,
greg k-h | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Mon, 2 Feb 2026 11:32:15 +0100",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | The previous patch has now been separated into four smaller ones, each one fixing a specific type of checkpatch.pl issue.
Bogdan Sandu (4):
media: ipu3: fix alignment
media: ipu3: use tabs
media: ipu3: avoid ending lines with paranthesis
media: ipu3: use BIT()
drivers/staging/media/ipu3/ipu3-css.c | 39 ++++... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:29 +0200",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Fix alignment with parentheses.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 22 +++++++++++-----------
drivers/staging/media/ipu3/ipu3-v4l2.c | 11 +++++------
drivers/staging/media/ipu3/ipu3.c | 4 ++--
3 files changed, 18 insertions(+), 19 deletions(-... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:30 +0200",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Use tabs instead of spaces.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-css.c b/drivers/staging/media/ipu3/ipu3-css.c
index 145501e90..e990eb5b3 100644
--- a/... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:31 +0200",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Don't end line with paranthesis.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 13 +++++--------
drivers/staging/media/ipu3/ipu3.c | 3 +--
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-css.c b/drivers/stagi... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:32 +0200",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Prefer BIT() macro over manual bitshift.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-mmu.c | 2 +-
drivers/staging/media/ipu3/ipu3-mmu.h | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-mmu.c b/drivers/staging/me... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:33 +0200",
"thread_id": "20260202175033.8640-4-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | On Mon, Feb 02, 2026 at 12:03:11PM +0200, Bogdan Sandu wrote:
Was this an AI generated patch?
Either way, it needs to be properly broken up into "one logical change
per patch" like all others.
thanks,
greg k-h | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Mon, 2 Feb 2026 11:14:26 +0100",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | I can assure you, it is not AI-generated.
per patch" like all others.
Understood. I'll resend it afterwards.
Thank you for your patience. | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 12:18:43 +0200",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 12:18:44 +0200",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | On Mon, Feb 02, 2026 at 12:18:44PM +0200, Bogdan Sandu wrote:
You resent the same thing again?
confused,
greg k-h | {
"author": "Greg KH <gregkh@linuxfoundation.org>",
"date": "Mon, 2 Feb 2026 11:32:15 +0100",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | The previous patch has now been separated into four smaller ones, each one fixing a specific type of checkpatch.pl issue.
Bogdan Sandu (4):
media: ipu3: fix alignment
media: ipu3: use tabs
media: ipu3: avoid ending lines with paranthesis
media: ipu3: use BIT()
drivers/staging/media/ipu3/ipu3-css.c | 39 ++++... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:29 +0200",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Fix alignment with parentheses.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 22 +++++++++++-----------
drivers/staging/media/ipu3/ipu3-v4l2.c | 11 +++++------
drivers/staging/media/ipu3/ipu3.c | 4 ++--
3 files changed, 18 insertions(+), 19 deletions(-... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:30 +0200",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Use tabs instead of spaces.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-css.c b/drivers/staging/media/ipu3/ipu3-css.c
index 145501e90..e990eb5b3 100644
--- a/... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:31 +0200",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Don't end line with paranthesis.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-css.c | 13 +++++--------
drivers/staging/media/ipu3/ipu3.c | 3 +--
2 files changed, 6 insertions(+), 10 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-css.c b/drivers/stagi... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:32 +0200",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | [PATCH] Cleanup ipu3 driver | Clean up warnings generated by ./scripts/checkpatch.pl regarding the ipu3 driver at /drivers/staging/media/ipu3
More specifically, the following files have been affected: ipu3-css.c, ipu3-mmu.c, ipu3-mmu.h, ipu3-v4l2.c, ipu3.c, ipu3.h
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/medi... | Prefer BIT() macro over manual bitshift.
Signed-off-by: Bogdan Sandu <bogdanelsandu2011@gmail.com>
---
drivers/staging/media/ipu3/ipu3-mmu.c | 2 +-
drivers/staging/media/ipu3/ipu3-mmu.h | 4 +++-
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drivers/staging/media/ipu3/ipu3-mmu.c b/drivers/staging/me... | {
"author": "Bogdan Sandu <bogdanelsandu2011@gmail.com>",
"date": "Mon, 2 Feb 2026 19:50:33 +0200",
"thread_id": "20260202175033.8640-5-bogdanelsandu2011@gmail.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (arm64 defconfig)
failed like this:
In file included from include/linux/srcu.h:49,
from include/linux/notifier.h:16,
from include/linux/random.h:10,
from arch/arm64/include/asm/pointer_auth.h:7,
... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 3 Mar 2022 19:04:50 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi Stephen,
Thanks for the report. My CI barked at me about this too this morning.
Seems like a surprising circularity in arm64's headers that maybe
should be fixed. But either way, I'll go with your forward declaration
approach.
Regards,
Jason | {
"author": "\"Jason A. Donenfeld\" <Jason@zx2c4.com>",
"date": "Thu, 3 Mar 2022 11:41:03 +0100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/mm/cpu_entry_area.c: In function 'init_cea_offsets':
arch/x86/mm/cpu_entry_area.c:38:23: error: implicit declaration of function 'prandom_u32_max'; did you mean 'prandom_u32_state'? [-Werror=implicit-funct... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 24 Oct 2022 13:23:19 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | I'll remove the removal commit for now and will plan on handling that
separately at the end of the 6.2 merge window.
Jason | {
"author": "\"Jason A. Donenfeld\" <Jason@zx2c4.com>",
"date": "Mon, 24 Oct 2022 06:28:53 +0200",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi Jason,
On Mon, 24 Oct 2022 06:28:53 +0200 "Jason A. Donenfeld" <Jason@zx2c4.com> wrote:
OK, thanks.
--
Cheers,
Stephen Rothwell | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 24 Oct 2022 17:33:58 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (arm64 defconfig)
failed like this:
arch/arm64/kernel/pi/kaslr_early.c: In function 'kaslr_early_init':
arch/arm64/kernel/pi/kaslr_early.c:97:22: error: implicit declaration of function '__early_cpu_has_rndr' [-Werror=implicit-function-declaration]
97... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 31 Oct 2022 17:09:56 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Mon, Oct 31, 2022 at 05:09:56PM +1100, Stephen Rothwell wrote:
Thanks, sorted.
Jason | {
"author": "\"Jason A. Donenfeld\" <Jason@zx2c4.com>",
"date": "Mon, 31 Oct 2022 11:31:10 +0100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
drivers/char/hw_random/powernv-rng.c: In function 'powernv_rng_read':
drivers/char/hw_random/powernv-rng.c:26:17: error: implicit declaration of function 'pnv_get_random_long'; did you mean 'get_random_long'? [... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Tue, 13 Dec 2022 14:36:22 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/mm/cpu_entry_area.c: In function 'init_cea_offsets':
arch/x86/mm/cpu_entry_area.c:39:23: error: implicit declaration of function 'prandom_u32_max'; did you mean 'prandom_u32_state'? [-Werror=implicit-funct... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 14 Dec 2022 12:53:59 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Wed, Dec 14, 2022 at 12:53:59PM +1100, Stephen Rothwell wrote:
The plan was the last chance before rc1, yea. I'll remove it for now so
that it stops breaking -next.
Jason | {
"author": "\"Jason A. Donenfeld\" <Jason@zx2c4.com>",
"date": "Tue, 13 Dec 2022 22:37:04 -0700",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (i386 defconfig)
failed like this:
In file included from arch/x86/kernel/cpu/rdrand.c:12:
arch/x86/include/asm/archrandom.h: In function 'rdrand_long':
arch/x86/include/asm/archrandom.h:25:9: error: implicit declaration of function 'WARN_ON' [-Werror=imp... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Mon, 25 Mar 2024 12:01:22 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (arm64 defconfig)
failed like this:
In file included from arch/arm64/include/asm/vdso/getrandom.h:8,
from lib/vdso/getrandom.c:11,
from <command-line>:
arch/arm64/include/asm/vdso.h:25:10: fatal error: generated/vdso-off... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 5 Sep 2024 20:19:30 +1000",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Thu, Sep 5, 2024 at 12:19 PM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
Thanks. Looks like, despite all our testing in review, this still got
missed, because it's a circular header dependency issue, so depending
on at what stage things were built, this was triggered or not. Fixing
up.
Jason | {
"author": "\"Jason A. Donenfeld\" <Jason@zx2c4.com>",
"date": "Thu, 5 Sep 2024 14:47:01 +0200",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (x86_64
allmodconfig) failed like this:
Caused by commit
38d1a9d296c8 ("random: Do not include <linux/prandom.h> in <linux/random.h>")
interacting with commit
5a90b60db5e6 ("drm/xe: Add a xe_bo subtest for shrinking / swapping")
from the drm-xe ... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Tue, 1 Oct 2024 13:44:23 +1000",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Tue, Oct 1, 2024 at 5:44 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
This was kind of expected when two commits are in flight in the same
area. IMO, the best way to solve this collision is to change the new
include in the DRM tree from <linux/random.h> to <linux/prandom.h>, as
is shown in the proposed patch.
... | {
"author": "Uros Bizjak <ubizjak@gmail.com>",
"date": "Tue, 1 Oct 2024 10:06:58 +0200",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
On Tue, 1 Oct 2024 13:44:23 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
The patch is now:
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 1 Oct 2024 13:33:48 +1000
Subject: [PATCH] fix up for "random: Do not include <linux/prandom.h> in
<linux/random.h>"
interacting with commit
5a90b60... | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Thu, 10 Oct 2024 15:38:55 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
On Thu, 10 Oct 2024 15:38:55 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
This patch is now needed when merging the drm tree and Linus' tree.
--
Cheers,
Stephen Rothwell | {
"author": "Stephen Rothwell <sfr@canb.auug.org.au>",
"date": "Wed, 20 Nov 2024 13:34:51 +1100",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Fri, Jan 23, 2026 at 09:48:19PM +0000, Mark Brown wrote:
Thank you for the report.
Wouldn't adding
struct completion;
at the top of arch/arm/include/asm/smp.h fix this?
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Fri, 23 Jan 2026 23:56:04 +0200",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | Hi all,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from /tmp/next/build/include/linux/smp.h:119,
from /tmp/next/build/include/linux/lockdep.h:14,
from /tmp/next/build/include/linux/spinlock.h:63,
... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Fri, 23 Jan 2026 21:48:19 +0000",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Fri, Jan 23, 2026 at 11:56:04PM +0200, Andy Shevchenko wrote:
That ougtht to do the bulk of it, though I see there's also at least:
/tmp/next/build/include/linux/dma-fence.h: In function '__dma_fence_is_later':
/tmp/next/build/include/linux/dma-fence.h:501:22: error: implicit declaration of
function 'lower_3... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Fri, 23 Jan 2026 22:10:56 +0000",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Fri, Jan 23, 2026 at 10:10:56PM +0000, Mark Brown wrote:
This (dma-fence.h) needs wordpart.h.
And this (freezer.h) for now requires kernel.h :-(
...
Okay, I need to reproduce that.
Thanks!
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Sat, 24 Jan 2026 00:18:45 +0200",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Sat, Jan 24, 2026 at 12:18:45AM +0200, Andy Shevchenko wrote:
I'd suggest testing some other configs/arches too, the -next build gives
up as soon as one thing errors out so there's possibly other things with
issues. | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Fri, 23 Jan 2026 22:22:47 +0000",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Fri, Jan 23, 2026 at 10:22:47PM +0000, Mark Brown wrote:
Yeah, it was x86 builds that I tested.
--
With Best Regards,
Andy Shevchenko | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Sat, 24 Jan 2026 00:44:10 +0200",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Fri, Jan 23, 2026 at 09:48:19PM +0000, Mark Brown wrote:
This regression is still present in today's -next. | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Mon, 2 Feb 2026 15:22:44 +0000",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | linux-next: build failure after merge of the random tree | Hi Theodore,
After merging the random tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:
In file included from include/linux/mmzone.h:10:0,
from include/linux/gfp.h:6,
from include/linux/umh.h:4,
from include/linux/kmod.h:22,
f... | On Mon, Feb 02, 2026 at 03:22:44PM +0000, Mark Brown wrote:
Please, revert this patch, as it shows more work is needed on arm (and maybe
other) side. Meanwhile I installed compiler for ARM and I see some issues even
after I fixed quite a few by the proposed changes (in this email thread).
--
With Best Regards,
Andy ... | {
"author": "Andy Shevchenko <andriy.shevchenko@linux.intel.com>",
"date": "Mon, 2 Feb 2026 19:34:17 +0200",
"thread_id": "aYDgGTtXCN8GMVI8@smile.fi.intel.com.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | From: Andreea Pintilie <anpintil@microsoft.com>
Update the partition VMM capability structure to match the hypervisor
representation to bring it to the up to date state. A precursor patch for
Root-on-Core scheduler feature support.
Signed-off-by: Andreea Pintilie <anpintil@microsoft.com>
Signed-off-by: Stanislav Kins... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Wed, 21 Jan 2026 22:35:54 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | From: Andreea Pintilie <anpintil@microsoft.com>
Query the hypervisor for integrated scheduler support and use it if
configured.
Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slici... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Wed, 21 Jan 2026 22:35:59 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | From: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com> Sent: Wednesday, January 21, 2026 2:36 PM
The tag_hv_message_from_child field is not used in the 2nd patch of this
patch set, so it is added but never used. Is it added just to be a placeholder
so that field vmm_enable_integrated_scheduler can be added... | {
"author": "Michael Kelley <mhklinux@outlook.com>",
"date": "Thu, 29 Jan 2026 17:46:21 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | From: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com> Sent: Wednesday, January 21, 2026 2:36 PM
hv_call_get_partition_property_ex() makes a hypercall, and then copies
back the number of bytes indicated by the 4th argument above; i.e.,
sizeof(root_sched_enabled). But using the size of a Linux type (size_t)... | {
"author": "Michael Kelley <mhklinux@outlook.com>",
"date": "Thu, 29 Jan 2026 17:47:02 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Thu, Jan 29, 2026 at 05:47:02PM +0000, Michael Kelley wrote:
<snip>
This was originally done to support kexec.
Here is the original commit message:
mshv: perform synic cleanup during kexec
Register a reboot notifier that performs synic cleanup when a kexec
is in progress.
One notable issue this... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Thu, 29 Jan 2026 11:09:46 -0800",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | From: Stanislav Kinsburskii <skinsburskii@linux.microsoft.com> Sent: Thursday, January 29, 2026 11:10 AM
FWIW, I don't see that commit message anywhere in a public source code
tree. The calls to register/unregister_reboot_notifier() were in the original
introduction of mshv_root_main.c in upstream commit 621191d709b14... | {
"author": "Michael Kelley <mhklinux@outlook.com>",
"date": "Fri, 30 Jan 2026 01:24:34 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Fri, Jan 30, 2026 at 01:24:34AM +0000, Michael Kelley wrote:
Yes, for now it's the best we have.
This code can be dropped later if we get a better way to handle kexec.
Yes. Thank you for the review and feedback!
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 07:49:05 -0800",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Thu, Jan 29, 2026 at 11:09:46AM -0800, Stanislav Kinsburskii wrote:
I don't think we need to fail here. If we don't find vmm caps, that
means we are on an older hypervisor that supports l1vh but not
integrated scheduler (yes, such a version exists). In this case since
integrated scheduler is not supported by the hy... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Fri, 30 Jan 2026 17:30:25 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Fri, Jan 30, 2026 at 01:24:34AM +0000, Michael Kelley wrote:
While that commit wasn't individually sent upstream but all the code
from that commit did land upstream probably bundled with other commits
when the mshv driver was introduced. So the reboot notifier is indeed
currently used for resetting the synic correc... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Fri, 30 Jan 2026 17:37:24 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | From: Anirudh Rayabharam <anirudh@anirudhrb.com> Sent: Friday, January 30, 2026 9:37 AM
Indeed, you are right. I confused the "mshv_root_sched_online" and
"mshv_cpuhp_online" cpuhp states. The reboot notifier removes the latter,
not the former. And the latter does substantive cleanup work on the SynIC
when the state ... | {
"author": "Michael Kelley <mhklinux@outlook.com>",
"date": "Fri, 30 Jan 2026 17:49:02 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Fri, Jan 30, 2026 at 05:30:25PM +0000, Anirudh Rayabharam wrote:
<snip>
The older hypervisor version won't have the integrated scheduler
capabity bit.
And we can't operate in core schedule mode if the integrated is enabled
underneath us.
Thanks,
Stanislav | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 10:37:38 -0800",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Fri, Jan 30, 2026 at 10:37:38AM -0800, Stanislav Kinsburskii wrote:
The older hypervisor won't have the integrated scheduler capability bit.
This means that the older hypervisor doesn't support integrated
scheduler (this is how vmm caps work: if the bit doesn't exist or
vmm caps themselves don't exist the feature s... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Fri, 30 Jan 2026 18:43:09 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Fri, Jan 30, 2026 at 06:43:09PM +0000, Anirudh Rayabharam wrote:
We can’t tell whether the hypervisor is older and simply doesn’t have
the VMM caps bit, or whether we just failed to fetch the VMM caps.
In other words, we can’t distinguish between “an older hypervisor
without integrated scheduler support” and “a ne... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Fri, 30 Jan 2026 10:51:10 -0800",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Fri, Jan 30, 2026 at 10:51:10AM -0800, Stanislav Kinsburskii wrote:
If we failed to fetch the VMM caps i.e. the hypervisor doesn't support
the vmm caps property, we must assume that all the bits in vmm caps are
0 (i.e. no features are available). This is how vmm capabilities are
supposed to be interpreted. This is ... | {
"author": "Anirudh Rayabharam <anirudh@anirudhrb.com>",
"date": "Fri, 30 Jan 2026 20:22:34 +0000",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH 0/2] Introduce Hyper-V integrated scheduler support | Microsoft Hypervisor originally provided two schedulers: root and core. The
root scheduler allows the root partition to schedule guest vCPUs across
physical cores, supporting both time slicing and CPU affinity (e.g., via
cgroups). In contrast, the core scheduler delegates vCPU-to-physical-core
scheduling entirely to th... | On Fri, Jan 30, 2026 at 08:22:34PM +0000, Anirudh Rayabharam wrote:
We don't need to support interim hypervisor versions in the upstream
kernel: these version will go away, and then this logic will become not
only a dead code path but also incorrect.
We can keep the existing logic that treats failure to fetch VMM as
... | {
"author": "Stanislav Kinsburskii <skinsburskii@linux.microsoft.com>",
"date": "Mon, 2 Feb 2026 09:19:39 -0800",
"thread_id": "aYDcq3xQKF6cCjwR@skinsburskii.localdomain.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The "qup-memory" interconnect path is optional and may not be defined
in all device trees. Unroll the loop-based ICC path initialization to
allow specific error handling for each path type.
The "qup-core" and "qup-config" paths remain mandatory and will fail
probe if missing, while "qup-memory" is now handled as optio... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:10 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add a new function geni_icc_set_bw_ab() that allows callers to set
average bandwidth values for all ICC (Interconnect) paths in a single
call. This function takes separate parameters for core, config, and DDR
average bandwidth values and applies them to the respective ICC paths.
This provides a more convenient API for... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:11 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently duplicate
code for initializing shared resources such as clocks and interconnect
paths.
Introduce a new helper API, geni_se_resources_init(), to centralize this
initialization logic, improving modularity and simplifying the probe
function.
Signed-off-by:... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:12 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Currently, core clk is handled individually in protocol drivers like
the I2C driver. Move this clock management to the common clock APIs
(geni_se_clks_on/off) that are already present in the common GENI SE
driver to maintain consistency across all protocol drivers.
Core clk is now properly managed alongside the other ... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:13 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI SE protocol drivers (I2C, SPI, UART) implement similar resource
activation/deactivation sequences independently, leading to code
duplication.
Introduce geni_se_resources_activate()/geni_se_resources_deactivate() to
power on/off resources.The activate function enables ICC, clocks, and TLMM
whereas the deactiva... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:14 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine drivers (I2C, SPI, and SERIAL) currently handle
the attachment of power domains. This often leads to duplicated code
logic across different driver probe functions.
Introduce a new helper API, geni_se_domain_attach(), to centralize
the logic for attaching "power" and "perf" domains to the GENI SE... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:15 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The GENI Serial Engine (SE) drivers (I2C, SPI, and SERIAL) currently
manage performance levels and operating points directly. This resulting
in code duplication across drivers. such as configuring a specific level
or find and apply an OPP based on a clock frequency.
Introduce two new helper APIs, geni_se_set_perf_leve... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:16 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Add DT bindings for the QUP GENI I2C controller on sa8255p platforms.
SA8255p platform abstracts resources such as clocks, interconnect and
GPIO pins configuration in Firmware. SCMI power and perf protocol
are utilized to request resource configurations.
SA8255p platform does not require the Serial Engine (SE) common... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:17 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Moving the serial engine setup to geni_i2c_init() API for a cleaner
probe function and utilizes the PM runtime API to control resources
instead of direct clock-related APIs for better resource management.
Enables reusability of the serial engine initialization like
hibernation and deep sleep features where hardware co... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:18 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | Refactor the resource initialization in geni_i2c_probe() by introducing
a new geni_i2c_resources_init() function and utilizing the common
geni_se_resources_init() framework and clock frequency mapping, making the
probe function cleaner.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Pravee... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:19 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To manage GENI serial engine resources during runtime power management,
drivers currently need to call functions for ICC, clock, and
SE resource operations in both suspend and resume paths, resulting in
code duplication across drivers.
The new geni_se_resources_activate() and geni_se_resources_deactivate()
helper APIs... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:20 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | To avoid repeatedly fetching and checking platform data across various
functions, store the struct of_device_id data directly in the i2c
private structure. This change enhances code maintainability and reduces
redundancy.
Acked-by: Viken Dadhaniya <viken.dadhaniya@oss.qualcomm.com>
Signed-off-by: Praveen Talari <prave... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:21 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH v4 00/13] Enable I2C on SA8255p Qualcomm platforms | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | The Qualcomm automotive SA8255p SoC relies on firmware to configure
platform resources, including clocks, interconnects and TLMM.
The driver requests resources operations over SCMI using power
and performance protocols.
The SCMI power protocol enables or disables resources like clocks,
interconnect paths, and TLMM (GP... | {
"author": "Praveen Talari <praveen.talari@oss.qualcomm.com>",
"date": "Mon, 2 Feb 2026 23:39:22 +0530",
"thread_id": "20260202180922.1692428-14-praveen.talari@oss.qualcomm.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | Simplify the mcasp_set_clk_pdir caller convention in start/stop stream
function, to make it so that set_clk_pdir gets called regardless when
stream starts and also disables when stream ends.
Functionality-wise, everything remains the same as the previously skipped
calls are now either correctly configured
(when McASP ... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:43 -0600",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | The current mcasp_is_synchronous() function does more than what it
proclaims, it also checks if McASP is a frame producer.
Therefore split the original function into two separate ones and
replace all occurrences with the new equivalent logic. So the functions
can be re-used when checking async/sync status in light of ... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:42 -0600",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | McASP supports the independent configuration of TX & RX clk and frame
sync registers. By default, the driver is configured in synchronous mode
where RX clock generator is disabled and it uses transmit clock signals as
bit clock and frame sync. Therefore add optional properties needed for
asynchronous mode.
Add ti,asyn... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:41 -0600",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | McASP has dedicated clock & frame sync registers for both transmit
and receive. Currently McASP driver only supports synchronous behavior and
couples both TX & RX settings.
Add logic that enables asynchronous mode via ti,async-mode property. In
async mode, playback & record can be done simultaneously with different
au... | {
"author": "Sen Wang <sen@ti.com>",
"date": "Thu, 29 Jan 2026 23:10:44 -0600",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On Thu, Jan 29, 2026 at 11:10:41PM -0600, Sen Wang wrote:
Please submit patches using subject lines reflecting the style for the
subsystem, this makes it easier for people to identify relevant patches.
Look at what existing commits in the area you're changing are doing and
make sure your subject lines visually resembl... | {
"author": "Mark Brown <broonie@kernel.org>",
"date": "Mon, 2 Feb 2026 12:44:32 +0000",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On 30/01/2026 07:10, Sen Wang wrote:
True, the naming was not too precise. It is tasked to decide if the TX
clock needs to be enabled for RX operation, which precisely when McASP
is in synchronous mode _and_ it is clock provider.
Acked-by: Peter Ujfalusi <peter.ujfalusi@gmail.com>
davinci_mcasp *mcasp, u32 ctl_reg,... | {
"author": "=?UTF-8?Q?P=C3=A9ter_Ujfalusi?= <peter.ujfalusi@gmail.com>",
"date": "Mon, 2 Feb 2026 18:42:20 +0200",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On 30/01/2026 07:10, Sen Wang wrote:
I'm not sure about this, but the sequence should be preserved, PDIR
change first.
--
Péter | {
"author": "=?UTF-8?Q?P=C3=A9ter_Ujfalusi?= <peter.ujfalusi@gmail.com>",
"date": "Mon, 2 Feb 2026 18:49:40 +0200",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH 0/4] ASoC: ti: davinci-mcasp: Add asynchronous mode support for McASP | This series adds asynchronous mode support to the McASP driver, which
enables independent configuration of bitclocks, frame sync, and audio
configurations between tx(playback) and rx(record). And achieves
simultaneous playback & record using different audio configurations.
It also adds two clean up patches to the McAS... | On 30/01/2026 07:10, Sen Wang wrote:
static void mcasp_start_rx(struct davinci_mcasp *mcasp)
In new code - while it might not match with old code - use producer
instead of master.
Otherwise it looks nice, I trust you have tested the sync and DIT mode.
With this nitpick addressed:
Acked-by: Peter Ujfalusi <peter.u... | {
"author": "=?UTF-8?Q?P=C3=A9ter_Ujfalusi?= <peter.ujfalusi@gmail.com>",
"date": "Mon, 2 Feb 2026 19:02:31 +0200",
"thread_id": "eec4df22-f664-45dd-a8e9-97c4714ffaa1@gmail.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Add verify-only public key crypto support for ML-DSA so that the
X.509/PKCS#7 signature verification code, as used by module signing,
amongst other things, can make use of it through the common crypto_sig API.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: Eric ... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:06 +0000",
"thread_id": "20260202170216.2467036-4-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Calculate the SHA256 hash for blacklisting purposes independently of the
signature hash (which may be something other than SHA256).
This is necessary because when ML-DSA is used, no digest is calculated.
Note that this represents a change of behaviour in that the hash used for
the blacklist check would previously hav... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:07 +0000",
"thread_id": "20260202170216.2467036-4-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Rename ->digest and ->digest_len to ->m and ->m_size to represent the input
to the signature verification algorithm, reflecting that ->digest may no
longer actually *be* a digest.
Signed-off-by: David Howells <dhowells@redhat.com>
Reviewed-by: Jarkko Sakkinen <jarkko@kernel.org>
cc: Lukas Wunner <lukas@wunner.de>
cc: ... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:08 +0000",
"thread_id": "20260202170216.2467036-4-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow the data to be verified in a PKCS#7 or CMS message to be passed
directly to an asymmetric cipher algorithm (e.g. ML-DSA) if it wants to do
whatever passes for hashing/digestion itself. The normal digestion of the
data is then skipped as that would be ignored unless another signed info in
the message has some oth... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:09 +0000",
"thread_id": "20260202170216.2467036-4-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Add support for ML-DSA keys and signatures to the CMS/PKCS#7 and X.509
implementations. ML-DSA-44, -65 and -87 are all supported. For X.509
certificates, the TBSCertificate is required to be signed directly; for
CMS, direct signing of the data is preferred, though use of SHA512 (and
only that) as an intermediate hash... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:10 +0000",
"thread_id": "20260202170216.2467036-4-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow ML-DSA module signing to be enabled.
Note that OpenSSL's CMS_*() function suite does not, as of OpenSSL-3.6,
support the use of CMS_NOATTR with ML-DSA, so the prohibition against using
signedAttrs with module signing has to be removed. The selected digest
then applies only to the algorithm used to calculate the... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:11 +0000",
"thread_id": "20260202170216.2467036-4-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH v16 0/7] x509, pkcs7, crypto: Add ML-DSA signing | Hi Lukas, Ignat,
[Note this is based on Eric Bigger's libcrypto-next branch].
These patches add ML-DSA module signing signing:
(1) Add a crypto_sig interface for ML-DSA, verification only.
(2) Generate a SHA256 hash of the X.509 TBSCertificate and check that in
the blacklist. Direct-sign ML-DSA doesn't gene... | Allow the rejection of authenticatedAttributes in PKCS#7 (signedAttrs in
CMS) to be waived in the kernel config for ML-DSA when used for module
signing. This reflects the issue that openssl < 4.0 cannot do this and
openssl-4 has not yet been released.
This does not permit RSA, ECDSA or ECRDSA to be so waived (behavio... | {
"author": "David Howells <dhowells@redhat.com>",
"date": "Mon, 2 Feb 2026 17:02:12 +0000",
"thread_id": "20260202170216.2467036-4-dhowells@redhat.com.mbox.gz"
} |
lkml | [PATCH 0/2] module: Remove SHA-1 support for module signing | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in f3b93547b91a ("module: sign with sha512 instead of
sha1 by default"). ... | SHA-1 is considered deprecated and insecure due to vulnerabilities that can
lead to hash collisions. Most distributions have already been using SHA-2
for module signing because of this. The default was also changed last year
from SHA-1 to SHA-512 in commit f3b93547b91a ("module: sign with sha512
instead of sha1 by defa... | {
"author": "Petr Pavlu <petr.pavlu@suse.com>",
"date": "Tue, 11 Nov 2025 16:48:31 +0100",
"thread_id": "20251111154923.978181-1-petr.pavlu@suse.com.mbox.gz"
} |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.