From: Pavel Fedin <p.fedin@samsung.com>
To: "'Krzysztof Kozlowski'" <k.kozlowski@samsung.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "'Rob Herring'" <robh+dt@kernel.org>,
"'Pawel Moll'" <pawel.moll@arm.com>,
"'Mark Rutland'" <mark.rutland@arm.com>,
"'Ian Campbell'" <ijc+devicetree@hellion.org.uk>,
"'Kumar Gala'" <galak@codeaurora.org>,
"'Kukjin Kim'" <kgene@kernel.org>
Subject: RE: [PATCH v5 0/4] Exynos SROMc configuration and Ethernet support for SMDK5410
Date: Thu, 05 Nov 2015 12:00:43 +0300 [thread overview]
Message-ID: <001c01d117a8$74d70c10$5e852430$@samsung.com> (raw)
In-Reply-To: <563B189D.4080907@samsung.com>
Hello!
> >>>>> This patchset also depends on Exynos 5410 pinctrl support, introduced by
> >>>>> patches 0003 and 0004 from this set:
> >>>>> [PATCH v4 0/5] ARM: EXYNOS: ODROID-XU DT and LEDs
> >>>>> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/330862.html
> >>>>
> >>>> Only the first patch made up to kernel. The rest (2-5) received feedback
> >>>> and I am waiting for fixing it. Andreas apparently loose the interest...
> >>>
> >>> I have rechecked the original thread on archives and found nothing new. Where can
> >>> i read those feedbacks? Perhaps it makes sense for me to pick them up and include
> >>> into my set.
> >>
> >> Go ahead. The only waiting feedback is at patch 2/5:
> >>
> >> http://lists.infradead.org/pipermail/linux-arm-kernel/2015-March/330910.html
> >> Javier's pointed use of linux,stdout-path and putting xxti in
> >> exynos5410.dtsi (and customizing it per board if needed).
> >>
> >> Patches already got reviews and acks so only 2/5 is the stopper.
> >
> > Ah, it's odroidXU device tree. Sorry, i don't have this particular board, and my patch
> actually doesn't need it. I could do some
> > blind modifications, but cannot test them, and this is out of my scope at all.
> > As mentioned in the commit msg, i need only 0003 and 0004 from there. Can they be picked up
> independently? They don't need 0002 by
> > themselves, only 0005 needs it.
>
> Indeed the order of patches is messed up and this makes the confusion. I
> was waiting for resend of entire patchset but you are right - this is
> not required. 3 and 4 can be applied independently.
>
> If they apply, I will pick up them after merge window.
They should. I have quite recent linux-next tree, i've just checked,
0003 applies with a small fuzz and 0004 applies without problems at all.
> If they don't, they will need rebasing by someone. Maybe you can take
> care of them?
Of course. Please notify me if rebasing will be needed, i'll do it.
> You have the SMDK5410 for testing, right?
Of course. And you can already get my
Tested-by: Pavel Fedin <p.fedin@samsung.com>
on those two because my experimental tree already uses them, and
everything works quite well.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
prev parent reply other threads:[~2015-11-05 9:00 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 9:16 Pavel Fedin
2015-11-03 9:16 ` [PATCH v5 1/4] Documentation: dt-bindings: Describe SROMc configuration Pavel Fedin
2015-11-04 8:09 ` Krzysztof Kozlowski
2015-11-03 9:16 ` [PATCH v5 2/4] ARM: dts: Add SROMc to Exynos 5410 Pavel Fedin
2015-11-04 8:12 ` Krzysztof Kozlowski
2015-11-03 9:16 ` [PATCH v5 3/4] drivers: exynos-srom: Add support for bank configuration Pavel Fedin
2015-11-04 8:20 ` Krzysztof Kozlowski
2015-11-05 10:40 ` Pavel Fedin
2015-11-05 11:09 ` Krzysztof Kozlowski
2015-11-03 9:16 ` [PATCH v5 4/4] ARM: dts: Add Ethernet chip to SMDK5410 Pavel Fedin
2015-11-04 8:28 ` Krzysztof Kozlowski
2015-11-05 11:14 ` Pavel Fedin
2015-11-05 11:27 ` Krzysztof Kozlowski
2015-11-05 11:36 ` Pavel Fedin
2015-11-04 7:36 ` [PATCH v5 0/4] Exynos SROMc configuration and Ethernet support for SMDK5410 Krzysztof Kozlowski
2015-11-05 7:59 ` Pavel Fedin
2015-11-05 8:07 ` Krzysztof Kozlowski
2015-11-05 8:44 ` Pavel Fedin
2015-11-05 8:51 ` Krzysztof Kozlowski
2015-11-05 9:00 ` Pavel Fedin [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='001c01d117a8$74d70c10$5e852430$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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
Powered by JetHome