* Re: linux-next: unable to fetch dlm tree
From: David Teigland @ 2009-10-13 15:13 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, LKML
In-Reply-To: <20091013100423.6afbb070.sfr@canb.auug.org.au>
On Tue, Oct 13, 2009 at 10:04:23AM +1100, Stephen Rothwell wrote:
> Hi David,
>
> Fetching the dlm tree for today's linux-next gives me
>
> fatal: Couldn't find remote ref refs/heads/next
>
> and, indeed, "git ls-remote" shows no "next" branch.
>
> I will use the dlm tree from yesterday.
Oops, sorry about that, I've put it back.
Dave
^ permalink raw reply
* Re: [PATCH] this_cpu: Use this_cpu_xx in trace_functions_graph.c
From: Tejun Heo @ 2009-10-13 14:57 UTC (permalink / raw)
To: Christoph Lameter
Cc: Stephen Rothwell, Rusty Russell, Ingo Molnar, linux-next,
linux-kernel
In-Reply-To: <alpine.DEB.1.10.0910131043460.8088@gentwo.org>
Christoph Lameter wrote:
> On Tue, 13 Oct 2009, Tejun Heo wrote:
>
>> Oh... one question tho. I used __this_cpu_*() as other conversions
>> but I think we should be using the version without the underscores.
>> The relationship between get_cpu_var() and __get_cpu_var() is
>> different from the one between this_cpu_*() and __this_cpu_*().
>
> For operations like inc/add/dec/sub you need to use the version with __
> otherwise the arches that do not support these operations will have to
> generate useless expensive code that disables / reenables preempt.
>
> For this_cpu_ptr / __this_cpu_ptr it does not matter. this_cpu_ptr gives
> you additional checks.
Yes, you're right. The naming scheme in percpu sucks really hard.
The subtle differences among [__]get_cpu_var(), [__]this_cpu_ptr() and
other this_cpu ops. Arghhhhhh.......
--
tejun
^ permalink raw reply
* Re: [PATCH] this_cpu: Use this_cpu_xx in trace_functions_graph.c
From: Tejun Heo @ 2009-10-13 14:47 UTC (permalink / raw)
To: Christoph Lameter
Cc: Stephen Rothwell, Rusty Russell, Ingo Molnar, linux-next,
linux-kernel
In-Reply-To: <alpine.DEB.1.10.0910131035450.11413@gentwo.org>
Christoph Lameter wrote:
> On Tue, 13 Oct 2009, Tejun Heo wrote:
>
>> ftrace_cpu_disabled usage in trace_functions_graph.c were left out
>> during this_cpu_xx conversion in commit 9288f99a causing compile
>> failure. Convert them.
>
> Thanks.
>
> Reviewed-by: Christoph Lameter <cl@linux-foundation.org>
Oh... one question tho. I used __this_cpu_*() as other conversions
but I think we should be using the version without the underscores.
The relationship between get_cpu_var() and __get_cpu_var() is
different from the one between this_cpu_*() and __this_cpu_*().
Thanks.
--
tejun
^ permalink raw reply
* Re: [PATCH] this_cpu: Use this_cpu_xx in trace_functions_graph.c
From: Christoph Lameter @ 2009-10-13 14:45 UTC (permalink / raw)
To: Tejun Heo
Cc: Stephen Rothwell, Rusty Russell, Ingo Molnar, linux-next,
linux-kernel
In-Reply-To: <4AD49317.6080503@kernel.org>
On Tue, 13 Oct 2009, Tejun Heo wrote:
> Oh... one question tho. I used __this_cpu_*() as other conversions
> but I think we should be using the version without the underscores.
> The relationship between get_cpu_var() and __get_cpu_var() is
> different from the one between this_cpu_*() and __this_cpu_*().
For operations like inc/add/dec/sub you need to use the version with __
otherwise the arches that do not support these operations will have to
generate useless expensive code that disables / reenables preempt.
For this_cpu_ptr / __this_cpu_ptr it does not matter. this_cpu_ptr gives
you additional checks.
^ permalink raw reply
* Re: [PATCH] this_cpu: Use this_cpu_xx in trace_functions_graph.c
From: Christoph Lameter @ 2009-10-13 14:36 UTC (permalink / raw)
To: Tejun Heo
Cc: Stephen Rothwell, Rusty Russell, Ingo Molnar, linux-next,
linux-kernel
In-Reply-To: <4AD48EC4.8040701@kernel.org>
On Tue, 13 Oct 2009, Tejun Heo wrote:
> ftrace_cpu_disabled usage in trace_functions_graph.c were left out
> during this_cpu_xx conversion in commit 9288f99a causing compile
> failure. Convert them.
Thanks.
Reviewed-by: Christoph Lameter <cl@linux-foundation.org>
^ permalink raw reply
* [PATCH] this_cpu: Use this_cpu_xx in trace_functions_graph.c
From: Tejun Heo @ 2009-10-13 14:29 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Rusty Russell, Christoph Lameter, Ingo Molnar, linux-next,
linux-kernel
In-Reply-To: <20091013144812.bdb376aa.sfr@canb.auug.org.au>
ftrace_cpu_disabled usage in trace_functions_graph.c were left out
during this_cpu_xx conversion in commit 9288f99a causing compile
failure. Convert them.
Signed-off-by: Tejun Heo <tj@kernel.org>
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Christoph Lameter <cl@linux-foundation.org>
---
This patch has been committed to percpu#for-next. Thanks.
kernel/trace/trace_functions_graph.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/kernel/trace/trace_functions_graph.c b/kernel/trace/trace_functions_graph.c
index 45e6c01..90a6daa 100644
--- a/kernel/trace/trace_functions_graph.c
+++ b/kernel/trace/trace_functions_graph.c
@@ -176,7 +176,7 @@ static int __trace_graph_entry(struct trace_array *tr,
struct ring_buffer *buffer = tr->buffer;
struct ftrace_graph_ent_entry *entry;
- if (unlikely(local_read(&__get_cpu_var(ftrace_cpu_disabled))))
+ if (unlikely(__this_cpu_read(per_cpu_var(ftrace_cpu_disabled))))
return 0;
event = trace_buffer_lock_reserve(buffer, TRACE_GRAPH_ENT,
@@ -240,7 +240,7 @@ static void __trace_graph_return(struct trace_array *tr,
struct ring_buffer *buffer = tr->buffer;
struct ftrace_graph_ret_entry *entry;
- if (unlikely(local_read(&__get_cpu_var(ftrace_cpu_disabled))))
+ if (unlikely(__this_cpu_read(per_cpu_var(ftrace_cpu_disabled))))
return;
event = trace_buffer_lock_reserve(buffer, TRACE_GRAPH_RET,
--
1.6.4.2
^ permalink raw reply related
* Re: linux-next: manual merge of the i7core_edac tree with Linus' tree
From: Stephen Rothwell @ 2009-10-13 11:53 UTC (permalink / raw)
To: Mauro Carvalho Chehab; +Cc: linux-next, linux-kernel, Ingo Molnar
In-Reply-To: <1209036982.100421255434636304.JavaMail.root@zmail05.collab.prod.int.phx2.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
Hi Mauro,
On Tue, 13 Oct 2009 07:50:36 -0400 (EDT) Mauro Carvalho Chehab <mchehab@redhat.com> wrote:
>
> Thanks for letting me know. I've rebased it fixing the merge conflict. For now,
> I just removed the call to edac_mce_parse() for Uncorrected Errors, since I'll
> eventually replace that part of the code with something better.
>
> You should now be able to merge it without merging conflicts.
OK, thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* Re: linux-next: manual merge of the i7core_edac tree with Linus' tree
From: Mauro Carvalho Chehab @ 2009-10-13 11:50 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Ingo Molnar
In-Reply-To: <20091012142328.710881fe.sfr@canb.auug.org.au>
----- "Stephen Rothwell" <sfr@canb.auug.org.au> escreveu:
> Hi Mauro,
>
> Today's linux-next merge of the i7core_edac tree got a conflict in
> arch/x86/kernel/cpu/mcheck/mce.c between commit
> f436f8bb73138bc74eb1c6527723e00988ad8a8a ("x86: EDAC: MCE: Fix MCE
> decoding callback logic") from Linus' tree and commit
> 699a7dbe1ffdf4b25c1475e45590b181c3e23087 ("edac_mce: Add an interface
> driver to report mce errors via edac") from the i7core_edac tree.
>
> I don't know how to resolve these two commits so I have dropped the
> i7core_edac tree for today.
Thanks for letting me know. I've rebased it fixing the merge conflict. For now,
I just removed the call to edac_mce_parse() for Uncorrected Errors, since I'll
eventually replace that part of the code with something better.
You should now be able to merge it without merging conflicts.
Cheers,
Mauro.
^ permalink raw reply
* Re: [BUILD-FAILURE] next-20091013 - s390x build breaks at mm/fault with !CONFIG_S390_EXEC_PROTECT
From: Kamalesh Babulal @ 2009-10-13 10:57 UTC (permalink / raw)
To: Martin Schwidefsky
Cc: linux-next, LKML, Stephen Rothwell, heiko.carstens, linux-s390
In-Reply-To: <20091013123335.6d6820b3@mschwide.boeblingen.de.ibm.com>
* Martin Schwidefsky <schwidefsky@de.ibm.com> [2009-10-13 12:33:35]:
> On Tue, 13 Oct 2009 15:36:48 +0530
> Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
>
> > next-20091013 randconfig build breaks on s390, with
> > CONFIG_S390_EXEC_PROTECT=y
> >
> > arch/s390/mm/fault.c: In function 'signal_return':
> > arch/s390/mm/fault.c:221: error: implicit declaration of function 'is_compat_task'
> > make[1]: *** [arch/s390/mm/fault.o] Error 1
> >
> > is_compat_task is defined at asm/compat.h, including the
> > header, helps
>
> I'll merge that info "[PATCH] fault handler performance optimization" if you
> don't mind.
Please feel free to merge it.
>
> --
> blue skies,
> Martin.
>
> "Reality continues to ruin my life." - Calvin.
>
Kamalesh
^ permalink raw reply
* Re: [BUILD-FAILURE] next-20091013 - s390x build breaks at mm/fault with !CONFIG_S390_EXEC_PROTECT
From: Martin Schwidefsky @ 2009-10-13 10:33 UTC (permalink / raw)
To: Kamalesh Babulal
Cc: linux-next, LKML, Stephen Rothwell, heiko.carstens, linux-s390
In-Reply-To: <20091013100648.GA7542@linux.vnet.ibm.com>
On Tue, 13 Oct 2009 15:36:48 +0530
Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:
> next-20091013 randconfig build breaks on s390, with
> CONFIG_S390_EXEC_PROTECT=y
>
> arch/s390/mm/fault.c: In function 'signal_return':
> arch/s390/mm/fault.c:221: error: implicit declaration of function 'is_compat_task'
> make[1]: *** [arch/s390/mm/fault.o] Error 1
>
> is_compat_task is defined at asm/compat.h, including the
> header, helps
I'll merge that info "[PATCH] fault handler performance optimization" if you
don't mind.
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
^ permalink raw reply
* [BUILD-FAILURE] next-20091013 - s390x build breaks at mm/fault with !CONFIG_S390_EXEC_PROTECT
From: Kamalesh Babulal @ 2009-10-13 10:06 UTC (permalink / raw)
To: schwidefsky
Cc: linux-next, LKML, Stephen Rothwell, heiko.carstens, linux-s390
In-Reply-To: <20091013162312.8b93998b.sfr@canb.auug.org.au>
Hi Martin,
next-20091013 randconfig build breaks on s390, with
CONFIG_S390_EXEC_PROTECT=y
arch/s390/mm/fault.c: In function 'signal_return':
arch/s390/mm/fault.c:221: error: implicit declaration of function 'is_compat_task'
make[1]: *** [arch/s390/mm/fault.o] Error 1
is_compat_task is defined at asm/compat.h, including the
header, helps
Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
--
arch/s390/mm/fault.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/s390/mm/fault.c b/arch/s390/mm/fault.c
index 43b3778..4e73e8b 100644
--- a/arch/s390/mm/fault.c
+++ b/arch/s390/mm/fault.c
@@ -34,6 +34,7 @@
#include <asm/pgtable.h>
#include <asm/s390_ext.h>
#include <asm/mmu_context.h>
+#include <asm/compat.h>
#include "../kernel/entry.h"
#ifndef CONFIG_64BIT
Kamalesh
^ permalink raw reply related
* Re: linux-next: net tree build failure
From: David Miller @ 2009-10-13 6:20 UTC (permalink / raw)
To: mchan; +Cc: sfr, linux-next, linux-kernel, shmulikr
In-Reply-To: <C27F8246C663564A84BB7AB34397724217C978403F@IRVEXCHCCR01.corp.ad.broadcom.com>
From: "Michael Chan" <mchan@broadcom.com>
Date: Mon, 12 Oct 2009 22:14:22 -0700
> I think adding #include <net/ip6_checksum.h> will work. Will send a
> patch right away. Thanks.
Too slow, I already fixed this :-)
^ permalink raw reply
* Re: linux-next: net tree build failure
From: David Miller @ 2009-10-13 6:19 UTC (permalink / raw)
To: sfr; +Cc: linux-next, linux-kernel, mchan, shmulikr
In-Reply-To: <20091013153308.af56910a.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Tue, 13 Oct 2009 15:33:08 +1100
> Today's linux-next build (powerpc allyesconfig) failed like this:
>
> drivers/net/cnic.c: In function 'cnic_init_storm_conn_bufs':
> drivers/net/cnic.c:1757: error: implicit declaration of functi
> on 'csum_ipv6_magic'
>
> Caused by commit 71034ba845c9ff219373066f904286c0b7506922 ("cnic: Add
> main functions to support bnx2x devices") which I have reverted for today.
It's because x86 and sparc64 seem to get the ipv6 checksum header
implicitly somehow.
I'll fix this as follows, thanks for the report Stephen:
cnic: Need to include net/ip6_checksum.h
drivers/net/cnic.c: In function 'cnic_init_storm_conn_bufs':
drivers/net/cnic.c:1757: error: implicit declaration of function 'csum_ipv6_magic'
Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
Signed-off-by: David S. Miller <davem@davemloft.net>
---
drivers/net/cnic.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/net/cnic.c b/drivers/net/cnic.c
index 6e7af7b..333b1d1 100644
--- a/drivers/net/cnic.c
+++ b/drivers/net/cnic.c
@@ -33,6 +33,7 @@
#include <net/route.h>
#include <net/ipv6.h>
#include <net/ip6_route.h>
+#include <net/ip6_checksum.h>
#include <scsi/iscsi_if.h>
#include "cnic_if.h"
--
1.6.4.4
^ permalink raw reply related
* linux-next: Tree for October 13
From: Stephen Rothwell @ 2009-10-13 5:23 UTC (permalink / raw)
To: linux-next; +Cc: LKML
[-- Attachment #1: Type: text/plain, Size: 7467 bytes --]
Changes since 20091012:
Dropped tree: i7core_edac (difficult merge conflict)
My fixes tree contains a build fix for powerpc/kvm.
The net tree gained a build failure for which I reverted a commit.
The sound tree lost its build failure.
The mfd tree still lost its build failure.
The voltage tree lost its build failure.
The suspend tree lost its build failure.
The percpu tree gained a build failure so I used the version from
next-20091012.
The tty tree gained a build failure for which I reverted a commit.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/v2.6/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 (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc
and sparc64 defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.
Below is a summary of the state of the merge.
We are up to 143 trees (counting Linus' and 22 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 fixes/fixes
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging sparc-current/master
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sound-current/for-linus
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/master
Merging quilt/driver-core.current
Merging quilt/tty.current
Merging quilt/usb.current
Merging quilt/staging.current
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-linus
Merging audit-current/for-linus
Merging crypto-current/master
Merging ide-curent/master
Merging dwmw2/master
Merging arm/devel
Merging davinci/for-next
Merging pxa/for-next
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
CONFLICT (content): Merge conflict in drivers/rtc/Kconfig
Merging m68knommu/for-next
Merging microblaze/next
Merging mips/mips-for-linux-next
Merging parisc/next
Merging powerpc/next
Merging 4xx/next
Merging galak/next
Merging s390/features
Merging sh/master
Merging sparc/master
Merging xtensa/master
Merging cifs/master
Merging configfs/linux-next
Merging ecryptfs/next
CONFLICT (content): Merge conflict in fs/ecryptfs/Kconfig
Merging ext3/for_next
Merging ext4/next
Merging fatfs/master
Merging fuse/for-next
Merging gfs2/master
Merging jfs/next
Merging nfs/linux-next
Merging nfsd/nfsd-next
Merging nilfs2/for-next
Merging ocfs2/linux-next
Merging squashfs/master
Merging udf/for_next
Merging v9fs/for-next
Merging ubifs/linux-next
Merging xfs/master
Merging reiserfs-bkl/reiserfs/kill-bkl
Merging vfs/for-next
Merging pci/linux-next
Merging hid/for-next
Merging quilt/i2c
Merging quilt/jdelvare-hwmon
Merging quilt/kernel-doc
Merging v4l-dvb/master
Merging quota/for_next
Merging kbuild/master
Merging kconfig/for-next
Merging ide/master
Merging libata/NEXT
Merging infiniband/for-next
Merging acpi/test
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/linux-next
Merging dlm/next
Merging scsi/master
Merging async_tx/next
Merging net/master
Merging wireless/master
Merging mtd/master
Merging crypto/master
Merging sound/for-next
Merging cpufreq/next
Merging quilt/rr
Merging mmc/next
Merging tmio-mmc/linux-next
Merging input/next
Merging lsm/for-next
Merging block/for-next
Merging quilt/device-mapper
Merging embedded/master
Merging firmware/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 mfd/for-next
Merging hdlc/hdlc-next
Merging drm/drm-next
Merging voltage/for-next
CONFLICT (content): Merge conflict in drivers/mfd/Kconfig
CONFLICT (content): Merge conflict in drivers/mfd/Makefile
Merging security-testing/next
Merging lblnet/master
Merging agp/agp-next
Merging uwb/for-upstream
Merging watchdog/master
Merging bdev/master
Merging dwmw2-iommu/master
Merging cputime/cputime
Merging osd/linux-next
Merging jc_docs/docs-next
Merging nommu/master
Merging trivial/for-next
Merging audit/for-next
Merging omap/for-next
Merging quilt/aoe
Merging suspend/linux-next
Merging bluetooth/master
Merging fsnotify/for-next
Merging irda/for-next
Merging hwlat/for-linus
Merging drbd/for-jens
CONFLICT (add/add): Merge conflict in drivers/block/drbd/Kconfig
CONFLICT (add/add): Merge conflict in drivers/block/drbd/Makefile
CONFLICT (add/add): Merge conflict in drivers/block/drbd/drbd_actlog.c
CONFLICT (add/add): Merge conflict in drivers/block/drbd/drbd_int.h
CONFLICT (add/add): Merge conflict in drivers/block/drbd/drbd_main.c
CONFLICT (add/add): Merge conflict in drivers/block/drbd/drbd_nl.c
CONFLICT (add/add): Merge conflict in drivers/block/drbd/drbd_receiver.c
CONFLICT (add/add): Merge conflict in drivers/block/drbd/drbd_req.c
CONFLICT (add/add): Merge conflict in drivers/block/drbd/drbd_worker.c
CONFLICT (add/add): Merge conflict in include/linux/drbd.h
Merging catalin/for-next
Merging alacrity/linux-next
CONFLICT (content): Merge conflict in lib/Kconfig
Merging i7core_edac/linux_next
CONFLICT (content): Merge conflict in arch/x86/kernel/cpu/mcheck/mce.c
CONFLICT (content): Merge conflict in drivers/edac/Makefile
$ git reset --hard
Merging tip/auto-latest
Merging oprofile/for-next
Merging percpu/for-next
$ git reset --hard HEAD^
Merging refs/next/20091012/percpu
Merging sfi/sfi-test
Merging asm-generic/next
Merging hwpoison/hwpoison
Merging quilt/driver-core
Merging quilt/tty
Merging quilt/usb
Merging quilt/staging
[master fe79f27] Revert "tty: esp: remove broken driver"
Merging scsi-post-merge/master
[master d8fba4d] Revert "cnic: Add main functions to support bnx2x devices."
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* Re: linux-next: net tree build failure
From: Michael Chan @ 2009-10-13 5:14 UTC (permalink / raw)
To: 'Stephen Rothwell', David S. Miller
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Shmulik Ravid - Rabinovitz
In-Reply-To: <20091013153308.af56910a.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Dave,
>
> Today's linux-next build (powerpc allyesconfig) failed like this:
>
> drivers/net/cnic.c: In function 'cnic_init_storm_conn_bufs':
> drivers/net/cnic.c:1757: error: implicit declaration of functi
> on 'csum_ipv6_magic'
>
> Caused by commit 71034ba845c9ff219373066f904286c0b7506922 ("cnic: Add
> main functions to support bnx2x devices") which I have
> reverted for today.
>
I think adding #include <net/ip6_checksum.h> will work. Will send a
patch right away. Thanks.
^ permalink raw reply
* linux-next: net tree build failure
From: Stephen Rothwell @ 2009-10-13 4:33 UTC (permalink / raw)
To: David S. Miller
Cc: linux-next, linux-kernel, Michael Chan,
Shmulik Ravid - Rabinovitz
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
Hi Dave,
Today's linux-next build (powerpc allyesconfig) failed like this:
drivers/net/cnic.c: In function 'cnic_init_storm_conn_bufs':
drivers/net/cnic.c:1757: error: implicit declaration of functi
on 'csum_ipv6_magic'
Caused by commit 71034ba845c9ff219373066f904286c0b7506922 ("cnic: Add
main functions to support bnx2x devices") which I have reverted for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* Re: linux-next: staging tree build failure
From: Stephen Rothwell @ 2009-10-13 4:21 UTC (permalink / raw)
To: Greg KH; +Cc: linux-next, linux-kernel, Alan Cox
In-Reply-To: <20091013150753.f738576e.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 136 bytes --]
Actually the tty tree ...
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* linux-next: staging tree build failure
From: Stephen Rothwell @ 2009-10-13 4:07 UTC (permalink / raw)
To: Greg KH; +Cc: linux-next, linux-kernel, Alan Cox
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi Greg,
Today's linux-next build (x86_64 allmodconfig) failed like this:
make[4]: *** No rule to make target `include/linux/hayesesp.h', needed by `usr/include/linux/.install'. Stop.
Caused by commit a724aa0a5ad2b3c6b5ee48e79a09e9fbc5cf3ec9 ("tty: esp:
remove broken driver") which I have reverted for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* linux-next: percpu tree build failure
From: Stephen Rothwell @ 2009-10-13 3:48 UTC (permalink / raw)
To: Tejun Heo, Rusty Russell, Christoph Lameter, Ingo Molnar
Cc: linux-next, linux-kernel
[-- Attachment #1: Type: text/plain, Size: 737 bytes --]
Hi all,
Today's linux-next build (x86_64 allmodconfig) failed like this:
kernel/trace/trace_functions_graph.c: In function '__trace_graph_entry':
kernel/trace/trace_functions_graph.c:179: error: request for member 'a' in something not a structure or union
kernel/trace/trace_functions_graph.c: In function '__trace_graph_return':
kernel/trace/trace_functions_graph.c:243: error: request for member 'a' in something not a structure or union
Caused by commit 9288f99aa52d90a5b82573c4b769c97c55af2f56 ("this_cpu: Use
this_cpu_xx for ftrace").
I have used the version of the percpu tree from next-20091012 for today.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* linux-next: tip tree build warning
From: Stephen Rothwell @ 2009-10-13 3:42 UTC (permalink / raw)
To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
Cc: linux-next, linux-kernel, Stephane Eranian
[-- Attachment #1: Type: text/plain, Size: 503 bytes --]
Hi all,
Today's linux-next build (x86_64 allmodconfig) produced this warning:
arch/x86/kernel/cpu/perf_event.c: In function 'intel_get_event_idx':
arch/x86/kernel/cpu/perf_event.c:1445: warning: 'event_constraint' is used uninitialized in this function
Introduced by commit b690081d4d3f6a23541493f1682835c3cd5c54a1
("perf_events: Add event constraints support for Intel processors").
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* Re: linux-next: suspend tree build failure
From: Stephen Rothwell @ 2009-10-13 0:58 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: linux-next, linux-kernel
In-Reply-To: <200910130044.12494.rjw@sisk.pl>
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
Hi Rafael,
On Tue, 13 Oct 2009 00:44:12 +0200 "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
>
> Thanks Stephen, I added your patch below to the suspend-2.6 tree.
Thanks.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* linux-next: unable to fetch jc_docs tree
From: Stephen Rothwell @ 2009-10-12 23:14 UTC (permalink / raw)
To: Jonathan Corbet; +Cc: linux-next, LKML
[-- Attachment #1: Type: text/plain, Size: 332 bytes --]
Hi Jonathan,
Fetching the jc_docs tree today gives me
git.lwn.net[0: 206.168.112.25]: errno=Connection timed out
fatal: unable to connect a socket (Connection timed out)
I will use the jc_docs tree from yesterday.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* linux-next: unable to fetch dlm tree
From: Stephen Rothwell @ 2009-10-12 23:04 UTC (permalink / raw)
To: David Teigland; +Cc: linux-next, LKML
[-- Attachment #1: Type: text/plain, Size: 327 bytes --]
Hi David,
Fetching the dlm tree for today's linux-next gives me
fatal: Couldn't find remote ref refs/heads/next
and, indeed, "git ls-remote" shows no "next" branch.
I will use the dlm tree from yesterday.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
^ permalink raw reply
* Re: linux-next: suspend tree build failure
From: Rafael J. Wysocki @ 2009-10-12 22:44 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: linux-next, linux-kernel
In-Reply-To: <20091012140002.10f1f3d1.sfr@canb.auug.org.au>
On Monday 12 October 2009, Stephen Rothwell wrote:
> Hi Rafael,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> drivers/base/power/main.c: In function 'device_pm_wait':
> drivers/base/power/main.c:218: error: 'TASK_UNINTERRUPTIBLE' undeclared (first use in this function)
> drivers/base/power/main.c:218: error: (Each undeclared identifier is reported only once
> drivers/base/power/main.c:218: error: for each function it appears in.)
> drivers/base/power/main.c:218: error: implicit declaration of function 'schedule'
> drivers/base/power/main.c: In function 'dbg_show_time':
> drivers/base/power/main.c:514: error: implicit declaration of function 'task_pid_nr'
> drivers/base/power/main.c: In function '__device_resume_noirq':
> drivers/base/power/main.c:551: error: 'TASK_NORMAL' undeclared (first use in this function)
> drivers/base/power/main.c: In function '__device_resume':
> drivers/base/power/main.c:713: error: 'TASK_NORMAL' undeclared (first use in this function)
> drivers/base/power/main.c: In function '__device_suspend_noirq':
> drivers/base/power/main.c:970: error: 'TASK_NORMAL' undeclared (first use in this function)
> drivers/base/power/main.c: In function '__device_suspend':
> drivers/base/power/main.c:1145: error: 'TASK_NORMAL' undeclared (first use in this function)
>
> Presumably caused by commit d43c36dc6b357fa1806800f18aa30123c747a6d1
> ("headers: remove sched.h from interrupt.h") from Linus' tree.
>
> I have added the following patch for today.
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Mon, 12 Oct 2009 13:48:27 +1100
> Subject: [PATCH] suspend: using TASK_ macros requires sched.h
Thanks Stephen, I added your patch below to the suspend-2.6 tree.
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/base/power/main.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
> index 3b09009..fb1c648 100644
> --- a/drivers/base/power/main.c
> +++ b/drivers/base/power/main.c
> @@ -29,6 +29,7 @@
> #include <linux/async.h>
> #include <linux/completion.h>
> #include <linux/time.h>
> +#include <linux/sched.h>
>
> #include "../base.h"
> #include "power.h"
Best,
Rafael
^ permalink raw reply
* Re: [PATCH -next] thinkpad_acpi: fix build, HOTKEY_POLL is optional
From: Henrique de Moraes Holschuh @ 2009-10-12 15:41 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Randy Dunlap, Stephen Rothwell, lenb, linux-next, LKML
In-Reply-To: <20091012125942.GA25464@elte.hu>
On Mon, 12 Oct 2009, Ingo Molnar wrote:
> * Henrique de Moraes Holschuh <hmh@hmh.eng.br> wrote:
> > On Fri, 09 Oct 2009, Randy Dunlap wrote:
> > > From: Randy Dunlap <randy.dunlap@oracle.com>
> > >
> > > Fix optional part of driver to be built optionally:
> >
> > NAK!
> >
> > This happens because of (linux-next) commit
> > 7f6443f7238a0aa9014b11a0a31ab76825d75cdf
> > "thinkpad-acpi: Fix build on !CONFIG_THINKPAD_ACPI_HOTKEY_POLL" by
> > Ingo.
> >
> > That commit is wrong, it must NOT be applied as explained in the
> > thread starting at http://lkml.org/lkml/2009/9/27/30.
>
> Yep, that was wrong - it should be gone now.
Thank you.
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
^ 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