From: Joe Damato <jdamato@fastly.com>
To: admiyo@os.amperecomputing.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Jeremy Kerr <jk@codeconstruct.com.au>,
Matt Johnston <matt@codeconstruct.com.au>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Huisong Li <lihuisong@huawei.com>
Subject: Re: [PATCH v16 0/1] MCTP Over PCC Transport
Date: Wed, 22 Jan 2025 13:13:47 -0800 [thread overview]
Message-ID: <Z5Ffi4PSf5LH0vOS@LQ3V64L9R2> (raw)
In-Reply-To: <20250122153549.1234888-1-admiyo@os.amperecomputing.com>
On Wed, Jan 22, 2025 at 10:35:47AM -0500, admiyo@os.amperecomputing.com wrote:
> From: Adam Young <admiyo@os.amperecomputing.com>
>
> This series adds support for the Management Control Transport Protocol (MCTP)
> over the Platform Communication Channel (PCC) mechanism.
FYI net-next is currently closed [1], so this will have to be
re-posted when it re-opens.
This could be reposted as an RFC, though, until net-next reopens if
you want to go that route.
[1]: https://lore.kernel.org/netdev/20250117182059.7ce1196f@kernel.org/
next prev parent reply other threads:[~2025-01-22 21:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-22 15:35 [PATCH v16 0/1] MCTP Over PCC Transport admiyo
2025-01-22 15:35 ` [PATCH v16 1/1] mctp pcc: Implement MCTP over " admiyo
2025-01-22 21:13 ` Joe Damato [this message]
2025-01-23 17:28 ` [PATCH v16 0/1] MCTP Over " Adam Young
2025-01-23 18:03 ` Joe Damato
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=Z5Ffi4PSf5LH0vOS@LQ3V64L9R2 \
--to=jdamato@fastly.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=admiyo@os.amperecomputing.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jk@codeconstruct.com.au \
--cc=kuba@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt@codeconstruct.com.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sudeep.holla@arm.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).