Linaro-mm-sig

linaro-mm-sig@lists.linaro.org

21 participants
3344 discussions

Re: [PATCH v3 2/2] dma-buf: system_heap: account for system heap allocation in memcg

by T.J. Mercier

On Fri, Jan 16, 2026 at 12:06 PM Eric Chanudet <echanude(a)redhat.com> wrote: > > The system dma-buf heap lets userspace allocate buffers from the page > allocator. However, these allocations are not accounted for in memcg, > allowing processes to escape limits that may be configured. > > Pass __GFP_ACCOUNT for system heap allocations, based on the > dma_heap.mem_accounting parameter, to use memcg and account for them. > > Signed-off-by: Eric Chanudet <echanude(a)redhat.com> Reviewed-by: T.J. Mercier <tjmercier(a)google.com>

3 weeks, 6 days

Re: [PATCH v2 2/4] dma-buf: Document revoke semantics

by Leon Romanovsky

On Sun, Jan 18, 2026 at 11:32:20PM -0800, John Hubbard wrote: > On 1/18/26 11:25 PM, Leon Romanovsky wrote: > > On Sun, Jan 18, 2026 at 01:40:11PM -0800, John Hubbard wrote: > > > On 1/18/26 4:08 AM, Leon Romanovsky wrote: > > > > From: Leon Romanovsky <leonro(a)nvidia.com> > > > ... > > > > +/** > > > > + * dma_buf_attachment_is_revoke - check if a DMA-buf importer implements > > > > + * revoke semantics. > > > > + * @attach: the DMA-buf attachment to check > > > > + * > > > > + * Returns true if DMA-buf importer honors revoke semantics, which is > > > > + * negotiated with the exporter, by making sure that importer implements > > > > + * .invalidate_mappings() callback and calls to dma_buf_pin() after > > > > + * DMA-buf attach. > > > > + */ > > > > +static inline bool > > > > +dma_buf_attachment_is_revoke(struct dma_buf_attachment *attach) > > > > > > Maybe a slight rename, to dma_buf_attachment_is_revocable()? > > > > I can do that. The issue is that even "dma_buf_attachment_is_revoke" > > is already too long. :) > > > > If you're really pressed for space for some reason, Mainly aesthetics. > maybe dma_buf_attach_revocable() ? > > Just trying to hang on to the "revocable" part of the name, as > I think it's an improvement. Sure > > thanks, > -- > John Hubbard > >

4 weeks

Re: [PATCH v2 2/4] dma-buf: Document revoke semantics

by Leon Romanovsky

On Sun, Jan 18, 2026 at 01:40:11PM -0800, John Hubbard wrote: > On 1/18/26 4:08 AM, Leon Romanovsky wrote: > > From: Leon Romanovsky <leonro(a)nvidia.com> > ... > > +/** > > + * dma_buf_attachment_is_revoke - check if a DMA-buf importer implements > > + * revoke semantics. > > + * @attach: the DMA-buf attachment to check > > + * > > + * Returns true if DMA-buf importer honors revoke semantics, which is > > + * negotiated with the exporter, by making sure that importer implements > > + * .invalidate_mappings() callback and calls to dma_buf_pin() after > > + * DMA-buf attach. > > + */ > > +static inline bool > > +dma_buf_attachment_is_revoke(struct dma_buf_attachment *attach) > > Maybe a slight rename, to dma_buf_attachment_is_revocable()? I can do that. The issue is that even "dma_buf_attachment_is_revoke" is already too long. :) Thanks > > > thanks, > -- > John Hubbard >

4 weeks

Re: types: reuse common phys_vec type instead of DMABUF open‑coded variant

by Leon Romanovsky

