From: Krzysiek Taraszka <dzimi@ep09.kernel.pl>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PPC and 2.2.21rc3 with modular ide subsystem
Date: Fri, 3 May 2002 18:51:56 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.44.0205031851010.29050-100000@ep09.kernel.pl> (raw)
In-Reply-To: <20020503164358.GC894@opus.bloom.county>
On Fri, 3 May 2002, Tom Rini wrote:
> Date: Fri, 3 May 2002 09:43:58 -0700
> From: Tom Rini <trini@kernel.crashing.org>
> To: Krzysiek Taraszka <dzimi@ep09.kernel.pl>
> Cc: linux-kernel@vger.kernel.org
> Subject: Re: PPC and 2.2.21rc3 with modular ide subsystem
>
> On Fri, May 03, 2002 at 06:05:34PM +0200, Krzysiek Taraszka wrote:
> > On Fri, 3 May 2002, Tom Rini wrote:
> >
> > > Date: Fri, 3 May 2002 08:53:13 -0700
> > > From: Tom Rini <trini@kernel.crashing.org>
> > > To: Krzysiek Taraszka <dzimi@ep09.kernel.pl>
> > > Cc: linux-kernel@vger.kernel.org
> > > Subject: Re: PPC and 2.2.21rc3 with modular ide subsystem
> > >
> > > On Fri, May 03, 2002 at 01:58:49PM +0200, Krzysiek Taraszka wrote:
> > >
> > > > I tried compile 2.2.21rc3 with modular ide subsystem and i got that
> > > > messages:
> > >
> > > Pmac IDE is not able to be built as a module. If you just have a PCI
> > > IDE card you want to use, you should be able to if you set
> > > CONFIG_BLK_DEV_IDE_PMAC to n. Otherwise you must compile it in.
> >
> > What about 2.4/2.5 kernels ?
>
> The same restrictions apply to 2.4 as well. It's planned to try and fix
> this issue in 2.5 at some point.
Thank you very much.
Krzysiek Taraszka (dzimi@pld.org.pl)
prev parent reply other threads:[~2002-05-03 16:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-03 11:58 Krzysiek Taraszka
2002-05-03 15:53 ` Tom Rini
2002-05-03 16:05 ` Krzysiek Taraszka
2002-05-03 16:43 ` Tom Rini
2002-05-03 16:51 ` Krzysiek Taraszka [this message]
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=Pine.LNX.4.44.0205031851010.29050-100000@ep09.kernel.pl \
--to=dzimi@ep09.kernel.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=trini@kernel.crashing.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
all inboxes | Powered by JetHome®