public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: rusty@rustcorp.com.au
Cc: Trent Piepho <xyzzy@speakeasy.org>,
	Rechberger Markus <mrechberger@gmail.com>,
	Linux DVB <linux-dvb@linuxtv.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>
Subject: [RFC PATCH 0/3] Fix module information when symbol_get is used
Date: Sat, 10 Mar 2007 02:31:22 -0200	[thread overview]
Message-ID: <1173501083.26213.403.camel@localhost> (raw)

Hi Rusty,

DVB code uses symbol_get/symbol_put functions at module.c to allow
dynamically add frontend modules (responsible for tuning and
demodulating the digital signal). The problem is that symbol_get doesn't
properly mark the module that requested it.

Trent worked on a fix for this, by using 3 patches. One on module.c,
another on mtd driver, and the last one on linux-dvb.

With the patch, lsmod produces output like this:
cx88_dvb               14084  0
or51132                 9988  1 cx88_dvb

Without it, this is what you get:
cx88_dvb               14084  0
or51132                 9988  1


 drivers/media/dvb/bt8xx/dst.c             |    5 -
 drivers/media/dvb/dvb-core/dvb_frontend.c |    9 +--
 drivers/mtd/chips/gen_probe.c             |    4 -
 include/linux/module.h                    |   13 ++--
 kernel/module.c                           |   87 ++++++++++++++++++++++--------
 5 files changed, 80 insertions(+), 38 deletions(-)


                 reply	other threads:[~2007-03-10  4:31 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=1173501083.26213.403.camel@localhost \
    --to=mchehab@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=dwmw2@infradead.org \
    --cc=linux-dvb@linuxtv.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mrechberger@gmail.com \
    --cc=rusty@rustcorp.com.au \
    --cc=xyzzy@speakeasy.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