Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

51 participants
3581 discussions

Cryptocurrency Scam Recovery Services; Top Firm to Recover Lost Crypto, Bitcoin, Lost Wallet, Consult ZEUS CRYPTO RECOVERY SERVICES

by karenschafer030＠gmail.com

ZEUS CRYPTO RECOVERY SERVICES is a specialized digital asset recovery and blockchain intelligence firm dedicated to helping individuals and organizations reclaim lost, stolen, or inaccessible cryptocurrency funds. Leveraging advanced blockchain forensics, cybersecurity expertise, and strategic investigative methods, ZEUS CRYPTO RECOVERY SERVICES works to trace digital transactions, identify fraudulent activity, and pursue viable recovery pathways. The company combines technical precision with legal and compliance awareness to support clients affected by scams, hacking incidents, phishing attacks, investment fraud, and wallet access issues. With a client-focused approach, ZEUS CRYPTO RECOVERY prioritizes transparency, confidentiality, and clear communication throughout the recovery process. Each case is handled with a structured assessment strategy, ensuring that clients receive an honest evaluation of recovery feasibility and actionable next steps. Driven by integrity and innovation, ZEUS aims to restore financial confidence in the evolving digital economy by delivering reliable, secure, and results-oriented crypto recovery solutions. Learn More on their Website: https://zeusrecoveryservices.com Email-Box: support(a)zeusrecoveryservices.com WhatsApp-Number: +447841900082

1 day, 8 hours

Cryptocurrency Scam Recovery Services; Top Firm to Recover Lost Crypto, Bitcoin, Lost Wallet, Consult ZEUS CRYPTO RECOVERY SERVICES

by karenschafer030＠gmail.com

1 day, 8 hours

BEST CRYPTO RECOVERY SERVICE HIRE WHISPERER HACKER RECOVERY

by David Newbill

