From: NeilBrown <neilb@suse.de>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Mikulas Patocka <mpatocka@redhat.com>,
Zdenek Kabelac <zkabelac@redhat.com>,
tglx@linutronix.de, ilya.dryomov@inktank.com,
umgwanakikbuti@gmail.com, Oleg Nesterov <oleg@redhat.com>,
Ingo Molnar <mingo@kernel.org>,
dm-devel@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove might_sleep from wait_event_cmd
Date: Wed, 4 Feb 2015 08:30:25 +1100 [thread overview]
Message-ID: <20150204083025.00facfb7@notabene.brown> (raw)
In-Reply-To: <20150203110630.GK26304@twins.programming.kicks-ass.net>
[-- Attachment #1: Type: text/plain, Size: 898 bytes --]
On Tue, 3 Feb 2015 12:06:30 +0100 Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, Feb 03, 2015 at 09:12:53AM +1100, NeilBrown wrote:
> > I support this patch.
>
> It should hopefully already be en-route to tip.
Hopefully that means it will be in 3.19-final...
Thanks, I'll drop my __wait_event_cmd patch then.
NeilBrown
>
> > However in case it doesn't get in, I've queued up a patch to change raid5.c
> > to use __wait_event_cmd instead...
>
> So those primitives are useful in their own; their typical use would be
> when you already know @cond to be false and want to avoid the extra
> invocation.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 811 bytes --]
next prev parent reply other threads:[~2015-02-03 21:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-02 14:39 [PATCH] Remove might_sleep from wait_event_cmd Mikulas Patocka
2015-02-02 22:12 ` NeilBrown
2015-02-03 11:06 ` Peter Zijlstra
2015-02-03 21:30 ` NeilBrown [this message]
2015-02-03 11:22 ` [tip:sched/urgent] sched/wait: Remove might_sleep() from wait_event_cmd() tip-bot for Mikulas Patocka
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=20150204083025.00facfb7@notabene.brown \
--to=neilb@suse.de \
--cc=dm-devel@redhat.com \
--cc=ilya.dryomov@inktank.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mpatocka@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=umgwanakikbuti@gmail.com \
--cc=zkabelac@redhat.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