From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: -mm merge plans for 2.6.26
Date: Fri, 16 May 2008 17:28:16 -0700 [thread overview]
Message-ID: <20080516172816.9d98c0f2.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080516170310.35d7b407.randy.dunlap@oracle.com>
On Fri, 16 May 2008 17:03:10 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Sun, 20 Apr 2008 07:20:53 -0700 Andrew Morton wrote:
>
> >
> > These can be found at
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.25/2.6.25-mm1
> >
> >
> >
> > #
> > # documentation
> > #
> > documentation-build-source-files-in-documentation-sub-dir.patch
> > documentation-build-source-files-in-documentation-sub-dir-update.patch
> > documentation-build-source-files-in-documentation-sub-dir-disable.patch
> >
> > Merge
>
> Hi,
> What happened to/with these?
I was going to ask you that. Last I heard,
a) stuff broke and
b) you had an updated version somewhere.
On Thu, 10 Apr 2008 17:56:30 -0700 Randy Dunlap <randy.dunlap@oracle.com> wrote:
> On Wed, 9 Apr 2008 14:54:09 -0700 Andrew Morton wrote:
>
> > make allmodconfig
> > gcc -I$(/bin/pwd)/include Documentation/accounting/getdelays.c -o getdelays
> >
> > In file included from /usr/src/devel/include/linux/netlink.h:5,
> > from /usr/src/devel/include/linux/genetlink.h:4,
> > from Documentation/accounting/getdelays.c:26:
> > /usr/src/devel/include/linux/types.h:203: error: expected specifier-qualifier-list before '__kernel_daddr_t'
>
>
> Those __kernel_* types shouldn't be used outside of the #ifdef __KERNEL__
> block, should they?
>
> Patch below fixes kernel side for me. Don't have any idea what it
> may do to userspace users of the header file.
>
> ---
> include/linux/types.h | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> --- mmotm-2008-0410-0157.orig/include/linux/types.h
> +++ mmotm-2008-0410-0157/include/linux/types.h
> @@ -200,8 +200,8 @@ typedef u32 resource_size_t;
> #endif /* __KERNEL__ */
>
> struct ustat {
> - __kernel_daddr_t f_tfree;
> - __kernel_ino_t f_tinode;
> + daddr_t f_tfree;
> + ino_t f_tinode;
> char f_fname[6];
> char f_fpack[6];
> };
I didn't apply that. I guess the "Don't have any idea" bit was scary.
next prev parent reply other threads:[~2008-05-17 0:28 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 14:20 Andrew Morton
2008-04-20 15:51 ` Jiri Slaby
2008-04-20 23:51 ` -mm merge plans for 2.6.26 (memcgroup) Hugh Dickins
2008-04-21 0:30 ` KAMEZAWA Hiroyuki
2008-04-21 6:24 ` Andrew Morton
[not found] ` <480C347C.6060702@linux.vnet.ibm.com>
2008-04-21 6:47 ` Balbir Singh
2008-04-21 9:42 ` Peter Zijlstra
2008-04-21 10:21 ` Balbir Singh
2008-04-21 10:40 ` KAMEZAWA Hiroyuki
2008-04-21 15:48 ` Paul Menage
2008-04-21 11:22 ` Hugh Dickins
2008-04-21 11:41 ` Andi Kleen
2008-04-21 12:13 ` Hugh Dickins
2008-04-21 13:31 ` kamezawa.hiroyu
2008-04-21 11:41 ` Balbir Singh
2008-05-17 0:03 ` -mm merge plans for 2.6.26 Randy Dunlap
2008-05-17 0:28 ` Andrew Morton [this message]
2008-05-17 2:07 ` Randy Dunlap
2008-05-17 4:30 ` Randy Dunlap
2008-05-19 20:26 ` Randy Dunlap
2008-05-19 20:38 ` Andrew Morton
2008-05-19 20:44 ` Sam Ravnborg
2008-05-23 8:05 ` Andrew Morton
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=20080516172816.9d98c0f2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.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
Powered by JetHome