From: David Miller <davem@davemloft.net>
To: bhelgaas@google.com
Cc: linux-pci@vger.kernel.org, netdev@vger.kernel.org, divy@chelsio.com
Subject: Re: [PATCH 06/12] cxgb3: Use standard #defines for PCIe Capability ASPM fields
Date: Fri, 07 Dec 2012 12:51:11 -0500 (EST) [thread overview]
Message-ID: <20121207.125111.884049913645755574.davem@davemloft.net> (raw)
In-Reply-To: <20121205205750.13851.10893.stgit@bhelgaas.mtv.corp.google.com>
From: Bjorn Helgaas <bhelgaas@google.com>
Date: Wed, 05 Dec 2012 13:57:50 -0700
> Use the standard #defines rather than bare numbers for PCIe Capability
> ASPM fields.
>
> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com>
This seems to depend upon another patch which presumably adds the
define of this new macro to a PCI header file. So I can't apply
this to my tree.
Just merge it wherever the dependency is:
Acked-by: David S. Miller <davem@davemloft.net>
prev parent reply other threads:[~2012-12-07 17:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121205205724.13851.50508.stgit@bhelgaas.mtv.corp.google.com>
2012-12-05 20:57 ` [PATCH 06/12] cxgb3: Use standard #defines for PCIe Capability ASPM fields Bjorn Helgaas
2012-12-07 17:51 ` 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=20121207.125111.884049913645755574.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhelgaas@google.com \
--cc=divy@chelsio.com \
--cc=linux-pci@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).