linux-kernel - Re: [PATCH] [v2] bcache: stop using the deprecated get

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: <CAK8P3a0GDUpXQ8WnS6ake2AuAu0Q1gZg+hFQVPgXCBqQ1sS+jw@mail.gmail.com>
Date:   Fri, 13 Jul 2018 20:57:13 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Coly Li <colyli@...e.de>
Cc:     Kent Overstreet <kent.overstreet@...il.com>,
        y2038 Mailman List <y2038@...ts.linaro.org>,
        Jens Axboe <axboe@...nel.dk>, Michael Lyle <mlyle@...e.org>,
        Tang Junhui <tang.junhui@....com.cn>,
        Hannes Reinecke <hare@...e.com>, linux-bcache@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] [v2] bcache: stop using the deprecated get_seconds()

On Fri, Jul 13, 2018 at 5:34 PM, Coly Li <colyli@...e.de> wrote:
> On 2018/7/13 10:20 PM, Arnd Bergmann wrote:
>> On Sat, Jun 23, 2018 at 10:12 AM, Coly Li <colyli@...e.de> wrote:

>>> Added to 4.19 for-next.
>>
>> I noticed this isn't part of linux-next (yet). Did it get dropped?
>>
>>       Arnd
>>
> Hi Arnd,
>
> It is here,
> https://git.kernel.org/pub/scm/linux/kernel/git/colyli/bcache-patches.git/tree/for-next/0004-bcache-stop-using-the-deprecated-get_seconds.patch

Ok, thanks for the confirmation!

> It is for Linux v4.19, the merge window is not available yet, and I
> don't post them to Jens yet.

That sounds like an odd way to handle your patches. Normally all patches
should be part of linux-next *before* the merge window so they get tested
as part of the linux-next kernel before the pull request to Linus is sent.

It's not important for me for this particular patch, but generally speaking,
the Documentation/process/2.Process.rst states:

"all patches merged during a given merge window should really have found
their way into linux-next some time before the merge window opens."

      Arnd