From: Timur Tabi <timur@freescale.com>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: dan.j.williams@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmatest: properly handle duplicate DMA channels
Date: Thu, 18 Sep 2008 10:34:40 -0500 [thread overview]
Message-ID: <48D27510.3060803@freescale.com> (raw)
In-Reply-To: <20080918173258.2640000b@hskinnemo-gx745.norway.atmel.com>
Haavard Skinnemoen wrote:
> ...though I don't really see why you have to use
> list_for_entry_safe()...
You use it in dmatest_remove_channel(), so I figured I'd do the same thing.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-09-18 15:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 15:21 [PATCH] dmatest: properly handle duplicate DMA channels Timur Tabi
2008-09-18 15:32 ` Haavard Skinnemoen
2008-09-18 15:34 ` Timur Tabi [this message]
2008-09-18 15:48 ` Haavard Skinnemoen
2008-09-19 23:31 ` Andrew Morton
2008-09-20 12:42 ` Haavard Skinnemoen
2008-09-20 21:40 ` Dan Williams
2008-09-20 22:20 ` Andrew Morton
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=48D27510.3060803@freescale.com \
--to=timur@freescale.com \
--cc=dan.j.williams@intel.com \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
/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.