All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Franco <stratus@acm.org>
To: kernel-janitors@vger.kernel.org
Subject: [Kernel-janitors] yield() calls on drivers/ status.
Date: Sat, 24 Apr 2004 21:07:45 +0000	[thread overview]
Message-ID: <408AD721.7040502@acm.org> (raw)

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

Hi list,

Linux Kernel 2.6.5 status:

cdrom/sonycd535.c:              2.6.6-rc2-kj1(patched)  (me)
cdrom/cdu31a.c:                 patch sent              (me)
macintosh/adb.c:                need investigation
message/i2o/i2o_core.c:         need investigation
message/i2o/i2o_core.c:         need investigation
mtd/chips/cfi_cmdset_0002.c:    need investigation
net/sb1000.c:                   patch sent              (me)
net/sb1000.c:                   patch sent              (me)
net/sis900.c:                   2.6.6-rc2-kj1(patched)  (maximilian)
net/depca.c:                    need investigation
net/sungem.c:                   need investigation
scsi/megaraid.c:                patch sent              (me)
scsi/ibmmca.c:                  need investigation
scsi/ibmmca.c:                  need investigation
scsi/NCR5380.c:                 need investigation
 

The Linux Kernel 2.6.6-rc2-bk3 status is the same as above,
there are no new yield() calls.

I'm planning to come back here and check the nine left drivers
in the next weekend, if someone can check some of these before,
it will be good.


Hope that helps,
Gustavo Franco -- <stratus@acm.org>

[-- 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-04-24 21:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=408AD721.7040502@acm.org \
    --to=stratus@acm.org \
    --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.