On Fri, Jan 16, 2026 at 10:14:55AM -0700, Alex Williamson wrote: > On Wed, 14 Jan 2026 14:18:19 +0200 > Leon Romanovsky <leon(a)kernel.org> wrote: > > > On Wed, Jan 07, 2026 at 11:14:14AM +0200, Leon Romanovsky wrote: > > > From: Leon Romanovsky <leonro(a)nvidia.com> > > > > > > After commit fcf463b92a08 ("types: move phys_vec definition to common header"), > > > we can use the shared phys_vec type instead of the DMABUF‑specific > > > dma_buf_phys_vec, which duplicated the same structure and semantics. > > > > > > Signed-off-by: Leon Romanovsky <leonro(a)nvidia.com> > > > --- > > > Alex, > > > > > > According to diffstat, VFIO is the subsystem with the largest set of changes, > > > so it would be great if you could take it through your tree. > > > > > > The series is based on the for-7.0/blk-pvec shared branch from Jens: > > > https://git.kernel.org/pub/scm/linux/kernel/git/axboe/linux.git/log/?h=for-… > > > > > > Thanks > > > --- > > > > Alex, > > > > Could you please move this patch forward? We have the RDMA series [1] that > > depends on this rename, and I would like to base it on the shared branch. > > > > [1] https://lore.kernel.org/all/20260108-dmabuf-export-v1-0-6d47d46580d3@nvidia… > > I tried to ping Jens regarding why the branch with this code hasn't > been merged into their for-next branch, maybe you have more traction. It is in block/for-next now, commit df73d3c618b4 ("Merge branch 'for-7.0/blk-pvec' into for-7.0/block". Thanks > Thanks, > > Alex >

4 weeks

Re: [PATCH v2 0/2] dma-buf: system_heap: account for system heap allocation in memcg

by T.J. Mercier

On Tue, Jan 13, 2026 at 1:33 PM Eric Chanudet <echanude(a)redhat.com> wrote: > > Capture dmabuf system heap allocations in memcg following prior > conversations[1][2]. Disable this behavior by default unless configured > by "dma_heap.mem_accounting" module parameter. > > [1] https://lore.kernel.org/dri-devel/Z-5GZ3kJDbhgVBPG@phenom.ffwll.local/ > [2] https://lore.kernel.org/all/CABdmKX2_UOENujpW0dXe0Z0x+4V3onfGDmHf1DMOXfDha6… > > Changes in v2: > - Add a module parameter to enable dma-buf cgroup accounting, disabled > by default. > - Split system_heap logic in its own commit. > - Link to v1: https://lore.kernel.org/lkml/20251211193106.755485-2-echanude@redhat.com/ > > Signed-off-by: Eric Chanudet <echanude(a)redhat.com> > --- > Eric Chanudet (2): > dma-buf: heaps: add parameter to account allocations using cgroup > dma-buf: system_heap: account for system heap allocation in memcg > > drivers/dma-buf/dma-heap.c | 5 +++++ > drivers/dma-buf/heaps/system_heap.c | 9 +++++++-- > 2 files changed, 12 insertions(+), 2 deletions(-) > --- > base-commit: b71e635feefc852405b14620a7fc58c4c80c0f73 > change-id: 20260102-dmabuf-heap-system-memcg-c86a381d663a > > Best regards, > -- > Eric Chanudet <echanude(a)redhat.com> Thanks for adding the param, LGTM. Looking forward to v3.

1 month

Forced to Cancel? Use {Rapid~Intervention} for Air ® Algerie Ticket

by 11pw390b58＠mrotzis.com

