From: 'Joerg Roedel' <joro@8bytes.org>
To: Cho KyongHo <pullip.cho@samsung.com>
Cc: 'Antonios Motakis' <a.motakis@virtualopensystems.com>,
linux-arm-kernel@lists.infradead.org,
iommu@lists.linux-foundation.org,
linux-samsung-soc@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
'Sachin Kamat' <sachin.kamat@linaro.org>,
'Varun Sethi' <Varun.Sethi@freescale.com>,
'open list' <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/2] iommu/exynos: Follow kernel coding style for __sysmmu_enable return type
Date: Wed, 14 Aug 2013 15:15:49 +0200 [thread overview]
Message-ID: <20130814131547.GA5889@8bytes.org> (raw)
In-Reply-To: <003101ce89ed$52317330$f6945990$@samsung.com>
KyongHo,
On Fri, Jul 26, 2013 at 07:46:01PM +0900, Cho KyongHo wrote:
> __sysmmu_enable() must return 1 if it is called with the same page table.
> I have fixed it exynos_iommu_attach_device() to always return zero on success
> in the next patchset which I will post today.
>
> Thank you.
When you are fine with these patches please put them on-top of your
patch-set when you re-submit. I will take them from there then.
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: joro@8bytes.org ('Joerg Roedel')
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] iommu/exynos: Follow kernel coding style for __sysmmu_enable return type
Date: Wed, 14 Aug 2013 15:15:49 +0200 [thread overview]
Message-ID: <20130814131547.GA5889@8bytes.org> (raw)
In-Reply-To: <003101ce89ed$52317330$f6945990$@samsung.com>
KyongHo,
On Fri, Jul 26, 2013 at 07:46:01PM +0900, Cho KyongHo wrote:
> __sysmmu_enable() must return 1 if it is called with the same page table.
> I have fixed it exynos_iommu_attach_device() to always return zero on success
> in the next patchset which I will post today.
>
> Thank you.
When you are fine with these patches please put them on-top of your
patch-set when you re-submit. I will take them from there then.
Joerg
next prev parent reply other threads:[~2013-08-14 13:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-25 15:34 [PATCHv2 1/2] iommu/exynos: add devices attached to the System MMU to an IOMMU group Antonios Motakis
2013-07-25 15:34 ` Antonios Motakis
2013-07-25 15:34 ` Antonios Motakis
[not found] ` <1374766502-14823-1-git-send-email-a.motakis-lrHrjnjw1UfHK3s98zE1ajGjJy/sRE9J@public.gmane.org>
2013-07-25 15:35 ` [PATCH 2/2] iommu/exynos: Follow kernel coding style for __sysmmu_enable return type Antonios Motakis
2013-07-25 15:35 ` Antonios Motakis
2013-07-25 15:35 ` Antonios Motakis
2013-07-26 10:46 ` Cho KyongHo
2013-07-26 10:46 ` Cho KyongHo
2013-08-14 13:15 ` 'Joerg Roedel' [this message]
2013-08-14 13:15 ` 'Joerg Roedel'
2013-08-16 11:21 ` Cho KyongHo
2013-08-16 11:21 ` Cho KyongHo
[not found] ` <20130816202151.b47fae1e9ed249d06baa37d1-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2013-08-18 13:33 ` Antonios Motakis
2013-08-18 13:33 ` Antonios Motakis
2013-08-18 13:33 ` Antonios Motakis
2013-07-26 4:48 ` [PATCHv2 1/2] iommu/exynos: add devices attached to the System MMU to an IOMMU group Sachin Kamat
2013-07-26 4:48 ` Sachin Kamat
2013-07-26 4:48 ` Sachin Kamat
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=20130814131547.GA5889@8bytes.org \
--to=joro@8bytes.org \
--cc=Varun.Sethi@freescale.com \
--cc=a.motakis@virtualopensystems.com \
--cc=iommu@lists.linux-foundation.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pullip.cho@samsung.com \
--cc=sachin.kamat@linaro.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.