From: Richard Weinberger <richard@nod.at>
To: Oleg Nesterov <oleg@redhat.com>
Cc: airlied@linux.ie, dri-devel@lists.freedesktop.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: block_all_signals() usage in DRM
Date: Mon, 25 May 2015 19:15:02 +0200 [thread overview]
Message-ID: <55635896.1040600@nod.at> (raw)
In-Reply-To: <20150525165032.GB32370@redhat.com>
Am 25.05.2015 um 18:50 schrieb Oleg Nesterov:
> AAAAOn 05/25, Richard Weinberger wrote:
>>
>> Is this functionality still in use/needed?
>
> All I can say it doesn't work.
>
>> Otherwise we could get rid of block_all_signals() and unpuzzle the signaling
>> code a bit. :-)
>
> Yes. I do not even remember when I reported this the first time. Perhaps
> more than 10 years ago.
>
> See the last attempt in 2011: https://lkml.org/lkml/2011/7/12/263
> I copied this email below.
Thank you Oleg, this makes sense.
I was actually wondering WTF this function is good for.
Thanks,
//richard
next prev parent reply other threads:[~2015-05-25 17:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-25 14:59 block_all_signals() usage in DRM Richard Weinberger
2015-05-25 16:50 ` Oleg Nesterov
2015-05-25 17:15 ` Richard Weinberger [this message]
2015-05-25 21:36 ` Dave Airlie
2015-05-25 21:31 ` Dave Airlie
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=55635896.1040600@nod.at \
--to=richard@nod.at \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oleg@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