From: Bjorn Helgaas <bhelgaas@google.com>
To: Yijing Wang <wangyijing@huawei.com>
Cc: linux-pci@vger.kernel.org, Hanjun Guo <guohanjun@huawei.com>,
Jiang Liu <liuj97@gmail.com>
Subject: Re: [PATCH] PCI: fix trivial typo for PCI_EXP_LNKCAP_CLKPM
Date: Wed, 29 May 2013 14:49:31 -0600 [thread overview]
Message-ID: <20130529204931.GA26388@google.com> (raw)
In-Reply-To: <1369818112-33136-1-git-send-email-wangyijing@huawei.com>
On Wed, May 29, 2013 at 05:01:52PM +0800, Yijing Wang wrote:
> Fix trivial typo for PCI_EXP_LNKCAP_CLKPM comment.
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
> ---
> include/uapi/linux/pci_regs.h | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Applied to pci/misc for v3.11, thanks!
> diff --git a/include/uapi/linux/pci_regs.h b/include/uapi/linux/pci_regs.h
> index 864e324..c3cc01d 100644
> --- a/include/uapi/linux/pci_regs.h
> +++ b/include/uapi/linux/pci_regs.h
> @@ -468,7 +468,7 @@
> #define PCI_EXP_LNKCAP_ASPMS 0x00000c00 /* ASPM Support */
> #define PCI_EXP_LNKCAP_L0SEL 0x00007000 /* L0s Exit Latency */
> #define PCI_EXP_LNKCAP_L1EL 0x00038000 /* L1 Exit Latency */
> -#define PCI_EXP_LNKCAP_CLKPM 0x00040000 /* L1 Clock Power Management */
> +#define PCI_EXP_LNKCAP_CLKPM 0x00040000 /* Clock Power Management */
> #define PCI_EXP_LNKCAP_SDERC 0x00080000 /* Surprise Down Error Reporting Capable */
> #define PCI_EXP_LNKCAP_DLLLARC 0x00100000 /* Data Link Layer Link Active Reporting Capable */
> #define PCI_EXP_LNKCAP_LBNC 0x00200000 /* Link Bandwidth Notification Capability */
> --
> 1.7.1
>
>
prev parent reply other threads:[~2013-05-29 20:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-29 9:01 [PATCH] PCI: fix trivial typo for PCI_EXP_LNKCAP_CLKPM Yijing Wang
2013-05-29 20:49 ` Bjorn Helgaas [this message]
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=20130529204931.GA26388@google.com \
--to=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=wangyijing@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.