CINXE.COM
LKML.ORG - the Linux Kernel Mailing List Archive
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> <link href="/css/frontpage.css" rel="stylesheet" type="text/css" /> <title>LKML.ORG - the Linux Kernel Mailing List Archive</title> <script type="text/javascript" src="/css/multiline-tooltip.js"></script> </head> <body onload="makeNiceTitles()"> <script type="text/javascript"> google_ad_client = "ca-pub-3128732077138691"; google_ad_slot = "7534865200"; google_ad_width = 728; google_ad_height = 90; google_page_url = document.location.href; </script> <table width="100%"> <tr class="quickbar"> <td width="25%"> <a href="/lkml/last100">Last 100 messages</a> </td> <td width="25%"> <a href="/lkml/today">Today's messages</a> </td> <td width="25%"> <a href="/lkml/yesterday">Yesterday's messages</a> </td> <td width="25%"> <a href="/hot.xml">Hottest Messages</a> </td> </tr> </table> <table width="100%"> <tr> <td colspan="2" align="center" valign="middle"></td> <td valign="top"> <div align="center"> <table cellspacing="1" cellpadding="0" border="0" bgcolor="#555653"> <tr> <td> <table id="kernelreleases" cellspacing="0" cellpadding="1" border="0" bgcolor="#dde8e8"> <tr> <td colspan="4" align="center" bgcolor="#fbffea"> <b>Latest kernels</b> </td> </tr> <tr class="c1"> <td> <b>mainline</b> </td> <td> <a title="tarfile of complete tree" href="https://git.kernel.org/torvalds/t/linux-6.14-rc7.tar.gz">6.14-rc7</a> </td> <td> <a title="patch against previous version" href="https://git.kernel.org/torvalds/p/v6.14-rc7/v6.13">patch</a> </td> <td> 聽 </td> </tr> <tr class="c0"> <td> <b>stable</b> </td> <td> <a title="tarfile of complete tree" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.13.7.tar.xz">6.13.7</a> </td> <td> <a title="patch against previous version" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/patch-6.13.7.xz">patch</a> </td> <td> <a title="changelog" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.13.7">log</a> </td> </tr> <tr class="c1"> <td> <b>longterm</b> </td> <td> <a title="tarfile of complete tree" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.12.19.tar.xz">6.12.19</a> </td> <td> <a title="patch against previous version" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/patch-6.12.19.xz">patch</a> </td> <td> <a title="changelog" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.12.19">log</a> </td> </tr> <tr class="c0"> <td> <b>longterm</b> </td> <td> <a title="tarfile of complete tree" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.6.83.tar.xz">6.6.83</a> </td> <td> <a title="patch against previous version" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/patch-6.6.83.xz">patch</a> </td> <td> <a title="changelog" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.6.83">log</a> </td> </tr> <tr class="c1"> <td> <b>longterm</b> </td> <td> <a title="tarfile of complete tree" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/linux-6.1.131.tar.xz">6.1.131</a> </td> <td> <a title="patch against previous version" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/patch-6.1.131.xz">patch</a> </td> <td> <a title="changelog" href="https://cdn.kernel.org/pub/linux/kernel/v6.x/ChangeLog-6.1.131">log</a> </td> </tr> <tr class="c0"> <td> <b>longterm</b> </td> <td> <a title="tarfile of complete tree" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.15.179.tar.xz">5.15.179</a> </td> <td> <a title="patch against previous version" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/patch-5.15.179.xz">patch</a> </td> <td> <a title="changelog" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.15.179">log</a> </td> </tr> <tr class="c1"> <td> <b>longterm</b> </td> <td> <a title="tarfile of complete tree" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.10.235.tar.xz">5.10.235</a> </td> <td> <a title="patch against previous version" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/patch-5.10.235.xz">patch</a> </td> <td> <a title="changelog" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.10.235">log</a> </td> </tr> <tr class="c0"> <td> <b>longterm</b> </td> <td> <a title="tarfile of complete tree" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.4.291.tar.xz">5.4.291</a> </td> <td> <a title="patch against previous version" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/patch-5.4.291.xz">patch</a> </td> <td> <a title="changelog" href="https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.4.291">log</a> </td> </tr> </table> </td> </tr> </table> </div> </td> </tr> <tr> <td valign="top"> <div align="center"> <table cellspacing="1" cellpadding="0" border="0" bgcolor="#555653"> <tr> <td> <table cellspacing="0" cellpadding="1" border="0" bgcolor="#dde8e8"> <tr> <td colspan="3" align="center" bgcolor="#fbffea"> <b> Latest messages </b> </td> </tr> <tr class="c1"> <td>Kim Phillips</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1243" title="Summary not available">Re: [PATCH 0/5] Provide SEV-ES/SEV-SNP support for...</a> </td> </tr> <tr class="c0"> <td>Namhyung Kim</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1242" title="Summary not available">[PATCH v3] perf trace: Implement syscall summary i...</a> </td> </tr> <tr class="c1"> <td>Qasim Ijaz</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1241" title="Summary not available">Re: [PATCH] net: dl2k: fix potential null deref in...</a> </td> </tr> <tr class="c0"> <td>David Woodhouse</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1240" title="Summary not available">Re: Using Restricted DMA for virtio-pci</a> </td> </tr> <tr class="c1"> <td>Biju Das</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1239" title="Summary not available">RE: [PATCH] drm: renesas: Extend RZ/G2L supported ...</a> </td> </tr> <tr class="c0"> <td>Alexey Nepomnyashih</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1238" title="Summary not available">[PATCH 6.1] efivarfs: Move efivarfs list into supe...</a> </td> </tr> <tr class="c1"> <td>Andy Shevchenko</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1237" title="Summary not available">[PATCH v1 1/2] Input: wdt87xx_i2c - tidy up ACPI I...</a> </td> </tr> <tr class="c0"> <td>Andy Shevchenko</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1236" title="Summary not available">[PATCH v1 2/2] Input: wdt87xx_i2c - switch to use ...</a> </td> </tr> <tr class="c1"> <td>Andy Shevchenko</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1235" title="Summary not available">[PATCH v1 0/2] Input: wdt87xx_i2c - a couple of cl...</a> </td> </tr> <tr class="c0"> <td>Ignacio Encinas Rubio</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1234" title="Ignacio Encinas Rubio writes: (Summary) What do you think, should we keep patch 1 after all?<br/> should we keep patch 1 after all?<br/> We could remove __arch_swab for architectures that always assume bit manipulation instructions availability, but then the kernel would fall back into ___constant_swab when CONFIG_ARCH_USE_BUILTIN_BSWAP=n. Thanks!<br/> Thanks!<br/> [1] <a href="https://lore.kernel.org/all/ce034f2b-2f6e-403a-81f1-680af4c72929@ghiti.fr/">https://lore.kernel.org/all/ce034f2b-2f6e-403a-81f1-680af4c72929@ghiti.fr/</a> [2] <a href="https://lore.kernel.org/all/20250319-riscv-swab-v2-2-d53b6d6ab915@iencinas.com/">https://lore.kernel.org/all/20250319-riscv-swab-v2-2-d53b6d6ab915@iencinas.com/</a> [3] <a href="https://gcc.gnu.org/onlinedocs/gcc-13.3.0/gccint.pdf">https://gcc.gnu.org/onlinedocs/gcc-13.3.0/gccint.pdf</a> [4] <a href="https://lore.kernel.org/all/20230512164815.2150839-1-jcmvbkbc@gmail.com/">https://lore.kernel.org/all/20230512164815.2150839-1-jcmvbkbc@gmail.com/</a> [5] <a href="https://lore.kernel.org/all/1664437198-31260-3">Re: [PATCH v2 1/2] include/uapi/linux/swab.h: move...</a> </td> </tr> <tr class="c1"> <td>"tip-bot2 for John Stultz"</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1233" title="&quot;tip-bot2 for John Stultz&quot; writes: (Summary) 94 +++++++++++++++++++++++++++----------- 1 file changed, 69 insertions(+), 25 deletions(-) diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c index 1e67d07..929846b 100644 --- a/kernel/time/timekeeping.c +++ b/kernel/time/timekeeping.c @@ -682,20 +682,19 @@ static void timekeeping_update_from_shadow(struct tk_data *tkd, unsigned int act } /** - * timekeeping_forward_now - update clock to the current time + * timekeeping_forward - update clock to given cycle now value * @tk: Pointer to the timekeeper to update + * @cycle_now: Current clocksource read value * * Forward the current clock to update its state since the last call to * update_wall_time(). ">[tip: timers/core] timekeeping: Fix possible incon...</a> </td> </tr> <tr class="c0"> <td>"tip-bot2 for John Stultz"</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1232" title="&quot;tip-bot2 for John Stultz&quot; writes: (Summary) CommitterDate: Fri, 21 Mar 2025 19:16:18 +01:00<br/> CommitterDate: Fri, 21 Mar 2025 19:16:18 +01:00<br/> selftests/timers: Improve skew_consistency by testing with other clockids selftests/timers: Improve skew_consistency by testing with other clockids Lei Chen reported a bug with CLOCK_MONOTONIC_COARSE having inconsistencies when NTP is adjusting the clock frequency.<br/> when NTP is adjusting the clock frequency.<br/> This has gone seemingly undetected for ~15 years, illustrating a clear gap in our testing.<br/> in our testing.<br/> The skew_consistency test is intended to catch this sort of problem, but was focused on only evaluating CLOCK_MONOTONIC, and thus missed the problem on CLOCK_MONOTONIC_COARSE.<br/> on CLOCK_MONOTONIC_COARSE.<br/> So adjust the test to run with all clockids for 60 seconds each instead of 10 minutes with just CLOCK_MONOTONIC.<br/> 10 minutes with just CLOCK_MONOTONIC.<br/> Reported-by: Lei Chen &lt;lei.chen@smartx.com&gt;<br/> Signed-off-by: John Stultz &lt;jstultz@google.com&gt">[tip: timers/core] selftests/timers: Improve skew_...</a> </td> </tr> <tr class="c1"> <td>Yury Norov</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1231" title="Yury Norov writes: (Summary) David sent a lengthy email that doesn't address them, either.<br/> address them, either.<br/> None of you guys submitted anything to bitmaps - neither in library, nor in tests. I always encourage people to increase testing coverage.<br/> encourage people to increase testing coverage.<br/> If you'd like to add new cases to existing tests - I'll be happy. If you'd like to add completely new tests based on KUNITs or whatever else - I'll be happy just as well.<br/> else - I'll be happy just as well.<br/> Thanks,<br/> Yury<br/> Yury<br/> Yury<br/> ">Re: distro support for CONFIG_KUNIT: [PATCH 0/3] b...</a> </td> </tr> <tr class="c0"> <td>"Michael S. Tsirkin"</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1230" title="&quot;Michael S. Tsirkin&quot; writes: (Summary) On Fri, Mar 21, 2025 at 03:38:10PM +0000, David Woodhouse wrote: &gt; systems without an IOMMU, which could result in the DMA accessing the &gt; Virtio already has a complicated relationship with the DMA API, because &gt; there were a bunch of early VMM bugs where the virtio devices where &gt; emulating the virtio device) not being *allowed* to arbitrarily access &gt; Either a virtual IOMMU needs to determine which guest memory the VMM &gt; reasonable way to allow an untrusted VMM to provide virtio devices with &gt; ">Re: Using Restricted DMA for virtio-pci</a> </td> </tr> <tr class="c1"> <td>Atish Patra</td> <td>聽</td> <td> <a href="/lkml/2025/3/21/1229" title="Atish Patra writes: (Summary) I did not find anything in the perf list or the json file.<br/> I am not sure if I missed something.<br/> I am not sure if I missed something.<br/> ++<br/> --<br/> /cycle-and-instruction-count.json<br/> /firmware.json<br/> /instruction.json<br/> /memory.json<br/> /microarch.json<br/> /watchpoint.json<br/> /cycle-and-instruction-count.json<br/> /firmware.json<br/> /instruction.json<br/> /memory.json<br/> /microarch.json<br/> /watchpoint.json<br/> mware.json (100%)<br/> struction.json<br/> mory.json<br/> croarch.json<br/> ware.json<br/> ruction.json<br/> ry.json<br/> oarch.json<br/> e-and-instruction-count.json<br/> ware.json<br/> ruction.json<br/> ry.json<br/> oarc">Re: [RESEND PATCH 0/7] perf vendor events riscv: U...</a> </td> </tr> </table> </td> </tr> </table> </div> </td> <td valign="top" colspan="2"> <div align="center"> <table cellspacing="1" cellpadding="0" border="0" bgcolor="#555653"> <tr> <td> <table cellspacing="0" cellpadding="1" border="0" bgcolor="#dde8e8"> <tr> <td colspan="3" align="center" bgcolor="#fbffea"> <b> Hottest messages </b> </td> </tr> <tr class="c1"> <td>Linus Torvalds</td> <td>聽</td> <td> <a href="/lkml/2024/1/6/180" title="Linus Torvalds writes: (Summary) Complain to clang people for being *extra* stupid - we told the compiler that it can use a register or memory, and clang decided "I'll use memory", so then when we gave it a memory location, it said "no, not *that* memory - I'll just reload it on stack".<br/> reload it on stack".<br/> In contrast, gcc gets this right - and for that udp.c case it just generates In contrast, gcc gets this right - and for that udp.c case it just generates addl 136(%rax),%ecx # frags_67-&gt;D.58941.D.58869.D.58836.csum, a adcl $0,%ecx # a<br/> adcl $0,%ecx # a<br/> like it should.<br/> like it should.<br/> And for csum_ipv6_magic, gcc generates this:<br/> And for csum_ipv6_magic, gcc generates this:<br/> addl %edx,%eax # tmp112, a<br/> adcl $0,%eax # a<br/> adcl $0,%eax # a<br/> IOW, the kernel is *right*, and this is purely clang being completely bogus. ">Re: x86/csum: Remove unnecessary odd handling</a> </td> </tr> <tr class="c0"> <td>Linus Torvalds</td> <td>聽</td> <td> <a href="/lkml/2025/2/20/2066" title="Linus Torvalds writes: (Summary) They basically become the maintainers of the Rust interfaces too.<br/> the Rust interfaces too.<br/> But maintainers who are taking the "I don't want to deal with Rust" option also then basically will obviously not have to bother with the Rust bindings - but as a result they also won't have any say on what goes on on the Rust side.<br/> goes on on the Rust side.<br/> So when you change the C interfaces, the Rust people will have to deal with the fallout, and will have to fix the Rust bindings. ">Re: Rust kernel policy</a> </td> </tr> <tr class="c1"> <td>Linus Torvalds</td> <td>聽</td> <td> <a href="/lkml/2025/2/6/1292" title="Linus Torvalds writes: (Summary) wrote: because I'm out of ideas.<br/> How about you accept the fact that maybe the problem is you. It has problems, but problems are a fact of life. It has problems, but problems are a fact of life. The same way it sure as hell wasn't the solution to politics.<br/> wasn't the solution to politics.<br/> Technical patches and discussions matter. Social media brigading - no than\k you.<br/> than\k you.<br/> Linus<br/> Linus<br/> Linus<br/> ">Re: On community influencing (was Re: [PATCH v8 2/...</a> </td> </tr> <tr class="c0"> <td>"Theodore Ts'o"</td> <td>聽</td> <td> <a href="/lkml/2021/4/19/907" title="&quot;Theodore Ts'o&quot; writes: (Summary) [ Feel free to forward this to other Linux kernel mailing lists as appropriate -- Ted ]<br/> appropriate -- Ted ]<br/> This year, the Maintainers and Kernel Summit is currently planned to be held in Dublin, Ireland, September 27 -- 29th. If you were not subscribed on to the kernel@lists.linux-dev mailing list from last year (or if you had removed yourself from the ksummit-discuss@lists.linux-foundation.org mailing list after the previous year's kernel and maintainers' summit summit), you can subscribe sending an e-mail to:<br/> subscribe sending an e-mail to:<br/> ksummit+subscribe@lists.linux.dev<br/> ksummit+subscribe@lists.linux.dev<br/> The mailing list archive is available at:<br/> The mailing list archive is available at:<br/> <a href="https://lore.kernel.org/ksummit">https://lore.kernel.org/ksummit</a><br/> <a href="https://lore.kernel.org/ksummit">https://lore.kernel.org/ksummit</a><br/> The program committee this year is composed of the following people: The program committee this year is com">Maintainers / Kernel Summit 2021 planning kick-off</a> </td> </tr> <tr class="c1"> <td>Steven Rostedt</td> <td>聽</td> <td> <a href="/lkml/2021/6/10/1041" title="Steven Rostedt writes: (Summary) On Thu, 10 Jun 2021 21:20:50 +0100<br/> Matthew Wilcox &lt;willy@infradead.org&gt; wrote:<br/> answered for everybody there.<br/> For presentations, I think this is a very good idea. But it wouldn't work for a BoF or a microconference.<br/> work for a BoF or a microconference.<br/> I also thought about doing this for a presentations. Perhaps instead of going in line to a microphone, go in line to a public laptop to type in your question. in line to a public laptop to type in your question. -- Steve<br/> -- Steve<br/> -- Steve<br/> ">Re: Maintainers / Kernel Summit 2021 planning kick...</a> </td> </tr> <tr class="c0"> <td>Philipp Zabel</td> <td>聽</td> <td> <a href="/lkml/2025/3/13/349" title="Philipp Zabel writes: (Summary) On Mi, 2025-03-12 at 22:59 +0100, Heiko Stuebner wrote: tten [-Werror=3Doverride-init]<br/> 0*4 + reg * 16 + bit)<br/> 562_DDRCRU_RESET_OFFSET'<br/> rk3562_register_offset[173]')<br/> 0*4 + reg * 16 + bit)<br/> 562_DDRCRU_RESET_OFFSET'<br/> ntel.com/<br/> into the clock tree, so this patch should of course also go that way. regards<br/> Philipp<br/> Philipp<br/> Philipp<br/> ">Re: [PATCH] dt-bindings: reset: fix double id on r...</a> </td> </tr> <tr class="c1"> <td>Aradhya Bhatia</td> <td>聽</td> <td> <a href="/lkml/2025/3/11/185" title="Aradhya Bhatia writes: Hi,<br/> Hi,<br/> All the patches within this series have been reviewed. Are there any more concerns that should be taken care of? Are there any more concerns that should be taken care of? Are there any more concerns that should be taken care of? On 26/02/25 21:22, Aradhya Bhatia wrote:<br/> base-commit: 8433c776e1eb1371f5cd40b5fd3a61f9c7b7f3ad ">Re: [PATCH v10 00/13] drm/bridge: cdns-dsi: Fix th...</a> </td> </tr> <tr class="c0"> <td>Dexuan Cui</td> <td>聽</td> <td> <a href="/lkml/2025/3/11/1265" title="Dexuan Cui writes: (Summary) PiBGcm9tOiBOYW1hbiBKYWluIDxuYW1qYWluQGxpbnV4Lm1pY3Jvc29mdC5jb20+DQo+IFNlbnQ6 IE1vbmRheSwgTWFyY2ggMTAsIDIwMjUgOTo0NSBQTQ0KPiA+IFsuLi5dDQo+ID4gSGkgR3JlZywN Cj4gPiBJIHVuZGVyc3RhbmQgdGhpcyBpcyBkZXZpYXRpbmcgZnJvbSB0aGUgZGlzY3Vzc2lvbnMg dGhhdCB3ZSBoYXZlIGhhZA0KPiA+IHRpbGwgbm93LCBidXQgSSB3YW50ZWQgdG8ga2luZGx5IHJl cXVlc3QgeW91ciBvcGluaW9uIG9uIHRoZSBmb2xsb3dpbmcNCj4gPiBhcHByb2FjaCwgd2hpY2gg Y2FtZSB1cCBpbiBvbmUgb2Ygb3VyIGludGVybmFsIGRpc2N1c3Npb25zLg0KPiA+DQo+ID4gQnkg bW92aW5nIHRoZSBzeXNmcyBjcmVhdGlvbiBsb2dpYyBmcm9tIGh2X3Vpb19wcm9iZSB0byBodl91 aW9fb3BlbiwgSQ0KPiA+IGJlbGlldmUgd2UgY2FuIGFkZHJlc3MgdGhpcyBwcm9ibGVtLiBIZXJl IGFyZSBzb21lIG9mIHRoZSBiZW5lZml0cyBvZg0KPiA+IHRoaXMgYXBwcm9hY2g6DQo+ID4NCj4g PiAqIFRoaXMgYXBwcm9hY2ggaW52b2x2ZXMgbWluaW1hbCBjaGFuZ2VzIGFuZCBwcm92aWRlcyBh IGxvY2FsaXplZA0KPiA+IHNvbHV0aW9uLg0KDQpJIHByZWZlciB0aGUgIkFwcHJvYWNoIDEiIGJl bG93LCB3aGljaCByZXF1aXJlcyBvbmx5IDEvMTAgb2YgdGhlIGNoYW5nZXMNCm9mICJBcHByb2Fj aCAyIi4NCg0KPiA+ICogU2luY2UgdGhlIHVzZS1jYXNlIG9mIHJpbmcgc3lzZnMgaXMgc3BlY2lm aWMgdG8gdWlvX2h2X2dlbmV"> RE: [PATCH] uio_hv_generic: Fix sysfs creation pa...</a> </td> </tr> <tr class="c1"> <td>Linus Torvalds</td> <td>聽</td> <td> <a href="/lkml/2025/2/23/351" title="Linus Torvalds writes: (Summary) But nothing is ever perfect, and you really shouldn't expect it to be.<br/> expect it to be.<br/> At the same time, people harping on some rust issues seem to do so not because rust is any worse, but because they have internalized our *normal* issues so much that they don't even think about them. So next time you want to write an email to complain about rust support: take a look in the mirror.<br/> support: take a look in the mirror.<br/> Is the problem actually the rust code causing you issue, or is the problem between the keyboard and the chair, and you just want to vent? ">Re: Rust kernel policy</a> </td> </tr> <tr class="c0"> <td>Cristian Marussi</td> <td>聽</td> <td> <a href="/lkml/2024/1/25/1045" title="Cristian Marussi writes: (Summary) Add a check and bail out early on remove too.<br/> Add a check and bail out early on remove too.<br/> Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008 Mem abort info: ESR = 0x0000000096000004 EC = 0x25: DABT (current EL), IL = 32 bits SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x04: level 0 translation fault Data abort info: ISV = 0, ISS = 0x00000004, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagAccess = 0 GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 user pgtable: 4k pages, 48-bit VAs, pgdp=00000001076e5000 [0000000000000008] pgd=0000000000000000, p4d=0000000000000000 Internal error: Oops: 0000000096000004 [#1] PREEMPT SMP Modules linked in: scmi_perf_domain(-) scmi_module scmi_core CPU: 0 PID: 231 Comm: rmmod Not tainted 6.7.0-00084-gb4b1f27d3b83-dirty #15 Hardware name: linux,dummy-virt (DT) pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) pc : scmi_perf_domain_remove+0x28/0x70 [scmi_perf_domain] lr : scmi_perf_domain_r">[PATCH] pmdomain: arm: Fix NULL dereference on scm...</a> </td> </tr> <tr class="c1"> <td>"tip-bot2 for Ard Biesheuvel"</td> <td>聽</td> <td> <a href="/lkml/2025/3/7/1883" title="&quot;tip-bot2 for Ard Biesheuvel&quot; writes: (Summary) - -/*----------------------------------------------------------------------*/ - -static const u32 crctab32[] = { - 0x00000000, 0x77073096, 0xee0e612c, 0x990951ba, 0x076dc419, - 0x706af48f, 0xe963a535, 0x9e6495a3, 0x0edb8832, 0x79dcb8a4, - 0xe0d5e91e, 0x97d2d988, 0x09b64c2b, 0x7eb17cbd, 0xe7b82d07, - 0x90bf1d91, 0x1db71064, 0x6ab020f2, 0xf3b97148, 0x84be41de, - 0x1adad47d, 0x6ddde4eb, 0xf4d4b551, 0x83d385c7, 0x136c9856, - 0x646ba8c0, 0xfd62f97a, 0x8a65c9ec, 0x14015c4f, 0x63066cd9, - 0xfa0f3d63, 0x8d080df5, 0x3b6e20c8, 0x4c69105e, 0xd56041e4, - 0xa2677172, 0x3c03e4d1, 0x4b04d447, 0xd20d85fd, 0xa50ab56b, - 0x35b5a8fa, 0x42b2986c, 0xdbbbc9d6, 0xacbcf940, 0x32d86ce3, - 0x45df5c75, 0xdcd60dcf, 0xabd13d59, 0x26d930ac, 0x51de003a, - 0xc8d75180, 0xbfd06116, 0x21b4f4b5, 0x56b3c423, 0xcfba9599, - 0xb8bda50f, 0x2802b89e, 0x5f058808, 0xc60cd9b2, 0xb10be924, - 0x2f6f7c87, 0x58684c11, 0xc1611dab, 0xb6662d3d, 0x76dc4190, - 0x01db7106, 0x98d220bc, 0xefd5102a, 0x71b18589, 0x06b6b51f, - 0x9fbfe4a5, 0xe8b8d433, 0x7807c9a2, 0x0f">[tip: x86/build] x86/boot: Drop CRC-32 checksum an...</a> </td> </tr> <tr class="c0"> <td>Petr Mladek</td> <td>聽</td> <td> <a href="/lkml/2025/3/17/1264" title="Petr Mladek writes: On Fri 2025-03-14 12:07:49, adamsimonelli@gmail.com wrote: Signed-off-by: Adam Simonelli &lt;adamsimonelli@gmail.com&gt; JFYI, the patch have been comitted into printk/linux.git, branch for-6.15.<br/> branch for-6.15.<br/> Best Regards,<br/> Petr<br/> Petr<br/> Petr<br/> ">Re: [PATCH v12 1/1] printk: Add an option to allow...</a> </td> </tr> <tr class="c1"> <td>Hector Martin</td> <td>聽</td> <td> <a href="/lkml/2025/2/7/9" title="Hector Martin writes: (Summary) I no longer have any faith left in the kernel development process or community management approach.<br/> community management approach.<br/> Apple/ARM platform development will continue downstream. 1 - 1 file changed, 1 deletion(-) diff --git a/MAINTAINERS b/MAINTAINERS index 1e930c7a58b13d8bbe6bf133ba7b36aa24c2b5e0..c9623439998709c9d6d6944cbd87e025356422da 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -2177,7 +2177,6 @@ F: sound/soc/codecs/cs42l84.* F: sound/soc/codecs/ssm3515.c ARM/APPLE MACHINE SUPPORT -M: Hector Martin &lt;marcan@marcan.st&gt; ">[PATCH] MAINTAINERS: Remove myself</a> </td> </tr> <tr class="c0"> <td>Armin Wolf</td> <td>聽</td> <td> <a href="/lkml/2025/3/5/73" title="Armin Wolf writes: (Summary) Am 03.03.25 um 20:04 schrieb Werner Sembach:<br/> Am 03.03.25 um 20:04 schrieb Werner Sembach:<br/> to<br/> ts<br/> l/git/lenb/linux.git turbostat<br/> s<br/> le<br/> eys.o<br/> uxedo/Kbuild<br/> tuxedo/Kconfig<br/> x86/tuxedo/nb02/Kbuild<br/> /x86/tuxedo/nb02/Kconfig<br/> s<br/> e<br/> orm/x86/tuxedo/nb02/platform.c<br/> +static u8 tux_nb02_touchp_toggle_seq[] =3D {<br/> Hi,<br/> Hi,<br/> please make this const.<br/> please make this const.<br/> t<br/> ))) { &gt; ">Re: [PATCH v2 2/2] Input: atkbd - Fix TUXEDO NB02 ...</a> </td> </tr> <tr class="c1"> <td>Alejandro Colomar</td> <td>聽</td> <td> <a href="/lkml/2025/3/7/1714" title="Alejandro Colomar writes: (Summary) And thanks to our sponsors!<br/> And thanks to our sponsors!<br/> - Adfinis &lt;<a href="https://adfinis.com/&gt;">https://adfinis.com/&gt;</a><br/> - Google &lt;<a href="https://opensource.google/&gt;">https://opensource.google/&gt;</a><br/> - Hudson River Trading &lt;<a href="https://www.hudsonrivertrading.com/&gt;">https://www.hudsonrivertrading.com/&gt;</a> - Meta &lt;<a href="https://www.meta.com/&gt;">https://www.meta.com/&gt;</a><br/> - Red Hat &lt;<a href="https://www.redhat.com/&gt;">https://www.redhat.com/&gt;</a><br/> - Red Hat &lt;<a href="https://www.redhat.com/&gt;">https://www.redhat.com/&gt;</a><br/> Have a lovely day!<br/> Alex<br/> Alex<br/> Alex<br/> You are receiving this message either because:<br/> You are receiving this message either because:<br/> a) (BCC) You contributed to this release.<br/> a) (BCC) You contributed to this release.<br/> b) You are subscribed to &lt;linux-man@vger.kernel.org&gt;, &lt;linux-kernel@vger.kernel.o">man-pages-6.13 released</a> </td> </tr> </table> </td> </tr> </table> </div> </td> </tr> </table> <hr /> <div align="center"> <div style="width: 70ex" align="left"> <h2>LKML.ORG?</h2> <p> In case you haven't read the titlebar of your webbrowser's window: this site is the (unofficial) Linux Kernel Mailing List archive. This mailing list is a rather high-volume list, where (technical) discussions on the design of, and bugs in the Linux kernel take place. If that scares you, please <a href="http://vger.kernel.org/lkml/">read the FAQ</a>. </p> <p> Things you might want to do right now: <ul><li><a href="/lkml/2024/">dive into the archive</a></li><li><a href="/lkml/last100/">read the last 100 messages</a></li><li><a href="/lkml/today/">read today's messages</a></li><li><a href="/lkml/yesterday/">read yesterday's message</a></li></ul></p> </div> </div> <div align="right"><i>(c) 2002-2024 <a href="http://jasper.es/">Jasper Spaans</a></i>|<a href="http://blog.jasper.es/categories.html#lkml-ref">Read the blog</a>|<a href="https://buysellads.com/buy/detail/244952">Advertise on this site.</a></div> <script type="text/javascript"> var _paq = _paq || []; /* tracker methods like "setCustomDimension" should be called before "trackPageView" */ _paq.push(["setDoNotTrack", true]); _paq.push(["disableCookies"]); _paq.push(['trackPageView']); _paq.push(['enableLinkTracking']); (function() { var u="//m.lkml.org/"; _paq.push(['setTrackerUrl', u+'matomo.php']); _paq.push(['setSiteId', '1']); var d=document, g=d.createElement('script'), s=d.getElementsByTagName('script')[0]; g.type='text/javascript'; g.async=true; g.defer=true; g.src=u+'matomo.js'; s.parentNode.insertBefore(g,s); })(); </script> </body> </html>