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]
Message-ID: <20170320165841.gpbevoscf2fjvods@kozik-lap>
Date:   Mon, 20 Mar 2017 18:58:41 +0200
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Tomasz Figa <tomasz.figa@...il.com>,
        Sylwester Nawrocki <s.nawrocki@...sung.com>,
        Linus Walleij <linus.walleij@...aro.org>,
        linux-arm-kernel@...ts.infradead.org,
        linux-samsung-soc@...r.kernel.org, linux-gpio@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: pinctrl: Add git tree to Samsung pinctrl
 entry

On Mon, Mar 20, 2017 at 06:48:51PM +0200, Krzysztof Kozlowski wrote:
> Add a Git tree on @kernel.org 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 <tomasz.figa@...il.com>
> Cc: Sylwester Nawrocki <s.nawrocki@...sung.com>
> Cc: Linus Walleij <linus.walleij@...aro.org>
> Signed-off-by: Krzysztof Kozlowski <krzk@...nel.org>
> 
> ---
> 
> 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
> kernel.org.
> 
> 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.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