From: Jens Axboe <jens.axboe@oracle.com>
To: dann frazier <dannf@hp.com>
Cc: akpm@linux-foundation.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, mikem@beardog.cce.hp.com,
brace@beardog.cce.hp.com, scameron@beardog.cce.hp.com,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Re: [PATCH] cciss: export linux/cciss_defs.h header
Date: Tue, 23 Feb 2010 08:39:02 +0100 [thread overview]
Message-ID: <20100223073901.GK1025@kernel.dk> (raw)
In-Reply-To: <20100223045221.GG3923@ldl.fc.hp.com>
On Mon, Feb 22 2010, dann frazier wrote:
> 'make headers_check' began to fail after cciss_defs.h was introduced in:
> 429c42c9d246f5bda868495c09974312a0177328
>
> usr/include/linux/cciss_ioctl.h:6: included file 'linux/cciss_defs.h' is not exported
Thanks Dann for the patch, and sorry Stephen for the breakage.
--
Jens Axboe
prev parent reply other threads:[~2010-02-23 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-23 2:26 linux-next: build failure after merge of the block tree Stephen Rothwell
2010-02-23 4:52 ` [PATCH] cciss: export linux/cciss_defs.h header dann frazier
2010-02-23 7:39 ` Jens Axboe [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=20100223073901.GK1025@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brace@beardog.cce.hp.com \
--cc=dannf@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mikem@beardog.cce.hp.com \
--cc=scameron@beardog.cce.hp.com \
--cc=sfr@canb.auug.org.au \
/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).