linux-next: Tree for March 13

linux-next: Tree for March 13

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

Hi all,

I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(tar balls at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).

You can see which trees have been included by looking in the Next/Trees
file in the source.  There are also quilt-import.log and merge.log files
in the Next directory.  Between each merge, the tree was built with
allmodconfig for both powerpc and x86_64.

There were a few merge conflicts (trivial) and two build breakages (both
in hand).

We are up to 47 trees, more are welcome (even if they are currently
empty).  The influx of new trees has been underwhelming.  Thanks to those
who have contributed, and to those who haven't, please do.

In particular, I have very few of the architecture trees ....

Status of my local build tests is at
http://kisskb.ellerman.id.au/kisskb/branch/9/.  If maintainers want to
give advice about cross compilers/configs that work, we are always open
to add more builds.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

Re: linux-next: Tree for March 13

[Geert Uytterhoeven]

On Thu, 13 Mar 2008, Stephen Rothwell wrote:
> Status of my local build tests is at
> http://kisskb.ellerman.id.au/kisskb/branch/9/.  If maintainers want to
> give advice about cross compilers/configs that work, we are always open
> to add more builds.

I noticed you added `m68k-allnoconfig', which fails because of the following
reasons:
  - There's no single CPU type enabled, hence we get:

	#define FPSTATESIZE error no_cpu_type_configured

  - There's no single platform type enabled, hence we get no definition of
    NR_IRQS:

	#error unknown nr of irqs

Well yes, these are all `features' of allnoconfig :-)
Or should we make sure you cannot build invalid configs like this?

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds

Re: linux-next: Tree for March 13 (PCI patch)

[Randy Dunlap]

On Thu, 13 Mar 2008 17:35:06 +1100 Stephen Rothwell wrote:

> Hi all,
> 
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> (tar balls at
> http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).

---

From: Randy Dunlap <randy.dunlap@oracle.com>

access.c uses udelay() so needs to #include delay.h.

next-20080313/drivers/pci/access.c:167: error: implicit declaration of function 'udelay'
make[3]: *** [drivers/pci/access.o] Error 1
make[2]: *** [drivers/pci] Error 2
make[1]: *** [drivers] Error 2
make[1]: *** Waiting for unfinished jobs....
make: *** [sub-make] Error 2

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 drivers/pci/access.c |    1 +
 1 file changed, 1 insertion(+)

--- next-20080313.orig/drivers/pci/access.c
+++ next-20080313/drivers/pci/access.c
@@ -1,3 +1,4 @@
+#include <linux/delay.h>
 #include <linux/pci.h>
 #include <linux/module.h>
 #include <linux/sched.h>

Re: linux-next: Tree for March 13 (PCI patch)

[Greg KH]

On Thu, Mar 13, 2008 at 10:02:35AM -0700, Randy Dunlap wrote:
> On Thu, 13 Mar 2008 17:35:06 +1100 Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> > (tar balls at
> > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).
> 
> ---
> 
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> access.c uses udelay() so needs to #include delay.h.
> 
> next-20080313/drivers/pci/access.c:167: error: implicit declaration of function 'udelay'
> make[3]: *** [drivers/pci/access.o] Error 1
> make[2]: *** [drivers/pci] Error 2
> make[1]: *** [drivers] Error 2
> make[1]: *** Waiting for unfinished jobs....
> make: *** [sub-make] Error 2
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  drivers/pci/access.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- next-20080313.orig/drivers/pci/access.c
> +++ next-20080313/drivers/pci/access.c
> @@ -1,3 +1,4 @@
> +#include <linux/delay.h>
>  #include <linux/pci.h>
>  #include <linux/module.h>
>  #include <linux/sched.h>

Thanks, I've merged this with the offending patch so there are no build
errors.

greg k-h

Re: linux-next: Tree for March 13

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1153 bytes --]

Hi Geert,

On Thu, 13 Mar 2008 11:31:39 +0100 (CET) Geert Uytterhoeven <geert@linux-m68k.org> wrote:
>
> I noticed you added `m68k-allnoconfig', which fails because of the following

This was an experiment.  I disabled it again.

> reasons:
>   - There's no single CPU type enabled, hence we get:
> 
> 	#define FPSTATESIZE error no_cpu_type_configured
> 
>   - There's no single platform type enabled, hence we get no definition of
>     NR_IRQS:
> 
> 	#error unknown nr of irqs
> 
> Well yes, these are all `features' of allnoconfig :-)
> Or should we make sure you cannot build invalid configs like this?

I think that for architectures that do allow allnoconfig to build, they
have a fallback for these situations.  allnoconfig is a good quick way to
see if the core code builds ok for an architecture.

So maybe you could choose (even at random) defaults for the above two
things rather than erroring.  That would also help with randconfig builds.

If you make it work, let me know and I will reenable the build.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]