From: Joe Perches <joe@perches.com>
To: netdev <netdev@vger.kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, David Miller <davem@davemloft.net>
Subject: drivers/net/Makefile - question about link order comment introduced in 2.3.43
Date: Wed, 06 Oct 2010 04:04:09 -0700 [thread overview]
Message-ID: <1286363049.2156.113.camel@Joe-Laptop> (raw)
It wasn't that way in 2.3.43-pre7 , but it is in 2.3.43
and has remained there since. There's nothing in lkml
history as far as I can find to describe a reason for it.
http://lkml.org/lkml/2000/2/10
(or thereabout)
Anyone know why it's like that or if that Makefile link
ordering is still needed?
Currently, drivers/net/Makefile line 42
#
# link order important here
#
obj-$(CONFIG_PLIP) += plip.o
[about 60 lines later...]
obj-$(CONFIG_STMMAC_ETH) += stmmac/
#
# end link order section
#
next reply other threads:[~2010-10-06 11:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 11:04 Joe Perches [this message]
2010-10-06 20:15 ` drivers/net/Makefile - question about link order comment introduced in 2.3.43 David Miller
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=1286363049.2156.113.camel@Joe-Laptop \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=sam@ravnborg.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