From: Timur Tabi <timur@freescale.com>
To: Varun Sethi <Varun.Sethi@freescale.com>
Cc: joerg.roedel@amd.com, iommu@lists.linux-foundation.org,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
scottwood@freescale.com
Subject: Re: [PATCH 0/4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation.
Date: Mon, 5 Nov 2012 16:05:40 -0600 [thread overview]
Message-ID: <50983834.30403@freescale.com> (raw)
In-Reply-To: <1352114361-25192-1-git-send-email-Varun.Sethi@freescale.com>
Varun Sethi wrote:
> This patchset provides the Freescale PAMU (Peripheral Access Management Unit) driver
> and the corresponding IOMMU API implementation. PAMU is the IOMMU present on Freescale
> QorIQ platforms. PAMU can authorize memory access, remap the memory address, and remap
> the I/O transaction type.
You forgot to send post these patches to
linuxppc-release@linux.freescale.net. May I suggest the following
git-send-email ... --bcc linuxppc-release@linux.freescale.net ...
whenever you post a patch upstream?
> This set consists of the following patches:
> 1. Addition of new field in the device (powerpc) archdata structure for storing iommu domain information
> pointer. This pointer is stored when the device is attached to a particular iommu domain.
> 2. Add PAMU bypass enable register to the ccsr_guts structure.
I don't see patch 2/4 posted anywhere.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Varun Sethi <Varun.Sethi@freescale.com>
Cc: scottwood@freescale.com, joerg.roedel@amd.com,
iommu@lists.linux-foundation.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation.
Date: Mon, 5 Nov 2012 16:05:40 -0600 [thread overview]
Message-ID: <50983834.30403@freescale.com> (raw)
In-Reply-To: <1352114361-25192-1-git-send-email-Varun.Sethi@freescale.com>
Varun Sethi wrote:
> This patchset provides the Freescale PAMU (Peripheral Access Management Unit) driver
> and the corresponding IOMMU API implementation. PAMU is the IOMMU present on Freescale
> QorIQ platforms. PAMU can authorize memory access, remap the memory address, and remap
> the I/O transaction type.
You forgot to send post these patches to
linuxppc-release@linux.freescale.net. May I suggest the following
git-send-email ... --bcc linuxppc-release@linux.freescale.net ...
whenever you post a patch upstream?
> This set consists of the following patches:
> 1. Addition of new field in the device (powerpc) archdata structure for storing iommu domain information
> pointer. This pointer is stored when the device is attached to a particular iommu domain.
> 2. Add PAMU bypass enable register to the ccsr_guts structure.
I don't see patch 2/4 posted anywhere.
--
Timur Tabi
Linux kernel developer at Freescale
WARNING: multiple messages have this Message-ID (diff)
From: Timur Tabi <timur@freescale.com>
To: Varun Sethi <Varun.Sethi@freescale.com>
Cc: <joerg.roedel@amd.com>, <iommu@lists.linux-foundation.org>,
<linuxppc-dev@lists.ozlabs.org>, <linux-kernel@vger.kernel.org>,
<scottwood@freescale.com>
Subject: Re: [PATCH 0/4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation.
Date: Mon, 5 Nov 2012 16:05:40 -0600 [thread overview]
Message-ID: <50983834.30403@freescale.com> (raw)
In-Reply-To: <1352114361-25192-1-git-send-email-Varun.Sethi@freescale.com>
Varun Sethi wrote:
> This patchset provides the Freescale PAMU (Peripheral Access Management Unit) driver
> and the corresponding IOMMU API implementation. PAMU is the IOMMU present on Freescale
> QorIQ platforms. PAMU can authorize memory access, remap the memory address, and remap
> the I/O transaction type.
You forgot to send post these patches to
linuxppc-release@linux.freescale.net. May I suggest the following
git-send-email ... --bcc linuxppc-release@linux.freescale.net ...
whenever you post a patch upstream?
> This set consists of the following patches:
> 1. Addition of new field in the device (powerpc) archdata structure for storing iommu domain information
> pointer. This pointer is stored when the device is attached to a particular iommu domain.
> 2. Add PAMU bypass enable register to the ccsr_guts structure.
I don't see patch 2/4 posted anywhere.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-11-05 22:05 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-05 11:19 [PATCH 0/4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2012-11-05 11:19 ` Varun Sethi
2012-11-05 11:19 ` [PATCH 1/4 v2] iommu/fsl: Store iommu domain information pointer in archdata Varun Sethi
2012-11-05 11:19 ` Varun Sethi
2012-11-05 11:19 ` [PATCH 3/4 v4] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver Varun Sethi
2012-11-05 11:19 ` Varun Sethi
2012-11-05 11:19 ` [PATCH 4/4 v4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Varun Sethi
2012-11-05 11:19 ` Varun Sethi
[not found] ` <1352114361-25192-4-git-send-email-Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-05 23:04 ` Timur Tabi
2012-11-05 23:04 ` Timur Tabi
2012-11-05 23:04 ` Timur Tabi
2012-11-05 23:11 ` Scott Wood
2012-11-05 23:11 ` Scott Wood
2012-11-05 23:11 ` Scott Wood
[not found] ` <1352114361-25192-3-git-send-email-Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-11-05 22:10 ` [PATCH 3/4 v4] iommu/fsl: Add iommu domain attributes required by fsl PAMU driver Timur Tabi
2012-11-05 22:10 ` Timur Tabi
2012-11-05 22:10 ` Timur Tabi
2012-11-05 22:21 ` Scott Wood
2012-11-05 22:21 ` Scott Wood
2012-11-05 22:21 ` Scott Wood
2012-11-05 23:56 ` Scott Wood
2012-11-05 23:56 ` Scott Wood
2012-11-05 23:56 ` Scott Wood
2012-11-05 22:05 ` Timur Tabi [this message]
2012-11-05 22:05 ` [PATCH 0/4] iommu/fsl: Freescale PAMU driver and IOMMU API implementation Timur Tabi
2012-11-05 22:05 ` Timur Tabi
-- strict thread matches above, loose matches on Subject: below --
2012-11-20 13:54 Varun Sethi
2012-11-20 13:54 ` Varun Sethi
2012-12-14 13:51 Varun Sethi
2012-12-14 13:51 ` Varun Sethi
[not found] ` <1355493114-21776-1-git-send-email-Varun.Sethi-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2012-12-21 1:46 ` Sethi Varun-B16395
2012-12-21 1:46 ` Sethi Varun-B16395
2012-12-21 1:46 ` Sethi Varun-B16395
2012-12-27 6:02 ` Sethi Varun-B16395
2012-12-27 6:02 ` Sethi Varun-B16395
2012-12-27 6:02 ` Sethi Varun-B16395
2013-01-03 5:21 ` Sethi Varun-B16395
2013-01-03 5:21 ` Sethi Varun-B16395
2013-01-03 5:21 ` Sethi Varun-B16395
[not found] ` <C5ECD7A89D1DC44195F34B25E172658D2F58B0-RL0Hj/+nBVDYdknt8GnhQq4g8xLGJsHaLnY5E4hWTkheoWH0uzbU5w@public.gmane.org>
2013-01-06 9:51 ` Joerg Roedel
2013-01-06 9:51 ` Joerg Roedel
2013-01-06 9:51 ` Joerg Roedel
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=50983834.30403@freescale.com \
--to=timur@freescale.com \
--cc=Varun.Sethi@freescale.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@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 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.