On Fri, Mar 14, 2025 at 03:43:23PM +0100, Miguel Ojeda wrote:
> On Thu, Mar 13, 2025 at 5:30 AM Joel Fernandes wrote:
> >
> > Reviewed-by: Joel Fernandes
> >
> > If no objections, I can queue it for 6.16 but let me know if Rust
> > maintainers
> > prefer to take it.
>
> Thanks! That would be gr
On Thu, Mar 13, 2025 at 5:30 AM Joel Fernandes wrote:
>
> Reviewed-by: Joel Fernandes
>
> If no objections, I can queue it for 6.16 but let me know if Rust maintainers
> prefer to take it.
Thanks! That would be great -- FWIW:
Acked-by: Miguel Ojeda
By the way, should `read_lock()` be marked t
On 12.03.25 11:17 AM, I Hsin Cheng wrote:
> Currenyly the implementation of "Guard" methods are basically wrappers
> around rcu's function within kernel. Building the kernel with llvm
> 18.1.8 on x86_64 machine will generate the following symbols:
>
> $ nm vmlinux | grep ' _R'.*Guard | rustfilt
>
On Wed, Mar 12, 2025 at 06:17:23PM +0800, I Hsin Cheng wrote:
> Currenyly the implementation of "Guard" methods are basically wrappers
> around rcu's function within kernel. Building the kernel with llvm
> 18.1.8 on x86_64 machine will generate the following symbols:
>
> $ nm vmlinux | grep ' _R'.
I Hsin Cheng writes:
> Currenyly the implementation of "Guard" methods are basically wrappers
"Currenyly" -> "Currently".
> around rcu's function within kernel. Building the kernel with llvm
> 18.1.8 on x86_64 machine will generate the following symbols:
>
> $ nm vmlinux | grep ' _R'.*Guard | r
On Wed Mar 12, 2025 at 11:17 AM CET, I Hsin Cheng wrote:
> Currenyly the implementation of "Guard" methods are basically wrappers
> around rcu's function within kernel. Building the kernel with llvm
> 18.1.8 on x86_64 machine will generate the following symbols:
>
> $ nm vmlinux | grep ' _R'.*Guard
6 matches
Mail list logo