From: Greg KH <gregkh@linuxfoundation.org>
To: Ritesh Harjani <ritesh.harjani@gmail.com>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <Will.Deacon@arm.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Russell King <rmk@arm.linux.org.uk>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] device.h: arm,dma-iommu: Move out dma_iommu_mapping struct
Date: Wed, 4 Jun 2014 11:59:26 -0700 [thread overview]
Message-ID: <20140604185926.GB30884@kroah.com> (raw)
In-Reply-To: <CAD15agbiuXiiAp62R-NeLeX3rgNftmyb+wGiSVx-FgtcXzxpHA@mail.gmail.com>
On Thu, Jun 05, 2014 at 12:16:28AM +0530, Ritesh Harjani wrote:
> Hi Greg,
>
> Thanks for reviewing.
>
> On Wed, Jun 4, 2014 at 11:21 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Wed, Jun 04, 2014 at 01:41:46PM +0530, ritesh.harjani@gmail.com wrote:
> >> From: Ritesh Harjani <ritesh.harjani@gmail.com>
> >>
> >> This patch moves out *mapping pointer of dma_iommu_mapping
> >> from arch/arm/include/asm/device.h to include/liunux/device.h
> >
> > Why? Who else can use this becides arm devices?
>
> Currently only arm and arm64 are the archs at this very moment but
> later other archs can make use of this, as its an arch independent
> code. (Similar to as some arch make use of iommu_area_alloc in
> iommu-helper.c)
>
> >
> >>
> >> Also, it moves out complete structre definition of dma_iommu_mapping
> >> to include/linux/iommu-helper.h
> >>
> >> This is done since arm iommu's dma-mapping arch independent code,
> >> needs to be moved out to lib/iommu-helper.c, this means
> >> dma_iommu_mapping will be arch independent and later other archs
> >> can make use of it.
> >
> > Will that really happen? Do you have patches that do that? I'd prefer
> > to not do stuff like this until you have a patch series that needs it,
> > otherwise this is just unneeded churn.
>
> Yes, foll link has the patch series, (under review)
> http://www.spinics.net/lists/arm-kernel/msg336896.html
Make this patch 1/3 of that series and resend, I don't want to take this
one if the others are not accepted.
thanks,
greg k-h
next prev parent reply other threads:[~2014-06-04 18:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-04 8:11 [PATCH 0/1] device.h: Move out arch independent " ritesh.harjani
2014-06-04 8:11 ` [PATCH 1/1] device.h: arm,dma-iommu: Move out " ritesh.harjani
2014-06-04 17:51 ` Greg KH
2014-06-04 18:46 ` Ritesh Harjani
2014-06-04 18:59 ` Greg KH [this message]
2014-06-05 9:18 ` Ritesh Harjani
2014-06-04 19:01 ` Greg KH
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=20140604185926.GB30884@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Will.Deacon@arm.com \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=ritesh.harjani@gmail.com \
--cc=rmk@arm.linux.org.uk \
/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
Powered by JetHome