From: Joerg Roedel <joro@8bytes.org>
To: Will Deacon <will@kernel.org>
Cc: jean-philippe@linaro.org, robin.murphy@arm.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] iommu/arm-smmu: Updates for 5.6
Date: Fri, 17 Jan 2020 11:02:55 +0100 [thread overview]
Message-ID: <20200117100255.GC15760@8bytes.org> (raw)
In-Reply-To: <20200116102548.GA14761@willie-the-truck>
On Thu, Jan 16, 2020 at 10:25:49AM +0000, Will Deacon wrote:
> Hi Joerg,
>
> Please pull these Arm SMMU updates for 5.6. The branch is based on your
> arm/smmu branch and includes a patch addressing the feedback from Greg
> about setting the module 'owner' field in the 'iommu_ops'.
>
> I've used a signed tag this time, so you can see the summary of the
> changes listed in there. The big deal is that we're laying the groundwork
> for PCIe PASID support in SMMUv3, and I expect to hook that up for PCIe
> masters in 5.7 once we've exported the necessary symbols to do so.
>
> Cheers,
>
> Will
>
> --->8
>
> The following changes since commit 1ea27ee2f76e67f98b9942988f1336a70d351317:
>
> iommu/arm-smmu: Update my email address in MODULE_AUTHOR() (2019-12-23 14:06:06 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-updates
Pulled, thanks Will.
_______________________________________________
iommu mailing list
iommu@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/iommu
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Will Deacon <will@kernel.org>
Cc: jean-philippe@linaro.org, robin.murphy@arm.com,
linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
kernel-team@android.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] iommu/arm-smmu: Updates for 5.6
Date: Fri, 17 Jan 2020 11:02:55 +0100 [thread overview]
Message-ID: <20200117100255.GC15760@8bytes.org> (raw)
In-Reply-To: <20200116102548.GA14761@willie-the-truck>
On Thu, Jan 16, 2020 at 10:25:49AM +0000, Will Deacon wrote:
> Hi Joerg,
>
> Please pull these Arm SMMU updates for 5.6. The branch is based on your
> arm/smmu branch and includes a patch addressing the feedback from Greg
> about setting the module 'owner' field in the 'iommu_ops'.
>
> I've used a signed tag this time, so you can see the summary of the
> changes listed in there. The big deal is that we're laying the groundwork
> for PCIe PASID support in SMMUv3, and I expect to hook that up for PCIe
> masters in 5.7 once we've exported the necessary symbols to do so.
>
> Cheers,
>
> Will
>
> --->8
>
> The following changes since commit 1ea27ee2f76e67f98b9942988f1336a70d351317:
>
> iommu/arm-smmu: Update my email address in MODULE_AUTHOR() (2019-12-23 14:06:06 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-updates
Pulled, thanks Will.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Joerg Roedel <joro@8bytes.org>
To: Will Deacon <will@kernel.org>
Cc: iommu@lists.linux-foundation.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robin.murphy@arm.com,
jean-philippe@linaro.org, kernel-team@android.com
Subject: Re: [GIT PULL] iommu/arm-smmu: Updates for 5.6
Date: Fri, 17 Jan 2020 11:02:55 +0100 [thread overview]
Message-ID: <20200117100255.GC15760@8bytes.org> (raw)
In-Reply-To: <20200116102548.GA14761@willie-the-truck>
On Thu, Jan 16, 2020 at 10:25:49AM +0000, Will Deacon wrote:
> Hi Joerg,
>
> Please pull these Arm SMMU updates for 5.6. The branch is based on your
> arm/smmu branch and includes a patch addressing the feedback from Greg
> about setting the module 'owner' field in the 'iommu_ops'.
>
> I've used a signed tag this time, so you can see the summary of the
> changes listed in there. The big deal is that we're laying the groundwork
> for PCIe PASID support in SMMUv3, and I expect to hook that up for PCIe
> masters in 5.7 once we've exported the necessary symbols to do so.
>
> Cheers,
>
> Will
>
> --->8
>
> The following changes since commit 1ea27ee2f76e67f98b9942988f1336a70d351317:
>
> iommu/arm-smmu: Update my email address in MODULE_AUTHOR() (2019-12-23 14:06:06 +0100)
>
> are available in the Git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/will/linux.git tags/arm-smmu-updates
Pulled, thanks Will.
next prev parent reply other threads:[~2020-01-17 10:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-16 10:25 [GIT PULL] iommu/arm-smmu: Updates for 5.6 Will Deacon
2020-01-16 10:25 ` Will Deacon
2020-01-16 10:25 ` Will Deacon
2020-01-17 10:02 ` Joerg Roedel [this message]
2020-01-17 10:02 ` Joerg Roedel
2020-01-17 10:02 ` 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=20200117100255.GC15760@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=will@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 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.