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] [day] [month] [year] [list]

Message-ID: <b73a9580-849a-d946-b203-2eacc31509eb@kernel.dk>
Date:   Fri, 13 Jul 2018 13:38:11 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Arnd Bergmann <arnd@...db.de>, Coly Li <colyli@...e.de>
Cc:     Kent Overstreet <kent.overstreet@...il.com>,
        y2038 Mailman List <y2038@...ts.linaro.org>,
        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 7/13/18 12:57 PM, Arnd Bergmann wrote:
> 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."

Coly does generally send before the merge window, I think the phrasing
is just a little bit off. Depending on risk, I usually tell folks to
submit their stuff for the next window at no later than -rc5 time,
so it'll be in for-next for a least two weeks before the merge window
opens.

-- 
Jens Axboe