From: Jeff Garzik <jeff@garzik.org>
To: Masakazu Mokuno <mokuno@sm.sony.co.jp>
Cc: netdev@vger.kernel.org,
Geoff Levand <geoffrey.levand@am.sony.com>,
Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Subject: Re: [PATCH] ps3: gigabit ethernet driver for PS3, take2
Date: Tue, 03 Jul 2007 09:11:09 -0400 [thread overview]
Message-ID: <468A4AED.7080907@garzik.org> (raw)
In-Reply-To: <20070703194416.91C5.MOKUNO@sm.sony.co.jp>
Masakazu Mokuno wrote:
>>> --- a/drivers/net/Makefile
>>> +++ b/drivers/net/Makefile
>>> @@ -60,6 +60,8 @@ obj-$(CONFIG_TIGON3) += tg3.o
>>> obj-$(CONFIG_BNX2) += bnx2.o
>>> spidernet-y += spider_net.o spider_net_ethtool.o
>>> obj-$(CONFIG_SPIDER_NET) += spidernet.o sungem_phy.o
>>> +obj-$(CONFIG_GELIC_NET) += ps3_gelic.o
>>> +ps3_gelic-objs += gelic_net.o
>>> obj-$(CONFIG_TC35815) += tc35815.o
>>> obj-$(CONFIG_SKGE) += skge.o
>>> obj-$(CONFIG_SKY2) += sky2.o
>>> --- /dev/null
>>> +++ b/drivers/net/gelic_net.c
>> The patch does not reflect the new name...
>
> The driver's module name is 'ps3_gelic.ko' and the souce file names are
> 'gelic_net.{c,h}'. As Geoff Levand said in the mail dated June 16, we
> have plan to add wireless support and its file name would be gelic_wireless.c.
> If this support added, the make file would be:
>
> obj-$(CONFIG_GELIC_NET) += ps3_gelic.o
> gelic-$(CONFIG_GELIC_WIRELESS) += gelic_wireless.o
> ps3_gelic-objs += gelic_net.o $(gelic-y)
For single-file modules, the source file prefix should match the output
file prefix.
No Linux driver does it any other way. It leads to confusion.
Jeff
next prev parent reply other threads:[~2007-07-03 13:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 10:39 [PATCH] ps3: gigabit ethernet driver for PS3, take2 MOKUNO Masakazu
2007-06-23 18:09 ` Geoff Levand
2007-06-26 2:48 ` Masakazu Mokuno
2007-07-02 12:30 ` Jeff Garzik
2007-07-03 12:01 ` Masakazu Mokuno
2007-07-03 13:11 ` Jeff Garzik [this message]
2007-07-03 15:11 ` Geert Uytterhoeven
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=468A4AED.7080907@garzik.org \
--to=jeff@garzik.org \
--cc=Geert.Uytterhoeven@sonycom.com \
--cc=geoffrey.levand@am.sony.com \
--cc=mokuno@sm.sony.co.jp \
--cc=netdev@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).