Re: [PATCH RESEND v2 00/19] random: Resolve circular include dependency and include

2024-09-09 Thread Jason A. Donenfeld
Hi Uros, On Mon, Sep 09, 2024 at 09:30:06PM +0200, Uros Bizjak wrote: > Besides GCC, clang can define various named address space via > address_space attribute: > > --cut here-- > #define __as(N) __attribute__((address_space(N))) > > void *foo(void __as(1) *x) { return x; } // error > >

Re: [PATCH RESEND v2 00/19] random: Resolve circular include dependency and include

2024-09-09 Thread Uros Bizjak
On Mon, Sep 9, 2024 at 5:57 PM Jason A. Donenfeld wrote: > On Mon, Sep 09, 2024 at 09:53:43AM +0200, Uros Bizjak wrote: > > a) Substitutes the inclusion of with the > > inclusion of where needed (patches 1 - 17). > > > > b) Removes legacy inclusion of from > > (patch 18). > > > > c) Includes

Re: [PATCH RESEND v2 00/19] random: Resolve circular include dependency and include

2024-09-09 Thread Jason A. Donenfeld
Hi Uros, On Mon, Sep 09, 2024 at 09:53:43AM +0200, Uros Bizjak wrote: > a) Substitutes the inclusion of with the > inclusion of where needed (patches 1 - 17). > > b) Removes legacy inclusion of from > (patch 18). > > c) Includes in (patch 19). Thanks for doing this. That seems like a fin

[PATCH RESEND v2 00/19] random: Resolve circular include dependency and include

2024-09-09 Thread Uros Bizjak
Resent due to missing linux-kernel@ mailing list inclusion. There were several attempts to resolve circular include dependency after the addition of percpu.h: 1c9df907da83 ("random: fix circular include dependency on arm64 after addition of percpu.h"), c0842fbc1b18 ("random32: move the pseudo-rand