From: Jeff Garzik <jgarzik@pobox.com>
To: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Cc: netdev@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH UPDATE #2] Extract chip specific code out of lasi_82596.c
Date: Mon, 02 Jul 2007 08:43:04 -0400 [thread overview]
Message-ID: <4688F2D8.6020308@pobox.com> (raw)
In-Reply-To: <20070627224622.GA13356@alpha.franken.de>
applied both patches.
Please provide an update that does at Andrew requested -- rather than
#include'ing lib82596.c, you should update the Makefile for relevant
drivers to look like
obj-$(CONFIG_FOO_BAR) += lib82596.o foo_bar_82596.o
and make sure it exports everything to make lib82596 a full fledged module.
next prev parent reply other threads:[~2007-07-02 12:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 22:46 [PATCH UPDATE #2] Extract chip specific code out of lasi_82596.c Thomas Bogendoerfer
2007-07-02 12:43 ` Jeff Garzik [this message]
2007-07-02 13:41 ` Thomas Bogendoerfer
2007-07-02 13:58 ` Jeff Garzik
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=4688F2D8.6020308@pobox.com \
--to=jgarzik@pobox.com \
--cc=akpm@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=tsbogend@alpha.franken.de \
/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).