From: "David S. Miller" <davem@davemloft.net>
To: akpm@osdl.org
Cc: jgarzik@pobox.com, netdev@oss.sgi.com, akpm@osdl.org,
geert@linux-m68k.org
Subject: Re: [patch 07/13] M68k HP Lance Ethernet: Fix leaks on probe/removal
Date: Wed, 24 Nov 2004 00:25:23 -0800 [thread overview]
Message-ID: <20041124002523.219cef78.davem@davemloft.net> (raw)
In-Reply-To: <200411220644.iAM6i6900649@mail.osdl.org>
On Sun, 21 Nov 2004 22:43:54 -0800
akpm@osdl.org wrote:
> From: Geert Uytterhoeven <geert@linux-m68k.org>
>
> HP Lance Ethernet: There's tons of leaks in the hplcance probing code, and it
> doesn't release the memory region on removal either (from Christoph Hellwig)
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>
This one looks like Jeff should review/merge it too.
prev parent reply other threads:[~2004-11-24 8:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 6:43 [patch 07/13] M68k HP Lance Ethernet: Fix leaks on probe/removal akpm
2004-11-24 8:25 ` David S. 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=20041124002523.219cef78.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=geert@linux-m68k.org \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.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).