From: "David S. Miller" <davem@davemloft.net>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: linux-kernel@vger.kernel.org, ultralinux@vger.kernel.org
Subject: Re: SPARC64: Modular floppy?
Date: Mon, 28 Feb 2005 15:51:42 -0800 [thread overview]
Message-ID: <20050228155142.12ae31a7.davem@davemloft.net> (raw)
In-Reply-To: <200502282007.j1SK7hgE031074@laptop11.inf.utfsm.cl>
On Mon, 28 Feb 2005 17:07:43 -0300
Horst von Brand <vonbrand@inf.utfsm.cl> wrote:
> So, either the dependencies have to get fixed so floppy can't be modular
> for this architecture, or the relevant functions have to move from entry.S
> to the module.
I think the former is the best solution. The assembler code really
needs to get at floppy.c symbols.
next prev parent reply other threads:[~2005-02-28 23:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 20:07 Horst von Brand
2005-02-28 23:51 ` David S. Miller [this message]
2005-03-01 1:53 ` Horst von Brand
2005-03-01 17:25 ` Randy.Dunlap
2005-03-01 19:26 ` Horst von Brand
2005-03-01 19:34 ` Randy.Dunlap
2005-03-01 23:04 ` David S. Miller
2005-03-01 19:49 Randy.Dunlap
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=20050228155142.12ae31a7.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=ultralinux@vger.kernel.org \
--cc=vonbrand@inf.utfsm.cl \
/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
Powered by JetHome