[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <baf577bd-61d8-4ab4-b815-70b2e989baf6@gmail.com>
Date: Wed, 11 Jun 2025 15:36:54 -0500
From: Andrew Ballance <andrewjballance@...il.com>
To: jbaron@...mai.com, jim.cromie@...il.com, daniel.almeida@...labora.com,
acourbot@...dia.com, ojeda@...nel.org, alex.gaynor@...il.com,
boqun.feng@...il.com, gary@...yguo.net, bjorn3_gh@...tonmail.com,
lossin@...nel.org, a.hindborg@...nel.org, aliceryhl@...gle.com,
tmgross@...ch.edu, dakr@...nel.org, gregkh@...uxfoundation.org,
rafael@...nel.org, rostedt@...dmis.org
Cc: viresh.kumar@...aro.org, lina+kernel@...hilina.net, tamird@...il.com,
jubalh@...oru.org, rust-for-linux@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/3] rust: add suppord for dynamic debug
On 6/11/25 3:29 PM, Andrew Ballance wrote:
> This uses the module_path! macro to get the module name, which will not
> be exactly the same as the c version if a kernel module contains multiple
> rust modules. e.g. it might be "kernel_module_name::rust_module_name".
> this does give a more accurate description of where the print statement
> is located but it exactly what the c version does.
oops. typo.
is *not* exactly what the c version does.
Best Regards
Andrew Ballance
Powered by blists - more mailing lists