From: "Martin Mareš" <mj@ucw.cz>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Dongdong Liu <liudongdong3@huawei.com>, linux-pci@vger.kernel.org
Subject: Re: [PATCH] lspci: Decode 10-Bit Tag Requester Enable
Date: Fri, 28 Aug 2020 22:56:28 +0200 [thread overview]
Message-ID: <mj+md-20200828.205604.86207.nikam@ucw.cz> (raw)
In-Reply-To: <20200828164931.GA2161257@bjorn-Precision-5520>
Hello!
> And we have a bit of a mess in the names here. There are a bunch of
> "PCI_EXP_DEV2_*" names that would be "PCI_EXP_DEVCTL2_*" if they
> followed the convention. You didn't start that trend, so I'm just
> pointing it out in case you or Martin want to clean it up. When I add
> names I try to use the same name between the Linux kernel source [1]
> and lspci.
Yes, could you please clean it up?
Otherwise it's OK.
Martin
next prev parent reply other threads:[~2020-08-28 21:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 7:21 [PATCH] lspci: Decode 10-Bit Tag Requester Enable Dongdong Liu
2020-08-28 1:01 ` Dongdong Liu
2020-08-28 16:49 ` Bjorn Helgaas
2020-08-28 20:56 ` Martin Mareš [this message]
2020-08-29 2:05 ` Dongdong Liu
2020-08-29 2:03 ` 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=mj+md-20200828.205604.86207.nikam@ucw.cz \
--to=mj@ucw.cz \
--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;
as well as URLs for NNTP newsgroup(s).