netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Petr Machata <petrm@nvidia.com>
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
	pabeni@redhat.com, netdev@vger.kernel.org, idosch@nvidia.com,
	amcohen@nvidia.com, danieller@nvidia.com, mlxsw@nvidia.com
Subject: Re: [PATCH net-next 0/6] mlxsw: Add support of latency TLV
Date: Sat, 21 Jan 2023 03:00:18 +0000	[thread overview]
Message-ID: <167427001876.13800.17696238078805509162.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1674123673.git.petrm@nvidia.com>

Hello:

This series was applied to netdev/net-next.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Thu, 19 Jan 2023 11:32:26 +0100 you wrote:
> Amit Cohen writes:
> 
> Ethernet Management Datagrams (EMADs) are Ethernet packets sent between
> the driver and device's firmware. They are used to pass various
> configurations to the device, but also to get events (e.g., port up)
> from it. After the Ethernet header, these packets are built in a TLV
> format.
> 
> [...]

Here is the summary with links:
  - [net-next,1/6] mlxsw: reg: Add TLV related fields to MGIR register
    https://git.kernel.org/netdev/net-next/c/42b4f757ba9c
  - [net-next,2/6] mlxsw: Enable string TLV usage according to MGIR output
    https://git.kernel.org/netdev/net-next/c/d84e2359e621
  - [net-next,3/6] mlxsw: core: Do not worry about changing 'enable_string_tlv' while sending EMADs
    https://git.kernel.org/netdev/net-next/c/563bd3c490dc
  - [net-next,4/6] mlxsw: emad: Add support for latency TLV
    https://git.kernel.org/netdev/net-next/c/695f7306d942
  - [net-next,5/6] mlxsw: core: Define latency TLV fields
    https://git.kernel.org/netdev/net-next/c/6ee0d3a9dc00
  - [net-next,6/6] mlxsw: Add support of latency TLV
    https://git.kernel.org/netdev/net-next/c/49f5b769d5bd

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2023-01-21  3:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-19 10:32 [PATCH net-next 0/6] mlxsw: Add support of latency TLV Petr Machata
2023-01-19 10:32 ` [PATCH net-next 1/6] mlxsw: reg: Add TLV related fields to MGIR register Petr Machata
2023-01-19 10:32 ` [PATCH net-next 2/6] mlxsw: Enable string TLV usage according to MGIR output Petr Machata
2023-01-19 10:32 ` [PATCH net-next 3/6] mlxsw: core: Do not worry about changing 'enable_string_tlv' while sending EMADs Petr Machata
2023-01-19 10:32 ` [PATCH net-next 4/6] mlxsw: emad: Add support for latency TLV Petr Machata
2023-01-19 10:32 ` [PATCH net-next 5/6] mlxsw: core: Define latency TLV fields Petr Machata
2023-01-19 10:32 ` [PATCH net-next 6/6] mlxsw: Add support of latency TLV Petr Machata
2023-01-20  1:18 ` [PATCH net-next 0/6] " Tony Nguyen
2023-01-21  3: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=167427001876.13800.17696238078805509162.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=amcohen@nvidia.com \
    --cc=danieller@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuba@kernel.org \
    --cc=mlxsw@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=petrm@nvidia.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;
as well as URLs for NNTP newsgroup(s).