From: Sam Ravnborg <sam@ravnborg.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>
Cc: git-commits-head@vger.kernel.org
Subject: Re: add fiemap.h to header-y
Date: Fri, 3 Apr 2009 08:46:40 +0200 [thread overview]
Message-ID: <20090403064640.GA13075@uranus.ravnborg.org> (raw)
In-Reply-To: <200904030459.n334xVpS019935@hera.kernel.org>
On Fri, Apr 03, 2009 at 04:59:31AM +0000, Linux Kernel Mailing List wrote:
> Gitweb: http://git.kernel.org/linus/8e2c3795c78d5c4e2e1f14ce751e9d08decbe9d3
> Commit: 8e2c3795c78d5c4e2e1f14ce751e9d08decbe9d3
> Parent: c90bfeb80f00c765a57f17442fea1a57756b9034
> Author: Eric Sandeen <sandeen@redhat.com>
> AuthorDate: Thu Apr 2 16:56:44 2009 -0700
> Committer: Linus Torvalds <torvalds@linux-foundation.org>
> CommitDate: Thu Apr 2 19:04:49 2009 -0700
>
> add fiemap.h to header-y
>
> Include fiemap.h in header-y; it defines the interface for the
> FS_IOC_FIEMAP file mapping ioctl.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
> ---
> include/linux/Kbuild | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/Kbuild b/include/linux/Kbuild
> index a67b622..ca9b9b9 100644
> --- a/include/linux/Kbuild
> +++ b/include/linux/Kbuild
> @@ -67,6 +67,7 @@ header-y += falloc.h
> header-y += fd.h
> header-y += fdreg.h
> header-y += fib_rules.h
> +header-y += fiemap.h
> header-y += firewire-cdev.h
> header-y += firewire-constants.h
> header-y += fuse.h
Before adding a new headers as an exported headers please fix it up.
This headers uses __u32/__u64 but fails to include <linux/types.h>
Sam
next parent reply other threads:[~2009-04-03 6:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200904030459.n334xVpS019935@hera.kernel.org>
2009-04-03 6:46 ` Sam Ravnborg [this message]
2009-04-03 15:00 ` add fiemap.h to header-y Eric Sandeen
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=20090403064640.GA13075@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=git-commits-head@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@redhat.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