linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <randy.dunlap@verizon.net>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: top stack (l)users for 2.5.68
Date: Wed, 23 Apr 2003 21:50:00 -0700	[thread overview]
Message-ID: <20030423215000.71bb1ef2.randy.dunlap@verizon.net> (raw)
In-Reply-To: <20030422115905.780cd1df.rddunlap@osdl.org>

| 
| 45 functions for 2.5.68, 44 for 2.5.67. The new one is this:
| 0xc0881136 mxb_init_done:                      sub    $0x51c,%esp
| 
| Michael, are there any reasons not to make saa7740_init static, global
| or both? The memory is gone forever either way.
| Moreover, wouldn't this be a candidate for __init and __initdata
| respectively?
| 
| Apart from that, patches for the marked (P) functions are in -je1, but
| might need some shaping up. Handle with care.
| 
| Everything else remains unchanged since 2.5.67.
| 
| 0xc05cff3c parport_config:                     sub    $0x490,%esp
| 0xc0c12366 sw_connect:                         sub    $0x490,%esp
| 0xc0c36c73 ixj_config:                         sub    $0x484,%esp
| 0xc0c18ef1 uinput_alloc_device:                sub    $0x480,%esp

For PCMCIA/PC Card drivers (parport and ixj above), what context do the
pcmcia event handlers run in?  Can they kmalloc()?  with what gfp_flags?

I'll post patches for sw_connect() and uinput_alloc_device() shortly.

-- 
~Randy

       reply	other threads:[~2003-04-24  4:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030422115905.780cd1df.rddunlap@osdl.org>
2003-04-24  4:50 ` Randy.Dunlap [this message]
2003-04-22 18:55 top stack (l)users for 2.5.68 Jörn Engel
2003-04-25  7:04 ` Michael Hunold
2003-04-25 12:52   ` Jörn Engel

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=20030423215000.71bb1ef2.randy.dunlap@verizon.net \
    --to=randy.dunlap@verizon.net \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).