Danilo Krummrich
2025-Jun-18 17:44 UTC
[PATCH v12 1/6] rust: enable `clippy::ptr_as_ptr` lint
On 6/18/25 6:45 PM, Miguel Ojeda wrote:> On Wed, Jun 18, 2025 at 3:54?PM Tamir Duberstein <tamird at gmail.com> wrote: >> >> @Andreas Hindborg could you please have a look for configfs? >> >> @Rafael J. Wysocki @Viresh Kumar could you please have a look for cpufreq? > > Thanks Tamir. > > Christian, Danilo, David, Greg, Tejun: It would also be nice to get > Acked-by's for your bits. Thanks!For the whole series and the bits I maintain: Acked-by: Danilo Krummrich <dakr at kernel.org> -- Independent from that, won't this potentially leave us with a lot of warnings from code that goes through other trees in the upcoming merge window? How do we deal with that?
Tamir Duberstein
2025-Jun-18 17:57 UTC
[PATCH v12 1/6] rust: enable `clippy::ptr_as_ptr` lint
On Wed, Jun 18, 2025 at 1:44?PM Danilo Krummrich <dakr at kernel.org> wrote:> > On 6/18/25 6:45 PM, Miguel Ojeda wrote: > > On Wed, Jun 18, 2025 at 3:54?PM Tamir Duberstein <tamird at gmail.com> wrote: > >> > >> @Andreas Hindborg could you please have a look for configfs? > >> > >> @Rafael J. Wysocki @Viresh Kumar could you please have a look for cpufreq? > > > > Thanks Tamir. > > > > Christian, Danilo, David, Greg, Tejun: It would also be nice to get > > Acked-by's for your bits. Thanks! > > For the whole series and the bits I maintain: > > Acked-by: Danilo Krummrich <dakr at kernel.org> > > -- > > Independent from that, won't this potentially leave us with a lot of warnings > from code that goes through other trees in the upcoming merge window? How do we > deal with that?I think the idea was to take this during rc so that all trees have it by the start of the next merge window. I'm not 100% clear on the kernel mechanics here, but that's my understanding.