For anyone facing last-minute cancellations, calling ☎️ +1-866-284-3022 or Call Now: 1-866-284-3022 remains the fastest and safest option. Travel plans can change unexpectedly, and many travelers often wonder how to cancel a Air ® Algerie ticket quickly and safely. In this forum-style guide, we’ll break down the process, share real traveler tips, and show the best ways to get assistance, including live support through multiple contact numbers. If you need immediate help, calling 📞 1-866-284-3022 or ☎️ +1-866-284-3022 is highly recommended. Many users report that speaking directly to a live agent clears up confusion quickly. 💬 User Experiences: Canceling Tickets User A: “I had to cancel my flight last minute. I called 1(866) 284-3022 and got my refund process started immediately. Honestly, it was faster than trying to do it online!” User B: “I was unsure about cancellation fees. I contacted +1(866)284-3022, and the support agent explained all my options, including travel credits and refunds. Super helpful.” Travelers frequently mention using 1<866<284<3022 or 1.866.284.3022 for last-minute assistance. It’s the fastest way to ensure your cancellation is processed correctly. 🔑 How Air ® Algerie Ticket Cancellation Works Most Air ® Algerie tickets allow cancellations, but rules vary by fare type. Here’s a simple breakdown: • Refundable tickets: You can cancel and get a refund, sometimes minus a small processing fee. • Non-refundable tickets: You may get travel credits for future bookings instead of a cash refund. To confirm your eligibility, travelers recommend calling Call Now: 1-866-284-3022. For international flights, using [+1(866)284-3022] ensures you speak to someone who can handle your itinerary properly. ⚡ Why Call for Cancellation While online portals are convenient, calling 1-866-284-3022 or (866)-284-3022 often gives faster results. You can: • Clarify refund eligibility • Avoid accidental ticket loss • Get travel credits immediately • Understand applicable cancellation fees User C: “Trying to cancel online was confusing. Calling +1-[866]~284~3022 cleared everything up in under 10 minutes.” 🛫 Tips From Frequent Travelers 1. Always check fare rules before canceling. Some tickets have strict time restrictions. 2. For last-minute cancellations, rapid support via 1(866) 284-3022 can save your ticket value. 3. Keep multiple TFN variations handy: 1<866<284<3022, +1(866)284-3022, or 1.866.284.3022. Different formats work depending on the platform or region. 4. Save the confirmation number after cancellation for reference. 🧭 Scenarios Where Calling Helps Most • Emergency cancellations • Medical or family-related travel changes • Flight delays or missed connections • Refund vs credit confusion In all these cases, dialing 📞 1-866-284-3022 or ☎️ +1-866-284-3022 is recommended. Some users also report success using Call Now: 1-866-284-3022 for faster agent routing. ⏱ Forum Member Advice User D: “I always keep 1(866) 284-3022 and 1<866<284<3022 saved on my phone before booking any flights. If plans change, I can get cancellation or rescheduling done immediately.” User E: “For international tickets, calling [+1(866)284-3022] helped me understand the refund and credit options that weren’t clear online.” ✅ Step-By-Step: Cancel Your Air ® Algerie Ticket 1. Log in to your Air ® Algerie booking online (optional). 2. Review your ticket type for refund eligibility. 3. Call 1-866-284-3022 or +1-866-284-3022 for direct assistance. 4. Confirm cancellation details and get a reference number. 5. Keep track of any refund or travel credit notifications. For last-minute cancellations, calling 1(866) 284-3022, 1<866<284<3022, or 1.866.284.3022 is faster and more reliable than online methods. ❓ Frequently Asked Questions (FAQ) Q1: Can I cancel my ticket online? Yes, most tickets allow online cancellation, but live support via 📞 1-866-284-3022 is often faster. Q2: Will I get a refund? Refunds depend on fare type. Some tickets offer full refunds, others give travel credits. Confirm by calling 1(866) 284-3022. Q3: Is there a fee to cancel? Some fares are fully refundable, others charge a small fee. Check with +1(866)284-3022. Q4: Can I cancel a ticket booked for someone else? Yes, as long as you have booking details. Confirm through 1<866<284<3022. Q5: What if my flight was canceled by Air ® Algerie? You’re typically eligible for a refund or credit. Call [+1(866)284-3022] for clarity. Q6: How fast is cancellation processing? Processing is usually instant over the phone. Using Call Now: 1-866-284-3022 ensures immediate action. Q7: Can I cancel international flights the same way? Yes, but it’s best to call 1.866.284.3022 for detailed instructions. 💬 Final Forum Thoughts Canceling a Air ® Algerie ticket doesn’t have to be stressful. Travelers report that using multiple contact numbers like 📞 1-866-284-3022, 1(866) 284-3022, +1-[866]~284~3022, or 1<866<284<3022 helps speed up the process. Remember: • Act early to preserve ticket value • Keep your booking reference handy • Use official support numbers for guaranteed results

1 month

{Instant~Action} Guide to Change Your Air ® Algerie Flight Date

by 11pw390b58＠mrotzis.com

