linux-kernel - Re: [GIT PULL] pinctrl: samsung: Pinctrl update for v4.13

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:   Tue, 20 Jun 2017 13:14:23 +0200
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Linus Walleij <linus.walleij@...aro.org>
Cc:     Tomasz Figa <tomasz.figa@...il.com>,
        Sylwester Nawrocki <s.nawrocki@...sung.com>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        linux-samsung-soc <linux-samsung-soc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [GIT PULL] pinctrl: samsung: Pinctrl update for v4.13

On Tue, Jun 20, 2017 at 10:08 AM, Linus Walleij
<linus.walleij@...aro.org> wrote:
> On Fri, Jun 9, 2017 at 6:48 PM, Krzysztof Kozlowski <krzk@...nel.org> wrote:
>
>> The following changes since commit 2ea659a9ef488125eb46da6eb571de5eae5c43f6:
>>
>>   Linux 4.12-rc1 (2017-05-13 13:19:49 -0700)
>>
>> are available in the git repository at:
>>
>>   git://git.kernel.org/pub/scm/linux/kernel/git/pinctrl/samsung.git tags/samsung-pinctrl-4.13
>>
>> for you to fetch changes up to a453f3693f2aa9ebba623f8cff1e3d7c5df96ddd:
>>
>>   pinctrl: samsung: Explicitly cast pointer returned by of_iomap() to iomem (2017-06-07 20:40:48 +0200)
>
> Pulled into my "devel" branch on the pin control tree.
>
> Pushing it to the build servers hoping all works.
>
> Thanks for your efforts to maintain Samsung pin control, it is
> much appreciated!

I will have another bunch of cleanups and one important fix (broken
for some time, around v4.10, so it's not a candidate for current RC
fix). It is pretty late. Will you still have time to pull them for
v4.13?

Best regards,
Krzysztof