From: David Miller <davem@davemloft.net>
To: segooon@gmail.com
Cc: kernel-janitors@vger.kernel.org,
klassert@mathematik.tu-chemnitz.de, eric.dumazet@gmail.com,
ben@decadent.org.uk, adobriyan@gmail.com, joe@perches.com,
netdev@vger.kernel.org
Subject: Re: [PATCH] net: 3c59x: fix leak of iomaps
Date: Fri, 23 Jul 2010 13:06:13 -0700 (PDT) [thread overview]
Message-ID: <20100723.130613.242150222.davem@davemloft.net> (raw)
In-Reply-To: <1279903485-28247-1-git-send-email-segooon@gmail.com>
From: Kulikov Vasiliy <segooon@gmail.com>
Date: Fri, 23 Jul 2010 20:44:44 +0400
> If vortex_probe1() fails we should unmap ioaddr mapped earlier.
>
> Signed-off-by: Kulikov Vasiliy <segooon@gmail.com>
Applied. Thanks for following up on this.
prev parent reply other threads:[~2010-07-23 20:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 16:44 [PATCH] net: 3c59x: fix leak of iomaps Kulikov Vasiliy
2010-07-23 20:06 ` 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=20100723.130613.242150222.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=adobriyan@gmail.com \
--cc=ben@decadent.org.uk \
--cc=eric.dumazet@gmail.com \
--cc=joe@perches.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=klassert@mathematik.tu-chemnitz.de \
--cc=netdev@vger.kernel.org \
--cc=segooon@gmail.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).