netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jeremy Kerr <jk@codeconstruct.com.au>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
	matt@codeconstruct.com.au, andrew@aj.id.au
Subject: Re: [PATCH net-next v2 0/3] MCTP flow support
Date: Fri, 29 Oct 2021 12:40:08 +0000	[thread overview]
Message-ID: <163551120837.27055.959178317809229965.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211029030145.633626-1-jk@codeconstruct.com.au>

Hello:

This series was applied to netdev/net-next.git (master)
by David S. Miller <davem@davemloft.net>:

On Fri, 29 Oct 2021 11:01:42 +0800 you wrote:
> For certain MCTP transport bindings, the binding driver will need to be
> aware of request/response pairing. For example, the i2c binding may need
> to set multiplexer configuration when expecting a response from a device
> behind a mux.
> 
> This series implements a mechanism for informing the driver about these
> flows, so it can implement transport-specific behaviour when a flow is
> in progress (ie, a response is expected, and/or we time-out on that
> expectation). We use a skb extension to notify the driver about the
> presence of a flow, and a new dev->ops callback to notify about a flow's
> destruction.
> 
> [...]

Here is the summary with links:
  - [net-next,v2,1/3] mctp: Return new key from mctp_alloc_local_tag
    https://git.kernel.org/netdev/net-next/c/212c10c3c658
  - [net-next,v2,2/3] mctp: Add flow extension to skb
    https://git.kernel.org/netdev/net-next/c/78476d315e19
  - [net-next,v2,3/3] mctp: Pass flow data & flow release events to drivers
    https://git.kernel.org/netdev/net-next/c/67737c457281

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



      parent reply	other threads:[~2021-10-29 12:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-29  3:01 [PATCH net-next v2 0/3] MCTP flow support Jeremy Kerr
2021-10-29  3:01 ` [PATCH net-next v2 1/3] mctp: Return new key from mctp_alloc_local_tag Jeremy Kerr
2021-10-29  3:01 ` [PATCH net-next v2 2/3] mctp: Add flow extension to skb Jeremy Kerr
2021-10-29  3:01 ` [PATCH net-next v2 3/3] mctp: Pass flow data & flow release events to drivers Jeremy Kerr
2021-10-29 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=163551120837.27055.959178317809229965.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrew@aj.id.au \
    --cc=davem@davemloft.net \
    --cc=jk@codeconstruct.com.au \
    --cc=kuba@kernel.org \
    --cc=matt@codeconstruct.com.au \
    --cc=netdev@vger.kernel.org \
    /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).