public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <jens.axboe@oracle.com>
To: dave young <hidave.darkstar@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] cdrom_sysctl_info fix
Date: Mon, 18 Jun 2007 09:05:19 +0200	[thread overview]
Message-ID: <20070618070519.GR6149@kernel.dk> (raw)
In-Reply-To: <a8e1da0706180003u35003bb6j706efc25c2b287db@mail.gmail.com>

On Mon, Jun 18 2007, dave young wrote:
> Hi,
> >> BTW, another problem, I can't find the CONFIG_CDROM option in kernel
> >> config menu. Is it deperacated? If it is true, is the module part
> >> still necessary?
> >
> >cdrom.o is a hardware independent helper module, it gets included if you
> >use atapi/scsi/etc cdrom drivers. See drivers/cdrom/Makefile.
> >
> I know. Sorry for my bad english, I means MODULE's part maybe
> deperacated, not uniform cdrom driver itsself.
> 
> For example  the module_init, module_exit and MODULE_LICENSE, I
> remember it could be a standalone module in 2.4 kernels. But now seems
> not possible. am I right?

It is a stand-alone module.

-- 
Jens Axboe


  reply	other threads:[~2007-06-18  7:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-14 14:24 [PATCH] cdrom_sysctl_info fix Dave Young
2007-06-14  6:40 ` dave young
2007-06-14 15:43   ` Randy Dunlap
2007-06-15  0:11     ` dave young
2007-06-15  1:41       ` Randy Dunlap
2007-06-15  5:58       ` Jens Axboe
2007-06-15 14:33         ` Dave Young
2007-06-15 13:26 ` Jens Axboe
2007-06-18 12:58   ` Dave Young
2007-06-18  6:27     ` Jens Axboe
2007-06-18  6:41       ` dave young
2007-06-18  6:43         ` Jens Axboe
2007-06-18  7:03           ` dave young
2007-06-18  7:05             ` Jens Axboe [this message]
2007-06-18  8:33               ` Questions on one PowerPC assembly instruction from hash_page gshan

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=20070618070519.GR6149@kernel.dk \
    --to=jens.axboe@oracle.com \
    --cc=hidave.darkstar@gmail.com \
    --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