public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: davem@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: recalc_sigpending() / recalc_sigpending_tsk() ?
Date: Thu, 28 Feb 2002 18:26:58 +0000	[thread overview]
Message-ID: <365.1014920818@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0202280854250.15607-100000@home.transmeta.com>
In-Reply-To: <Pine.LNX.4.33.0202280854250.15607-100000@home.transmeta.com>


torvalds@transmeta.com said:
>  Not a chance in hell. The backwards compatibility looks like a
> trivial one-liner:

>    compat-2.4.h:
> 	#define recalc_sigpending() recalc_sigpending(current)

> so what are you complaining about? 

Fine. I was trying to define a back-compat version of recalc_sigpending_tsk()
too, before going through all the code and changing recalc_sigpending(current)
to recalc_sigpending and recalc_sigpending(other) to recalc_sigpending_tsk() 
- but as you rightly point out there's no justification for using the latter
in any of the driver or fs code that I'm trying to support - and hence it
isn't present, and doesn't need the compat support.


--
dwmw2



  reply	other threads:[~2002-02-28 18:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-28 16:31 recalc_sigpending() / recalc_sigpending_tsk() ? David Woodhouse
2002-02-28 16:59 ` Linus Torvalds
2002-02-28 18:26   ` David Woodhouse [this message]
2002-03-01 15:33   ` David Woodhouse
2002-03-01 15:33     ` David S. Miller
2002-03-01 15:37     ` David Woodhouse
2002-03-01 15:49       ` David S. Miller
2002-03-01 16:28       ` David Woodhouse
2002-03-01 16:49     ` Linus Torvalds
2002-03-01 17:05       ` David Woodhouse
2002-03-01 17:40       ` David Howells
2002-03-01 17:43         ` David Woodhouse
2002-03-01 19:01       ` [PATCH] small proposal Martin Dalecki

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=365.1014920818@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.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