From: patchwork-bot+netdevbpf@kernel.org
To: Rahul Rameshbabu <sergeantsagara@protonmail.com>
Cc: netdev@vger.kernel.org, rust-for-linux@vger.kernel.org,
edumazet@google.com, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, andrew@lunn.ch, fujita.tomonori@gmail.com,
aliceryhl@google.com
Subject: Re: [PATCH net-next v2] rust: net::phy scope ThisModule usage in the module_phy_driver macro
Date: Tue, 17 Dec 2024 12:40:31 +0000 [thread overview]
Message-ID: <173443923101.882122.15033663641815587249.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241214194242.19505-1-sergeantsagara@protonmail.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Sat, 14 Dec 2024 19:43:06 +0000 you wrote:
> Similar to the use of $crate::Module, ThisModule should be referred to as
> $crate::ThisModule in the macro evaluation. The reason the macro previously
> did not cause any errors is because all the users of the macro would use
> kernel::prelude::*, bringing ThisModule into scope.
>
> Signed-off-by: Rahul Rameshbabu <sergeantsagara@protonmail.com>
> Reviewed-by: FUJITA Tomonori <fujita.tomonori@gmail.com>
> Reviewed-by: Alice Ryhl <aliceryhl@google.com>
>
> [...]
Here is the summary with links:
- [net-next,v2] rust: net::phy scope ThisModule usage in the module_phy_driver macro
https://git.kernel.org/netdev/net-next/c/d22f955cc2cb
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2024-12-17 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-14 19:43 [PATCH net-next v2] rust: net::phy scope ThisModule usage in the module_phy_driver macro Rahul Rameshbabu
2024-12-17 12:40 ` patchwork-bot+netdevbpf [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=173443923101.882122.15033663641815587249.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aliceryhl@google.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fujita.tomonori@gmail.com \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rust-for-linux@vger.kernel.org \
--cc=sergeantsagara@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.