All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: mmotm 2008-10-02-16-17 uploaded
Date: Thu, 2 Oct 2008 20:37:59 -0700	[thread overview]
Message-ID: <20081002203759.55f49dad.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081002203230.27b92b30.rdunlap@xenotime.net>

On Thu, 2 Oct 2008 20:32:30 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote:

> On Thu, 2 Oct 2008 17:17:16 -0700 (PDT) Randy.Dunlap wrote:
> 
> > On Thu, 2 Oct 2008, akpm@linux-foundation.org wrote:
> > 
> > > The mm-of-the-moment snapshot 2008-10-02-16-17 has been uploaded to
> > > 
> > >    http://userweb.kernel.org/~akpm/mmotm/
> > > 
> > > It contains the following patches against 2.6.27-rc8:
> > 
> > 10 out of 10 build randconfig failures on i386;
> > 10 out of 10 build randconfig failures on x86_64.
> > 
> > Summary for i386:
> > 
> > build-r9491.out:/home/rdunlap/linsrc/mmotm-2008-1002-1617/fs/autofs4/dev-ioctl.c:310: error: too 
> > many arguments to function 'dentry_open'
> > 
> > ~~~ (with copy-and-paste line breaks)
> > 
> > build-r9502.out:/home/rdunlap/linsrc/mmotm-2008-1002-1617/arch/x86/kernel/io_apic_32.c:1539: warn
> > ing: format '%08x' expects type 'unsigned int', but argument 2 has type 'u64'
> > build-r9502.out:/home/rdunlap/linsrc/mmotm-2008-1002-1617/arch/x86/kernel/io_apic_32.c:1540: warn
> > ing: format '%08x' expects type 'unsigned int', but argument 2 has type 'u64'
> 
> Weren't these already fixed once?  Could they be in one of the 180-or-so
> -tip branches but you don't have it?

That's a workable theory.

> > 
> > Summary for x86_64:
> > 
> > (lots of these)
> > build-r9493.out:/home/rdunlap/linsrc/mmotm-2008-1002-1617/arch/x86/kernel/io_apic_64.c:1284: warn
> > ing: format '%08x' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
> > build-r9493.out:/home/rdunlap/linsrc/mmotm-2008-1002-1617/arch/x86/kernel/io_apic_64.c:1285: warn
> > ing: format '%08x' expects type 'unsigned int', but argument 2 has type 'long unsigned int'
> 
> Same question for these...
> 
> > build-r9493.out:/home/rdunlap/linsrc/mmotm-2008-1002-1617/fs/autofs4/dev-ioctl.c:310: error: too 
> > many arguments to function 'dentry_open'
> 
> You (akpm) made a patch (autofs4-add-miscellaneous-device-for-ioctls-fix-fix-3.patch)
> which adds arg4 to this call to dentry_open() but I can't find why/where a 4th arg
> was added and the patch doesn't seem to be needed here/now.  what gives?
> 

Some other tree which fell out of the pile changed the dentry_open()
interface so that fix isn't needed until it is needed again.

Really, it's not worth bothering about at present.  I wonder what's on TV?

  reply	other threads:[~2008-10-03  3:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-02 23:18 mmotm 2008-10-02-16-17 uploaded akpm
2008-10-03  0:17 ` Randy.Dunlap
2008-10-03  0:45   ` Andrew Morton
2008-10-03  3:32   ` Randy Dunlap
2008-10-03  3:37     ` Andrew Morton [this message]
2008-10-03  3:43       ` Randy Dunlap
2008-10-07  7:33   ` KAMEZAWA Hiroyuki
2008-10-07 16:18     ` Yinghai Lu
2008-10-07 23:47       ` KAMEZAWA Hiroyuki
2008-10-08  0:01         ` Andrew Morton
2008-10-08  0:34           ` KAMEZAWA Hiroyuki
2008-10-08  9:50           ` Ingo Molnar

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=20081002203759.55f49dad.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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.