From: David Miller <davem@davemloft.net>
To: fujita.tomonori@lab.ntt.co.jp
Cc: netdev@vger.kernel.org, rolandd@cisco.com, eli@mellanox.co.il,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mlx4: replace the dma_sync_single_range_for_cpu/device API
Date: Fri, 19 Feb 2010 12:39:31 -0800 (PST) [thread overview]
Message-ID: <20100219.123931.229106308.davem@davemloft.net> (raw)
In-Reply-To: <20100219164408H.fujita.tomonori@lab.ntt.co.jp>
From: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Date: Fri, 19 Feb 2010 16:44:29 +0900
> On Thu, 11 Feb 2010 14:31:22 -0800
> Roland Dreier <rdreier@cisco.com> wrote:
>
>> > > There are only two users of the dma_sync_single_range_for_cpu/device
>> > > API in mainline (mlx4 and ssb). The
>> > > dma_sync_single_range_for_cpu/device API has never been documented and
>> > > the dma_sync_single_for_cpu/device API also support a partial sync.
>> > >
>> > > This converts mlx4 to use the dma_sync_single_for_cpu/device API
>> > > (preparations for the removal of the dma_sync_single_range_for_cpu/device API).
>> > >
>> > > Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
>> >
>> > Acked-by: David S. Miller <davem@davemloft.net>
>>
>> Dave, please go ahead and merge this -- this affects the mlx4 ethernet
>> driver, so it's your area anyway.
>
> Seems that net-next still doesn't have this. Can you please merge
> this?
I'll take care of this later today.
prev parent reply other threads:[~2010-02-19 20:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 4:57 [PATCH] mlx4: replace the dma_sync_single_range_for_cpu/device API FUJITA Tomonori
2010-02-05 5:09 ` David Miller
2010-02-11 22:31 ` Roland Dreier
2010-02-19 7:44 ` FUJITA Tomonori
2010-02-19 20:39 ` David Miller [this message]
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=20100219.123931.229106308.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eli@mellanox.co.il \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rolandd@cisco.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).