From: jg1.han@samsung.com (Jingoo Han)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V6 3/3] ARM: dts: Add pcie controller node for Samsung EXYNOS5440 SoC
Date: Thu, 20 Jun 2013 17:40:13 +0900 [thread overview]
Message-ID: <00c901ce6d91$c8382010$58a86030$@samsung.com> (raw)
In-Reply-To: <20130620100013.6000458f@skate>
On Thursday, June 20, 2013 5:00 PM, Thomas Petazzoni wrote:
>
> Dear Jingoo Han,
>
> On Thu, 20 Jun 2013 16:57:32 +0900, Jingoo Han wrote:
>
> > > > - pinctrl {
> > > > + pin_ctrl: pinctrl {
> > > > compatible = "samsung,exynos5440-pinctrl";
> > >
> > > I know I'm nitpicking, but isn't this change completely unrelated to
> > > PCIe support?
> >
> > This change is related to PCIe support.
> > Without this, I cannot use gpio binding.
> >
> > This change was guided by Thomas Abraham (Author of Samsung pinctrl).
> > Also, it was confirmed by Kukjin Kim (Maintainer of Samsung SoC).
> >
> > Thank you for your caring. :)
>
> I mean, the change is fine for sure, but it should maybe part of a
> separate patch as it is more a fix than really the introduction of the
> PCIe controller node, as the patch title suggests. This would also for
> example allow this fix to be merged right now (for 3.11), regardless of
> what happens for the rest of your PCIe patches.
>
CC'ed Tomasz Figa
OK, I see.
I will separate this patch to two patches, as Tomasz Figa mentioned.
(http://www.spinics.net/lists/linux-samsung-soc/msg19639.html)
Thank you.
Best regards,
Jingoo Han
next prev parent reply other threads:[~2013-06-20 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 7:12 [PATCH V6 3/3] ARM: dts: Add pcie controller node for Samsung EXYNOS5440 SoC Jingoo Han
2013-06-20 7:48 ` Thomas Petazzoni
2013-06-20 7:57 ` Jingoo Han
2013-06-20 8:00 ` Thomas Petazzoni
2013-06-20 8:40 ` Jingoo Han [this message]
2013-06-20 8:04 ` Tomasz Figa
2013-06-20 8:25 ` Jingoo Han
2013-06-20 9:36 ` Tomasz Figa
2013-06-20 10:16 ` Arnd Bergmann
2013-06-20 11:04 ` Jingoo Han
2013-06-20 11:42 ` Tomasz Figa
2013-06-20 9:03 ` Arnd Bergmann
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='00c901ce6d91$c8382010$58a86030$@samsung.com' \
--to=jg1.han@samsung.com \
--cc=linux-arm-kernel@lists.infradead.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).