All of lore.kernel.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Yuri Tikhonov <yur@emcraft.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] ppc: Marvell mv64x60 drivers for ppc platforms fix
Date: Mon, 25 Jun 2007 12:14:54 +0200	[thread overview]
Message-ID: <e0e9d630d6957b397ca8cd8263616fcb@kernel.crashing.org> (raw)
In-Reply-To: <200706251351.55868.yur@emcraft.com>

>  The mv64x60 driver has no support for compiling as a module. Built-in 
> only.

Yeah I expected that that is the case right now.  Could be
fixed later though.

> And I think there is no much sense in making the driver which provide 
> you
> with such a base stuff as a boot console, ethernet, etc. to be a LKM.

That's orthogonal to expressing it as one "module" in Kbuild,
which is really just about grouping highly interdependent
stuff together.

But anyway, your patch looks good, I was just suggesting to
clean it up some more.  You don't have to do it now if you
don't want to, I'm sure it will happen later :-)

[Oh, and don't top-post.]

>>> +mv64x60-$(CONFIG_PCI)          += mv64x60_pci.o
>>> +obj-$(CONFIG_MV64X60)          += $(mv64x60-y) mv64x60_pic.o
>>> mv64x60_dev.o
>>
>> How about
>>
>> mv64x60-pci-$(CONFIG_PCI)      += mv64x60_pci.o
>> mv64x60-objs                   := $(mv64x60-pci-y) mv64x60_pic.o
>> mv64x60_dev.o
>> obj-$(CONFIG_MV64X60)          += mv64x60.o
>>
>> so you can build it is a module, too (although other things
>> might be preventing that right now)?


Segher

  reply	other threads:[~2007-06-25 10:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-25  8:47 [PATCH] ppc: Marvell mv64x60 drivers for ppc platforms fix Yuri Tikhonov
2007-06-25  9:11 ` Segher Boessenkool
2007-06-25  9:51   ` Yuri Tikhonov
2007-06-25 10:14     ` Segher Boessenkool [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-06-24 11:52 Yuri Tikhonov
2007-06-24 22:46 ` Dale Farnsworth
2007-06-25  1:49   ` Kumar Gala

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=e0e9d630d6957b397ca8cd8263616fcb@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=yur@emcraft.com \
    /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.