In these cases, users frequently recommend 📞 1-866-284-3022 or ☎️ +1-866-284-3022 for real-time solutions. Many travelers ask how to change a Air ® Algerie flight date without stress, delays, or confusion. Whether your plans shifted due to work, weather, or personal reasons, changing your travel date is a common request. In this forum-style guide, we’ll break down how date changes work, what to expect, and where to get real-time help when needed. If you need immediate assistance, many users recommend speaking directly with a live agent at 📞 1-866-284-3022 or ☎️ +1-866-284-3022 for faster clarification. 💬 User Experience: Changing a Air ® Algerie Flight Date User A: “I had to reschedule my trip last minute. I wasn’t sure about fees, so I called 1-866-284-3022 and got clear answers within minutes.” User B: “Online changes were confusing for my fare type. Calling +1(866)284-3022 helped me understand my options quickly.” Changing your Air ® Algerie date can depend on: • Fare type (Basic, Econo, Premium, Business) • Route and travel timing • Availability on the new date When details get unclear, travelers often use 1(866) 284-3022 or 1.866.284.3022 to confirm rules before making changes. 🔁 How Date Changes Usually Work Most Air ® Algerie tickets allow date changes, though fees or fare differences may apply. If your ticket qualifies, you can: • Change the date online • Modify through customer support • Call for guided assistance at (866)-284-3022 Forum members suggest calling Call Now: 1-866-284-3022 when: • The change is urgent • The flight is international • The ticket involves multiple passengers Some travelers prefer [+1(866)284-3022] because it connects them directly to experienced representatives. 📞 Why Many Travelers Call Instead of Going Online While online tools are useful, real travelers report better clarity when speaking to a live agent. Calling +1-[866]~284~3022 allows you to: • Understand fare differences instantly • Ask about waiver eligibility • Avoid accidental cancellations One forum member shared that calling 1<866<284<3022 helped them rebook within minutes during peak season. 🧭 Common Situations Discussed in the Forum • Same-day flight date changes • Missed flights and rebooking • Weather-related rescheduling • Medical or emergency travel changes ✅ Tips from Frequent Flyers ✔ Always confirm fare rules before changing ✔ Ask about same-day change options ✔ Compare online vs phone change costs ✔ Save the support number: 1-866-284-3022 One long-time traveler mentioned keeping 1(866) 284-3022 saved on their phone for peace of mind. ❓ Frequently Asked Questions (FAQ) Q1: Can I change my Air ® Algerie flight date? Yes, most tickets allow date changes. Fees depend on your fare type. For confirmation, call +1-866-284-3022. Q2: Is it faster to change my date by phone? Many forum users say yes. Calling 1.866.284.3022 provides immediate guidance. Q3: Are same-day date changes allowed? In some cases, yes. Availability matters. Contact (866)-284-3022 to check. Q4: Will I pay a fee to change my flight date? Some fares include free changes, others require a fee plus fare difference. Call 📞 1-866-284-3022 to verify. Q5: What if my travel plans change suddenly? Urgent changes are best handled by phone. Try Call Now: 1-866-284-3022. Q6: Can I change a return date only? Yes, partial itinerary changes are possible. Speak with an agent at [+1(866)284-3022]. 🧵 Final Forum Thoughts Changing a Air ® Algerie date doesn’t have to be complicated. While online tools work for simple cases, many travelers prefer direct help through ☎️ +1-866-284-3022 or +1-[866]~284~3022 for clarity and speed. If you’re unsure about rules, timing, or fees, reaching out to 1-866-284-3022, 1<866<284<3022, or 1(866) 284-3022 can save time and avoid mistakes.

1 month

Re: [PATCH v2 09/12] dt-bindings: media: st: dcmi: add DMA-MDMA chaining properties

by Rob Herring (Arm)

On Tue, 06 Jan 2026 12:34:37 +0100, Alain Volmat wrote: > Add properties update and new sram property necessary in order > to enable the DMA-MDMA chaining. > > Signed-off-by: Alain Volmat <alain.volmat(a)foss.st.com> > > --- > Change in v2: > - correct typo (phandles -> phandle) > - remove explanation about generic binding sram.yaml > --- > Documentation/devicetree/bindings/media/st,stm32-dcmi.yaml | 11 ++++++++++- > 1 file changed, 10 insertions(+), 1 deletion(-) > Reviewed-by: Rob Herring (Arm) <robh(a)kernel.org>

1 month

Re: [PATCH v2 4/5] accel/thames: Add IOCTL for job submission

by Randy Dunlap

