public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Mike Frysinger <vapier.adi@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	linux-arch@vger.kernel.org
Subject: Re: Build regressions/improvements in v3.0-rc5
Date: Sat, 2 Jul 2011 10:38:32 +0200	[thread overview]
Message-ID: <201107021038.33066.arnd@arndb.de> (raw)
In-Reply-To: <CAMjpGUcrZpqDwi8r+BmyDV29-FcU9miJLv-dHGjUYY_GLYLU8A@mail.gmail.com>

On Saturday 02 July 2011 01:15:16 Mike Frysinger wrote:
> 
> On Fri, Jul 1, 2011 at 18:05, Arnd Bergmann wrote:
> > --- a/kernel/resource.c
> > +++ b/kernel/resource.c
> > @@ -21,7 +21,7 @@
> >  #include <linux/pfn.h>
> >  #include <asm/io.h>
> >
> > -
> > +#ifdef IO_SPACE_LIMIT
> >  struct resource ioport_resource = {
> >        .name   = "PCI IO",
> >        .start  = 0,
> > @@ -29,6 +29,7 @@ struct resource ioport_resource = {
> >        .flags  = IORESOURCE_IO,
> >  };
> >  EXPORT_SYMBOL(ioport_resource);
> > +#endif
> 
> hmm, asm-generic/io.h unconditionally sets this to 0xffff.  should
> that depend on CONFIG_HAS_IOPORT ?

Yes, that's probably another small change we should do. Right now,
building without HAS_IOPORT is broken in little ways all over the
place, so I expect there will be more of these once we look in all
the places. Regarding asm-generic/io.h, we probably want to
conditionally disable large parts of it.

Thanks,

	Arnd

      reply	other threads:[~2011-07-02  8:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-29  8:13 Build regressions/improvements in v3.0-rc5 Geert Uytterhoeven
2011-06-29 21:06 ` Build regressions/improvements in v3.0-rc5 (arch/cris) Randy Dunlap
2011-06-30  8:23   ` Américo Wang
2011-06-29 21:06 ` Build regressions/improvements in v3.0-rc5 (ssize_t ???) Randy Dunlap
2011-06-30  6:59   ` Geert Uytterhoeven
2011-06-30  7:16     ` Mikael Starvik
2011-06-30  8:01     ` Christoph Hellwig
2011-06-30  8:43       ` Geert Uytterhoeven
2011-06-30  8:56         ` Christoph Hellwig
2011-06-30  9:32           ` Geert Uytterhoeven
2011-06-30  9:44             ` Christoph Hellwig
2011-06-30 17:07         ` Andreas Schwab
2011-07-01  5:25           ` Mikael Starvik
2011-07-01  8:34             ` Andreas Schwab
2011-06-30 16:12     ` Randy Dunlap
2011-06-29 21:21 ` Build regressions/improvements in v3.0-rc5 (xfs on cris) Randy Dunlap
2011-06-29 21:24   ` Christoph Hellwig
2011-06-30  8:34     ` Américo Wang
2011-07-01 22:05 ` Build regressions/improvements in v3.0-rc5 Arnd Bergmann
2011-07-01 23:15   ` Mike Frysinger
2011-07-02  8:38     ` Arnd Bergmann [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=201107021038.33066.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=geert@linux-m68k.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier.adi@gmail.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