From: Michal Marek <mmarek@suse.cz>
To: Joe Perches <joe@perches.com>
Cc: jeffrey.t.kirsher@intel.com, Sam Ravnborg <sam@ravnborg.org>,
linux-kbuild@vger.kernel.org, "Brandeburg,
Jesse" <jesse.brandeburg@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Wyborny, Carolyn" <carolyn.wyborny@intel.com>,
"Skidmore, Donald C" <donald.c.skidmore@intel.com>,
"Rose, Gregory V" <gregory.v.rose@intel.com>,
"Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
e1000-devel <e1000-devel@lists.sourceforge.net>
Subject: Re: [RFC PATCH net-next] drivers/net Documentation/networking: Create directory intel_wired_lan
Date: Thu, 14 Oct 2010 23:37:33 +0200 [thread overview]
Message-ID: <4CB7781D.80103@suse.cz> (raw)
In-Reply-To: <1287084643.1117.602.camel@Joe-Laptop>
On 14.10.2010 21:30, Joe Perches wrote:
> On Thu, 2010-10-14 at 02:34 -0700, Jeff Kirsher wrote:
>> On Wed, 2010-10-13 at 22:57 -0700, Joe Perches wrote:
>>> On Wed, 2010-10-13 at 21:57 -0700, Jeff Kirsher wrote:
>>>> On Wed, 2010-10-13 at 15:28 -0700, Joe Perches wrote:
>>>> Sorry I am not ignoring you, I was taking a closer look at your patch.
>>>>> What regression testing would actually be done?
>>>> The Makefile and Kconfig needs more work. I applied your patch and none
>>>> of the Intel Wired drivers build.
>>> Care to describe the Makefile/Kconfig issues you have seen?
>>> I built it allyesconfig, defconfig, allmodconfig and allnoconfig.
>> Yeah, I found all of those built without errors, but if you build the
>> Intel Wired LAN drivers as modules, you will not find the *.ko files
>> after the build. The Kconfig files look fine, the problem was with the
>> Makefiles. Instead of creating a drivers/net/intel_wired_lan/Makefile,
>> I simply changed the path in drivers/net/Makefile to the updated path
>> and that resolved the issue.
>
> (adding a few cc's and a link for history)
>
> http://lkml.org/lkml/2010/10/10/207
>
> That's the way I had done it originally as well, but I found
> you couldn't build the directory with:
>
> make drivers/net/intel_wired_lan/
>
> so I created a Makefile in the new directory below with
> the elements necessary.
>
> Perhaps there's some missing functionality in the build system
> when the Kconfig file resides in a higher directory and the
> directory being built doesn't have a Kconfig file?
This has nothing to do with Kconfig files, I assume you meant Makefiles.
> I think it'd wrong to duplicate the makefile components in
> 2 places to allow "make subdir/" and I wonder if there's a
> good solution for this.
There is no duplication needed, drivers/net/Makefile needs to contain
obj-y += intel_wired_lan/ and drivers/net/intel_wired_lan/Makefile
similar lines for its subdirs. I see your original patch was lacking an
entry in drivers/net/Makefile, so perhaps that was the problem Jeff was
seeing?
Michal
next prev parent reply other threads:[~2010-10-14 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1286743352.11039.165.camel@Joe-Laptop>
[not found] ` <AANLkTikVKufQRuMGd=cdig7ff4k2aw9Q1FWwMz3pgon-@mail.gmail.com>
[not found] ` <1286841648.26045.17.camel@Joe-Laptop>
[not found] ` <1287008906.1117.428.camel@Joe-Laptop>
[not found] ` <1287032255.4113.14.camel@jtkirshe-MOBL1>
[not found] ` <1287035857.1117.528.camel@Joe-Laptop>
[not found] ` <1287048849.3319.20.camel@jtkirshe-MOBL1>
2010-10-14 19:30 ` [RFC PATCH net-next] drivers/net Documentation/networking: Create directory intel_wired_lan Joe Perches
2010-10-14 21:37 ` Michal Marek [this message]
2010-10-14 22:20 ` Jeff Kirsher
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=4CB7781D.80103@suse.cz \
--to=mmarek@suse.cz \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jesse.brandeburg@intel.com \
--cc=joe@perches.com \
--cc=john.ronciak@intel.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=sam@ravnborg.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