WHISPERER HACKER RECOVERY specialize in retrieving cryptocurrencies that owners can no longer access. Since cryptocurrencies rely on cryptographic keys for security, losing these keys typically means losing access to one’s funds permanently. Recovery requires deep technical knowledge, advanced hacking skills, and sophisticated tools to bypass security barriers without compromising the integrity of the assets.WHISPERER HACKER RECOVERY distinguishes itself through a combination of cutting-edge technology and experienced professionals who understand blockchain systems intricately. Their approach often involves forensic analysis, password cracking, and key regeneration techniques designed to recover wallets and funds that other services might consider irretrievable. Homepage > whispershackerrecovery . c o m WhatApp ; +44 (73 5 22, 191 25 Mailbox; info @ whispershackerrecovery. c o m

1 day, 8 hours

Best Crypto Recovery Services consult OPTIMISTIC HACKER GAIUS

by patricklucas0522＠gmail.com

I am beyond grateful to Optimistic Hacker Gaius for recovering my scammed crypto. After losing a significant amount to a sophisticated scam, I thought all hope was lost. But Gaius stepped in, explained the process, and worked tirelessly to track and recover my funds. His professionalism and expertise were evident throughout. Thanks to him, I got everything back. If you're in a similar situation, I highly recommend reaching out to Gaius. Truly a lifesaver!" CONTACT INF....... MAIL BOX: support @optimistichackargaius.co.m WEBSITE: https //optimistichackargaius.co.m WHATSapp: +44 737 674 0569

1 day, 14 hours

Best Crypto Recovery Services consult OPTIMISTIC HACKER GAIUS

by patricklucas0522＠gmail.com

1 day, 14 hours

USDT BTC & ETH LOST TO SCAMMER ONLINE VISIT AUTOTECH RECOVERY COMPANY FOR HELP

by josiahdavidson1122＠gmail.com

I am writing to wholeheartedly endorse the exceptional services of Autotech Recovery Company, a company that specializes in recovering lost cryptocurrencies. My experience with them was nothing short of phenomenal, and I am grateful for their expertise and professionalism in retrieving my stolen crypto assets. I fell victim to a cryptocurrency scam after meeting a supposed "friend" through a YouTube video. This individual gained my trust over time, and I unfortunately invested a significant amount of money in a fake cryptocurrency scheme. It wasn't until I tried to withdraw my funds that I realized I had been scammed. The perpetrators had vanished, leaving me with a substantial financial loss and a deep sense of frustration. That's when I discovered Autotech Recovery Company through an online search. I was skeptical at first, given the nature of my situation, but their website and customer testimonials instilled a sense of hope. I decided to reach out to them, and from the initial consultation, I was impressed by their knowledge, empathy, and confidence in their abilities. The team at Autotech Recovery Company took the time to understand my situation, asking pertinent questions and providing a clear explanation of their recovery process. They were transparent about the potential outcomes and kept me informed throughout the entire retrieval process. Their communication was exceptional, and I appreciated the regular updates, which helped to alleviate my anxiety. What struck me most about Autotech Recovery Company was their technical expertise and persistence. They employed cutting-edge technology and innovative strategies to track down the scammers and recover my lost funds. Their dedication to my case was unwavering, and they worked tirelessly to ensure a successful outcome. Thanks to Autotech Recovery Company, I was able to recover a significant portion of my lost cryptocurrency. Their services were worth every penny, and I am grateful for their assistance in mitigating the financial damage caused by the scam. I highly recommend their services to anyone who has fallen victim to cryptocurrency fraud or any other type of online scam. In conclusion, Autotech Recovery Company is a trustworthy and reliable company that delivers on its promises. Their expertise, professionalism, and commitment to customer satisfaction are truly exceptional. If you find yourself in a similar situation, do not hesitate to reach out to them. They will work tirelessly to recover your lost assets and provide you with the peace of mind that comes with knowing you are in capable hands. INFO ABOUT THE COMPANY: WhatsApp: +1 (227) 262-0643 Telegram: +1 (971) 487-6062 Email: support(a)autotechrecoverycompany.com

1 day, 18 hours

Best Crypto Bitcoin Recovery Service | Best Crypto Asset Recovery Service Hire iFORCE HACKER RECOVERY

by Eddie Jolley

I spent a lot of time researching ways to recover stolen Bitcoin after I unexpectedly lost $120,000 during a trade. During my search, I came across multiple testimonials and ads praising the services of iForce Hacker Recovery, so I decided to reach out. I was extremely impressed with the assistance I received. Not only did I get my $120,000 back, but my hacked social media accounts were also restored. If you ever find yourself in a similar situation, don't stress—just contact iForce Hacker Recovery. They can help you recover everything you’ve lost from hacking incidents. Website: ht tps://iforcehackers. co m WhatsApp: +1 240-803-3706 Email: iforcehk @ consultant. c om

1 day, 18 hours

Re: [PATCH v2 0/3] dma-buf: heaps: cma: enable dmem cgroup accounting

by T.J. Mercier

On Wed, Feb 18, 2026 at 9:15 AM Eric Chanudet <echanude(a)redhat.com> wrote: Hi Eric, > An earlier series[1] from Maxime introduced dmem to the cma allocator in > an attempt to use it generally for dma-buf. Restart from there and apply > the charge in the narrower context of the CMA dma-buf heap instead. > > In line with introducing cgroup to the system heap[2], this behavior is > enabled based on dma_heap.mem_accounting, disabled by default. > > dmem is chosen for CMA heaps as it allows limits to be set for each > region backing each heap. The charge is only put in the dma-buf heap for > now as it guaranties it can be accounted against a userspace process > that requested the allocation. But CMA memory is system memory, and regular (non-CMA) movable allocations can occur out of these CMA areas. So this splits system memory accounting between memcg (from [2]) and dmem. If I want to put a limit on system memory use I have to adjust multiple limits (memcg + dmems) and know how to divide the total between them all. How do you envision using this combination of different controllers? Thanks, T.J. > [1] https://lore.kernel.org/all/20250310-dmem-cgroups-v1-0-2984c1bc9312@kernel.… > [2] https://lore.kernel.org/all/20260116-dmabuf-heap-system-memcg-v3-0-ecc6b62c… > > Signed-off-by: Eric Chanudet <echanude(a)redhat.com> > --- > Changes in v2: > - Rebase on Maxime's introduction of dmem to the cma allocator: > https://lore.kernel.org/all/20250310-dmem-cgroups-v1-0-2984c1bc9312@kernel.… > - Remove the dmem region registration from the cma dma-buf heap > - Remove the misplaced logic for the default region. > - Link to v1: https://lore.kernel.org/r/20260130-dmabuf-heap-cma-dmem-v1-1-3647ea993e99@r… > > --- > Eric Chanudet (1): > dma-buf: heaps: cma: charge each cma heap's dmem > > Maxime Ripard (2): > cma: Register dmem region for each cma region > cma: Provide accessor to cma dmem region > > drivers/dma-buf/heaps/cma_heap.c | 15 ++++++++++++++- > include/linux/cma.h | 9 +++++++++ > mm/cma.c | 20 +++++++++++++++++++- > mm/cma.h | 3 +++ > 4 files changed, 45 insertions(+), 2 deletions(-) > --- > base-commit: 948e195dfaa56e48eabda591f97630502ff7e27e > change-id: 20260128-dmabuf-heap-cma-dmem-f4120a2df4a8 > > Best regards, > -- > Eric Chanudet <echanude(a)redhat.com> >

1 day, 18 hours

Re: [PATCH v2 3/3] dma-buf: heaps: cma: charge each cma heap's dmem

by Christian König

On 2/19/26 18:10, Eric Chanudet wrote: > On Thu, Feb 19, 2026 at 08:17:28AM +0100, Christian König wrote: >> >> >> On 2/18/26 18:14, Eric Chanudet wrote: >>> The cma dma-buf heaps let userspace allocate buffers in CMA regions >>> without enforcing limits. Since each cma region registers in dmem, >>> charge against it when allocating a buffer in a cma heap. >>> >>> Signed-off-by: Eric Chanudet <echanude(a)redhat.com> >>> --- >>> drivers/dma-buf/heaps/cma_heap.c | 15 ++++++++++++++- >>> 1 file changed, 14 insertions(+), 1 deletion(-) >>> >>> diff --git a/drivers/dma-buf/heaps/cma_heap.c b/drivers/dma-buf/heaps/cma_heap.c >>> index 49cc45fb42dd7200c3c14384bcfdbe85323454b1..bbd4f9495808da19256d97bd6a4dca3e1b0a30a0 100644 >>> --- a/drivers/dma-buf/heaps/cma_heap.c >>> +++ b/drivers/dma-buf/heaps/cma_heap.c >>> @@ -27,6 +27,7 @@ >>> #include <linux/scatterlist.h> >>> #include <linux/slab.h> >>> #include <linux/vmalloc.h> >>> +#include <linux/cgroup_dmem.h> >>> >>> #define DEFAULT_CMA_NAME "default_cma_region" >>> >>> @@ -58,6 +59,7 @@ struct cma_heap_buffer { >>> pgoff_t pagecount; >>> int vmap_cnt; >>> void *vaddr; >>> + struct dmem_cgroup_pool_state *pool; >>> }; >>> >>> struct dma_heap_attachment { >>> @@ -276,6 +278,7 @@ static void cma_heap_dma_buf_release(struct dma_buf *dmabuf) >>> kfree(buffer->pages); >>> /* release memory */ >>> cma_release(cma_heap->cma, buffer->cma_pages, buffer->pagecount); >>> + dmem_cgroup_uncharge(buffer->pool, buffer->len); >>> kfree(buffer); >>> } >>> >>> @@ -319,9 +322,17 @@ static struct dma_buf *cma_heap_allocate(struct dma_heap *heap, >>> if (align > CONFIG_CMA_ALIGNMENT) >>> align = CONFIG_CMA_ALIGNMENT; >>> >>> + if (mem_accounting) { >> >> Since mem_accounting is a module parameter it is possible to make it changeable during runtime. >> >> IIRC it currently is read only, but maybe add a one line comment that the cma heap now depends on that. >> > > Agreed, while read-only it is easily missed without at least a comment. > Alternatively, should that value be captured in the init callback to > guaranty it is set once and make this requirement clearer? It probably makes more sense to make nails with heads and make it runtime configurable. I'm not sure how exactly dmem_cgroup_try_charge()/dmem_cgroup_uncharge() works, could be that it works correctly out of the box and you just need to initialize buffer->pool to NULL when mem_accounting is not enabled. Regards, Christian. > > Thanks, > >> Apart from that the series looks totally sane to me. >> >> Regards, >> Christian. >> >>> + ret = dmem_cgroup_try_charge( >>> + cma_get_dmem_cgroup_region(cma_heap->cma), size, >>> + &buffer->pool, NULL); >>> + if (ret) >>> + goto free_buffer; >>> + } >>> + >>> cma_pages = cma_alloc(cma_heap->cma, pagecount, align, false); >>> if (!cma_pages) >>> - goto free_buffer; >>> + goto uncharge_cgroup; >>> >>> /* Clear the cma pages */ >>> if (PageHighMem(cma_pages)) { >>> @@ -376,6 +387,8 @@ static struct dma_buf *cma_heap_allocate(struct dma_heap *heap, >>> kfree(buffer->pages); >>> free_cma: >>> cma_release(cma_heap->cma, cma_pages, pagecount); >>> +uncharge_cgroup: >>> + dmem_cgroup_uncharge(buffer->pool, size); >>> free_buffer: >>> kfree(buffer); >>> >>> >> >

1 day, 20 hours

Re: [PATCH 08/13] dt-bindings: serial: fsl-linflexuart: add clock input properties

by Krzysztof Kozlowski

On 16/02/2026 16:02, Larisa Grigore wrote: > From: Radu Pirea <radu-nicolae.pirea(a)nxp.com> > > Add optional support for the two clock inputs used by the LINFlexD UART > controller: > - "lin": LIN_BAUD_CLK > - "ipg": LINFLEXD_CLK > > The clock inputs are kept optional to maintain compatibility with the > S32V234 platform. Does S32V234 have the clocks? I don't understand the "maintain compatibility" in this context. Either you have or you have not clocks, which should be expressed in schema (: false, see example schema). > > Signed-off-by: Radu Pirea <radu-nicolae.pirea(a)nxp.com> > Co-developed-by: Larisa Grigore <larisa.grigore(a)oss.nxp.com> > Signed-off-by: Larisa Grigore <larisa.grigore(a)oss.nxp.com> > --- > .../bindings/serial/fsl,s32-linflexuart.yaml | 18 ++++++++++++++++++ > 1 file changed, 18 insertions(+) > > diff --git a/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml b/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml > index 4171f524a928..885f0b1b3492 100644 > --- a/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml > +++ b/Documentation/devicetree/bindings/serial/fsl,s32-linflexuart.yaml > @@ -34,6 +34,14 @@ properties: > interrupts: > maxItems: 1 > > + clocks: > + maxItems: 2 > + > + clock-names: > + items: > + - const: lin > + - const: ipg > + > required: > - compatible > - reg > @@ -48,3 +56,13 @@ examples: > reg = <0x40053000 0x1000>; > interrupts = <0 59 4>; > }; > + > + - | > + serial@401c8000 { > + compatible = "nxp,s32g2-linflexuart", > + "fsl,s32v234-linflexuart"; > + reg = <0x401C8000 0x3000>; > + interrupts = <0 82 1>; > + clocks = <&clks 14>, <&clks 13>; > + clock-names = "lin", "ipg"; Just add the clocks to existing example. No need for new example for each new property. > + }; Best regards, Krzysztof

2 days, 6 hours

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig