From: Roland Dreier <rdreier@cisco.com>
To: Steve Wise <swise@opengridcomputing.com>
Cc: tom@opengridcomputing.com, netdev@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH 2.6.19-rc3 v2 1/2] amso1100 - Use dma_alloc_coherent instead of kmalloc/dma_map_single.
Date: Fri, 27 Oct 2006 16:35:06 -0700 [thread overview]
Message-ID: <adar6wt1get.fsf@cisco.com> (raw)
In-Reply-To: <20061027222835.10329.14982.stgit@dell3.ogc.int> (Steve Wise's message of "Fri, 27 Oct 2006 17:28:35 -0500")
tsk, tsk:
fatal: 7 lines add trailing whitespaces.
applied to for-2.6.19 anyway, thanks.
prev parent reply other threads:[~2006-10-27 23:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-27 22:28 [PATCH 2.6.19-rc3 v2 1/2] amso1100 - Use dma_alloc_coherent instead of kmalloc/dma_map_single Steve Wise
2006-10-27 22:28 ` [PATCH 2.6.19-rc3 v2 2/2] amso1100 - Fix incorrect pr_debug() Steve Wise
2006-10-27 23:33 ` Roland Dreier
2006-10-27 23:35 ` Roland Dreier [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=adar6wt1get.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=swise@opengridcomputing.com \
--cc=tom@opengridcomputing.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).