* Re: linux-next: sparc/firmware build failure
From: David Woodhouse @ 2008-11-18 15:37 UTC (permalink / raw)
To: David Miller; +Cc: sfr, linux-next, jaswinder
In-Reply-To: <20081112.225748.255613824.davem@davemloft.net>
On Wed, 2008-11-12 at 22:57 -0800, David Miller wrote:
> > The firmware tree is still dropped. Please do a merge with Linus' tree
> > and fix the conflicts.
>
> Yes, pretty please David :-)
Apologies for the delay. This should be up to date again now.
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
^ permalink raw reply
* Re: linux-next: lblnet tree build failure
From: Paul Moore @ 2008-11-18 14:26 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next
In-Reply-To: <20081118151112.aa7fa93d.sfr@canb.auug.org.au>
On Monday 17 November 2008 11:11:12 pm Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> In file included from include/net/cipso_ipv4.h:43,
> from net/ipv4/ip_options.c:26:
> include/net/netlabel.h:512: error: redefinition of
> 'netlbl_cfg_cipsov4_add' include/net/netlabel.h:477: error: previous
> definition of 'netlbl_cfg_cipsov4_add' was here
> include/net/netlabel.h:517: error: redefinition of
> 'netlbl_cfg_cipsov4_del' include/net/netlabel.h:482: error: previous
> definition of 'netlbl_cfg_cipsov4_del' was here
> include/net/netlabel.h:522: error: conflicting types for
> 'netlbl_cfg_cipsov4_map_add' include/net/netlabel.h:490: error:
> previous definition of 'netlbl_cfg_cipsov4_map_add' was here
>
> I have dropped the lblnet tree for today.
Okay, sorry about that, I'll get it fixed up for tomorrow.
--
paul moore
linux @ hp
^ permalink raw reply
* Re: linux-next: manual merge of the security-testing tree
From: James Morris @ 2008-11-18 7:55 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, Jeff Layton, Steve French, David Howells
In-Reply-To: <20081117154410.dc25a2d9.sfr@canb.auug.org.au>
On Mon, 17 Nov 2008, Stephen Rothwell wrote:
> Hi James,
>
> Today's linux-next merge of the security-testing tree got a conflict in
> fs/cifs/misc.c between commit 14fbf50d695207754daeb96270b3027a3821121f
> ("cifs: reinstate sharing of SMB sessions sans races") from the cifs tree
> and commit a001e5b558f25eb1e588522d73ac949b643b7a37 ("CRED: Wrap task
> credential accesses in the CIFS filesystem") from the security-testing
> tree.
>
> I fixed it up (see below) and can carry it for a short while.
I merged with linus to resolve this, in
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/security-testing-2.6#next
commit f3a5c547012a09f38f7c27b17a8e3150b69cd259
Please test.
- James
--
James Morris
<jmorris@namei.org>
^ permalink raw reply
* linux-next: Tree for November 18
From: Stephen Rothwell @ 2008-11-18 6:17 UTC (permalink / raw)
To: linux-next; +Cc: LKML
[-- Attachment #1: Type: text/plain, Size: 6489 bytes --]
Hi all,
Changes since 20081117:
Dropped trees (temporarily):
lblnet (build problem)
userns (it depends on creds)
semaphore-removal (due to unfixed conflicts against Linus' tree)
firmware (unfixed build failure)
The net tree gained a conflict against the net-current tree.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).
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
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig,
44x_defconfig and allyesconfig and i386, sparc and sparc64 defconfig.
Below is a summary of the state of the merge.
We are up to 125 trees (counting Linus' and 14 trees of patches pending for
Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging powerpc-merge/merge
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sparc-current/master
Merging sound-current/for-linus
Merging arm-current/master
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-2.6.26
Merging dwmw2/master
Merging arm/devel
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging quilt/m68k
Merging m68knommu/for-next
Merging mips/mips-for-linux-next
Merging parisc/master
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging pxa/for-next
Merging s390/features
CONFLICT (content): Merge conflict in include/linux/kernel.h
Merging sh/master
Merging sparc/master
Merging x86/auto-x86-next
Merging xtensa/master
Merging quilt/driver-core
Merging quilt/usb
Merging tip-core/auto-core-next
Merging cpus4096/auto-cpus4096-next
Merging ftrace/auto-ftrace-next
Merging genirq/auto-genirq-next
Merging safe-poison-pointers/auto-safe-poison-pointers-next
Merging sched/auto-sched-next
Merging stackprotector/auto-stackprotector-next
Merging timers/auto-timers-next
Merging pci/linux-next
Merging quilt/device-mapper
Merging hid/mm
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
Merging jfs/next
Merging kbuild/master
Merging quilt/ide
Merging libata/NEXT
Merging nfs/linux-next
Merging xfs/master
Merging infiniband/for-next
Merging acpi/test
Merging nfsd/nfsd-next
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/master
Merging dlm/next
Merging scsi/master
Merging ocfs2/linux-next
Merging ext4/next
Merging async_tx/next
Merging udf/for_next
Merging net/master
CONFLICT (content): Merge conflict in drivers/isdn/i4l/isdn_net.c
Merging mtd/master
Merging wireless/master
Merging crypto/master
Merging vfs/for-next
Merging sound/for-next
Merging cpufreq/next
Merging v9fs/for-next
Merging quilt/rr
CONFLICT (content): Merge conflict in drivers/net/virtio_net.c
Merging cifs/master
CONFLICT (content): Merge conflict in fs/cifs/connect.c
Merging mmc/next
Merging gfs2/master
Merging input/next
Merging semaphore/semaphore
Merging bkl-removal/bkl-removal
Merging ubifs/linux-next
Merging lsm/for-next
Merging block/for-next
Merging embedded/master
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging kmemcheck/auto-kmemcheck-next
CONFLICT (content): Merge conflict in MAINTAINERS
CONFLICT (content): Merge conflict in arch/x86/mm/Makefile
CONFLICT (content): Merge conflict in mm/slab.c
CONFLICT (content): Merge conflict in mm/slub.c
Merging generic-ipi/auto-generic-ipi-next
Merging mfd/for-next
Merging hdlc/hdlc-next
CONFLICT (delete/modify): drivers/net/wan/syncppp.c deleted in hdlc/hdlc-next and modified in HEAD. Version HEAD of drivers/net/wan/syncppp.c left in tree.
$ git rm -f drivers/net/wan/syncppp.c
Merging drm/drm-next
Merging voltage/for-next
Merging security-testing/next
CONFLICT (content): Merge conflict in fs/cifs/misc.c
CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_cred.h
CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_globals.h
CONFLICT (content): Merge conflict in fs/xfs/xfs_vnodeops.h
Merging lblnet/master
$ git reset --hard HEAD^
Merging quilt/ttydev
CONFLICT (content): Merge conflict in fs/devpts/inode.c
Merging agp/agp-next
Merging oprofile/auto-oprofile-next
Merging fastboot/auto-fastboot-next
Merging sparseirq/auto-sparseirq-next
Merging iommu/auto-iommu-next
Merging uwb/for-upstream
Merging watchdog/master
Merging proc/proc
Merging bdev/master
Merging dwmw2-iommu/master
Merging cpu_alloc/cpu_alloc
CONFLICT (content): Merge conflict in kernel/lockdep.c
CONFLICT (content): Merge conflict in kernel/module.c
Applying cpu_alloc: merge_fix_1
Applying undefined reference to __per_cpu_start
Merging cputime/cputime
Merging perfmon3/master
Merging osd/linux-next
Merging fatfs/master
Merging quilt/staging
Merging scsi-post-merge/master
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* linux-next: cpu_alloc tree patch (Was: Re: next-20081106: undefined reference to `__per_cpu_start')
From: Stephen Rothwell @ 2008-11-18 4:33 UTC (permalink / raw)
To: Christoph Lameter
Cc: Alexey Dobriyan, linux-next, linux-kernel, rusty,
Haavard Skinnemoen
In-Reply-To: <Pine.LNX.4.64.0811071235040.5387@quilx.com>
[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]
Hi Christoph,
On Fri, 7 Nov 2008 12:40:17 -0600 (CST) Christoph Lameter <cl@linux-foundation.org> wrote:
>
> All of these have no invocation of the PERCPU macro from
> asm-generic/vmlinus.lds.h in their arch vmlinux.lds.S. Thus the symbols
> are missing. They are kind of irrelevant since we are only interested in
> the difference between those...
>
> Either we add the PERCPU() macro invocations to each arches vmlinux.lds.S
> file or we need to special case each time __per_cpu_end/__start is used.
> The only use added for the cpu allocator is in include/linux/percpu.h
>
> Make it conditional on CONFIG_SMP
>
> Signed-off-by: Christoph Lameter <cl@linux-foundation.org>
I have applied this to linux-next today. It is not clear to me if this
is a fix for the cpu_alloc tree or the zero-based per_cpu area patches or
a combination of both. If the first, please apply this to the cpu_alloc
tree or I will have to drop the tree. Otherwise, let me know where it
belongs.
Also, considering the "discussions" between Rusty and yourself, I may
need to drop the cpu_alloc tree until they are resolved.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* linux-next: lblnet tree build failure
From: Stephen Rothwell @ 2008-11-18 4:11 UTC (permalink / raw)
To: Paul Moore; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
Hi Paul,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
In file included from include/net/cipso_ipv4.h:43,
from net/ipv4/ip_options.c:26:
include/net/netlabel.h:512: error: redefinition of 'netlbl_cfg_cipsov4_add'
include/net/netlabel.h:477: error: previous definition of 'netlbl_cfg_cipsov4_add' was here
include/net/netlabel.h:517: error: redefinition of 'netlbl_cfg_cipsov4_del'
include/net/netlabel.h:482: error: previous definition of 'netlbl_cfg_cipsov4_del' was here
include/net/netlabel.h:522: error: conflicting types for 'netlbl_cfg_cipsov4_map_add'
include/net/netlabel.h:490: error: previous definition of 'netlbl_cfg_cipsov4_map_add' was here
I have dropped the lblnet tree for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Re: linux-next: sh tree build warning
From: Paul Mundt @ 2008-11-18 3:42 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, Magnus Damm
In-Reply-To: <20081117103446.e5c66fec.sfr@canb.auug.org.au>
On Mon, Nov 17, 2008 at 10:34:46AM +1100, Stephen Rothwell wrote:
> Hi Paul,
>
> Today's linux-next build (x86_64 allmodconfig) produced these warning:
>
> drivers/usb/gadget/m66592-udc.c: In function 'm66592_probe':
> drivers/usb/gadget/m66592-udc.c:1672: warning: label 'clean_up2' defined but not used
> drivers/usb/host/r8a66597-hcd.c: In function 'r8a66597_probe':
> drivers/usb/host/r8a66597-hcd.c:2401: warning: label 'clean_up2' defined but not used
>
> Added by commit 985fc7c81c7852f2e104c71cbe913ace683c9e6a ("sh: sh_mobile
> usbf clock framework support").
Fixed, thanks.
^ permalink raw reply
* linux-next: manual merge of the net tree
From: Stephen Rothwell @ 2008-11-18 0:51 UTC (permalink / raw)
To: David Miller; +Cc: linux-next, Harvey Harrison
[-- Attachment #1: Type: text/plain, Size: 624 bytes --]
Hi Dave,
Today's linux-next merge of the net tree got a conflict in
drivers/isdn/i4l/isdn_net.c between commit
584c650b4e6fa16f9ab45d382f86ad6d9c625227 ("isdn: remove extra byteswap in
isdn_net_ciscohdlck_slarp_send_reply") from the net-current tree and
commit 00bcd522ea0a62f5e2a9c6ad4924cbbd8d05b026 ("isdn: use %pI4, remove
get_{u8/u16/u32} and put_{u8/u16/u32} inlines") from the net tree.
I fixed it up by using the version from the net tree. I assume that this
will be fixed in that tree shortly.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
From: Jens Axboe @ 2008-11-17 18:06 UTC (permalink / raw)
To: Alexander Beregalov; +Cc: LKML, linux-next
In-Reply-To: <a4423d670811170739w3cab002aqda014ab87ebed529@mail.gmail.com>
On Mon, Nov 17 2008, Alexander Beregalov wrote:
> 2008/11/15 Alexander Beregalov <a.beregalov@gmail.com>:
> > 2008/11/15 Jens Axboe <jens.axboe@oracle.com>:
> >> On Fri, Nov 14 2008, Alexander Beregalov wrote:
> >>> WARNING: at block/blk-barrier.c:246 blk_do_ordered+0x22b/0x26a()
> >>> Modules linked in:
> >>> Pid: 0, comm: swapper Not tainted 2.6.28-rc4-next-20081114 #3
> >>> Call Trace:
> >>> <IRQ> [<ffffffff80236d63>] warn_on_slowpath+0x58/0x7d
> >>> [<ffffffff802570e3>] ? mark_lock+0x1c/0x37a
> >>> [<ffffffff803a69f9>] ? elv_rb_del+0x30/0x4b
> >>> [<ffffffff803b1092>] ? cfq_remove_request+0x180/0x1d8
> >>> [<ffffffff803afd03>] ? __cfq_slice_expired+0xd6/0xeb
> >>> [<ffffffff803afd31>] ? cfq_slice_expired+0x19/0x1b
> >>> [<ffffffff803b1832>] ? cfq_dispatch_requests+0x2c1/0x37e
> >>> [<ffffffff803aa98c>] blk_do_ordered+0x22b/0x26a
> >>> [<ffffffff803a6560>] elv_next_request+0x1d0/0x210
> >>> [<ffffffff80439c7c>] scsi_request_fn+0x9e/0x539
> >>> [<ffffffff80255c66>] ? put_lock_stats+0xe/0x27
> >>> [<ffffffff803a827e>] blk_invoke_request_fn+0x3b/0x6e
> >>> [<ffffffff803a87fd>] __blk_run_queue+0x25/0x29
> >>> [<ffffffff803a8822>] blk_run_queue+0x21/0x35
> >>> [<ffffffff80439509>] scsi_run_queue+0x2cf/0x379
> >>> [<ffffffff8043a33e>] scsi_next_command+0x36/0x46
> >>> [<ffffffff8043a509>] scsi_end_request+0x92/0xa4
> >>> [<ffffffff8043aae7>] scsi_io_completion+0x1a7/0x3ad
> >>> [<ffffffff80434551>] scsi_finish_command+0xe9/0xf2
> >>> [<ffffffff8043afd5>] scsi_softirq_done+0x10e/0x117
> >>> [<ffffffff803ac393>] blk_done_softirq+0x7f/0x8f
> >>> [<ffffffff8023c173>] __do_softirq+0x70/0x101
> >>> [<ffffffff8020cc0c>] call_softirq+0x1c/0x28
> >>> [<ffffffff8020e229>] do_softirq+0x39/0x8a
> >>> [<ffffffff8023bd78>] irq_exit+0x45/0xa2
> >>> [<ffffffff8020e53a>] do_IRQ+0x16a/0x19c
> >>> [<ffffffff8020bceb>] ret_from_intr+0x0/0xf
> >>> <EOI> [<ffffffff80212e09>] ? mwait_idle+0x3e/0x48
> >>> [<ffffffff80212e00>] ? mwait_idle+0x35/0x48
> >>> [<ffffffff8020a940>] ? cpu_idle+0x51/0xba
> >>> [<ffffffff80514f9c>] ? rest_init+0x70/0x72
> >>> ---[ end trace 115cb4be7e150bb9 ]---
> >>
> >> I'm assuming this is new with -next and doesn't happen with 2.6.28-rc4?
> > Yes.
> >> Is it reproducible in -next?
> > I have seen it only once yet.
>
> I have the same warning on 2.6.28-rc5-next-20081117, reproducible on dbench.
How big is the file system, how much ram do you have, what are your
mount options, how many dbench clients, and what dbench version? I tried
reproducing it today with no luck on -git + for-2.6.29.
--
Jens Axboe
^ permalink raw reply
* Re: next-20081114: WARNING: at block/blk-barrier.c:246 blk_do_ordered()
From: Alexander Beregalov @ 2008-11-17 15:39 UTC (permalink / raw)
To: Jens Axboe; +Cc: LKML, linux-next
In-Reply-To: <a4423d670811150925qf74b63dy1ef923347140a8fe@mail.gmail.com>
2008/11/15 Alexander Beregalov <a.beregalov@gmail.com>:
> 2008/11/15 Jens Axboe <jens.axboe@oracle.com>:
>> On Fri, Nov 14 2008, Alexander Beregalov wrote:
>>> WARNING: at block/blk-barrier.c:246 blk_do_ordered+0x22b/0x26a()
>>> Modules linked in:
>>> Pid: 0, comm: swapper Not tainted 2.6.28-rc4-next-20081114 #3
>>> Call Trace:
>>> <IRQ> [<ffffffff80236d63>] warn_on_slowpath+0x58/0x7d
>>> [<ffffffff802570e3>] ? mark_lock+0x1c/0x37a
>>> [<ffffffff803a69f9>] ? elv_rb_del+0x30/0x4b
>>> [<ffffffff803b1092>] ? cfq_remove_request+0x180/0x1d8
>>> [<ffffffff803afd03>] ? __cfq_slice_expired+0xd6/0xeb
>>> [<ffffffff803afd31>] ? cfq_slice_expired+0x19/0x1b
>>> [<ffffffff803b1832>] ? cfq_dispatch_requests+0x2c1/0x37e
>>> [<ffffffff803aa98c>] blk_do_ordered+0x22b/0x26a
>>> [<ffffffff803a6560>] elv_next_request+0x1d0/0x210
>>> [<ffffffff80439c7c>] scsi_request_fn+0x9e/0x539
>>> [<ffffffff80255c66>] ? put_lock_stats+0xe/0x27
>>> [<ffffffff803a827e>] blk_invoke_request_fn+0x3b/0x6e
>>> [<ffffffff803a87fd>] __blk_run_queue+0x25/0x29
>>> [<ffffffff803a8822>] blk_run_queue+0x21/0x35
>>> [<ffffffff80439509>] scsi_run_queue+0x2cf/0x379
>>> [<ffffffff8043a33e>] scsi_next_command+0x36/0x46
>>> [<ffffffff8043a509>] scsi_end_request+0x92/0xa4
>>> [<ffffffff8043aae7>] scsi_io_completion+0x1a7/0x3ad
>>> [<ffffffff80434551>] scsi_finish_command+0xe9/0xf2
>>> [<ffffffff8043afd5>] scsi_softirq_done+0x10e/0x117
>>> [<ffffffff803ac393>] blk_done_softirq+0x7f/0x8f
>>> [<ffffffff8023c173>] __do_softirq+0x70/0x101
>>> [<ffffffff8020cc0c>] call_softirq+0x1c/0x28
>>> [<ffffffff8020e229>] do_softirq+0x39/0x8a
>>> [<ffffffff8023bd78>] irq_exit+0x45/0xa2
>>> [<ffffffff8020e53a>] do_IRQ+0x16a/0x19c
>>> [<ffffffff8020bceb>] ret_from_intr+0x0/0xf
>>> <EOI> [<ffffffff80212e09>] ? mwait_idle+0x3e/0x48
>>> [<ffffffff80212e00>] ? mwait_idle+0x35/0x48
>>> [<ffffffff8020a940>] ? cpu_idle+0x51/0xba
>>> [<ffffffff80514f9c>] ? rest_init+0x70/0x72
>>> ---[ end trace 115cb4be7e150bb9 ]---
>>
>> I'm assuming this is new with -next and doesn't happen with 2.6.28-rc4?
> Yes.
>> Is it reproducible in -next?
> I have seen it only once yet.
I have the same warning on 2.6.28-rc5-next-20081117, reproducible on dbench.
^ permalink raw reply
* linux-next: Tree for November 17
From: Stephen Rothwell @ 2008-11-17 7:06 UTC (permalink / raw)
To: linux-next; +Cc: LKML
[-- Attachment #1: Type: text/plain, Size: 6453 bytes --]
Hi all,
Changes since 20081114:
Undropped trees:
sound
osd
Dropped trees (temporarily):
userns (it depends on creds)
semaphore-removal (due to unfixed conflicts against Linus' tree)
firmware (unfixed build failure)
The cifs tree gained a conflict against the net tree.
The hdlc tree lost a conflict.
The security-testing tree gained a conflict against the cifs tree.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
(patches at
http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).
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
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig,
44x_defconfig and allyesconfig and i386, sparc and sparc64 defconfig.
Below is a summary of the state of the merge.
We are up to 125 trees (counting Linus' and 14 trees of patches pending for
Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Jan Dittmer for adding the linux-next tree to his build tests
at http://l4x.org/k/ , the guys at http://test.kernel.org/ and Randy
Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging powerpc-merge/merge
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sparc-current/master
Merging sound-current/for-linus
Merging arm-current/master
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/usb.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-2.6.26
Merging dwmw2/master
Merging arm/devel
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging quilt/m68k
Merging m68knommu/for-next
Merging mips/mips-for-linux-next
Merging parisc/master
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging pxa/for-next
Merging s390/features
CONFLICT (content): Merge conflict in include/linux/kernel.h
Merging sh/master
Merging sparc/master
Merging x86/auto-x86-next
Merging xtensa/master
Merging quilt/driver-core
Merging quilt/usb
Merging tip-core/auto-core-next
Merging cpus4096/auto-cpus4096-next
Merging ftrace/auto-ftrace-next
Merging genirq/auto-genirq-next
Merging safe-poison-pointers/auto-safe-poison-pointers-next
Merging sched/auto-sched-next
Merging stackprotector/auto-stackprotector-next
Merging timers/auto-timers-next
Merging pci/linux-next
Merging quilt/device-mapper
Merging hid/mm
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
Merging jfs/next
Merging kbuild/master
Merging quilt/ide
Merging libata/NEXT
Merging nfs/linux-next
Merging xfs/master
Merging infiniband/for-next
Merging acpi/test
Merging nfsd/nfsd-next
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/master
Merging dlm/next
Merging scsi/master
Merging ocfs2/linux-next
Merging ext4/next
Merging async_tx/next
Merging udf/for_next
Merging net/master
Merging mtd/master
Merging wireless/master
Merging crypto/master
Merging vfs/for-next
Merging sound/for-next
Merging cpufreq/next
Merging v9fs/for-next
Merging quilt/rr
CONFLICT (content): Merge conflict in drivers/net/virtio_net.c
Merging cifs/master
CONFLICT (content): Merge conflict in fs/cifs/connect.c
Merging mmc/next
Merging gfs2/master
Merging input/next
Merging semaphore/semaphore
Merging bkl-removal/bkl-removal
Merging ubifs/linux-next
Merging lsm/for-next
Merging block/for-next
Merging embedded/master
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
Merging backlight/for-mm
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging kmemcheck/auto-kmemcheck-next
CONFLICT (content): Merge conflict in MAINTAINERS
CONFLICT (content): Merge conflict in arch/x86/mm/Makefile
CONFLICT (content): Merge conflict in mm/slab.c
CONFLICT (content): Merge conflict in mm/slub.c
Merging generic-ipi/auto-generic-ipi-next
Merging mfd/for-next
Merging hdlc/hdlc-next
CONFLICT (delete/modify): drivers/net/wan/syncppp.c deleted in hdlc/hdlc-next and modified in HEAD. Version HEAD of drivers/net/wan/syncppp.c left in tree.
$ git rm -f drivers/net/wan/syncppp.c
Merging drm/drm-next
Merging voltage/for-next
Merging security-testing/next
CONFLICT (content): Merge conflict in fs/cifs/misc.c
CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_cred.h
CONFLICT (content): Merge conflict in fs/xfs/linux-2.6/xfs_globals.h
CONFLICT (content): Merge conflict in fs/xfs/xfs_vnodeops.h
Merging lblnet/master
Merging quilt/ttydev
CONFLICT (content): Merge conflict in fs/devpts/inode.c
Merging agp/agp-next
Merging oprofile/auto-oprofile-next
Merging fastboot/auto-fastboot-next
Merging sparseirq/auto-sparseirq-next
Merging iommu/auto-iommu-next
Merging uwb/for-upstream
Merging watchdog/master
Merging proc/proc
Merging bdev/master
Merging dwmw2-iommu/master
Merging cpu_alloc/cpu_alloc
CONFLICT (content): Merge conflict in kernel/lockdep.c
CONFLICT (content): Merge conflict in kernel/module.c
Applying cpu_alloc: merge_fix_1
Merging cputime/cputime
Merging perfmon3/master
Merging osd/linux-next
Merging fatfs/master
Merging quilt/staging
Merging scsi-post-merge/master
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Re: Automated Build Infrastructure
From: Randy Dunlap @ 2008-11-17 5:24 UTC (permalink / raw)
To: linux-next; +Cc: Stephen Rothwell, Richard Holden
In-Reply-To: <4920F951.5080109@oracle.com>
Randy Dunlap wrote:
> Stephen Rothwell wrote:
>> Hi Richard,
>>
>> On Sun, 16 Nov 2008 20:32:39 -0700 Richard Holden <aciddeath@gmail.com> wrote:
>>> Does anyone have any scripts to kick off compilation when Stephen
>>> releases a new linux-next? I've started to plan out my own but wanted
>>> to see if anyone had something first so I don't reinvent the wheel.
>> In case it helps, your most reliable trigger would be the LATEST-IS file
>> in http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/
>> changing. I think Randy Dunlap (cc'd) has some stuff.
>
> Hi,
>
> My scripts are available in
> http://www.xenotime.net/linux/scripts/
>
> The scripts are: grab_kernel (for mainline), grab_next (for -next),
> and get-mmotm (for mmotm). They all work with tarballs and patches,
> not git trees. get-mmotm requires an mainline tree for its patch
> series to be applied to. The 'kcurrent' script tells me what
> linux-next or mmotm applies to:
>
> The latest stable version of the Linux kernel is: 2.6.27.6
> The latest prepatch for the stable Linux kernel tree is: 2.6.28-rc5
> The latest snapshot for the stable Linux kernel tree is: 2.6.28-rc5-git1
> The latest 2.4 version of the Linux kernel is: 2.4.36.9
> The latest prepatch for the 2.4 Linux kernel tree is: 2.4.37-rc2
> The latest 2.2 version of the Linux kernel is: 2.2.26
> The latest prepatch for the 2.2 Linux kernel tree is: 2.2.27-rc2
> The latest -mm patch to the stable Linux kernels is: 2.6.28-rc2-mm1
> mmotm-2008-1114-2050 ... applies to: 2.6.28-rc4
> next-20081114 ... applies to: v2.6.28-rc4
>
> grab_kernel downloads & applies any mainline kernel (except for
> -stable kernels); it knows how to apply -rc & -git patches (zipped).
>
> If you have any questions about them, just ask.
OK, these scripts don't do the automated kickoff part.
For that, I'm using Crucible (crucible.sf.net).
The scripts are all in the subversion repository at sf.net.
--
~Randy
^ permalink raw reply
* Re: Automated Build Infrastructure
From: Randy Dunlap @ 2008-11-17 4:55 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Richard Holden, linux-next
In-Reply-To: <20081117144535.6981ecef.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Richard,
>
> On Sun, 16 Nov 2008 20:32:39 -0700 Richard Holden <aciddeath@gmail.com> wrote:
>> Does anyone have any scripts to kick off compilation when Stephen
>> releases a new linux-next? I've started to plan out my own but wanted
>> to see if anyone had something first so I don't reinvent the wheel.
>
> In case it helps, your most reliable trigger would be the LATEST-IS file
> in http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/
> changing. I think Randy Dunlap (cc'd) has some stuff.
Hi,
My scripts are available in
http://www.xenotime.net/linux/scripts/
The scripts are: grab_kernel (for mainline), grab_next (for -next),
and get-mmotm (for mmotm). They all work with tarballs and patches,
not git trees. get-mmotm requires an mainline tree for its patch
series to be applied to. The 'kcurrent' script tells me what
linux-next or mmotm applies to:
The latest stable version of the Linux kernel is: 2.6.27.6
The latest prepatch for the stable Linux kernel tree is: 2.6.28-rc5
The latest snapshot for the stable Linux kernel tree is: 2.6.28-rc5-git1
The latest 2.4 version of the Linux kernel is: 2.4.36.9
The latest prepatch for the 2.4 Linux kernel tree is: 2.4.37-rc2
The latest 2.2 version of the Linux kernel is: 2.2.26
The latest prepatch for the 2.2 Linux kernel tree is: 2.2.27-rc2
The latest -mm patch to the stable Linux kernels is: 2.6.28-rc2-mm1
mmotm-2008-1114-2050 ... applies to: 2.6.28-rc4
next-20081114 ... applies to: v2.6.28-rc4
grab_kernel downloads & applies any mainline kernel (except for
-stable kernels); it knows how to apply -rc & -git patches (zipped).
If you have any questions about them, just ask.
--
~Randy
^ permalink raw reply
* linux-next: manual merge of the security-testing tree
From: Stephen Rothwell @ 2008-11-17 4:44 UTC (permalink / raw)
To: James Morris; +Cc: linux-next, Jeff Layton, Steve French, David Howells
Hi James,
Today's linux-next merge of the security-testing tree got a conflict in
fs/cifs/misc.c between commit 14fbf50d695207754daeb96270b3027a3821121f
("cifs: reinstate sharing of SMB sessions sans races") from the cifs tree
and commit a001e5b558f25eb1e588522d73ac949b643b7a37 ("CRED: Wrap task
credential accesses in the CIFS filesystem") from the security-testing
tree.
I fixed it up (see below) and can carry it for a short while.
Steve, you should apply the patch from the security-testing (creds) tree
that was sent to you - its dependencies are upstream already.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
2343ec9bd0c5c15a77e7261355dc93a075e8f753
diff --cc fs/cifs/misc.c
index 46c8c7b,ec36410..1913b65
--- a/fs/cifs/misc.c
+++ b/fs/cifs/misc.c
@@@ -343,13 -347,13 +343,13 @@@ header_assemble(struct smb_hdr *buffer
/* BB Add support for establishing new tCon and SMB Session */
/* with userid/password pairs found on the smb session */
/* for other target tcp/ip addresses BB */
- if (current->fsuid != treeCon->ses->linux_uid) {
+ if (current_fsuid() != treeCon->ses->linux_uid) {
cFYI(1, ("Multiuser mode and UID "
"did not match tcon uid"));
- read_lock(&GlobalSMBSeslock);
- list_for_each(temp_item, &GlobalSMBSessionList) {
- ses = list_entry(temp_item, struct cifsSesInfo, cifsSessionList);
+ read_lock(&cifs_tcp_ses_lock);
+ list_for_each(temp_item, &treeCon->ses->server->smb_ses_list) {
+ ses = list_entry(temp_item, struct cifsSesInfo, smb_ses_list);
- if (ses->linux_uid == current->fsuid) {
+ if (ses->linux_uid == current_fsuid()) {
if (ses->server == treeCon->ses->server) {
cFYI(1, ("found matching uid substitute right smb_uid"));
buffer->Uid = ses->Suid;
^ permalink raw reply
* Re: Automated Build Infrastructure
From: Stephen Rothwell @ 2008-11-17 3:45 UTC (permalink / raw)
To: Richard Holden; +Cc: linux-next, Randy Dunlap
In-Reply-To: <A938C8A5-205C-4DBF-A242-3966757C02E6@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
Hi Richard,
On Sun, 16 Nov 2008 20:32:39 -0700 Richard Holden <aciddeath@gmail.com> wrote:
>
> Does anyone have any scripts to kick off compilation when Stephen
> releases a new linux-next? I've started to plan out my own but wanted
> to see if anyone had something first so I don't reinvent the wheel.
In case it helps, your most reliable trigger would be the LATEST-IS file
in http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/
changing. I think Randy Dunlap (cc'd) has some stuff.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Automated Build Infrastructure
From: Richard Holden @ 2008-11-17 3:32 UTC (permalink / raw)
To: linux-next
Does anyone have any scripts to kick off compilation when Stephen
releases a new linux-next? I've started to plan out my own but wanted
to see if anyone had something first so I don't reinvent the wheel.
-Richard Holden
^ permalink raw reply
* Re: linux-next: manual merge of the rr tree
From: David Miller @ 2008-11-17 2:57 UTC (permalink / raw)
To: rusty; +Cc: sfr, linux-next, wangchen, markmc
In-Reply-To: <200811160902.53029.rusty@rustcorp.com.au>
From: Rusty Russell <rusty@rustcorp.com.au>
Date: Sun, 16 Nov 2008 09:02:52 +1030
> They missed 2.6.28, they're 2.6.29 material. I've fixed them with s/dev-
> >priv/netdev_priv(dev)/, and will send them to netdev now.
I haven't seen them posted yet, so could you please clarify you're
definition of "now"? :-)
^ permalink raw reply
* linux-next: manual merge of the cifs tree
From: Stephen Rothwell @ 2008-11-17 2:42 UTC (permalink / raw)
To: Steve French, linux-cifs-client; +Cc: linux-next, Harvey Harrison, Jeff Layton
Hi Steve,
Today's linux-next merge of the cifs tree got a conflict in
fs/cifs/connect.c between commit be859405487324ed548f1ba11dc949b8230ab991
("fs: replace NIPQUAD()") from the net tree and commit
14fbf50d695207754daeb96270b3027a3821121f ("cifs: reinstate sharing of SMB
sessions sans races") from the cifs tree.
I have fixed it up (see below) and can carry it as necessary.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
diff --cc fs/cifs/connect.c
index 2df8e6d,a3dc0d7..0000000
--- a/fs/cifs/connect.c
+++ b/fs/cifs/connect.c
@@@ -2078,43 -2176,44 +2176,44 @@@ cifs_mount(struct super_block *sb, stru
} else if (!rc) {
cFYI(1, ("Existing smb sess not found"));
pSesInfo = sesInfoAlloc();
- if (pSesInfo == NULL)
+ if (pSesInfo == NULL) {
rc = -ENOMEM;
- else {
- pSesInfo->server = srvTcp;
- sprintf(pSesInfo->serverName, "%pI4",
- &sin_server.sin_addr.s_addr);
- }
+ goto mount_fail_check;
+ }
+
+ /* new SMB session uses our srvTcp ref */
+ pSesInfo->server = srvTcp;
- sprintf(pSesInfo->serverName, "%u.%u.%u.%u",
- NIPQUAD(sin_server->sin_addr.s_addr));
++ sprintf(pSesInfo->serverName, "%pI4",
++ &sin_server->sin_addr.s_addr);
+
+ write_lock(&cifs_tcp_ses_lock);
+ list_add(&pSesInfo->smb_ses_list, &srvTcp->smb_ses_list);
+ write_unlock(&cifs_tcp_ses_lock);
+
+ /* volume_info.password freed at unmount */
+ if (volume_info.password) {
+ pSesInfo->password = volume_info.password;
+ /* set to NULL to prevent freeing on exit */
+ volume_info.password = NULL;
+ }
+ if (volume_info.username)
+ strncpy(pSesInfo->userName, volume_info.username,
+ MAX_USERNAME_SIZE);
+ if (volume_info.domainname) {
+ int len = strlen(volume_info.domainname);
+ pSesInfo->domainName = kmalloc(len + 1, GFP_KERNEL);
+ if (pSesInfo->domainName)
+ strcpy(pSesInfo->domainName,
+ volume_info.domainname);
+ }
+ pSesInfo->linux_uid = volume_info.linux_uid;
+ pSesInfo->overrideSecFlg = volume_info.secFlg;
+ down(&pSesInfo->sesSem);
- if (!rc) {
- /* volume_info.password freed at unmount */
- if (volume_info.password) {
- pSesInfo->password = volume_info.password;
- /* set to NULL to prevent freeing on exit */
- volume_info.password = NULL;
- }
- if (volume_info.username)
- strncpy(pSesInfo->userName,
- volume_info.username,
- MAX_USERNAME_SIZE);
- if (volume_info.domainname) {
- int len = strlen(volume_info.domainname);
- pSesInfo->domainName =
- kmalloc(len + 1, GFP_KERNEL);
- if (pSesInfo->domainName)
- strcpy(pSesInfo->domainName,
- volume_info.domainname);
- }
- pSesInfo->linux_uid = volume_info.linux_uid;
- pSesInfo->overrideSecFlg = volume_info.secFlg;
- down(&pSesInfo->sesSem);
- /* BB FIXME need to pass vol->secFlgs BB */
- rc = cifs_setup_session(xid, pSesInfo,
- cifs_sb->local_nls);
- up(&pSesInfo->sesSem);
- if (!rc)
- atomic_inc(&srvTcp->socketUseCount);
- }
+ /* BB FIXME need to pass vol->secFlgs BB */
+ rc = cifs_setup_session(xid, pSesInfo,
+ cifs_sb->local_nls);
+ up(&pSesInfo->sesSem);
}
/* search for existing tcon to this server share */
^ permalink raw reply
* linux-next: sh tree build warning
From: Stephen Rothwell @ 2008-11-16 23:34 UTC (permalink / raw)
To: Paul Mundt; +Cc: linux-next, Magnus Damm
[-- Attachment #1: Type: text/plain, Size: 602 bytes --]
Hi Paul,
Today's linux-next build (x86_64 allmodconfig) produced these warning:
drivers/usb/gadget/m66592-udc.c: In function 'm66592_probe':
drivers/usb/gadget/m66592-udc.c:1672: warning: label 'clean_up2' defined but not used
drivers/usb/host/r8a66597-hcd.c: In function 'r8a66597_probe':
drivers/usb/host/r8a66597-hcd.c:2401: warning: label 'clean_up2' defined but not used
Added by commit 985fc7c81c7852f2e104c71cbe913ace683c9e6a ("sh: sh_mobile
usbf clock framework support").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Re: linux-next: next-20081114 build failure
From: David Miller @ 2008-11-16 20:42 UTC (permalink / raw)
To: sfr; +Cc: linux-next, wangchen
In-Reply-To: <20081116223612.02c1c06f.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Sun, 16 Nov 2008 22:36:12 +1100
> Today's linux-next build (mips allmodconfig) failed like this:
>
> drivers/net/dm9000.c:1450: error: expected ')' before ';' token
> drivers/net/dm9000.c:1455: error: expected ';' before '}' token
I just checked the following fix into net-next-2.6
Let me know if it doesn't work
dm9000: Fix build error.
Reported by Stephen Rothwell:
drivers/net/dm9000.c:1450: error: expected ')' before ';' token
drivers/net/dm9000.c:1455: error: expected ';' before '}' token
Signed-off-by: David S. Miller <davem@davemloft.net>
---
drivers/net/dm9000.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/net/dm9000.c b/drivers/net/dm9000.c
index 0d9a217..bcf9291 100644
--- a/drivers/net/dm9000.c
+++ b/drivers/net/dm9000.c
@@ -1447,7 +1447,7 @@ dm9000_drv_remove(struct platform_device *pdev)
platform_set_drvdata(pdev, NULL);
unregister_netdev(ndev);
- dm9000_release_board(pdev, (board_info_t *) netdev_priv(ndev);
+ dm9000_release_board(pdev, (board_info_t *) netdev_priv(ndev));
free_netdev(ndev); /* free device structure */
dev_dbg(&pdev->dev, "released and freed device\n");
--
1.5.6.5
^ permalink raw reply related
* Re: linux-next: osd tree build failure
From: Stephen Rothwell @ 2008-11-16 12:21 UTC (permalink / raw)
To: Boaz Harrosh; +Cc: linux-next
In-Reply-To: <491FF27A.6090400@panasas.com>
[-- Attachment #1: Type: text/plain, Size: 432 bytes --]
Hi Boaz,
On Sun, 16 Nov 2008 12:14:18 +0200 Boaz Harrosh <bharrosh@panasas.com> wrote:
>
> Hi Stephen, I'm so sorry. I accidentally pushed the wrong branch.
That would explain it.
> (Anything left to do by hand is an error to happen)
Yes, automate much as possible.
> I have fix that just now.
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* linux-next: parisc build failure
From: Stephen Rothwell @ 2008-11-16 12:13 UTC (permalink / raw)
To: Kyle McMartin, linux-parisc; +Cc: linux-next, LKML, Alan Cox
[-- Attachment #1: Type: text/plain, Size: 1336 bytes --]
Hi Kyle,
Today's linux-next build (parisc allmodconfig) failed like this:
In file included from drivers/serial/mux.c:38:
include/linux/serial_core.h: In function 'uart_handle_sysrq_char':
include/linux/serial_core.h:450: error: 'struct uart_port' has no member named 'sysrq'
include/linux/serial_core.h:451: error: 'struct uart_port' has no member named 'sysrq'
include/linux/serial_core.h:451: error: 'struct uart_port' has no member named 'sysrq'
include/linux/serial_core.h:453: error: 'struct uart_port' has no member named 'sysrq'
include/linux/serial_core.h:456: error: 'struct uart_port' has no member named 'sysrq'
include/linux/serial_core.h:473: error: 'struct uart_port' has no member named 'sysrq'
include/linux/serial_core.h:474: error: 'struct uart_port' has no member named 'sysrq'
include/linux/serial_core.h:477: error: 'struct uart_port' has no member named 'sysrq'
This is happening in mainline as well. In fact, this has been happening
back as far as I have results (Aug 27). The sysrq element of struct
uart_port is dependent on CONFIG_SERIAL_CORE_CONSOLE while the references
failing above are dependent on SUPPORT_SYSRQ which is defined if
CONFIG_MAGIC_SYSRQ is defined in mux.c.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* Re: linux-next: next-20081114 build failure
From: David Howells @ 2008-11-16 11:43 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: dhowells, James Morris, linux-next
In-Reply-To: <20081116223008.4772920e.sfr@canb.auug.org.au>
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Today's linux-next build (mips defconfig) failed like this:
>
> fs/nfsctl.c:45: error: implicit declaration of function 'current_cred'
>
> This is why you need explicit includes ...
Oops. I really need to cull the number of creds trees I've got. I didn't
apply your patches to all of them.
David
^ permalink raw reply
* linux-next: next-20081114 build failure
From: Stephen Rothwell @ 2008-11-16 11:36 UTC (permalink / raw)
To: David S. Miller; +Cc: linux-next, Wang Chen
[-- Attachment #1: Type: text/plain, Size: 486 bytes --]
Hi Dave,
Today's linux-next build (mips allmodconfig) failed like this:
drivers/net/dm9000.c:1450: error: expected ')' before ';' token
drivers/net/dm9000.c:1455: error: expected ';' before '}' token
Caused by commit 4cf1653aa90c6320dc8032443b5e322820aa28b1 ("netdevice:
safe convert to netdev_priv() #part-2") which left a closing ')' off one
of the conversions.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
* linux-next: next-20081114 build failure
From: Stephen Rothwell @ 2008-11-16 11:30 UTC (permalink / raw)
To: James Morris; +Cc: linux-next, David Howells
[-- Attachment #1: Type: text/plain, Size: 308 bytes --]
Hi James, David,
Today's linux-next build (mips defconfig) failed like this:
fs/nfsctl.c:45: error: implicit declaration of function 'current_cred'
This is why you need explicit includes ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox