From: Christoph Hellwig <hch@infradead.org>
To: Dongdong Liu <liudongdong3@huawei.com>
Cc: helgaas@kernel.org, hch@infradead.org, linux-pci@vger.kernel.org
Subject: Re: [PATCH V2 5/5] PCI: Enable 10-Bit tag support for PCIe RP devices
Date: Tue, 11 May 2021 16:29:48 +0100 [thread overview]
Message-ID: <YJqi7M/2bg0v5HvG@infradead.org> (raw)
In-Reply-To: <1620745965-91535-1-git-send-email-liudongdong3@huawei.com>
> + /*
> + * PCIe spec 5.0r1.0 section 2.2.6.2 implementation note
> + * For configurations where a Requester with 10-Bit Tag Requester capability
> + * targets Completers where some do and some do not have 10-Bit Tag
> + * Completer capability, how the Requester determines which NPRs include
> + * 10-Bit Tags is outside the scope of this specification. So we do not consider
> + * hotplug scenario.
> + */
Please avoid > 80 char lines that make comments completely unreadable.
next prev parent reply other threads:[~2021-05-11 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 15:12 [PATCH V2 5/5] PCI: Enable 10-Bit tag support for PCIe RP devices Dongdong Liu
2021-05-11 15:24 ` Dongdong Liu
2021-05-11 15:31 ` Christoph Hellwig
2021-05-12 7:34 ` Dongdong Liu
2021-05-11 15:29 ` Christoph Hellwig [this message]
2021-05-12 7:35 ` Dongdong Liu
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=YJqi7M/2bg0v5HvG@infradead.org \
--to=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.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