From: patchwork-bot+netdevbpf@kernel.org
To: Khang Nguyen <khangng@os.amperecomputing.com>
Cc: jk@codeconstruct.com.au, matt@codeconstruct.com.au,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
ampere-linux-kernel@lists.amperecomputing.com,
phong@os.amperecomputing.com, thang@os.amperecomputing.com,
khpham@amperecomputing.com, pvo@amperecomputing.com,
quan@os.amperecomputing.com, chanh@os.amperecomputing.com,
thu@os.amperecomputing.com, hieul@amperecomputing.com,
openbmc@lists.ozlabs.org, patches@amperecomputing.com
Subject: Re: [PATCH net-next] net: mctp: Expose transport binding identifier via IFLA attribute
Date: Sat, 09 Nov 2024 17:50:34 +0000 [thread overview]
Message-ID: <173117463401.2982634.225795456177475066.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20241105071915.821871-1-khangng@os.amperecomputing.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 5 Nov 2024 14:19:15 +0700 you wrote:
> MCTP control protocol implementations are transport binding dependent.
> Endpoint discovery is mandatory based on transport binding.
> Message timing requirements are specified in each respective transport
> binding specification.
>
> However, we currently have no means to get this information from MCTP
> links.
>
> [...]
Here is the summary with links:
- [net-next] net: mctp: Expose transport binding identifier via IFLA attribute
https://git.kernel.org/netdev/net-next/c/580db513b4a9
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-11-09 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 7:19 Khang Nguyen
2024-11-07 3:05 ` Matt Johnston
2024-11-08 4:41 ` Jakub Kicinski
2024-11-08 5:47 ` Khang D Nguyen
2024-11-08 8:10 ` Jeremy Kerr
2024-11-09 17:50 ` 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=173117463401.2982634.225795456177475066.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=ampere-linux-kernel@lists.amperecomputing.com \
--cc=andrew+netdev@lunn.ch \
--cc=chanh@os.amperecomputing.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hieul@amperecomputing.com \
--cc=horms@kernel.org \
--cc=jk@codeconstruct.com.au \
--cc=khangng@os.amperecomputing.com \
--cc=khpham@amperecomputing.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=pabeni@redhat.com \
--cc=patches@amperecomputing.com \
--cc=phong@os.amperecomputing.com \
--cc=pvo@amperecomputing.com \
--cc=quan@os.amperecomputing.com \
--cc=thang@os.amperecomputing.com \
--cc=thu@os.amperecomputing.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®