From: Sam Ravnborg <sam@ravnborg.org>
To: Roland Dreier <rdreier@cisco.com>
Cc: "Bryan O'Sullivan" <bos@pathscale.com>,
rolandd@cisco.com, gregkh@suse.de, akpm@osdl.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH 18 of 20] ipath - kbuild infrastructure
Date: Thu, 9 Mar 2006 19:56:04 +0100 [thread overview]
Message-ID: <20060309185604.GA24004@mars.ravnborg.org> (raw)
In-Reply-To: <ada4q27ld33.fsf@cisco.com>
On Thu, Mar 09, 2006 at 09:53:04AM -0800, Roland Dreier wrote:
> > + depends on 64BIT && (PCIEPORTBUS || X86_HT)
>
> > --- /dev/null Thu Jan 1 00:00:00 1970 +0000
> > +++ b/drivers/infiniband/hw/ipath/Makefile Thu Mar 9 08:46:47 2006 -0800
>
> I've been suggesting that new files be called "Kbuild", since Sam has
> deprecated the "Makefile" name.
Eventually - yes.
But not just now. Kbuild was introduced because it was needed in the
top-level directory and it made good sense to do so.
But for now keeping Makefile is a good choice. This is anyway what
people are used to.
Sam
next prev parent reply other threads:[~2006-03-09 18:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ac5354bb50d515de2a5c.1141922831@localhost.localdomain>
2006-03-09 17:53 ` [PATCH 18 of 20] ipath - kbuild infrastructure Roland Dreier
2006-03-09 18:56 ` Sam Ravnborg [this message]
2006-03-09 19:00 ` Roland Dreier
2006-03-09 21:15 ` Sam Ravnborg
2006-03-09 23:24 ` Sam Ravnborg
2006-03-10 0:35 [PATCH 0 of 20] [RFC] ipath driver - another round for review Bryan O'Sullivan
2006-03-10 0:35 ` [PATCH 18 of 20] ipath - kbuild infrastructure Bryan O'Sullivan
2006-03-13 18:10 ` Adrian Bunk
2006-03-13 18:38 ` Robert Walsh
2006-03-13 19:24 ` Bryan O'Sullivan
2006-03-13 19:36 ` Sam Ravnborg
2006-03-13 19:39 ` Bryan O'Sullivan
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=20060309185604.GA24004@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@osdl.org \
--cc=bos@pathscale.com \
--cc=davem@davemloft.net \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
--cc=rolandd@cisco.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