From: David Miller <davem@davemloft.net>
To: mchan@broadcom.com
Cc: nhorman@tuxdriver.com, netdev@vger.kernel.org, mcan@broadcom.com
Subject: Re: [PATCH] bnx2: Clean up remaining iounmap
Date: Thu, 27 Sep 2012 19:19:18 -0400 (EDT) [thread overview]
Message-ID: <20120927.191918.866136563370603675.davem@davemloft.net> (raw)
In-Reply-To: <1348684433.7220.78.camel@LTIRV-MCHAN1.corp.ad.broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Wed, 26 Sep 2012 11:33:53 -0700
> On Wed, 2012-09-26 at 13:22 -0400, Neil Horman wrote:
>> commit c0357e975afdbbedab5c662d19bef865f02adc17 modified bnx2 to switch from
>> using ioremap/iounmap to pci_iomap/pci_iounmap. They missed a spot in the error
>> path of bnx2_init_one though. This patch just cleans that up.
>>
>> Signed-off-by: Neil Horman <nhorman@tuxdriver.com>
>> CC: Michael Chan <mcan@broadcom.com>
>> CC: "David S. Miller" <davem@davemloft.net>
>
> Acked-by: Michael Chan <mchan@broadcom.com>
Applied, thanks.
prev parent reply other threads:[~2012-09-27 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-26 17:22 [PATCH] bnx2: Clean up remaining iounmap Neil Horman
2012-09-26 18:33 ` Michael Chan
2012-09-27 23:19 ` 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=20120927.191918.866136563370603675.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mcan@broadcom.com \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.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).