On 26 May 2015 at 02:50, Oleg Nesterov wrote:
> On 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 re
On 26 May 2015 at 00:59, Richard Weinberger wrote:
> Hi!
>
> drivers/gpu/drm/drm_lock.c is the only remaining user of block_all_signals():
It's the only user of it, ever. The API was introduced for the drm locking code.
No other user will ever exist. Just to clear up the an API exists with
one u
Am 25.05.2015 um 18:50 schrieb Oleg Nesterov:
> On 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
On 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 tha
Hi!
drivers/gpu/drm/drm_lock.c is the only remaining user of block_all_signals():
/* don't set the block all signals on the master process for now
* really probably not the correct answer but lets us debug xkb
* xserver for now */
if (!file_priv->is_master) {
