From: Aksh Garg <a-garg7@ti.com>
To: Niklas Cassel <cassel@kernel.org>
Cc: <linux-pci@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<bhelgaas@google.com>, <corbet@lwn.net>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <s-vadapalli@ti.com>,
<danishanwar@ti.com>, <srk@ti.com>
Subject: Re: [RFC PATCH 1/4] PCI: Add documentation for DOE endpoint support
Date: Wed, 18 Feb 2026 16:51:29 +0530 [thread overview]
Message-ID: <498fb6c1-36b4-4e10-a4ff-de734563cae4@ti.com> (raw)
In-Reply-To: <aY-KkFE9Ya2ZF8ED@fedora>
Hi Niklas,
On 14/02/26 02:03, Niklas Cassel wrote:
> On Fri, Feb 13, 2026 at 06:06:00PM +0530, Aksh Garg wrote:
>> From: Aksh Garg <a-garg7@ti.com>
>>
>> Document the architecture and implementation details for the Data Object
>> Exchange (DOE) framework for PCIe Endpoint devices.
>>
>> Co-developed-by: Siddharth Vadapalli <s-vadapalli@ti.com>
>> Signed-off-by: Siddharth Vadapalli <s-vadapalli@ti.com>
>> Signed-off-by: Aksh Garg <a-garg7@ti.com>
>> ---
>
> Usually documentation is added as the final patch in a series.
>
I had placed this documentation patch before the code implementation in
this RFC to allow reviewers to have a look at the architectural design
first, enabling them to provide meaningful feedback on the overall
approach before examining the specific code details.
> I think this patch should just be squashed with patch 4/4, and the
> squashed patch then being the final patch in the series - patch 3/3.
>
I will keep this mind while posting the normal patch series.
Thanks!
>
> Kind regards,
> Niklas
next prev parent reply other threads:[~2026-02-18 11:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-13 12:35 [RFC PATCH 0/4] PCI: Add DOE support for endpoint Aksh Garg
2026-02-13 12:36 ` [RFC PATCH 1/4] PCI: Add documentation for DOE endpoint support Aksh Garg
2026-02-13 20:33 ` Niklas Cassel
2026-02-18 11:21 ` Aksh Garg [this message]
2026-02-13 12:36 ` [RFC PATCH 2/4] PCI/DOE: Move common definitions to the header file Aksh Garg
2026-02-22 13:01 ` Lukas Wunner
2026-02-23 7:30 ` Aksh Garg
2026-02-13 12:36 ` [RFC PATCH 3/4] PCI/DOE: Add DOE mailbox support for endpoint functions Aksh Garg
2026-02-13 13:21 ` Niklas Cassel
2026-02-18 4:28 ` Alistair Francis
2026-03-04 14:18 ` Manivannan Sadhasivam
2026-03-06 12:14 ` Aksh Garg
2026-02-22 13:06 ` Lukas Wunner
2026-02-23 10:44 ` Aksh Garg
2026-03-04 14:17 ` Manivannan Sadhasivam
2026-03-06 8:17 ` Aksh Garg
2026-02-13 12:36 ` [RFC PATCH 4/4] PCI: Document APIs for endpoint DOE implementation Aksh Garg
2026-02-13 13:16 ` [RFC PATCH 0/4] PCI: Add DOE support for endpoint Niklas Cassel
2026-03-04 14:22 ` Manivannan Sadhasivam
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=498fb6c1-36b4-4e10-a4ff-de734563cae4@ti.com \
--to=a-garg7@ti.com \
--cc=bhelgaas@google.com \
--cc=cassel@kernel.org \
--cc=corbet@lwn.net \
--cc=danishanwar@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=s-vadapalli@ti.com \
--cc=srk@ti.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
all inboxes | Powered by JetHome®