Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

49 participants
6027 discussions

2026 Top Guide To Recover Lost Cryptocurrency With Trusted Agency

by ezra Jack

If you have been the victim of a cryptocurrency scam in 2026 — whether through a fake investment platform, pig-butchering romance scheme, phishing attack, wallet drainer, impersonation fraud, or address-poisoning trick — filing an official complaint is one of the most important early actions you can take. A well-documented complaint creates a legal record, helps law enforcement track patterns and perpetrators, may trigger platform-level freezes or investigations, and significantly strengthens any legitimate recovery effort. Autopsy Mainnet Recovery (AMR) , widely regarded as one of the top legitimate crypto recovery companies in 2026, assists victims not only with advanced blockchain tracing and legal coordination but also with preparing strong, compliant scam complaints that maximize the chances of successful asset recovery. Autopsy Mainnet Recovery (AMR) 's many years of experience helping individuals in New York City and worldwide have shown that victims who file thorough reports early — and then immediately engage professional recovery support — have the highest realistic probability of reclaiming stolen funds. This step-by-step guide explains exactly how to file an effective crypto scam complaint in 2026 and why hiring a trusted recovery expert like Autopsy Mainnet Recovery (AMR) right afterward is essential for turning your report into real recovery action. Step 1: Immediately Secure Your Environment & Stop Further Loss Before filing any complaint, protect what remains. Cease all contact with the scammer — no replies, no additional payments, no “verification” transfers. Revoke suspicious token approvals (especially on Ethereum-compatible chains) using Revoke.cash or Etherscan’s approval checker. Disconnect compromised devices from the internet. Change passwords on all related accounts from a clean device. Transfer any untouched cryptocurrency to a brand-new hardware wallet (Ledger, Trezor, etc.) never exposed to the compromised environment. Enable app-based multi-factor authentication (not SMS) everywhere. Why this step matters first: Any further loss weakens your case and makes tracing harder. Step 2: Preserve All Evidence (Do Not Delete or Alter Anything) A strong complaint depends on complete, unaltered evidence. Collect and securely save (offline USB or encrypted cloud): Transaction IDs (TXIDs) and full hashes Your wallet address and the scammer’s wallet address Exact timestamps of every transaction Full screenshots of scam communications (email, Telegram, WhatsApp, Discord, SMS, social media) Screenshots of fake websites, trading platforms, phishing pages, fabricated profit dashboards Any platform names, URLs, usernames, wallet addresses, or promotional materials Copies of any investment promises, “guaranteed return” claims, or withdrawal blocks Tip from Autopsy Mainnet Recovery (AMR) : Even seemingly small details (e.g., a username or partial URL) can help forensic teams link wallets and identify scammer clusters. Step 3: File Your Official Crypto Scam Complaint (Within 24–48 Hours) File with the following authorities and platforms — each plays a different role in building your case. A. Local Law Enforcement (Critical First Report) In New York City: File online via the NYPD website or in person at your local precinct. Provide a clear narrative: what happened, when, how much was lost, wallet addresses, TXIDs, and attach all evidence. Request a police report number — this becomes a key reference for federal agencies and recovery professionals. B. FBI Internet Crime Complaint Center (IC3) File at ic3.gov Select “Cryptocurrency” as the crime type and provide detailed narrative + evidence upload The IC3 aggregates data for federal investigations and often shares with specialized crypto task forces. C. Federal Trade Commission (FTC) File at reportfraud.ftc.gov Use the “Imposter Scams” or “Investment Scams” category The FTC tracks trends and shares data with law enforcement. D. Chainabuse.com Submit a public scam report with wallet addresses and TXIDs Chainabuse is used by many exchanges and recovery firms to flag high-risk addresses. E. Affected Platforms Report to the exchange, wallet provider, or app involved (if any). They may freeze related accounts or flag addresses. Tip from Autopsy Mainnet Recovery (AMR) : Keep every confirmation number and reference ID. These are used when Autopsy Mainnet Recovery (AMR) submits forensic reports to authorities for wallet freezes or seizures. Step 4: Hire a Trusted, Legitimate Recovery Expert Immediately Filing a complaint is essential, but it rarely recovers funds on its own. Professional tracing, real-time monitoring, and legal coordination are required to turn a report into actual asset reclamation. Hire Autopsy Mainnet Recovery (AMR) right after filing your complaint — do not wait. Contact Autopsy Mainnet Recovery (AMR) securely at: Website: autopsymainnetsolutions.com Email: info(a)autopsymainnetsolutions.com Submit your police/IC3/FTC report numbers and all evidence for a free, confidential case evaluation. XHR will quickly assess traceability and begin forensic work while the trail is fresh. Why Autopsy Mainnet Recovery (AMR) is one of the top choices for scam recovery in 2026: Free initial evaluation — no obligation, no private key/seed phrase requests Advanced blockchain forensics — transaction mapping, address clustering, pattern detection, cross-chain tracing, real-time alerts Strong U.S. law enforcement partnerships — forensic reports formatted for freezes, subpoenas, KYC enforcement, and seizures Transparent process — regular updates, realistic expectations, often success-based fees Full post-recovery support — secure asset return + comprehensive security hardening (hardware wallets, multi-sig, MFA, audits, scam education) Step 5: Support the Recovery Process & Protect Your Future Once Autopsy Mainnet Recovery (AMR) begins work, stay responsive to any additional evidence requests. They will trace the funds, prepare legal documentation, and coordinate enforcement action. After recovery (partial or full), Autopsy Mainnet Recovery (AMR) guides you through: Hardware wallet setup with passphrase protection Multi-signature wallets for larger holdings Regular token permission audits App-based MFA and scam-awareness training Final urgent advice for 2026 victims: Do not give private keys or seed phrases to any service before work begins. File your official complaints today, then immediately contact Autopsy Mainnet Recovery (AMR) — one of the most trusted and effective legitimate recovery services in the United States — for professional, ethical, and results-oriented help: Website: autopsymainnetsolutions.com Website: https://autospyrec.site Email: info(a)autopsymainnetsolutions.com Your stolen cryptocurrency may still be traceable. Act now. Preserve your evidence. Choose trust. Reclaim your assets.

