From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Allen Kay <allen.m.kay@intel.com>,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: [ACS v2 1/1] clean up base on Matt Wilcox feedback.
Date: Wed, 16 Sep 2009 19:20:35 -0700 [thread overview]
Message-ID: <20090916192035.24302d24@jbarnes-g45> (raw)
In-Reply-To: <20090917021841.GL29320@parisc-linux.org>
On Wed, 16 Sep 2009 20:18:41 -0600
Matthew Wilcox <matthew@wil.cx> wrote:
> On Wed, Sep 16, 2009 at 07:07:41PM -0700, Allen Kay wrote:
> > +/* Access Control Service */
> > +#define PCI_ACS_CAP 0x04 /* ACS Capability
> > Register */ +#define PCI_ACS_CTRL 0x06 /*
> > ACS Control Register */ +#define PCI_ACS_EGRESS_CTL_V
> > 0x08 /* ACS Egress Control Vector */ +#define
> > PCI_ACS_SV 0x01 /* Source Validation */
> > +#define PCI_ACS_TB 0x02 /* Translation
> > Blocking */ +#define PCI_ACS_RR 0x04 /* P2P
> > Request Redirect */ +#define PCI_ACS_CR
> > 0x08 /* P2P Completion Redirect */ +#define
> > PCI_ACS_UF 0x10 /* Upstream Forwarding */
> > +#define PCI_ACS_EC 0x20 /* P2P Egress
> > Control */ +#define PCI_ACS_DT 0x40 /*
> > Direct Translated P2P */
>
> Oops, I wasn't clear. The convention in this file is to use one space
> after the #define for register names and two spaces for bits within
> those registers. Also, the bits generally go after the register to
> which they apply.
>
> So what I meant was more like this:
>
> #define PCI_ACS_CAP 0x04 /* ACS Capability
> Register */ #define PCI_ACS_SV 0x01 /* Source
> Validation */ #define PCI_ACS_TB 0x02 /*
> Translation Blocking */ #define PCI_ACS_RR
> 0x04 /* P2P Request Redirect */ ...
> #define PCI_ACS_CTRL 0x06 /* ACS Control
> Register */ #define PCI_ACS_EGRESS_CTL_V 0x08 /* ACS
> Egress Control Vector */
>
> Since the bits are the same between CAP and CTRL, they don't need to
> be repeated.
>
> With this change,
>
> Reviewed-by: Matthew Wilcox <willy@linux.intel.com>
Allen, easiest for me if you respin with Matthew's suggestion and a
full changelong + Matthew's reviewed-by. Then I can just git am it.
Thanks,
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-09-17 2:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 2:07 [ACS v2 1/1] clean up base on Matt Wilcox feedback Allen Kay
2009-09-17 2:18 ` Matthew Wilcox
2009-09-17 2:20 ` Jesse Barnes [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=20090916192035.24302d24@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=allen.m.kay@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
/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