From: "Chris Leech" <christopher.leech@intel.com>
To: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH 2/9] I/OAT
Date: Fri, 31 Mar 2006 11:04:14 -0800 [thread overview]
Message-ID: <41b516cb0603311104h617a0a7bnc0daefc024911f17@mail.gmail.com> (raw)
In-Reply-To: <20060330062124.GA8545@2ka.mipt.ru>
> Could you please describe how struct ioat_dma_chan channels are freed?
Sorry, I got distracted by other issues and never ended up following
up on this. You're right, and it's just sloppiness on my part for
missing it, those structs are being leaked on module unload. I'll fix
it. Thanks.
-Chris
prev parent reply other threads:[~2006-03-31 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-29 22:54 Chris Leech
2006-03-30 6:21 ` Evgeniy Polyakov
2006-03-31 19:04 ` Chris Leech [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=41b516cb0603311104h617a0a7bnc0daefc024911f17@mail.gmail.com \
--to=christopher.leech@intel.com \
--cc=chris.leech@gmail.com \
--cc=johnpol@2ka.mipt.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®