linux-kernel - RE: [PATCH v5 0/4] Exynos SROMc configuration and Ethernet support for SMDK5410

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 05 Nov 2015 12:00:43 +0300
From:	Pavel Fedin <p.fedin@...sung.com>
To:	'Krzysztof Kozlowski' <k.kozlowski@...sung.com>,
	devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
	linux-samsung-soc@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	'Rob Herring' <robh+dt@...nel.org>,
	'Pawel Moll' <pawel.moll@....com>,
	'Mark Rutland' <mark.rutland@....com>,
	'Ian Campbell' <ijc+devicetree@...lion.org.uk>,
	'Kumar Gala' <galak@...eaurora.org>,
	'Kukjin Kim' <kgene@...nel.org>
Subject: RE: [PATCH v5 0/4] Exynos SROMc configuration and Ethernet support for
 SMDK5410

 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@...sung.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


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/