From: Mark Brown <broonie@kernel.org>
To: hubcap <hubcap@omnibond.com>
Cc: viro@zeniv.linux.org.uk, Guenter Roeck <linux@roeck-us.net>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH V3 14/7] Orangefs: Swap order of include files
Date: Thu, 6 Aug 2015 10:18:25 +0100 [thread overview]
Message-ID: <20150806091825.GP20873@sirena.org.uk> (raw)
In-Reply-To: <1438804120-10923-3-git-send-email-hubcap@logtruck.clemson.edu>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On Wed, Aug 05, 2015 at 03:48:40PM -0400, hubcap wrote:
> From: Guenter Roeck <linux@roeck-us.net>
>
> spinlock_types.h requires types from linux/types.h.
> Including spinlock_types.h first may result in the following build errors,
> as seen with arm:allmodconfig.
Please stop CCing me on this stuff - like I say I'm pretty sure there's
a typo and this was intended to go to someone else.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-08-06 9:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1437143897-9069-1-git-send-email-root@logtruck.clemson.edu>
2015-07-24 19:09 ` [PATCH V3 8/7] Orangefs: kernel client update 1 Mike Marshall
2015-07-28 20:27 ` [PATCH V3 9/7] Orangefs: sooth most sparse complaints hubcap
2015-07-29 19:57 ` [PATCH V3 10/7] Orangefs: address problems found by static checker hubcap
2015-07-30 20:33 ` [PATCH V3 11/7] Orangefs: large integer implicitly truncated to unsigned type hubcap
2015-07-31 7:36 ` Christoph Hellwig
2015-07-31 8:26 ` Al Viro
2015-08-05 19:48 ` [PATCH V3 12/7] Orangefs: use inode_set_bytes for directories hubcap
2015-08-05 19:48 ` [PATCH V2 13/7] fs: orangefs: remove execute priviliges from module params hubcap
2015-08-05 19:48 ` [PATCH V3 14/7] Orangefs: Swap order of include files hubcap
2015-08-06 9:18 ` Mark Brown [this message]
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=20150806091825.GP20873@sirena.org.uk \
--to=broonie@kernel.org \
--cc=hubcap@omnibond.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.