From: Roland Dreier <rdreier@cisco.com>
To: "Bryan O'Sullivan" <bos@pathscale.com>
Cc: rolandd@cisco.com, gregkh@suse.de, akpm@osdl.org,
davem@davemloft.net, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH 1 of 20] ipath - core driver header files
Date: Thu, 09 Mar 2006 09:19:59 -0800 [thread overview]
Message-ID: <adaek1blem8.fsf@cisco.com> (raw)
In-Reply-To: <55ad4136aa293c14dccc.1141922814@localhost.localdomain> (Bryan O'Sullivan's message of "Thu, 9 Mar 2006 08:46:54 -0800")
> +#include "ipath_common.h"
> +#include "ipath_debug.h"
> +#include "ipath_registers.h"
> +#include <linux/interrupt.h>
> +#include <asm/io.h>
The usual style is to include <linux/> first, then <asm/>, and finally
your own local headers.
- R.
next parent reply other threads:[~2006-03-09 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55ad4136aa293c14dccc.1141922814@localhost.localdomain>
2006-03-09 17:19 ` Roland Dreier [this message]
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 1 of 20] ipath - core driver header files 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=adaek1blem8.fsf@cisco.com \
--to=rdreier@cisco.com \
--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=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