linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Oleg Nesterov <oleg@redhat.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	linux-spi <linux-spi@vger.kernel.org>
Subject: Re: [PATCH/RFC] signal: Export signal_wake_up_state() to modules
Date: Fri, 5 May 2017 04:22:00 -0700	[thread overview]
Message-ID: <20170505112200.GA2939@infradead.org> (raw)
In-Reply-To: <CAMuHMdVUymKQzt9Rk1mgXxJdVD1O8yFQ6CxFAZDiLRDM795-Ew@mail.gmail.com>

On Fri, May 05, 2017 at 01:08:47PM +0200, Geert Uytterhoeven wrote:
> Of course I can add a flag to indicate abortion, and just call complete_all(),
> but IMHO that's a bit silly, given wait_for_completion_interruptible() already
> provides this side channel information through -ERESTARTSYS.

Even if this was the right channel (which I'm not sure about) it
should be provided as an abstract API operating on the completion.

  reply	other threads:[~2017-05-05 11:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-05  9:49 [PATCH/RFC] signal: Export signal_wake_up_state() to modules Geert Uytterhoeven
2017-05-05 10:07 ` Christoph Hellwig
2017-05-05 10:13   ` Geert Uytterhoeven
2017-05-05 11:08     ` Geert Uytterhoeven
2017-05-05 11:22       ` Christoph Hellwig [this message]
2017-05-05 11:35         ` Geert Uytterhoeven
2017-05-06 19:42 ` Oleg Nesterov
2017-05-07  9:47   ` Geert Uytterhoeven

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=20170505112200.GA2939@infradead.org \
    --to=hch@infradead.org \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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).