linux-kernel - Re: [PATCH 0/5] pinctrl: samsung: Data structure clean-up

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] [day] [month] [year] [list]

Date:	Thu, 2 Oct 2014 09:18:21 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Tomasz Figa <tomasz.figa@...il.com>
Cc:	linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Kukjin Kim <kgene.kim@...sung.com>,
	Marek Szyprowski <m.szyprowski@...sung.com>,
	Bartlomiej Zolnierkiewicz <b.zolnierkie@...sung.com>
Subject: Re: [PATCH 0/5] pinctrl: samsung: Data structure clean-up

On Sat, Sep 27, 2014 at 2:50 PM, Tomasz Figa <tomasz.figa@...il.com> wrote:
> On 25.09.2014 09:49, Tomasz Figa wrote:
>> On 25.09.2014 09:47, Linus Walleij wrote:
>>> On Tue, Sep 23, 2014 at 9:05 PM, Tomasz Figa <tomasz.figa@...il.com> wrote:
>>>
>>>> This series intends to clean up data structures used by pinctrl-samsung driver.
>>>> More specifically, it separates initial compile time constants from data used
>>>> at runtime, allowing unused variant data to be dropped and selected structures
>>>> constified to improve safety.
>>>
>>> I like the patch set, tried to apply it but patch 3/5 failed to apply to the
>>> devel branch for pinctrl.
>>>
>>> Can you rebase this on my "devel" branch, include Marek's Tested-by
>>> tag and resend, and I'll take it for v3.18.
>>
>> Sure. Will do that today evening. Probably clashed with some other
>> changes queued in the meantime.
>
> Uhm. I went back home and forgot about this series until now. Sorry.
>
> I have rebased it on your "devel" branch, although it seems like this
> branch is missing [1], which in turn seems to be already present in your
> "for-next" branch and is going to cause a merge conflict with this
> series. Should I still proceed with posting the series based on "devel"?
>
> [1] f6a8249f9e55d pinctrl: exynos: Lock GPIOs as interrupts when used as
> EINTs

Bah I must have accidentally applied the patch to my for-next
branch instead of devel, and then wiped it out of existence when
I later reset the for-next branch to devel.

Please resend all 5 rebased on devel.

Yours,
Linus Walleij
--
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/