linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christian Lamparter <chunkeey@web.de>
To: maximilian attems <max@stro.at>
Cc: linux-wireless@vger.kernel.org, Bob Copeland <me@bobcopeland.com>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] ath: add module information
Date: Mon, 13 Apr 2009 23:18:32 +0200	[thread overview]
Message-ID: <200904132318.32767.chunkeey@web.de> (raw)
In-Reply-To: <20090413204430.GH31922@baikonur.stro.at>

On Monday 13 April 2009 22:44:30 maximilian attems wrote:
> On Mon, Apr 13, 2009 at 10:44:23PM +0200, Christian Lamparter wrote:
> > diff --git a/drivers/net/wireless/ath/Makefile b/drivers/net/wireless/ath/Makefile
> > index a005b91..4bb0132 100644
> > --- a/drivers/net/wireless/ath/Makefile
> > +++ b/drivers/net/wireless/ath/Makefile
> > @@ -3,5 +3,4 @@ obj-$(CONFIG_ATH9K)		+= ath9k/
> >  obj-$(CONFIG_AR9170_USB)        += ar9170/
> >  
> >  obj-$(CONFIG_ATH_COMMON)	+= ath.o
> > -ath-objs 		:= regd.o
> > -
> > +ath-objs 		:= main.o regd.o
> 
> why do you put that in a different file and not in ath.c?
which ath.c?

besides, is this possible?
as kbuild will then generate two ath.o
- one from ath.c.
- when all ath-objs are merged into ath.o
  so we end up reading & writing to the same file?!

Regards,
	Chr

  parent reply	other threads:[~2009-04-13 21:18 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-13 20:44 [PATCH] ath: add module information Christian Lamparter
2009-04-13 20:44 ` maximilian attems
2009-04-13 21:00   ` Luis R. Rodriguez
2009-04-13 21:08     ` Luis R. Rodriguez
2009-04-13 21:11     ` Bob Copeland
2009-04-13 21:18   ` Christian Lamparter [this message]
2009-04-14 11:58 ` Christoph Hellwig
2009-04-14 20:11   ` [PATCH v2] " Christian Lamparter

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=200904132318.32767.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.com \
    --cc=max@stro.at \
    --cc=me@bobcopeland.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 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).