[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1378450038.19204.6.camel@joe-AO722>
Date: Thu, 05 Sep 2013 23:47:18 -0700
From: Joe Perches <joe@...ches.com>
To: "Brandeburg, Jesse" <jesse.brandeburg@...el.com>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>,
"e1000-devel@...ts.sourceforge.net"
<e1000-devel@...ts.sourceforge.net>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"gospo@...hat.com" <gospo@...hat.com>,
"sassmann@...hat.com" <sassmann@...hat.com>
Subject: Re: [E1000-devel] [net-next v5 8/8] i40e: include i40e in kernel
proper
On Fri, 2013-09-06 at 06:28 +0000, Brandeburg, Jesse wrote:
> On Sep 5, 2013, at 11:15 PM, "Stephen Hemminger" <stephen@...workplumber.org<mailto:stephen@...workplumber.org>> wrote:
>
> Dumb question why is this named Kbuild instead of Makefile like almost
> every other network driver?
>
> All the new kids are doing it, we'll at least that is what I thought when I made it.
>
> Re-reading https://www.kernel.org/doc/Documentation/kbuild/makefiles.txt
>
> I see that Makefile is preferred but Kbuild overrides Makefile.
>
> Either way works, but I would prefer not to rename it at this point but would gladly do so in a follow up patch
Please do.
I suppose it makes _some_ sense to use Kbuild in the
include paths but I think Makefile in places where
compilations are done is better.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists