From: Jens Axboe <axboe@kernel.dk>
To: Arnd Bergmann <arnd@arndb.de>, Coly Li <colyli@suse.de>
Cc: Kent Overstreet <kent.overstreet@gmail.com>,
y2038 Mailman List <y2038@lists.linaro.org>,
Michael Lyle <mlyle@lyle.org>,
Tang Junhui <tang.junhui@zte.com.cn>,
Hannes Reinecke <hare@suse.com>,
linux-bcache@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] [v2] bcache: stop using the deprecated get_seconds()
Date: Fri, 13 Jul 2018 13:38:11 -0600 [thread overview]
Message-ID: <b73a9580-849a-d946-b203-2eacc31509eb@kernel.dk> (raw)
In-Reply-To: <CAK8P3a0GDUpXQ8WnS6ake2AuAu0Q1gZg+hFQVPgXCBqQ1sS+jw@mail.gmail.com>
On 7/13/18 12:57 PM, Arnd Bergmann wrote:
> On Fri, Jul 13, 2018 at 5:34 PM, Coly Li <colyli@suse.de> wrote:
>> On 2018/7/13 10:20 PM, Arnd Bergmann wrote:
>>> On Sat, Jun 23, 2018 at 10:12 AM, Coly Li <colyli@suse.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
prev parent reply other threads:[~2018-07-13 19:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-22 13:48 [PATCH] [v2] bcache: stop using the deprecated get_seconds() Arnd Bergmann
2018-06-23 8:12 ` Coly Li
2018-07-13 14:20 ` Arnd Bergmann
2018-07-13 15:34 ` Coly Li
2018-07-13 18:57 ` Arnd Bergmann
2018-07-13 19:38 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b73a9580-849a-d946-b203-2eacc31509eb@kernel.dk \
--to=axboe@kernel.dk \
--cc=arnd@arndb.de \
--cc=colyli@suse.de \
--cc=hare@suse.com \
--cc=kent.overstreet@gmail.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlyle@lyle.org \
--cc=tang.junhui@zte.com.cn \
--cc=y2038@lists.linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox