[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CANiq72=j8iDJSTbLJ__r3XAk8tHC8cFFqRjj7YN3zO=8CYQWBg@mail.gmail.com>
Date: Mon, 10 Apr 2023 05:43:32 +0200
From: Miguel Ojeda <miguel.ojeda.sandonis@...il.com>
To: Asahi Lina <lina@...hilina.net>
Cc: Miguel Ojeda <ojeda@...nel.org>,
Alex Gaynor <alex.gaynor@...il.com>,
Wedson Almeida Filho <wedsonaf@...il.com>,
Boqun Feng <boqun.feng@...il.com>, Gary Guo <gary@...yguo.net>,
Björn Roy Baron <bjorn3_gh@...tonmail.com>,
rust-for-linux@...r.kernel.org, linux-kernel@...r.kernel.org,
asahi@...ts.linux.dev, Finn Behrens <me@...enk.dev>,
Sumera Priyadarsini <sylphrenadin@...il.com>,
Vincenzo Palazzo <vincenzopalazzodev@...il.com>
Subject: Re: [PATCH v2] rust: macros: Allow specifying multiple module aliases
On Thu, Mar 23, 2023 at 1:35 PM Asahi Lina <lina@...hilina.net> wrote:
>
> Modules can (and usually do) have multiple alias tags, in order to
> specify multiple possible device matches for autoloading. Allow this by
> changing the alias ModuleInfo field to an Option<Vec<String>>.
>
> Note: For normal device IDs this is autogenerated by modpost (which is
> not properly integrated with Rust support yet), so it is useful to be
> able to manually add device match aliases for now, and should still be
> useful in the future for corner cases that modpost does not handle.
>
> This pulls in the expect_group() helper from the rfl/rust branch
> (with credit to authors).
Applied to `rust-next`. Thanks!
Cheers,
Miguel
Powered by blists - more mailing lists