All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anupam Kapoor <anupam.kapoor@gmail.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [Kernel-janitors] Re: set_current_state
Date: Mon, 28 Jun 2004 13:33:12 +0000	[thread overview]
Message-ID: <e3177630406280621640323ae@mail.gmail.com> (raw)
In-Reply-To: <20040627223356.GA1653@masina>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

hi,

i just checked with the latest sources and there are 417 entries with
'current->state'. is a blind search-replace to set_current_state ok ?

can you please let me know ?

kind regards
anupam

On Mon, 28 Jun 2004 00:33:56 +0200, Domen Puncer <domen@coderock.org> wrote:
> 
> On 27/06/04 14:24 -0500, Jay Bourque wrote:
> > New guy here,
> >
> > I've been following the discussion lately and with talk about the
> > TODO list badly needing updating, I was wondering how up to
> > date the kj.pl script is.  In particular, I ran it against the
> > net/core/dev.c file and it showed that current->state needs to be
> > changed to set_current_state. Is this still something that needs
> > to be done?
> 
> Yes.
> If you look at set_current_state, you see it's basically the same, with
> a memory barrier.
> 
> 
> 
> >
> > Thanks,
> > -Jay
> > _______________________________________________
> > Kernel-janitors mailing list
> > Kernel-janitors@lists.osdl.org
> > http://lists.osdl.org/mailman/listinfo/kernel-janitors
> 
> 
> 
> noname - 1K Download 
>

[-- Attachment #2: Type: text/plain, Size: 167 bytes --]

_______________________________________________
Kernel-janitors mailing list
Kernel-janitors@lists.osdl.org
http://lists.osdl.org/mailman/listinfo/kernel-janitors

  reply	other threads:[~2004-06-28 13:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-27 22:33 [Kernel-janitors] Re: set_current_state Domen Puncer
2004-06-28 13:33 ` Anupam Kapoor [this message]
2004-06-28 14:33 ` Domen Puncer
2004-06-30 11:09 ` Anupam Kapoor
2004-06-30 12:30 ` Felipe W Damasio
2004-06-30 12:56 ` Anupam Kapoor
2004-06-30 12:58 ` Felipe W Damasio

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=e3177630406280621640323ae@mail.gmail.com \
    --to=anupam.kapoor@gmail.com \
    --cc=kernel-janitors@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.