From: Peter Zijlstra <peterz@infradead.org>
To: Michal Hocko <mhocko@kernel.org>
Cc: Nikolay Borisov <nborisov@suse.com>,
linux-kernel@vger.kernel.org, vbabka.lkml@gmail.com,
linux-mm@kvack.org, mingo@redhat.com
Subject: Re: [PATCH v3] lockdep: Teach lockdep about memalloc_noio_save
Date: Fri, 3 Mar 2017 09:22:50 +0100 [thread overview]
Message-ID: <20170303082250.GU6515@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20170303080419.GA31582@dhcp22.suse.cz>
On Fri, Mar 03, 2017 at 09:04:20AM +0100, Michal Hocko wrote:
> On Wed 01-03-17 17:18:54, Michal Hocko wrote:
> > Yes I think it would be better to send it sonner rahter than later.
> > People also might want to backport it to older kernels...
>
> Would you mind if I took this patch and route it via Andrew? I plan to
> resubmit my scope NOFS patchset [1] and [2] will need to be refreshed on
> top of it so it would be easier for me that way.
>
> [1] http://lkml.kernel.org/r/20170206140718.16222-1-mhocko@kernel.org
> [2] http://lkml.kernel.org/r/20170206140718.16222-4-mhocko@kernel.org
No real objection, but note that Ingo send out a pull request on the
sched.h split earlier today so double check that it compiles etc..
next prev parent reply other threads:[~2017-03-03 8:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-01 11:29 [PATCH v3] lockdep: Teach lockdep about memalloc_noio_save Nikolay Borisov
2017-03-01 12:09 ` Michal Hocko
2017-03-01 15:46 ` Peter Zijlstra
2017-03-01 16:01 ` Peter Zijlstra
2017-03-01 16:05 ` Michal Hocko
2017-03-01 16:12 ` Peter Zijlstra
2017-03-01 16:18 ` Michal Hocko
2017-03-03 8:04 ` Michal Hocko
2017-03-03 8:22 ` Peter Zijlstra [this message]
2017-03-03 8:31 ` Michal Hocko
2017-03-03 8:37 ` Michal Hocko
2017-03-03 8:50 ` Peter Zijlstra
2017-03-03 6:50 ` Mike Galbraith
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=20170303082250.GU6515@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mingo@redhat.com \
--cc=nborisov@suse.com \
--cc=vbabka.lkml@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;
as well as URLs for NNTP newsgroup(s).