1 week, 6 days

2026 Effective Methods To Reclaim Scammed Crypto Using Recovery Experts

by Mata Marcus

1 week, 6 days

2026 Best Ways To Retrieve Stolen Cryptocurrency Through Recovery Service

by Sandra Lopez

1 week, 6 days

2026 Top Strategies For Recovering Lost Crypto With Expert Company

by florabenson93＠gmail.com

1 week, 6 days

2026 Proven Ways To Reclaim Scammed Cryptocurrency With Trusted Recovery Agency

by aubreyasher46＠gmail.com

1 week, 6 days

2026 Top Methods To Retrieve Stolen Crypto Using Expert Recovery Service

by masoncaleb2a＠gmail.com

1 week, 6 days

2026 Top Ways On How Recover Lost Cryptocurrency With Best Recovery Company

by codykayson983＠gmail.com

1 week, 6 days

Re: [PATCH 5/9] accel/neutron: Add GEM buffer object support

by kernel test robot

Hi Ioana, kernel test robot noticed the following build warnings: [auto build test WARNING on 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f] url: https://github.com/intel-lab-lkp/linux/commits/Ioana-Ciocoi-Radulescu/drm-g… base: 6de23f81a5e08be8fbf5e8d7e9febc72a5b5f27f patch link: https://lore.kernel.org/r/20260226-neutron-v1-5-46eccb3bb50a%40nxp.com patch subject: [PATCH 5/9] accel/neutron: Add GEM buffer object support config: arm64-allmodconfig (https://download.01.org/0day-ci/archive/20260227/202602270531.MP8x6wo3-lkp@…) compiler: clang version 19.1.7 (https://github.com/llvm/llvm-project cd708029e0b2869e80abe31ddb175f7c35361f90) reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260227/202602270531.MP8x6wo3-lkp@…) If you fix the issue in a separate patch/commit (i.e. not just a new version of the same patch/commit), kindly add following tags | Reported-by: kernel test robot <lkp(a)intel.com> | Closes: https://lore.kernel.org/oe-kbuild-all/202602270531.MP8x6wo3-lkp@intel.com/ All warnings (new ones prefixed by >>): >> drivers/accel/neutron/neutron_gem.c:52:6: warning: variable 'gem_obj' is used uninitialized whenever 'if' condition is true [-Wsometimes-uninitialized] 52 | if (drm_WARN_ON(drm, !IS_ALIGNED(dma_obj->dma_addr, NEUTRON_BO_ALIGN))) { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ include/drm/drm_print.h:789:2: note: expanded from macro 'drm_WARN_ON' 789 | drm_WARN((drm), (x), "%s", \ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 790 | "drm_WARN_ON(" __stringify(x) ")") | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ include/drm/drm_print.h:779:2: note: expanded from macro 'drm_WARN' 779 | WARN(condition, "%s %s: [drm] " format, \ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 780 | dev_driver_string(__drm_to_dev(drm)), \ | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 781 | dev_name(__drm_to_dev(drm)), ## arg) | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ include/asm-generic/bug.h:163:36: note: expanded from macro 'WARN' 163 | #define WARN(condition, format...) ({ \ | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 164 | int __ret_warn_on = !!(condition); \ | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 165 | if (unlikely(__ret_warn_on)) \ | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 166 | __WARN_printf(TAINT_WARN, format); \ | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 167 | unlikely(__ret_warn_on); \ | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 168 | }) | ~~ drivers/accel/neutron/neutron_gem.c:67:21: note: uninitialized use occurs here 67 | drm_gem_object_put(gem_obj); | ^~~~~~~ drivers/accel/neutron/neutron_gem.c:52:2: note: remove the 'if' if its condition is always false 52 | if (drm_WARN_ON(drm, !IS_ALIGNED(dma_obj->dma_addr, NEUTRON_BO_ALIGN))) { | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 53 | ret = -EFAULT; | ~~~~~~~~~~~~~~ 54 | goto out_put; | ~~~~~~~~~~~~~ 55 | } | ~ drivers/accel/neutron/neutron_gem.c:38:32: note: initialize the variable 'gem_obj' to silence this warning 38 | struct drm_gem_object *gem_obj; | ^ | = NULL 1 warning generated. vim +52 drivers/accel/neutron/neutron_gem.c 33 34 int neutron_ioctl_create_bo(struct drm_device *drm, void *data, struct drm_file *filp) 35 { 36 struct drm_neutron_create_bo *args = data; 37 struct drm_gem_dma_object *dma_obj; 38 struct drm_gem_object *gem_obj; 39 size_t size; 40 int ret; 41 42 if (!args->size || args->pad) 43 return -EINVAL; 44 45 size = ALIGN(args->size, NEUTRON_BO_ALIGN); 46 47 dma_obj = drm_gem_dma_create(drm, size); 48 if (IS_ERR(dma_obj)) 49 return PTR_ERR(dma_obj); 50 51 /* We expect correctly aligned buffers, but double-check */ > 52 if (drm_WARN_ON(drm, !IS_ALIGNED(dma_obj->dma_addr, NEUTRON_BO_ALIGN))) { 53 ret = -EFAULT; 54 goto out_put; 55 } 56 57 gem_obj = &dma_obj->base; 58 ret = drm_gem_handle_create(filp, gem_obj, &args->handle); 59 if (ret) 60 goto out_put; 61 62 args->map_offset = drm_vma_node_offset_addr(&gem_obj->vma_node); 63 args->size = gem_obj->size; 64 65 out_put: 66 /* No need to keep a reference of the GEM object. Freeing is handled by user */ 67 drm_gem_object_put(gem_obj); 68 69 return ret; 70 } 71 -- 0-DAY CI Kernel Test Service https://github.com/intel/lkp-tests/wiki

