From: "Damien Riégel" <damien.riegel@silabs.com>
To: "Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Damien Riégel" <damien.riegel@silabs.com>
Cc: <greybus-dev@lists.linaro.org>, "Johan Hovold" <johan@kernel.org>,
"Alex Elder" <elder@kernel.org>, <linux-kernel@vger.kernel.org>,
"Silicon Labs Kernel Team" <linux-devel@silabs.com>
Subject: Re: [PATCH v2 01/14] greybus: cpc: add minimal CPC Host Device infrastructure
Date: Tue, 27 Jan 2026 16:11:52 -0500 [thread overview]
Message-ID: <DFZOIW5D4MG8.VPP4RYISK8L3@silabs.com> (raw)
In-Reply-To: <2026011639-prewar-drilling-9bc9@gregkh>
On Fri Jan 16, 2026 at 10:11 AM EST, Greg Kroah-Hartman wrote:
> On Thu, Jan 15, 2026 at 10:57:54AM -0500, Damien Riégel wrote:
>> As the first step for adding CPC support with Greybus, add a very
>> minimal module for CPC Host Devices. For now, this module only proxies
>> calls to the Greybus Host Device API and does nothing useful, but
>> further commits will use this base to add features.
>
> What is "CPC"? I don't see a description of that anywhere here, sorry.
Yeah, it seems I forgot to introduce the term here, and in the cover
letter as well. I'll resend a version that explains what CPC is and that
also addresses Jerome's comments.
thanks,
damien
next prev parent reply other threads:[~2026-01-27 21:12 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 15:57 [PATCH v2 00/14] greybus: introduce CPC as transport layer Damien Riégel
2026-01-15 15:57 ` [PATCH v2 01/14] greybus: cpc: add minimal CPC Host Device infrastructure Damien Riégel
2026-01-16 15:11 ` Greg Kroah-Hartman
2026-01-27 21:11 ` Damien Riégel [this message]
2026-01-15 15:57 ` [PATCH v2 02/14] greybus: cpc: introduce CPC cport structure Damien Riégel
2026-01-15 15:57 ` [PATCH v2 03/14] greybus: cpc: use socket buffers instead of gb_message in TX path Damien Riégel
2026-01-15 15:57 ` [PATCH v2 04/14] greybus: cpc: pack cport ID in Greybus header Damien Riégel
2026-01-15 15:57 ` [PATCH v2 05/14] greybus: cpc: switch RX path to socket buffers Damien Riégel
2026-01-15 15:57 ` [PATCH v2 06/14] greybus: cpc: introduce CPC header structure Damien Riégel
2026-01-15 21:46 ` Jérôme Pouiller
2026-01-15 15:58 ` [PATCH v2 07/14] greybus: cpc: account for CPC header size in RX and TX path Damien Riégel
2026-01-15 15:58 ` [PATCH v2 08/14] greybus: cpc: add and validate sequence numbers Damien Riégel
2026-01-15 21:46 ` Jérôme Pouiller
2026-01-15 15:58 ` [PATCH v2 09/14] greybus: cpc: acknowledge all incoming messages Damien Riégel
2026-01-15 15:58 ` [PATCH v2 10/14] greybus: cpc: use holding queue instead of sending out immediately Damien Riégel
2026-01-15 15:58 ` [PATCH v2 11/14] greybus: cpc: honour remote's RX window Damien Riégel
2026-01-15 15:58 ` [PATCH v2 12/14] greybus: cpc: let host device drivers dequeue TX frames Damien Riégel
2026-01-15 15:58 ` [PATCH v2 13/14] greybus: cpc: add private data pointer in CPC Host Device Damien Riégel
2026-01-15 15:58 ` [PATCH v2 14/14] greybus: cpc: add CPC SDIO host driver Damien Riégel
2026-01-15 21:46 ` Jérôme Pouiller
2026-01-15 22:34 ` Jérôme Pouiller
2026-01-15 21:46 ` [PATCH v2 00/14] greybus: introduce CPC as transport layer Jérôme Pouiller
2026-01-15 22:48 ` Jérôme Pouiller
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=DFZOIW5D4MG8.VPP4RYISK8L3@silabs.com \
--to=damien.riegel@silabs.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=johan@kernel.org \
--cc=linux-devel@silabs.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®