From: Borislav Petkov <bp@amd64.org>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Ingo Molnar <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Borislav Petkov <borislav.petkov@amd.com>
Subject: Re: [PATCH 1/2] tools: Add Makefile.lib
Date: Thu, 22 Mar 2012 22:15:57 +0100 [thread overview]
Message-ID: <20120322211557.GB1462@aftab> (raw)
In-Reply-To: <20120322210732.GA21154@merkur.ravnborg.org>
On Thu, Mar 22, 2012 at 10:07:32PM +0100, Sam Ravnborg wrote:
> On Thu, Mar 22, 2012 at 06:01:52PM +0100, Borislav Petkov wrote:
> > From: Borislav Petkov <borislav.petkov@amd.com>
> >
> > Put generic enough build settings which could be reused by other tools
> > into a common Makefile.lib file.
>
> I assume that the reason to use the filename "Makefile.lib" is that
> scripts/Makefile.lib uses the same extension.
Yep.
> But whoever idiot(*) that decided to use that extension deserve to be shot!
Ye^W^W.. oops, oh no, please no! :-)
> It is not a library per see, it is just a bunch of stuff you include
> in another makefile.
> So Makefile.include would be better - and as an added benefit vim
> does not barf on it.
Makes sense, will do, thanks.
> (*) I actually shave him quite often...
LOL.
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
next prev parent reply other threads:[~2012-03-22 21:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-22 17:01 [PATCH 0/2] tools: Add a toplevel Makefile Borislav Petkov
2012-03-22 17:01 ` [PATCH 1/2] tools: Add Makefile.lib Borislav Petkov
2012-03-22 21:07 ` Sam Ravnborg
2012-03-22 21:15 ` Borislav Petkov [this message]
2012-03-22 17:01 ` [PATCH 2/2] tools: Add a toplevel Makefile Borislav Petkov
2012-03-22 18:33 ` Christoph Lameter
2012-03-22 21:04 ` Borislav Petkov
2012-03-22 21:47 ` Christoph Lameter
2012-03-26 10:27 ` Pekka Enberg
2012-03-29 12:33 ` Borislav Petkov
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=20120322211557.GB1462@aftab \
--to=bp@amd64.org \
--cc=acme@infradead.org \
--cc=borislav.petkov@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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