From: David Howells <dhowells@redhat.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: dhowells@redhat.com, Andrew Morton <akpm@linux-foundation.org>,
linux-arch <linux-arch@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 4/5] byteorder: fix direct byteswap includes
Date: Fri, 04 Jul 2008 16:37:43 +0100 [thread overview]
Message-ID: <27042.1215185863@redhat.com> (raw)
In-Reply-To: <1215144734.16647.70.camel@brick>
Harvey Harrison <harvey.harrison@gmail.com> wrote:
> +#include <asm/byteorder.h>
Please use <linux/byteorder.h> rather than <asm/byteorder.h> when including
stuff from .c files outside the include and arch directories.
And whilst you're at it, Documentation/byteorder.txt is yours for the
creation:-)
David
next prev parent reply other threads:[~2008-07-04 15:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 4:12 [PATCH 4/5] byteorder: fix direct byteswap includes Harvey Harrison
2008-07-04 15:37 ` David Howells [this message]
2008-07-04 16:37 ` Harvey Harrison
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=27042.1215185863@redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=harvey.harrison@gmail.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).