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  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, 21 Mar 2017 09:54:34 +0900
From:   Tomasz Figa <>
To:     Krzysztof Kozlowski <>
Cc:     Sylwester Nawrocki <>,
        Linus Walleij <>,
        linux-arm-kernel <>,
        "" <>,
        linux-kernel <>
Subject: Re: [PATCH] MAINTAINERS: pinctrl: Add git tree to Samsung pinctrl entry

2017-03-21 1:58 GMT+09:00 Krzysztof Kozlowski <>:
> On Mon, Mar 20, 2017 at 06:48:51PM +0200, Krzysztof Kozlowski wrote:
>> Add a Git tree on for maintaining the Samsung pinctrl
>> drivers.  The tree will be maintained in a shared model between current
>> Samsung pinctrl maintainers.  Pull requests will be going to Linus
>> Walleij.
>> Also add the patchwork for linux-samsung-soc mailing list which will be
>> used for handling the patches.
>> Cc: Tomasz Figa <>
>> Cc: Sylwester Nawrocki <>
>> Cc: Linus Walleij <>
>> Signed-off-by: Krzysztof Kozlowski <>

Acked-by: Tomasz Figa <>

>> ---
>> As of now, only I have the access to this git tree. Tomasz is welcomed
>> to join anytime. We are also waiting for Sywlester to get account on

I'll stay alerted. :) Please let me know whenever you both guys are
busy and I can kick in. Will keep reviewing the patches as well.

>> For the Patchwork, I use it also for Exynos/Samsung ARM architecture
>> maintenance.  I will add appropriate permissions to Sylwester so we can
>> share it.
>> ---
> Linus,
> I talked with Sylwester few days ago and we agreed on a shared mainainer
> model.  Mostly because:
> 1. Only Sylwester from three of us works in Samsung,
> 2. It helps distributing the load in case of any holidays/travel etc,
> 3. It might also make easier for future transitions.
> For this release I can start taking the patches. Please let me know:
> 1. Can I base on Torvalds' rc-1 or you prefer basing on top of your
>    branches? In the second case your branches should not be rebased.
> 2. When do you expect pull requests (preferred time and acceptable late
>    stuff)?
> Also, I will add this tree to the linux-next + auto-builders.

Thanks Krzysztof, you're doing some really good work here! :)

Best regards,

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux - Powered by OpenVZ