Re: [PATCH 1/4] rust: macros: Add support for 'imports_ns' to module!
From: Uwe Kleine-König
Date: Sat Nov 01 2025 - 04:07:54 EST
Hello Daniel, hello Miguel,
On Fri, Oct 31, 2025 at 02:12:29PM +0100, Daniel Gomez wrote:
> On 31/10/2025 13.57, Miguel Ojeda wrote:
> > On Fri, Oct 31, 2025 at 8:47 AM Uwe Kleine-König <ukleinek@xxxxxxxxxx> wrote:
> > > Can I have some blessing to take this patch via my pwm tree? Would you
> > > prefer a tag to also merge it into your tree? Then I would apply it on
> > > top of 6.18-rc1 and provide a tag for you to merge.
> >
> > Sounds fine to me, but I am Cc'ing the modules maintainers since they
> > were not, just in case:
Good idea, thanks for catching that.
> > Acked-by: Miguel Ojeda <ojeda@xxxxxxxxxx>
> > [...]
>
> Uwe, that's okay from modules side:
>
> Acked-by: Daniel Gomez <da.gomez@xxxxxxxxxxx>
Thanks for your Acks, I applied patches #1-#3 to
https://git.kernel.org/pub/scm/linux/kernel/git/ukleinek/linux.git pwm/for-next
(#4 was applied already).
> FYI, I haven't merged Andreas's patches (rust: extend `module!` macro with
> integer parameter support) yet, which add rust/macros/module.rs to our
> MAINTAINERS file list. So, it's fine from modules side to go through your tree.
> I was aiming to merge these patches along with some others for this week but
> I've found a regression in kmod testing introduced in the latest v6.18-rc1,
> which is taking me some extra time.
If the issues you mentioned are sorted out and you apply patches that
conflict with the changes I committed, please get in touch that we
coordinate if/how to sort them out.
Also if the need for a tag to share the commit arises, please coordinate
and don't just merge the just now created commits, as I like to be able
to rewrite my tree for late Acks etc. So I'd like to prepare and know
when commits become set in stone.
Best regards
Uwe
Attachment:
signature.asc
Description: PGP signature