From: Joe Perches <joe@perches.com>
To: Vladimir Kondratiev <qca_vkondrat@qca.qualcomm.com>,
Michal Marek <mmarek@suse.cz>
Cc: "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: Wed, 09 Apr 2014 09:06:41 -0700 [thread overview]
Message-ID: <1397059601.14321.19.camel@joe-AO722> (raw)
In-Reply-To: <2146187.nt2BTDzSlP@lx-vladimir>
(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.
> 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.
Michal? Any opinion?
next prev parent reply other threads:[~2014-04-09 16:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1396946179-11677-1-git-send-email-qca_vkondrat@qca.qualcomm.com>
[not found] ` <1396946179-11677-2-git-send-email-qca_vkondrat@qca.qualcomm.com>
2014-04-08 16:14 ` [PATCH 1/5] wil6210: Convert to Kbuild Joe Perches
2014-04-09 14:08 ` Vladimir Kondratiev
2014-04-09 16:06 ` Joe Perches [this message]
2014-04-10 8:22 ` Michal Marek
2014-04-10 10:23 ` Vladimir Kondratiev
2014-04-10 11:06 ` Michal Marek
2014-04-10 12:37 ` Vladimir Kondratiev
2014-04-10 11:14 ` Johannes Berg
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=1397059601.14321.19.camel@joe-AO722 \
--to=joe@perches.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mmarek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=qca_vkondrat@qca.qualcomm.com \
--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;
as well as URLs for NNTP newsgroup(s).