From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, ultralinux@vger.kernel.org
Subject: Re: SPARC64: Modular floppy?
Date: Tue, 01 Mar 2005 17:25:38 +0000 [thread overview]
Message-ID: <4224A592.1050909@osdl.org> (raw)
In-Reply-To: <200503010153.j211rGXB006246@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
> "David S. Miller" <davem@davemloft.net> said:
>
>>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.
>
>
>>From my cursory look the stuff depending on the floppy.c symbols is just
> in the floppy-related code. Can't that be just included in floppy.c?
> (Could be quite a mess, but it looks like short stretches).
The code in entry.S looks self-contained (to me:), so moving it
somewhere else should just be a SMOP (mostly kbuild stuff)....
--
~Randy
WARNING: multiple messages have this Message-ID (diff)
From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: "David S. Miller" <davem@davemloft.net>,
linux-kernel@vger.kernel.org, ultralinux@vger.kernel.org
Subject: Re: SPARC64: Modular floppy?
Date: Tue, 01 Mar 2005 09:25:38 -0800 [thread overview]
Message-ID: <4224A592.1050909@osdl.org> (raw)
In-Reply-To: <200503010153.j211rGXB006246@laptop11.inf.utfsm.cl>
Horst von Brand wrote:
> "David S. Miller" <davem@davemloft.net> said:
>
>>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.
>
>
>>From my cursory look the stuff depending on the floppy.c symbols is just
> in the floppy-related code. Can't that be just included in floppy.c?
> (Could be quite a mess, but it looks like short stretches).
The code in entry.S looks self-contained (to me:), so moving it
somewhere else should just be a SMOP (mostly kbuild stuff)....
--
~Randy
next prev parent reply other threads:[~2005-03-01 17:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 20:07 SPARC64: Modular floppy? Horst von Brand
2005-02-28 20:07 ` Horst von Brand
2005-02-28 23:51 ` David S. Miller
2005-02-28 23:51 ` David S. Miller
2005-03-01 1:53 ` Horst von Brand
2005-03-01 1:53 ` Horst von Brand
2005-03-01 17:25 ` Randy.Dunlap [this message]
2005-03-01 17:25 ` Randy.Dunlap
2005-03-01 19:26 ` Horst von Brand
2005-03-01 19:26 ` Horst von Brand
2005-03-01 19:34 ` Randy.Dunlap
2005-03-01 19:34 ` Randy.Dunlap
2005-03-01 23:04 ` David S. Miller
2005-03-01 23:04 ` David S. Miller
2005-03-01 19:49 ` Randy.Dunlap
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=4224A592.1050909@osdl.org \
--to=rddunlap@osdl.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.