1 week, 6 days

Re: [PATCH 3/9] dt-bindings: npu: Add bindings for NXP Neutron

by Conor Dooley

On Thu, Feb 26, 2026 at 03:40:42PM +0200, Ioana Ciocoi-Radulescu wrote: > Add the bindings for Neutron, a Neural Processing Unit from NXP. > > Signed-off-by: Jiwei Fu <jiwei.fu(a)nxp.com> You are the author and submitter. What did Jiwei do? > Signed-off-by: Ioana Ciocoi-Radulescu <ruxandra.radulescu(a)nxp.com> > --- > .../devicetree/bindings/npu/nxp,imx95-neutron.yaml | 95 ++++++++++++++++++++++ > 1 file changed, 95 insertions(+) > > diff --git a/Documentation/devicetree/bindings/npu/nxp,imx95-neutron.yaml b/Documentation/devicetree/bindings/npu/nxp,imx95-neutron.yaml > new file mode 100644 > index 000000000000..ba1f6851866b > --- /dev/null > +++ b/Documentation/devicetree/bindings/npu/nxp,imx95-neutron.yaml > @@ -0,0 +1,95 @@ > +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) > +%YAML 1.2 > +--- > +$id: http://devicetree.org/schemas/npu/nxp,imx95-neutron.yaml# > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: NXP Neutron NPU > + > +maintainers: > + - Ioana Ciocoi-Radulescu <ruxandra.radulescu(a)nxp.com> > + - Jiwei Fu <jiwei.fu(a)nxp.com> > + > +description: > + Neutron is an NPU from NXP targeting edge AI inference applications. > + Initially supported on i.MX95 SoCs. > + > +properties: > + compatible: > + enum: > + - nxp,imx95-neutron > + > + reg: > + items: > + - description: Register space > + - description: Instruction area of the TCM space > + - description: Data area of the TCM space > + > + reg-names: > + items: > + - const: regs > + - const: itcm > + - const: dtcm > + > + memory-region: > + description: > + Phandle referencing a "shared-dma-pool" to be used for Neutron > + inference buffers, which need to be 1MB aligned. > + > + The memory region must be defined with alignment of 1MB and size > + should be large enough to accommodate the targeted ML models. It > + should be marked as reusable. > + maxItems: 1 > + > + interrupts: > + maxItems: 1 > + > + clocks: > + minItems: 2 > + maxItems: 3 > + > + clock-names: > + minItems: 2 > + items: > + - const: npu > + - const: npu_apb > + - const: npu_cgc clocks should be done as reg is, with the descriptions in the !-names property. Not really keen on the names either, these are all npu clocks so the npu prefix is odd. Additionally, why is the number of clocks variable when you only have one platform? > + > + iommus: > + maxItems: 1 > + > + power-domains: > + maxItems: 1 > + > +required: > + - compatible > + - reg > + - reg-names > + - memory-region > + - interrupts Odd that clocks are not mandatory! > + > +additionalProperties: false > + > +examples: > + - | > + #include <dt-bindings/interrupt-controller/arm-gic.h> > + #include <dt-bindings/interrupt-controller/irq.h> > + > + bus { > + #address-cells = <2>; > + #size-cells = <2>; > + > + neutron@4ab00000 { "neutron" is not a generic node name. This should be something like "accelerator" or similar. pw-bot: changes-requested Cheers, Conor. > + compatible = "nxp,imx95-neutron"; > + reg = <0x0 0x4ab00000 0x0 0x00000400>, > + <0x0 0x4AB10000 0x0 0x00010000>, > + <0x0 0x4AB08000 0x0 0x00008000>; > + reg-names = "regs", "itcm", "dtcm"; > + memory-region = <&neutron_pool>; > + interrupts = <GIC_SPI 318 IRQ_TYPE_LEVEL_HIGH>; > + clocks = <&scmi_clk 68>, <&scmi_clk 67>; > + clock-names = "npu", "npu_apb"; > + power-domains = <&scmi_devpd 20>; > + }; > + }; > +... > > -- > 2.34.1 >

1 week, 6 days

Re: [PATCH 19/61] affs: update format strings for u64 i_ino

by David Sterba

On Thu, Feb 26, 2026 at 10:55:21AM -0500, Jeff Layton wrote: > Update format strings and local variable types in affs for the > i_ino type change from unsigned long to u64. > > Signed-off-by: Jeff Layton <jlayton(a)kernel.org> Acked-by: David Sterba <dsterba(a)suse.com>

2 weeks

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig