netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "Hennerich, Michael" <Michael.Hennerich@analog.com>,
	netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
	uclinux-dist-devel@blackfin.uclinux.org
Subject: Re: [Uclinux-dist-devel] [PATCH] wireless: adf702x: new driver for ADF7020/21 parts
Date: Tue, 22 Dec 2009 08:09:43 -0500	[thread overview]
Message-ID: <8bd0f97a0912220509w641a4e2cv615bc6d690cabab0@mail.gmail.com> (raw)
In-Reply-To: <1261486016.609.4.camel@localhost.localdomain>

On Tue, Dec 22, 2009 at 07:46, Marcel Holtmann wrote:
>> >>  drivers/net/wireless/Kconfig   |   11 +
>> >>  drivers/net/wireless/Makefile  |    2 +
>> >>  drivers/net/wireless/adf702x.c |  788
>> >>  include/linux/spi/adf702x.h    |   33 ++
>> >>  4 files changed, 834 insertions(+), 0 deletions(-)
>> >>  create mode 100644 drivers/net/wireless/adf702x.c
>> >>  create mode 100644 include/linux/spi/adf702x.h
>> >
>> >And why is the header file under SPI includes. It could be as easily in
>> >the same directory as the driver *.c file itself. No reason to spread it
>> >over the whole tree if nothing else includes it.
>>
>> It under include/linux/spi/ because it includes platform data which is used by board support files.
>
> that is no argument to move it there. It is a driver specific header and
> so keep it in the same location as the driver itself.

that is incorrect.  for devices that need platform resources, the
structure is in a header in the include/ tree.  it cannot be in
drivers/net/ where boards are unable to include it.

whether it goes in linux/spi/ or linux/net/ or somewhere else we dont
really care.  linux/spi/ seems to be the best match so far.
-mike

  parent reply	other threads:[~2009-12-22 13:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22  2:12 [PATCH] wireless: adf702x: new driver for ADF7020/21 parts Mike Frysinger
2009-12-22  3:05 ` Marcel Holtmann
2009-12-22 10:38   ` Hennerich, Michael
2009-12-22 12:46     ` Marcel Holtmann
2009-12-22 12:56       ` Hennerich, Michael
2009-12-22 13:09       ` Mike Frysinger [this message]
2009-12-22  3:44 ` Ben Hutchings
2009-12-22 11:46   ` Hennerich, Michael
2009-12-22 16:02     ` Ben Hutchings
2010-01-19  7:37       ` [Uclinux-dist-devel] " Mike Frysinger
2010-01-19  7:39 ` [PATCH v2] " Mike Frysinger

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=8bd0f97a0912220509w641a4e2cv615bc6d690cabab0@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=Michael.Hennerich@analog.com \
    --cc=davem@davemloft.net \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=uclinux-dist-devel@blackfin.uclinux.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).