linux-kernel - Re: [PATCH 0/4] fujitsu

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: <CAHp75VehOapj3kBCEVH+ad2XzghU6v6nLGkQDntdj-E2Ue-dTA@mail.gmail.com>
Date:   Fri, 3 Feb 2017 16:13:40 +0200
From:   Andy Shevchenko <andy.shevchenko@...il.com>
To:     Michał Kępień <kernel@...pniu.pl>
Cc:     Darren Hart <dvhart@...radead.org>,
        Jonathan Woithe <jwoithe@...t42.net>,
        Platform Driver <platform-driver-x86@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/4] fujitsu_init() cleanup

On Fri, Feb 3, 2017 at 4:06 PM, Michał Kępień <kernel@...pniu.pl> wrote:
> Darren, Andy,
>
> Please drop this patch series for now.  I will send a rebased v2 after a
> long overdue patch series from Alan Jenkins gets applied in a reworked
> form.

Noted.

Just for you information. Our repo now consists three branches: fixes,
for-next, and testing. testing is kinda for internal use, it might be
broken or be in a wrong state.
Better to use for-next as a base. For this cycle (which is my first as
a co-maintainer) I missed a proper workflow.
That's why I just rebased for-next. It will be not the case in the future.

Darren, consider above as a summary of sync mail for this week.

> However, your input is still essential for determining the future shape
> of fujitsu-laptop.  I quoted the essential parts of my discussion with
> Jonathan below.

I'm about to leave, I'm going to follow this later.
Thanks!

-- 
With Best Regards,
Andy Shevchenko