From: Kishon Vijay Abraham I <kishon@ti.com>
To: Jingoo Han <jg1.han@samsung.com>
Cc: "'Bjorn Helgaas'" <bhelgaas@google.com>,
<linux-pci@vger.kernel.org>, <linux-samsung-soc@vger.kernel.org>,
"'Kukjin Kim'" <kgene.kim@samsung.com>,
Pratyush Anand <pratyush.anand@st.com>,
Mohit KUMAR <Mohit.KUMAR@st.com>,
"'Arnd Bergmann'" <arnd@arndb.de>,
"'Sean Cross'" <xobs@kosagi.com>,
"'SRIKANTH TUMKUR SHIVANAND'" <ts.srikanth@samsung.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2] pci: exynos: split into two parts such as Synopsys part and Exynos part
Date: Thu, 11 Jul 2013 14:24:36 +0530 [thread overview]
Message-ID: <51DE72CC.9050001@ti.com> (raw)
In-Reply-To: <001201ce7dfa$716b3370$54419a50$@samsung.com>
Hi,
On Thursday 11 July 2013 11:19 AM, Jingoo Han wrote:
> Exynos PCIe IP consists of Synopsys specific part and Exynos
> specific part. Only core block is a Synopsys designware part;
> other parts are Exynos specific.
> Also, the Synopsys designware part can be shared with other
> platforms; thus, it can be split two parts such as Synopsys
> designware part and Exynos specific part.
>
> Signed-off-by: Jingoo Han <jg1.han@samsung.com>
> Cc: Pratyush Anand <pratyush.anand@st.com>
> Cc: Mohit KUMAR <Mohit.KUMAR@st.com>
> ---
.
.
<snip>
.
.
> +
> +/* Exynos PCIe driver does not allow module unload */
Just curious, why is this restriction?
Thanks
Kishon
next prev parent reply other threads:[~2013-07-11 8:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 5:49 [PATCH V2] pci: exynos: split into two parts such as Synopsys part and Exynos part Jingoo Han
2013-07-11 6:40 ` Kishon Vijay Abraham I
2013-07-11 7:05 ` Jingoo Han
2013-07-11 8:35 ` Kishon Vijay Abraham I
2013-07-11 8:54 ` Kishon Vijay Abraham I [this message]
2013-07-12 0:00 ` Jingoo Han
2013-07-12 5:23 ` Kishon Vijay Abraham I
2013-07-11 15:41 ` Thierry Reding
2013-07-11 23:28 ` Jingoo Han
2013-07-12 17:15 ` Thierry Reding
2013-07-15 8:26 ` Jingoo Han
2013-07-12 10:01 ` Kishon Vijay Abraham I
2013-07-12 17:31 ` Thierry Reding
2013-07-15 8:25 ` Jingoo Han
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=51DE72CC.9050001@ti.com \
--to=kishon@ti.com \
--cc=Mohit.KUMAR@st.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=jg1.han@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=pratyush.anand@st.com \
--cc=ts.srikanth@samsung.com \
--cc=xobs@kosagi.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).