From: David Miller <davem@davemloft.net>
To: wangyijing@huawei.com
Cc: m@bues.ch, trivial@kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, guohanjun@huawei.com
Subject: Re: [PATCH 6/6] ssb/trivial: replace numeric with standard PM state macros
Date: Fri, 28 Jun 2013 22:12:09 -0700 (PDT) [thread overview]
Message-ID: <20130628.221209.720726659697001242.davem@davemloft.net> (raw)
In-Reply-To: <1372338011-29248-1-git-send-email-wangyijing@huawei.com>
From: Yijing Wang <wangyijing@huawei.com>
Date: Thu, 27 Jun 2013 21:00:11 +0800
> Use standard PM state macros PCI_Dx instead of numeric 0/1/2..
>
> Signed-off-by: Yijing Wang <wangyijing@huawei.com>
Applied.
prev parent reply other threads:[~2013-06-29 5:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-27 13:00 [PATCH 6/6] ssb/trivial: replace numeric with standard PM state macros Yijing Wang
2013-06-29 5:12 ` David Miller [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=20130628.221209.720726659697001242.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m@bues.ch \
--cc=netdev@vger.kernel.org \
--cc=trivial@kernel.org \
--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 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).