linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Szepe <szepe@pinerecords.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.21-rc2 IDE Modular non-compile
Date: Sun, 11 May 2003 21:57:08 +0200	[thread overview]
Message-ID: <20030511195708.GC5376@louise.pinerecords.com> (raw)
In-Reply-To: <1052671379.29920.11.camel@dhcp22.swansea.linux.org.uk>

> [alan@lxorguk.ukuu.org.uk]
> 
> On Sul, 2003-05-11 at 16:03, Tomas Szepe wrote:
> > The patch (against 2.4.21-rc2-ac1) is rather large, because it
> > 	o  moves cmd640.c from drivers/ide/pci to drivers/ide, and
> > 	o  deletes cmd640.h as it is no longer used.
> 
> Please dont move cmd640, the drivers dont go in the top ide directory

[CC list trimmed]

I can't seem to get make to build the objects in pci/ before compiling
in the top level ide directory and a cross-directory dependency on
pci/cmd640.o isn't exactly nice. :(  I could use some help, fs/Makefile
does exactly what ide needs (builds objects in fs's subdirs then links them
together with fs/*.o, except for for -y, not -m) but contains no magic
whatsoever as far as I can tell.

T.

      reply	other threads:[~2003-05-11 19:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-09  6:35 2.4.21-rc2 IDE Modular non-compile Rusty Russell
2003-05-09  6:53 ` Christoph Hellwig
2003-05-09  8:30   ` Rusty Russell
2003-05-10 10:26   ` Tomas Szepe
2003-05-10 11:38     ` Tomas Szepe
2003-05-10 11:39       ` Tomas Szepe
2003-05-10 14:30     ` Alan Cox
2003-05-10 14:31     ` Alan Cox
2003-05-11 15:03       ` Tomas Szepe
2003-05-11 16:43         ` Alan Cox
2003-05-11 19:57           ` Tomas Szepe [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=20030511195708.GC5376@louise.pinerecords.com \
    --to=szepe@pinerecords.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --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;
as well as URLs for NNTP newsgroup(s).