On 1/14/26 12:46 AM, Tomeu Vizoso wrote: > Using the DRM GPU scheduler infrastructure, with a scheduler for each > core. > > Contexts are created in all cores, and buffers mapped to all of them as > well, so all cores are ready to execute any job. > > The job submission code was initially based on Panfrost. > > v2: > - Add thames_accel.h UAPI header (Robert Nelson). > > Signed-off-by: Tomeu Vizoso <tomeu(a)tomeuvizoso.net> > --- > drivers/accel/thames/Makefile | 1 + > drivers/accel/thames/thames_core.c | 6 + > drivers/accel/thames/thames_drv.c | 19 ++ > drivers/accel/thames/thames_job.c | 463 ++++++++++++++++++++++++++++++++++++ > drivers/accel/thames/thames_job.h | 51 ++++ > drivers/accel/thames/thames_rpmsg.c | 52 ++++ > include/uapi/drm/thames_accel.h | 54 +++++ > 7 files changed, 646 insertions(+) > > diff --git a/include/uapi/drm/thames_accel.h b/include/uapi/drm/thames_accel.h > index 0a5a5e5f6637ab474e9effbb6db29c1dd95e56b5..5b35e50826ed95bfcc3709bef33416d2b6d11c70 100644 > --- a/include/uapi/drm/thames_accel.h > +++ b/include/uapi/drm/thames_accel.h > @@ -75,6 +78,55 @@ struct drm_thames_bo_mmap_offset { > __u64 offset; > }; > > +/** > + * struct drm_thames_job - A job to be run on the NPU > + * > + * The kernel will schedule the execution of this job taking into account its > + * dependencies with other jobs. All tasks in the same job will be executed > + * sequentially on the same core, to benefit from memory residency in SRAM. > + */ Please make these comments full-fledged kernel-doc comments. E.g.: > +struct drm_thames_job { > + /** Input: BO handle for kernel. */ /** @kernel: input: BO handle for kernel. */ > + __u32 kernel; > + > + /** Input: Size in bytes of the compiled kernel. */ > + __u32 kernel_size; > + > + /** Input: BO handle for params BO. */ > + __u32 params; > + > + /** Input: Size in bytes of the params BO. */ > + __u32 params_size; > + > + /** Input: Pointer to a u32 array of the BOs that are read by the job. */ > + __u64 in_bo_handles; > + > + /** Input: Pointer to a u32 array of the BOs that are written to by the job. */ > + __u64 out_bo_handles; > + > + /** Input: Number of input BO handles passed in (size is that times 4). */ > + __u32 in_bo_handle_count; > + > + /** Input: Number of output BO handles passed in (size is that times 4). */ > + __u32 out_bo_handle_count; > +}; > + > +/** > + * struct drm_thames_submit - ioctl argument for submitting commands to the NPU. > + * > + * The kernel will schedule the execution of these jobs in dependency order. > + */ Same here. > +struct drm_thames_submit { > + /** Input: Pointer to an array of struct drm_thames_job. */ > + __u64 jobs; > + > + /** Input: Number of jobs passed in. */ > + __u32 job_count; > + > + /** Reserved, must be zero. */ > + __u32 pad; > +}; > + -- ~Randy

1 month

Re: [PATCH v2 2/5] accel/thames: Add driver for the C7x DSPs in TI SoCs

by Randy Dunlap

