From: Roy Zang <tie-fei.zang@freescale.com>
To: Kevin Hao <haokexin@gmail.com>
Cc: Yuanquan Chen <Yuanquan.Chen@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2] powerpc/fsl-pci:fix incorrect iounmap pci hose->private_data
Date: Wed, 24 Apr 2013 01:33:54 +0800 [thread overview]
Message-ID: <5176C602.9050507@freescale.com> (raw)
In-Reply-To: <20130423091327.GA23644@pek-khao-d1.corp.ad.wrs.com>
On 04/23/2013 05:13 PM, Kevin Hao wrote:
> On Tue, Apr 23, 2013 at 11:18:03PM +0800, Roy Zang wrote:
>> pci hose->private_data will be used by other function, for example,
>> fsl_pcie_check_link(), so do not iounmap it.
> I already sent out a same patch ten days ago. :-)
>
> http://patchwork.ozlabs.org/patch/236293/
>
> Thanks,
> Kevin
>
I do not notice it. That is good :-)
Kumar,
You can pick up the post from Kevin.
Thanks.
Roy
prev parent reply other threads:[~2013-04-23 9:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 15:18 [PATCH v2] powerpc/fsl-pci:fix incorrect iounmap pci hose->private_data Roy Zang
2013-04-23 9:13 ` Kevin Hao
2013-04-23 17:33 ` Roy Zang [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=5176C602.9050507@freescale.com \
--to=tie-fei.zang@freescale.com \
--cc=Yuanquan.Chen@freescale.com \
--cc=haokexin@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).