From: Joel Soete <soete.joel@scarlet.be>
To: Takashi Iwai <tiwai@suse.de>
Cc: "James.Bottomley" <James.Bottomley@HansenPartnership.com>,
linux-mips <linux-mips@linux-mips.org>,
ralf <ralf@linux-mips.org>,
linux-parisc <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] mips: Add dma_mmap_coherent()
Date: Sat, 23 Aug 2008 19:39:58 +0000 [thread overview]
Message-ID: <48B0678E.9010208@scarlet.be> (raw)
In-Reply-To: <s5hy72pmefh.wl%tiwai@suse.de>
Hello Takashi,
Takashi Iwai wrote:
> At Fri, 22 Aug 2008 13:04:36 +0100,
> Joel Soete wrote:
>> Hello Takashi et al.,
> ...
>> I build and boot successfully kernel 32bit including your patch on 2 systems
>> (a b2k using sba and a d380 using ccio).
>
> Thanks for testing!
>
welcome ;-)
>> I just noticed that the above code is ~ the same; otoh there is also a
>> iommu-helpers.h containing also common code to those 2 drivers. So may be for
>> easiest maintenance, could you merge and move this code in this 'helper' as
>> follow:
>> --- ./drivers/parisc/iommu-helpers.h.Orig 2008-08-01 12:57:22.000000000 +0000
>> +++ ./drivers/parisc/iommu-helpers.h 2008-08-22 08:07:26.000000000 +0000
>
> That sounds like a good idea.
>
> One concern is to define a non-inline function in *.h. But,
Yes (I thought too but didn't find any other good reason then avoiding useless duplicate code)
> iommu-helper.h is included only by these two drivers, so there is no
> problem as now, although a comment would be more helpful.
>
Yes I hope it will be enough for this stuff to be accepted ;-)
>
>>> diff --git a/include/asm-parisc/dma-mapping.h b/include/asm-parisc/dma-mapping.h
>>> index 53af696..5b357b3 100644
>>> --- a/include/asm-parisc/dma-mapping.h
>>> +++ b/include/asm-parisc/dma-mapping.h
>> The small issue encountered: against latest Kyle git tree (dated 2008-07-29)
>> this file was moved in arch/parisc/include/asm.
>
> Yes. My patches are still based on older version (2.6.27-rc2 or so).
>
> git cares renaming well, so it shouldn't be a big problem.
> I just tested it now and git-pull (oh now it's "git pull" :) renames
> it automatically indeed.
>
Cool (tbh I know very few about git just git clone to grab a tree and git pull to get update from time to time ;-))
>
> thanks,
>
> Takashi
> --
Tx to your attention,
J.
next prev parent reply other threads:[~2008-08-23 19:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 12:04 [PATCH] mips: Add dma_mmap_coherent() Joel Soete
2008-08-22 12:17 ` Takashi Iwai
2008-08-23 19:39 ` Joel Soete [this message]
2008-08-26 15:25 ` Takashi Iwai
2008-08-26 21:01 ` Grant Grundler
2008-08-27 5:42 ` Takashi Iwai
2008-08-27 10:38 ` Ralf Baechle
2008-08-27 14:06 ` James Bottomley
[not found] <s5hk5eezcfe.wl%tiwai@suse.de>
2008-08-20 16:27 ` James Bottomley
2008-08-20 16:53 ` Takashi Iwai
2008-08-20 17:58 ` James Bottomley
2008-08-21 10:19 ` Takashi Iwai
2008-08-21 13:55 ` James Bottomley
2008-08-21 16:01 ` Takashi Iwai
2008-08-21 16:03 ` Takashi Iwai
2008-08-21 21:41 ` Thomas Bogendoerfer
2008-08-22 6:07 ` Takashi Iwai
2008-08-22 9:41 ` Thomas Bogendoerfer
2008-08-22 10:23 ` Takashi Iwai
2008-08-22 14:36 ` Thomas Bogendoerfer
2008-08-22 14:47 ` Takashi Iwai
2008-08-21 10:20 ` Ralf Baechle
2008-08-21 10:25 ` Takashi Iwai
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=48B0678E.9010208@scarlet.be \
--to=soete.joel@scarlet.be \
--cc=James.Bottomley@HansenPartnership.com \
--cc=linux-mips@linux-mips.org \
--cc=linux-parisc@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=tiwai@suse.de \
/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