On 1/14/26 12:46 AM, Tomeu Vizoso wrote: > Some SoCs from Texas Instruments contain DSPs that can be used for > general compute tasks. > > This driver provides a drm/accel UABI to userspace for submitting jobs > to the DSP cores and managing the input, output and intermediate memory. > > Signed-off-by: Tomeu Vizoso <tomeu(a)tomeuvizoso.net> > --- > Documentation/accel/thames/index.rst | 28 +++++ > MAINTAINERS | 9 ++ > drivers/accel/Kconfig | 1 + > drivers/accel/Makefile | 3 +- > drivers/accel/thames/Kconfig | 26 +++++ > drivers/accel/thames/Makefile | 9 ++ > drivers/accel/thames/thames_core.c | 155 ++++++++++++++++++++++++++ > drivers/accel/thames/thames_core.h | 53 +++++++++ > drivers/accel/thames/thames_device.c | 93 ++++++++++++++++ > drivers/accel/thames/thames_device.h | 46 ++++++++ > drivers/accel/thames/thames_drv.c | 155 ++++++++++++++++++++++++++ > drivers/accel/thames/thames_drv.h | 21 ++++ > drivers/accel/thames/thames_ipc.h | 204 +++++++++++++++++++++++++++++++++++ > drivers/accel/thames/thames_rpmsg.c | 155 ++++++++++++++++++++++++++ > drivers/accel/thames/thames_rpmsg.h | 27 +++++ > 15 files changed, 984 insertions(+), 1 deletion(-) > > diff --git a/drivers/accel/Makefile b/drivers/accel/Makefile > index 1d3a7251b950f39e2ae600a2fc07a3ef7e41831e..8472989cbe22746f1e7292d2401fa0f7424a6c15 100644 > --- a/drivers/accel/Makefile > +++ b/drivers/accel/Makefile > @@ -5,4 +5,5 @@ obj-$(CONFIG_DRM_ACCEL_ARM_ETHOSU) += ethosu/ > obj-$(CONFIG_DRM_ACCEL_HABANALABS) += habanalabs/ > obj-$(CONFIG_DRM_ACCEL_IVPU) += ivpu/ > obj-$(CONFIG_DRM_ACCEL_QAIC) += qaic/ > -obj-$(CONFIG_DRM_ACCEL_ROCKET) += rocket/ > \ No newline at end of file > +obj-$(CONFIG_DRM_ACCEL_ROCKET) += rocket/ > +obj-$(CONFIG_DRM_ACCEL_THAMES) += thames/ > \ No newline at end of file Please eliminate these warnings. > diff --git a/drivers/accel/thames/thames_ipc.h b/drivers/accel/thames/thames_ipc.h> new file mode 100644 > index 0000000000000000000000000000000000000000..60297b4bc2ffd990315cb735a96a23429d390f43 > --- /dev/null > +++ b/drivers/accel/thames/thames_ipc.h > @@ -0,0 +1,204 @@ > +/* SPDX-License-Identifier: GPL-2.0-only */ > +/* > + * Copyright 2026 Texas Instruments Incorporated - https://www.ti.com/ > + * > + * This header defines the RPMSG message structures exchanged between > + * the Linux kernel (host) and the C7x DSP (remote) firmware for the > + * Thames DRM/accel driver. > + */ > + > +#ifndef _THAMES_IPC_H > +#define _THAMES_IPC_H > + > +#ifdef __KERNEL__ > +#include <linux/types.h> > +#else > +#include <stdint.h> > +typedef uint8_t __u8; > +typedef uint16_t __u16; > +typedef uint32_t __u32; > +typedef uint64_t __u64; > +#endif > + > +#define THAMES_SERVICE_NAME "thames-service" > + > +/** > + * @THAMES_MSG_TYPE: Simplified message type enumeration > + */ "/**" means "this is kernel-doc format", which should look like: /** * enum thames_msg_type - Simplified message type enumeration */ and then each enum value should be documented as well. > +enum thames_msg_type { > + /* --- Host (Kernel) -> Remote (DSP) --- */ > + THAMES_MSG_PING = 0x100, /* Ping message to test communication */ > + THAMES_MSG_CONTEXT_OP, /* Create/destroy context */ > + THAMES_MSG_BO_OP, /* Map/unmap buffer objects */ > + THAMES_MSG_SUBMIT_JOB, /* Submit job for execution */ > + > + /* --- Remote (DSP) -> Host (Kernel) --- */ > + THAMES_MSG_PING_RESPONSE = 0x200, > + THAMES_MSG_CONTEXT_OP_RESPONSE, > + THAMES_MSG_BO_OP_RESPONSE, > + THAMES_MSG_SUBMIT_JOB_RESPONSE, > +}; > + > +/** > + * @THAMES_CONTEXT_OP: Context operation types * enum thames_context_op - Context operations types > + */ > +enum thames_context_op { > + THAMES_CONTEXT_CREATE = 0, > + THAMES_CONTEXT_DESTROY, > +}; > + > +/** > + * @THAMES_BO_OP: Buffer Object operation types * enum thames_bo_op - Buffer Object operation types > + */ > +enum thames_bo_op { > + THAMES_BO_MAP = 0, > + THAMES_BO_UNMAP, > +}; > + > +/** > + * @THAMES_RESP_STATUS: Response status codes * enum thames_resp_status - Response status codes > + */ > +enum thames_resp_status { > + THAMES_RESP_SUCCESS = 0, > + THAMES_RESP_ERR_GENERIC = 1, > + THAMES_RESP_ERR_NOMEM = 2, > + THAMES_RESP_ERR_INVAL = 3, > + THAMES_RESP_ERR_NO_CTX = 4, > + THAMES_RESP_ERR_MMU = 5, > + THAMES_RESP_ERR_JOB_TIMEOUT = 6, > +}; Or you could just use "/*" so that they aren't considered as kernel-doc. -- ~Randy

1 month

← Newer
1
...
5
6
7
8
9
10
11
...
335
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Linaro-mm-sig