netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <bhutchings@solarflare.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: netdev@vger.kernel.org, linux-net-drivers@solarflare.com,
	Jeff Garzik <jgarzik@pobox.com>,
	David Miller <davem@davemloft.net>
Subject: Re: [PATCH 8/8] New driver "sfc" for Solarstorm SFC4000 controller (try #8)
Date: Mon, 24 Mar 2008 10:34:40 +0000	[thread overview]
Message-ID: <20080324103438.GA24160@solarflare.com> (raw)
In-Reply-To: <20080324085202.GA4845@infradead.org>

Christoph Hellwig wrote:
> > +++ b/drivers/net/sfc/Makefile
> > @@ -0,0 +1,23 @@
> > +
> > +# Final objects
> > +sfc_o = sfc.o
> > +
> > +# Constituent objects
> > +sfc_elements_o :=
> > +sfc_elements_o += efx.o
> > +sfc_elements_o += falcon.o
> > +sfc_elements_o += tx.o
> > +sfc_elements_o += rx.o
> > +sfc_elements_o += falcon_xmac.o
> > +sfc_elements_o += i2c-direct.o
> > +sfc_elements_o += ethtool.o
> > +sfc_elements_o += xfp_phy.o
> > +sfc_elements_o += mdio_10g.o
> > +sfc_elements_o += tenxpress.o
> > +sfc_elements_o += boards.o
> > +sfc_elements_o += sfe4001.o
> > +
> > +obj-$(CONFIG_SFC) += $(sfc_o)
> > +
> > +sfc-objs = $(sfc_elements_o)
> 
> Very strange makefile.  This should be:
> 
> sfc-y			+= efx.o falcon.o tx.o rx.o falcon_xmac.o \					   i2c-direct.o ethtool.o xfp_phy.o mdio_10g.o \
> 			   tenxpress.o boards.o sfe4001.o
> 
> obj-$(CONFIG_SFC)	+= sfc.o

The Makefile and all the source files are derived from an internal
version, processed to remove code that's not suitable for upstream.
But they're not strictly tracking that version any more, so we could
just write it the simple way.

Ben.

-- 
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.

      reply	other threads:[~2008-03-24 10:35 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-12  1:21 [PATCH 0/8] New driver "sfc" for Solarstorm SFC4000 controller (try #8) Ben Hutchings
2008-03-12  1:22 ` [PATCH 1/8] " Ben Hutchings
2008-03-24  5:32   ` David Miller
2008-03-24 10:29     ` Ben Hutchings
2008-03-24 20:22       ` David Miller
2008-03-25 12:54         ` Ben Hutchings
2008-03-25 23:37           ` David Miller
2008-03-26 11:58             ` Ben Hutchings
2008-03-25 15:40     ` Ben Hutchings
2008-03-12  1:23 ` [PATCH 2/8] " Ben Hutchings
2008-03-24  5:35   ` David Miller
2008-03-12  1:24 ` [PATCH 3/8] " Ben Hutchings
2008-03-24  5:36   ` David Miller
2008-03-12  1:24 ` [PATCH 4/8] " Ben Hutchings
2008-03-24  5:37   ` David Miller
2008-03-12  1:25 ` [PATCH 5/8] " Ben Hutchings
2008-03-24  5:38   ` David Miller
2008-03-12  1:25 ` [PATCH 6/8] " Ben Hutchings
2008-03-24  5:39   ` David Miller
2008-03-12  1:26 ` [PATCH 7/8] " Ben Hutchings
2008-03-24  5:40   ` David Miller
2008-03-12  1:26 ` [PATCH 8/8] " Ben Hutchings
2008-03-12  1:45   ` Ben Hutchings
2008-03-12  2:01     ` David Miller
2008-03-12  2:29       ` David Miller
2008-03-24  5:40   ` David Miller
2008-03-24  8:52   ` Christoph Hellwig
2008-03-24 10:34     ` Ben Hutchings [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=20080324103438.GA24160@solarflare.com \
    --to=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=hch@infradead.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-net-drivers@solarflare.com \
    --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).