From: patchwork-bot+netdevbpf@kernel•org
To: Jakub Kicinski <kuba@kernel•org>
Cc: davem@davemloft•net, netdev@vger•kernel.org, edumazet@google•com,
pabeni@redhat•com, chuck.lever@oracle•com
Subject: Re: [PATCH net 0/3] ynl: another license adjustment
Date: Fri, 17 Mar 2023 04:30:21 +0000 [thread overview]
Message-ID: <167902742191.2591.16100149181556138691.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230315230351.478320-1-kuba@kernel.org>
Hello:
This series was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel•org>:
On Wed, 15 Mar 2023 16:03:48 -0700 you wrote:
> Hopefully the last adjustment to the licensing of the specs.
> I'm still the author so should be fine to do this.
>
> Jakub Kicinski (3):
> tools: ynl: make definitions optional again
> ynl: broaden the license even more
> ynl: make the tooling check the license
>
> [...]
Here is the summary with links:
- [net,1/3] tools: ynl: make definitions optional again
https://git.kernel.org/netdev/net/c/054abb515f34
- [net,2/3] ynl: broaden the license even more
https://git.kernel.org/netdev/net/c/4e16b6a748df
- [net,3/3] ynl: make the tooling check the license
https://git.kernel.org/netdev/net/c/cfab77c0b545
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:[~2023-03-17 4:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 23:03 [PATCH net 0/3] ynl: another license adjustment Jakub Kicinski
2023-03-15 23:03 ` [PATCH net 1/3] tools: ynl: make definitions optional again Jakub Kicinski
2023-03-15 23:03 ` [PATCH net 2/3] ynl: broaden the license even more Jakub Kicinski
2023-03-15 23:03 ` [PATCH net 3/3] ynl: make the tooling check the license Jakub Kicinski
2023-03-15 23:53 ` [PATCH net 0/3] ynl: another license adjustment Chuck Lever III
2023-03-17 4:30 ` 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=167902742191.2591.16100149181556138691.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel$(echo .)org \
--cc=chuck.lever@oracle$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=edumazet@google$(echo .)com \
--cc=kuba@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=pabeni@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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