From: patchwork-bot+netdevbpf@kernel.org
To: Ricardo B. Marliere <ricardo@marliere.net>
Cc: isdn@linux-pingi.de, gregkh@linuxfoundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] isdn: constify struct class usage
Date: Fri, 08 Mar 2024 05:00:37 +0000 [thread overview]
Message-ID: <170987403759.8362.17894165442379063106.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240305-class_cleanup-isdn-v1-0-6f0edca75b61@marliere.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 05 Mar 2024 17:04:46 -0300 you wrote:
> This is a simple and straight forward cleanup series that aims to make the
> class structures in isdn constant. This has been possible since 2023 [1].
>
> [1]: https://lore.kernel.org/all/2023040248-customary-release-4aec@gregkh/
>
> Signed-off-by: Ricardo B. Marliere <ricardo@marliere.net>
>
> [...]
Here is the summary with links:
- [1/2] isdn: mISDN: make elements_class constant
https://git.kernel.org/netdev/net-next/c/479b4bc867b9
- [2/2] isdn: capi: make capi_class constant
https://git.kernel.org/netdev/net-next/c/12fbd67ea3f4
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-03-08 5:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 20:04 [PATCH 0/2] isdn: constify struct class usage Ricardo B. Marliere
2024-03-05 20:04 ` [PATCH 1/2] isdn: mISDN: make elements_class constant Ricardo B. Marliere
2024-03-06 19:55 ` Simon Horman
2024-03-05 20:04 ` [PATCH 2/2] isdn: capi: make capi_class constant Ricardo B. Marliere
2024-03-06 19:55 ` Simon Horman
2024-03-08 5:00 ` 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=170987403759.8362.17894165442379063106.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ricardo@marliere.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox