From: Jens Axboe <axboe@kernel.dk>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Kees Cook <keescook@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jan Kara <jack@suse.cz>, Johannes Weiner <hannes@cmpxchg.org>,
Nicholas Piggin <npiggin@gmail.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Matthew Wilcox <mawilcox@microsoft.com>,
Jeff Layton <jlayton@redhat.com>,
linux-block@vger.kernel.org, Linux-MM <linux-mm@kvack.org>
Subject: Re: [PATCH] block/laptop_mode: Convert timers to use timer_setup()
Date: Thu, 5 Oct 2017 13:49:38 -0600 [thread overview]
Message-ID: <c04f0253-4ed5-3c3e-d9c5-0263ab277b8c@kernel.dk> (raw)
In-Reply-To: <a74e292d-a0c5-6e75-576b-bb29580028e2@kernel.dk>
On 10/05/2017 01:41 PM, Jens Axboe wrote:
> On 10/05/2017 01:23 PM, Thomas Gleixner wrote:
>> On Thu, 5 Oct 2017, Jens Axboe wrote:
>>> On 10/05/2017 11:49 AM, Kees Cook wrote:
>>>> Yes, totally true. tglx and I ended up meeting face-to-face at the
>>>> Kernel Recipes conference and we solved some outstanding design issues
>>>> with the conversion. The timing meant the new API went into -rc3,
>>>> which seemed better than missing an entire release cycle, or carrying
>>>> deltas against maintainer trees that would drift. (This is actually my
>>>> second massive refactoring of these changes...)
>>>
>>> Honestly, I think the change should have waited for 4.15 in that case.
>>> Why the rush? It wasn't ready for the merge window.
>>
>> Come on. You know very well that a prerequisite for global changes which is
>> not yet used in Linus tree can get merged post merge windew in order to
>> avoid massive inter maintainer tree dependencies. We've done that before.
>
> My point is that doing it this late makes things harder than they should
> have been. If this was in for -rc1, it would have made things a lot
> easier. Or even -rc2. I try and wait to fork off the block tree for as
> long as I can, -rc2 is generally where that happens.
Timing of the change aside, this patch doesn't even apply to the 4.15
block tree:
checking file block/blk-core.c
checking file include/linux/writeback.h
Hunk #1 succeeded at 309 (offset -20 lines).
checking file mm/page-writeback.c
Hunk #1 FAILED at 1977.
Hunk #2 FAILED at 1988.
2 out of 2 hunks FAILED
--
Jens Axboe
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-10-05 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 0:49 Kees Cook
2017-10-05 14:56 ` Jens Axboe
2017-10-05 17:49 ` Kees Cook
2017-10-05 18:26 ` Jens Axboe
2017-10-05 18:49 ` Kees Cook
2017-10-05 18:56 ` Jens Axboe
2017-10-05 19:23 ` Thomas Gleixner
2017-10-05 19:41 ` Jens Axboe
2017-10-05 19:49 ` Jens Axboe [this message]
2017-10-05 21:53 ` Thomas Gleixner
2017-10-05 22:07 ` Jens Axboe
2017-10-05 22:58 ` Kees Cook
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=c04f0253-4ed5-3c3e-d9c5-0263ab277b8c@kernel.dk \
--to=axboe@kernel.dk \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=jack@suse.cz \
--cc=jlayton@redhat.com \
--cc=keescook@chromium.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=mhocko@suse.com \
--cc=npiggin@gmail.com \
--cc=tglx@linutronix.de \
--cc=vdavydov.dev@gmail.com \
/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