From: Thomas Gleixner <tglx@linutronix.de>
To: Jens Axboe <axboe@kernel.dk>
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 21:23:10 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.20.1710052102480.2398@nanos> (raw)
In-Reply-To: <57ad0ef1-e147-8507-9922-aa72ad47350e@kernel.dk>
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.
There are only a few options we have for such global changes:
- Delay everything for a full release and keep hunting the ever changing
code and the new users of old interfaces, which is a pain in the
butt. I know what I'm talking about.
- Apply everything in a central tree, which is prone to merge conflicts
in next when maintainer trees contain changes in the same area. So
getting it through the maintainers is the best option for this kind of
stuff.
- Create a separate branch for other maintainers to pull, which I did
often enough in the past to avoid merge dependencies. I decided not
to offer that branch this time, because it would be been necessary to
pull it into a gazillion of trees. So we decided that Linus tree as a
dependency is good enough.
Just for the record:
Last time I did this for block you did not complain, that you got
something based on -rc3 from me because you wanted to have these
changes in your tree so you could apply the depending multi-queue
patches. tip irq/for-block exists for a reason.
So what's the difference to pull -rc3 this time? Nothing, just the
fact that you are not interested in the change.
So please stop this hypocritical ranting right here.
Thanks,
tglx
--
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:23 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 [this message]
2017-10-05 19:41 ` Jens Axboe
2017-10-05 19:49 ` Jens Axboe
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=alpine.DEB.2.20.1710052102480.2398@nanos \
--to=tglx@linutronix.de \
--cc=akpm@linux-foundation.org \
--cc=axboe@kernel.dk \
--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=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