public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>
To: Michal Marek <mmarek@suse.cz>
Cc: Joe Perches <joe@perches.com>,
	"John W . Linville" <linville@tuxdriver.com>,
	<linux-wireless@vger.kernel.org>, <wil6210@qca.qualcomm.com>,
	netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/5] wil6210: Convert to Kbuild
Date: Thu, 10 Apr 2014 13:23:18 +0300	[thread overview]
Message-ID: <1949326.Ead3K8R9Y2@lx-vladimir> (raw)
In-Reply-To: <534654D7.4080904@suse.cz>

On Thursday, April 10, 2014 10:22:47 AM Michal Marek wrote:
> On 2014-04-09 18:06, Joe Perches wrote:
> > (adding Michal Marek)
> > 
> > On Wed, 2014-04-09 at 17:08 +0300, Vladimir Kondratiev wrote:
> >> On Tuesday, April 08, 2014 09:14:51 AM Joe Perches wrote:
> >>> On Tue, 2014-04-08 at 11:36 +0300, Vladimir Kondratiev wrote:
> >>>> Convert Makefile -> Kbuild,
> >>>> to make off-kernel development easier and less intrusive.
> >>> No drivers/net directory uses Kbuild.
> >>> Why should this?
> >>
> >> because it makes it easier to do off-kernel development, and then
> >> move things to the proper location within the kernel without
> >> conflicting changes in the Makefile.
> 
> You can create a GNUmakefile for this purpose, it takes precedence over
> Makefile.
> 
> 
> >> As I understand, Kbuild is better choice because it is really not
> >> standalone "Makefile", it is intended to be included by the real
> >> Makefile. Thus, distinct name is better.
> >> Are there any reasons why not using Kbuild? I did not found
> >> guidelines when use Kbuild and when not.
> 
> Kbuild is a slightly better choice because it better describes the
> content, but I don't think its needed to rename existing Makefiles just
> because of that. Kbuild is needed in the toplevel directory or in
> arch/*/, where Makefile has a different special meaning. The out of tree
> build use case can be solved by a GNUmakefile.
> 

Originally, I followed the code found at
drivers/scsi/osd/
They have Kbuild for in-kernel use and Makefile for out-of-tree

But now I found, Documentation/kbuild/makefiles.txt says:
---cut---
The preferred name for the kbuild files are 'Makefile' but 'Kbuild' can
be used and if both a 'Makefile' and a 'Kbuild' file exists, then the 'Kbuild'
file will be used.
---cut---

Accordingly to this, would you say I should drop this patch and go with
GNUmakefile + Makefile for internal development? I am pretty neutral with
this, just need to know what is the proper way.

Thanks, Vladimir 

  reply	other threads:[~2014-04-10 10:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-08  8:36 [PATCH 0/5] wil6210 patches Vladimir Kondratiev
2014-04-08  8:36 ` [PATCH 1/5] wil6210: Convert to Kbuild Vladimir Kondratiev
2014-04-08 16:14   ` Joe Perches
2014-04-09 14:08     ` Vladimir Kondratiev
2014-04-09 16:06       ` Joe Perches
2014-04-10  8:22         ` Michal Marek
2014-04-10 10:23           ` Vladimir Kondratiev [this message]
2014-04-10 11:06             ` Michal Marek
2014-04-10 12:37               ` Vladimir Kondratiev
2014-04-10 11:14             ` Johannes Berg
2014-04-08  8:36 ` [PATCH 2/5] wil6210: fix printouts for better readability Vladimir Kondratiev
2014-04-08  8:36 ` [PATCH 3/5] wil6210: sync with the latest FW API Vladimir Kondratiev
2014-04-08  8:36 ` [PATCH 4/5] wil6210: relaxed check for BACK start sequence Vladimir Kondratiev
2014-04-08  8:36 ` [PATCH 5/5] wil6210: Use larger Tx rings Vladimir Kondratiev

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=1949326.Ead3K8R9Y2@lx-vladimir \
    --to=qca_vkondrat@qca.qualcomm.com \
    --cc=joe@perches.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mmarek@suse.cz \
    --cc=netdev@vger.kernel.org \
    --cc=wil6210@qca.qualcomm.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