From: kiran.padwal@smartplayin.com
To: Will Deacon <will.deacon@arm.com>
Cc: "joro@8bytes.org" <joro@8bytes.org>,
"hdoyu@nvidia.com" <hdoyu@nvidia.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH] iommu: Make of_device_id array const
Date: Fri, 12 Sep 2014 08:44:50 -0400 (EDT) [thread overview]
Message-ID: <1410525890.331211558@apps.rackspace.com> (raw)
In-Reply-To: <20140911135119.GH6158@arm.com>
On Thursday, September 11, 2014 9:51am, "Will Deacon" <will.deacon@arm.com> said:
> On Thu, Sep 11, 2014 at 02:37:36PM +0100, Kiran Padwal wrote:
>> Make of_device_id array const, because all OF functions handle it as const.
>>
>> Signed-off-by: Kiran Padwal <kiran.padwal@smartplayin.com>
>> ---
>> drivers/iommu/arm-smmu.c | 2 +-
>> drivers/iommu/omap-iommu.c | 2 +-
>> drivers/iommu/tegra-gart.c | 2 +-
>> drivers/iommu/tegra-smmu.c | 2 +-
>> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> Ha, I've seen a few of these patches recently. Did some tool just get
> support for detecting this?
No
>
> Anyway, looks fine and should probably go via Joerg.
>
> Will
>
WARNING: multiple messages have this Message-ID (diff)
From: kiran.padwal@smartplayin.com (kiran.padwal at smartplayin.com)
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] iommu: Make of_device_id array const
Date: Fri, 12 Sep 2014 08:44:50 -0400 (EDT) [thread overview]
Message-ID: <1410525890.331211558@apps.rackspace.com> (raw)
In-Reply-To: <20140911135119.GH6158@arm.com>
On Thursday, September 11, 2014 9:51am, "Will Deacon" <will.deacon@arm.com> said:
> On Thu, Sep 11, 2014 at 02:37:36PM +0100, Kiran Padwal wrote:
>> Make of_device_id array const, because all OF functions handle it as const.
>>
>> Signed-off-by: Kiran Padwal <kiran.padwal@smartplayin.com>
>> ---
>> drivers/iommu/arm-smmu.c | 2 +-
>> drivers/iommu/omap-iommu.c | 2 +-
>> drivers/iommu/tegra-gart.c | 2 +-
>> drivers/iommu/tegra-smmu.c | 2 +-
>> 4 files changed, 4 insertions(+), 4 deletions(-)
>
> Ha, I've seen a few of these patches recently. Did some tool just get
> support for detecting this?
No
>
> Anyway, looks fine and should probably go via Joerg.
>
> Will
>
next prev parent reply other threads:[~2014-09-12 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 13:37 [PATCH] iommu: Make of_device_id array const Kiran Padwal
2014-09-11 13:37 ` Kiran Padwal
[not found] ` <1410442656-21112-1-git-send-email-kiran.padwal-edOiRQu9Xnj5XLMNweQjbQ@public.gmane.org>
2014-09-11 13:51 ` Will Deacon
2014-09-11 13:51 ` Will Deacon
2014-09-11 13:51 ` Will Deacon
2014-09-12 12:44 ` kiran.padwal [this message]
2014-09-12 12:44 ` kiran.padwal at smartplayin.com
2014-09-25 14:01 ` Joerg Roedel
2014-09-25 14:01 ` Joerg Roedel
2014-09-25 14:01 ` 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=1410525890.331211558@apps.rackspace.com \
--to=kiran.padwal@smartplayin.com \
--cc=hdoyu@nvidia.com \
--cc=iommu@lists.linux-foundation.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=swarren@wwwdotorg.org \
--cc=thierry.reding@gmail.com \
--cc=will.deacon@arm.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.