From: Joerg Roedel <joro@8bytes.org>
To: Varun Sethi <Varun.Sethi@freescale.com>
Cc: scottwood@freescale.com, iommu@lists.linux-foundation.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
stuart.yoder@freescale.com
Subject: Re: [PATCH 3/6] powerpc/fsl_pci: Added defines for the FSL PCI controller BRR1 register.
Date: Wed, 27 Feb 2013 12:33:36 +0100 [thread overview]
Message-ID: <20130227113336.GI26252@8bytes.org> (raw)
In-Reply-To: <1361191939-21260-4-git-send-email-Varun.Sethi@freescale.com>
On Mon, Feb 18, 2013 at 06:22:16PM +0530, Varun Sethi wrote:
> Macros for checking FSL PCI controller version.
>
> Signed-off-by: Varun Sethi <Varun.Sethi@freescale.com>
> ---
> arch/powerpc/include/asm/pci-bridge.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/pci-bridge.h b/arch/powerpc/include/asm/pci-bridge.h
> index 025a130..c12ed78 100644
> --- a/arch/powerpc/include/asm/pci-bridge.h
> +++ b/arch/powerpc/include/asm/pci-bridge.h
> @@ -14,6 +14,10 @@
>
> struct device_node;
>
> +/* FSL PCI controller BRR1 register */
> +#define PCI_FSL_BRR1 0xbf8
> +#define PCI_FSL_BRR1_VER 0xffff
> +
Please merge this patch with the one where you actually make use of
these defines for the first time.
Joerg
next prev parent reply other threads:[~2013-02-27 11:33 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 12:52 [PATCH 0/6 v8] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2013-02-18 12:52 ` [PATCH 1/6 v8] iommu/fsl: Store iommu domain information pointer in archdata Varun Sethi
2013-02-27 11:30 ` Joerg Roedel
2013-02-27 12:04 ` Sethi Varun-B16395
2013-02-28 15:51 ` Kumar Gala
2013-03-01 1:24 ` Alexey Kardashevskiy
2013-03-01 8:55 ` Sethi Varun-B16395
2013-03-01 10:07 ` Alexey Kardashevskiy
2013-03-01 16:21 ` Yoder Stuart-B08248
2013-03-04 6:35 ` Sethi Varun-B16395
2013-02-18 12:52 ` [PATCH 2/6] powerpc/fsl_pci: Store the platform device information corresponding to the pci controller Varun Sethi
2013-02-26 0:09 ` Stuart Yoder
2013-02-26 6:16 ` Sethi Varun-B16395
2013-02-27 10:45 ` Joerg Roedel
2013-02-27 10:56 ` Sethi Varun-B16395
2013-02-28 15:45 ` Kumar Gala
2013-03-07 9:14 ` Sethi Varun-B16395
2013-03-07 10:37 ` Joerg Roedel
2013-02-18 12:52 ` [PATCH 3/6] powerpc/fsl_pci: Added defines for the FSL PCI controller BRR1 register Varun Sethi
2013-02-27 11:33 ` Joerg Roedel [this message]
2013-02-28 15:46 ` Kumar Gala
2013-02-18 12:52 ` [PATCH 4/6] iommu/fsl: Add window permission flags for iommu_domain_window_enable API Varun Sethi
2013-02-18 12:52 ` [PATCH 5/6 v8] iommu/fsl: Add addtional attributes specific to the PAMU driver Varun Sethi
2013-02-27 11:38 ` Joerg Roedel
2013-02-18 12:52 ` [PATCH 6/6 v8] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2013-02-19 10:04 ` Diana Craciun
2013-02-19 10:27 ` Sethi Varun-B16395
2013-02-19 15:59 ` Diana Craciun
2013-02-20 9:41 ` Sethi Varun-B16395
2013-02-26 22:33 ` Stuart Yoder
2013-02-27 11:56 ` Sethi Varun-B16395
2013-02-28 0:03 ` Stuart Yoder
2013-03-01 23:27 ` Stuart Yoder
2013-03-04 11:31 ` Sethi Varun-B16395
2013-03-04 16:55 ` Yoder Stuart-B08248
2013-02-25 10:15 ` [PATCH 0/6 " Sethi Varun-B16395
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=20130227113336.GI26252@8bytes.org \
--to=joro@8bytes.org \
--cc=Varun.Sethi@freescale.com \
--cc=iommu@lists.linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=stuart.yoder@freescale.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).