2017-03-21 1:58 GMT+09:00 Krzysztof Kozlowski <krzk@xxxxxxxxxx>: > 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@xxxxxxxxx> >> Cc: Sylwester Nawrocki <s.nawrocki@xxxxxxxxxxx> >> Cc: Linus Walleij <linus.walleij@xxxxxxxxxx> >> Signed-off-by: Krzysztof Kozlowski <krzk@xxxxxxxxxx> Acked-by: Tomasz Figa <tomasz.figa@xxxxxxxxx> >> >> --- >> >> 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. 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, Tomasz -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html