public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <Werner.Almesberger@epfl.ch>
To: Keith Owens <kaos@ocs.com.au>
Cc: David Luyer <david_luyer@pacific.net.au>,
	alan@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: PATCH: "Pass module parameters" to built-in drivers
Date: Mon, 22 Jan 2001 19:08:07 +0100	[thread overview]
Message-ID: <20010122190807.R18286@almesberger.net> (raw)
In-Reply-To: <20010122165638.E4979@almesberger.net> <5766.980181036@ocs3.ocs-net>
In-Reply-To: <5766.980181036@ocs3.ocs-net>; from kaos@ocs.com.au on Tue, Jan 23, 2001 at 03:30:36AM +1100

Keith Owens wrote:
> It is part of my total Makefile rewrite for 2.5.

Oh, I see. Too bad.

> A clean implementation of module parameters mapping to setup code requires
> the mapping of a source file to the module it is linked into.

I was afraid that this would be a problem (and hoping that you've found
some miracle solution ;-)

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, ICA, EPFL, CH           Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2001-01-22 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-21  4:54 PATCH: "Pass module parameters" to built-in drivers David Luyer
2001-01-21  5:09 ` Keith Owens
2001-01-22 15:56   ` Werner Almesberger
2001-01-22 16:30     ` Keith Owens
2001-01-22 18:08       ` Werner Almesberger [this message]
2001-01-22 21:55       ` Russell King
2001-01-23  6:37         ` Keith Owens
2001-01-23  9:18     ` Richard Guenther
2001-01-24 13:32   ` Paul Gortmaker
2001-01-24 20:57     ` Keith Owens

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=20010122190807.R18286@almesberger.net \
    --to=werner.almesberger@epfl.ch \
    --cc=alan@redhat.com \
    --cc=david_luyer@pacific.net.au \
    --cc=kaos@ocs.com.au \
    --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