From: Jakub Kicinski <kuba@kernel.org>
To: Shinas Rasheed <srasheed@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<hgani@marvell.com>, <vimleshk@marvell.com>, <egallen@redhat.com>,
<mschmidt@redhat.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<davem@davemloft.net>, <wizhao@redhat.com>, <kheib@redhat.com>,
<konguyen@redhat.com>, Veerasenareddy Burru <vburru@marvell.com>,
"Sathesh Edara" <sedara@marvell.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next v3] octeon_ep: add PF-VF mailbox communication
Date: Tue, 12 Dec 2023 16:10:30 -0800 [thread overview]
Message-ID: <20231212161030.5eb7b84e@kernel.org> (raw)
In-Reply-To: <20231211063355.2630028-2-srasheed@marvell.com>
On Sun, 10 Dec 2023 22:33:52 -0800 Shinas Rasheed wrote:
> Implement mailbox communication between PF and VFs.
> PF-VF mailbox is used for all control commands from VF to PF and
> asynchronous notification messages from PF to VF.
This patch was not designated as 1/4 in the subject so patchwork
thought it's a separate posting, and the series lacks patch 1/4.
You gotta repost so that patchwork can ingest this properly.
--
pw-bot: cr
next prev parent reply other threads:[~2023-12-13 0:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-11 6:33 [PATCH net-next v3 0/4] add PF-VF mailbox support Shinas Rasheed
2023-12-11 6:33 ` [PATCH net-next v3] octeon_ep: add PF-VF mailbox communication Shinas Rasheed
2023-12-13 0:10 ` Jakub Kicinski [this message]
2023-12-11 6:33 ` [PATCH net-next v3 2/4] octeon_ep: PF-VF mailbox version support Shinas Rasheed
2023-12-11 8:46 ` Leon Romanovsky
2023-12-11 10:31 ` [EXT] " Shinas Rasheed
2023-12-11 11:23 ` Leon Romanovsky
2023-12-11 14:51 ` Shinas Rasheed
2023-12-11 15:16 ` Leon Romanovsky
2023-12-11 15:39 ` Shinas Rasheed
2023-12-11 6:33 ` [PATCH net-next v3 3/4] octeon_ep: control net framework to support VF offloads Shinas Rasheed
2023-12-11 6:33 ` [PATCH net-next v3 4/4] octeon_ep: support firmware notifications for VFs Shinas Rasheed
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=20231212161030.5eb7b84e@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=kheib@redhat.com \
--cc=konguyen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sedara@marvell.com \
--cc=srasheed@marvell.com \
--cc=vburru@marvell.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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).