* [PATCH] clean up of netif_rx_reschedule() changes in drivers
From: Kamalesh Babulal @ 2008-12-29 10:25 UTC (permalink / raw)
To: Stephen Rothwell
Cc: David S. Miller, Neil Horman, linux-next, LKML, Linus, netdev,
ppc-dev
In-Reply-To: <20081229110041.0eca977a.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> [2008-12-29 11:00:41]:
> Hi Dave, Neil,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> drivers/net/ibmveth.c: In function 'ibmveth_poll':
> drivers/net/ibmveth.c:1034: warning: passing argument 1 of 'netif_rx_reschedule' from incompatible pointer type
> drivers/net/ibmveth.c:1034: error: too many arguments to function 'netif_rx_reschedule'
>
> Another miss in commit 908a7a16b852ffd618a9127be8d62432182d81b4 ("net: Remove
> unused netdev arg from some NAPI interfaces").
>
> I have added the following patch for today.
>
> (I wonder how many more there will be? :-()
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/
>
> From: Stephen Rothwell <sfr@canb.auug.org.au>
> Date: Mon, 29 Dec 2008 10:56:00 +1100
> Subject: [PATCH] net: ibmveth NAPI interface cleanup fix
>
> Commit 908a7a16b852ffd618a9127be8d62432182d81b4 ("net: Remove unused
> netdev arg from some NAPI interfaces") missed one spot.
Hi Stephen,
Thanks, the patch fixes the build failure for me.
Tested-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
> Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> ---
> drivers/net/ibmveth.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/ibmveth.c b/drivers/net/ibmveth.c
> index 1f055a9..9bc0f17 100644
> --- a/drivers/net/ibmveth.c
> +++ b/drivers/net/ibmveth.c
> @@ -1031,7 +1031,7 @@ static int ibmveth_poll(struct napi_struct *napi, int budget)
> netif_rx_complete(napi);
>
> if (ibmveth_rxq_pending_buffer(adapter) &&
> - netif_rx_reschedule(netdev, napi)) {
> + netif_rx_reschedule(napi)) {
> lpar_rc = h_vio_signal(adapter->vdev->unit_address,
> VIO_IRQ_DISABLE);
> goto restart_poll;
> --
> 1.6.0.5
I hit similar build failure due to the change in the netif_rx_reschedule()
drivers/net/ehea/ehea_main.c: In function 'ehea_poll':
drivers/net/ehea/ehea_main.c:844: warning: passing argument 1 of 'netif_rx_reschedule' from incompatible pointer type
drivers/net/ehea/ehea_main.c:844: error: too many arguments to function 'netif_rx_reschedule'
make[3]: *** [drivers/net/ehea/ehea_main.o] Error 1
greping through the sources for the changes missed out, we have
./drivers/net/arm/ixp4xx_eth.c:507: netif_rx_reschedule(dev, napi)) {
./drivers/net/arm/ep93xx_eth.c:310: if (more && netif_rx_reschedule(dev, napi))
./drivers/net/wan/ixp4xx_hss.c:657: netif_rx_reschedule(dev, napi)) {
Signed-off-by: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
--
drivers/net/arm/ep93xx_eth.c | 2 +-
drivers/net/arm/ixp4xx_eth.c | 2 +-
drivers/net/wan/ixp4xx_hss.c | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/net/arm/ep93xx_eth.c b/drivers/net/arm/ep93xx_eth.c
index 6ecc600..3ec20cc 100644
--- a/drivers/net/arm/ep93xx_eth.c
+++ b/drivers/net/arm/ep93xx_eth.c
@@ -307,7 +307,7 @@ poll_some_more:
}
spin_unlock_irq(&ep->rx_lock);
- if (more && netif_rx_reschedule(dev, napi))
+ if (more && netif_rx_reschedule(napi))
goto poll_some_more;
}
diff --git a/drivers/net/arm/ixp4xx_eth.c b/drivers/net/arm/ixp4xx_eth.c
index 26af411..5fce1d5 100644
--- a/drivers/net/arm/ixp4xx_eth.c
+++ b/drivers/net/arm/ixp4xx_eth.c
@@ -504,7 +504,7 @@ static int eth_poll(struct napi_struct *napi, int budget)
netif_rx_complete(napi);
qmgr_enable_irq(rxq);
if (!qmgr_stat_empty(rxq) &&
- netif_rx_reschedule(dev, napi)) {
+ netif_rx_reschedule(napi)) {
#if DEBUG_RX
printk(KERN_DEBUG "%s: eth_poll"
" netif_rx_reschedule successed\n",
diff --git a/drivers/net/wan/ixp4xx_hss.c b/drivers/net/wan/ixp4xx_hss.c
index 0c68025..2dc2416 100644
--- a/drivers/net/wan/ixp4xx_hss.c
+++ b/drivers/net/wan/ixp4xx_hss.c
@@ -654,7 +654,7 @@ static int hss_hdlc_poll(struct napi_struct *napi, int budget)
netif_rx_complete(dev, napi);
qmgr_enable_irq(rxq);
if (!qmgr_stat_empty(rxq) &&
- netif_rx_reschedule(dev, napi)) {
+ netif_rx_reschedule(napi)) {
#if DEBUG_RX
printk(KERN_DEBUG "%s: hss_hdlc_poll"
" netif_rx_reschedule succeeded\n",
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
^ permalink raw reply related
* Re: linux-next: timers tree build failure
From: Stephen Rothwell @ 2008-12-29 10:14 UTC (permalink / raw)
To: Ingo Molnar; +Cc: Thomas Gleixner, H. Peter Anvin, linux-next, Takashi Iwai
In-Reply-To: <20081229093125.GA27293@elte.hu>
[-- Attachment #1: Type: text/plain, Size: 283 bytes --]
Hi Ingo,
On Mon, 29 Dec 2008 10:31:25 +0100 Ingo Molnar <mingo@elte.hu> wrote:
>
> yes, trivial oneliner conflict, i pushed out a new auto-timers-next tree.
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
* Re: linux-next: origin tree build failure
From: Aleksey Senin @ 2008-12-29 9:58 UTC (permalink / raw)
To: general@lists.openfabrics.org
Cc: linux-next, LKML, Linus, Stephen Rothwell, Roland Dreier
In-Reply-To: <ada4p0nve4r.fsf@cisco.com>
After another investigation of this problem, I think that proposed
solution is #ifdef as good for a first stage. IPv6 support is mandatory
when we are talking about running linux in some organization. But, of
course, the way how it implemented in IB stack should be changed. So on
the second stage, I'd like drop out these "defines" and at the time of
module initialization obtain addresses of IPv6 functions and in the case
if they are present at the runtime, call them. It should be nice
solution for RMDA_CM and IPoIB modules.
On Sun, 2008-12-28 at 19:44 -0800, Roland Dreier wrote:
> > ERROR: ".ipv6_chk_addr" [drivers/infiniband/core/ib_addr.ko] undefined!
> > ERROR: ".ip6_route_output" [drivers/infiniband/core/ib_addr.ko] undefined!
> >
> > Caused by commit 38617c64bf9a10bf20e41d95b69bb81e8560fe9d ("RDMA/addr:
> > Add support for translating IPv6 addresses"). This requires a dependency
> > on IPV6.
>
> So how do we want to fix this? (This question is mostly directed to the
> IB guys) One possibility is to make all this depend on IPV6 in Kconfig,
> but I think we want the RDMA CM to be buildable/usable even if IPv6
> isn't enabled. A better option is to just put all the IPv6 related
> stuff into
>
> #if defined(CONFIG_IPV6) || defined(CONFIG_IPV6_MODULE)
>
> and add a Kconfig dependency on (IPV6 || IPV6=n) as we did for IPoIB.
>
> But then this leads to the behavior that loading the RDMA CM will cause
> the ipv6 module to be loaded if IPV6=m in the kernel config, even if the
> administrator doesn't want to enable IPv6, just as with IPoIB today.
> And people already complain about that.
>
> Anyone see a better solution (which we could use for IPoIB even)?
>
> - R.
^ permalink raw reply
* Re: linux-next: timers tree build failure
From: Ingo Molnar @ 2008-12-29 9:31 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Thomas Gleixner, H. Peter Anvin, linux-next, Takashi Iwai
In-Reply-To: <20081229133028.363f5094.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi all,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> sound/core/hrtimer.c: In function 'snd_hrtimer_open':
> sound/core/hrtimer.c:60: error: 'struct hrtimer' has no member named 'cb_mode'
> sound/core/hrtimer.c:60: error: 'HRTIMER_CB_IRQSAFE_UNLOCKED' undeclared (first use in this function)
>
> See below ... the sound tree changes are now in Linus' tree, so this
> needs fixing before the timers tree gets merged.
>
> I have applied the merge fix below (which is also in the sound tree) to
> the timers tree for today.
yes, trivial oneliner conflict, i pushed out a new auto-timers-next tree.
Ingo
^ permalink raw reply
* Re: [xfs-masters] linux-next: xfs tree build warnings
From: Stephen Rothwell @ 2008-12-29 8:51 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: David Chinner, xfs-masters, linux-next
In-Reply-To: <20081229083650.GA14699@lst.de>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
Hi Christoph,
On Mon, 29 Dec 2008 09:36:50 +0100 Christoph Hellwig <hch@lst.de> wrote:
>
> On Mon, Dec 29, 2008 at 07:26:49PM +1100, Stephen Rothwell wrote:
> > Hi David,
> >
> > Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> Yeah, just noticed when doing my first ppc64 build after a while. For
> now I threw a patch in to always make xfs_ino and unsigned long long
> and it works so far. I'll make sure this or another fix goes in through
> the usual ways.
Thanks. We do seem to be actually getting somewhere towards making u64
unsigned long long everywhere ...
--
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
* [ofa-general] Re: linux-next: origin tree build failure
From: Aleksey Senin @ 2008-12-29 8:48 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: Roland Dreier, linux-next, Linus, LKML, general
In-Reply-To: <20081229114321.4b6baea5.sfr@canb.auug.org.au>
I'm going to change it by adding
#if defined(CONFIG_IPV6) || defined(CONFIG_IPV6_MODULE)
exactly as it solved in ipoib module and as Roland says.
On Mon, 2008-12-29 at 11:43 +1100, Stephen Rothwell wrote:
> Hi Roland,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> ERROR: ".ipv6_chk_addr" [drivers/infiniband/core/ib_addr.ko] undefined!
> ERROR: ".ip6_route_output" [drivers/infiniband/core/ib_addr.ko] undefined!
>
> Caused by commit 38617c64bf9a10bf20e41d95b69bb81e8560fe9d ("RDMA/addr:
> Add support for translating IPv6 addresses"). This requires a dependency
> on IPV6.
>
> I have reverted that commit for today (which fixes the build, but may not
> be the correct solution).
^ permalink raw reply
* Re: [xfs-masters] linux-next: xfs tree build warnings
From: Christoph Hellwig @ 2008-12-29 8:36 UTC (permalink / raw)
To: Stephen Rothwell; +Cc: David Chinner, xfs-masters, linux-next
In-Reply-To: <20081229192649.7099188b.sfr@canb.auug.org.au>
On Mon, Dec 29, 2008 at 07:26:49PM +1100, Stephen Rothwell wrote:
> Hi David,
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
Yeah, just noticed when doing my first ppc64 build after a while. For
now I threw a patch in to always make xfs_ino and unsigned long long
and it works so far. I'll make sure this or another fix goes in through
the usual ways.
^ permalink raw reply
* linux-next: xfs tree build warnings
From: Stephen Rothwell @ 2008-12-29 8:26 UTC (permalink / raw)
To: David Chinner, xfs-masters; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 1909 bytes --]
Hi David,
Today's linux-next build (powerpc ppc64_defconfig) failed like this:
fs/xfs/xfs_inode.c: In function 'xfs_iflush_int':
fs/xfs/xfs_inode.c:3055: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3062: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3072: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3083: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3095: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_inode.c:3102: warning: format '%Lu' expects type 'long long unsigned int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c: In function 'xlog_recover_do_inode_trans':
fs/xfs/xfs_log_recover.c:2300: warning: format '%Ld' expects type 'long long int', but argument 6 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2311: warning: format '%Ld' expects type 'long long int', but argument 5 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2344: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2357: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2370: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
fs/xfs/xfs_log_recover.c:2380: warning: format '%Ld' expects type 'long long int', but argument 7 has type 'xfs_ino_t'
I am just flagging these to be consistent. Ingo will probably say
something about u64 and unsigned long long vs. unsigned long ...
--
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: rr tree build failure
From: Stephen Rothwell @ 2008-12-29 8:12 UTC (permalink / raw)
To: Rusty Russell; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 838 bytes --]
Hi Rusty,
Today's linux-next build (x86_64 allmodconfig) failed like this:
In file included from include/linux/smp.h:33,
from include/linux/topology.h:33,
from include/linux/mmzone.h:763,
from include/linux/gfp.h:4,
from include/linux/kmod.h:22,
from include/linux/module.h:13,
from include/linux/crypto.h:21,
from arch/x86/kernel/asm-offsets_64.c:7,
from arch/x86/kernel/asm-offsets.c:4:
arch/x86/include/asm/smp.h: In function 'num_booting_cpus':
arch/x86/include/asm/smp.h:152: error: implicit declaration of function 'cpus_weight'
I have dropped the rr 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: manual merge of the rr tree
From: Stephen Rothwell @ 2008-12-29 8:02 UTC (permalink / raw)
To: Rusty Russell; +Cc: linux-next
In-Reply-To: <20081229184721.0a7c80d8.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
Hi Rusty,
On Mon, 29 Dec 2008 18:47:21 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the rr tree got a conflict in
> kernel/rcuclassic.c between commit
> 6a7b3dc3440f7b5a9b67594af01ed562cdeb41e4 ("sched: convert nohz_cpu_mask
> to cpumask_var_t") from the cpus4096 tree and commit
> fe9482e26320b110e102afa01f84c3302d0b1593 ("cpumask: convert RCU
> implementations") from the rr tree.
>
> I fixed it up (used the rr tree version) and can carry the fix as
> necessary.
Which I assume was wrong since I got this warning:
kernel/rcuclassic.c: In function 'rcu_start_batch':
kernel/rcuclassic.c:398: warning: passing argument 3 of 'cpumask_andnot' from incompatible pointer type
So I added back the '&' on the third argument.
--
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: manual merge of the rr tree
From: Stephen Rothwell @ 2008-12-29 7:51 UTC (permalink / raw)
To: Rusty Russell; +Cc: linux-next, David Howells
[-- Attachment #1: Type: text/plain, Size: 536 bytes --]
Hi Rusty,
Today's linux-next merge of the rr tree got a conflict in
kernel/workqueue.c between commit
6cc88bc45ce8043171089c9592da223dfab91823 ("CRED: Rename is_single_threaded
() to is_wq_single_threaded()") from the Linus' tree and commit
74356d280154b04fb6d9dae10833a6ab6203735a
("cpumask:convert-kernel_workqueue.c") from the rr tree.
I fixed it up (used the rr tree version) and can carry the fix as
necessary.
--
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: manual merge of the rr tree
From: Stephen Rothwell @ 2008-12-29 7:47 UTC (permalink / raw)
To: Rusty Russell; +Cc: linux-next
[-- Attachment #1: Type: text/plain, Size: 527 bytes --]
Hi Rusty,
Today's linux-next merge of the rr tree got a conflict in
kernel/rcuclassic.c between commit
6a7b3dc3440f7b5a9b67594af01ed562cdeb41e4 ("sched: convert nohz_cpu_mask
to cpumask_var_t") from the cpus4096 tree and commit
fe9482e26320b110e102afa01f84c3302d0b1593 ("cpumask: convert RCU
implementations") from the rr tree.
I fixed it up (used the rr tree version) and can carry the fix as
necessary.
--
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: net tree build failure
From: Stephen Rothwell @ 2008-12-29 6:45 UTC (permalink / raw)
To: Dan Williams; +Cc: linux-next, David Miller, Eric W. Biederman
In-Reply-To: <20081120133036.3a4aea4a.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1533 bytes --]
Hi Dan,
On Thu, 20 Nov 2008 13:30:36 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next build (powerpc ppc64_defconfig) failed like this:
>
> net/core/dev.c: In function 'net_dev_init':
> net/core/dev.c:4775: error: implicit declaration of function 'netdev_dma_register'
>
> A bad interaction between commit 505d4f73dda9e20d59da05008f1f5eb432613e71
> "net: Guaranetee the proper ordering of the loopback device. v2" from the
> net tree (which moved a call to netdev_dma_register) and commit
> 8f3da0d613494b02f8628bb5dbf2366f0298505c "dmaengine: kill struct
> dma_client and supporting infrastructure" from the async_tx tree (which
> removes the call).
>
> I added the below patch to fix up the merge and can carry it.
This now occurs when I merge the async_tx tree as the net tree has been
merged into Linus' tree. You should fix this (by merging Linus' tree
into yours and doing the fixup below as part of the merge commit) before
asking Linus to pull your tree.
> diff --git a/net/core/dev.c b/net/core/dev.c
> index c3f5713..e9cf36e 100644
> --- a/net/core/dev.c
> +++ b/net/core/dev.c
> @@ -4772,8 +4772,6 @@ static int __init net_dev_init(void)
> if (register_pernet_device(&default_device_ops))
> goto out;
>
> - netdev_dma_register();
> -
> open_softirq(NET_TX_SOFTIRQ, net_tx_action);
> open_softirq(NET_RX_SOFTIRQ, net_rx_action);
>
--
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: driver-core tree build failure
From: Stephen Rothwell @ 2008-12-29 6:34 UTC (permalink / raw)
To: Greg KH; +Cc: Mark McLoughlin, linux-next
In-Reply-To: <20081223042932.GD1928@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 2272 bytes --]
Hi Greg,
On Mon, 22 Dec 2008 20:29:32 -0800 Greg KH <greg@kroah.com> wrote:
>
> On Mon, Dec 22, 2008 at 02:50:46PM +0000, Mark McLoughlin wrote:
> > On Mon, 2008-12-22 at 23:59 +1100, Stephen Rothwell wrote:
> > > Hi Greg,
> > >
> > > Today's linux-next build (powerpc allnoconfig) failed like this:
> > >
> > > drivers/base/core.c: In function '__root_device_register':
> > > drivers/base/core.c:1277: error: dereferencing pointer to incomplete type
> > >
> > > Caused by bf86dbd2451d1012c2c968a960470e485b869f5b ("driver core: add
> > > root_device_register()"). This needs to cope with !CONFIG_MODULES (where
> > > struct module is not defined).
> >
> > Ouch, my bad.
> >
> > > I applied the following patch but only for today because it is too hard
> > > to revert the above patch ...
> > >
> > > --
> > > Cheers,
> > > Stephen Rothwell sfr@canb.auug.org.au
> > > http://www.canb.auug.org.au/~sfr/
> > >
> > > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > > Date: Mon, 22 Dec 2008 23:50:56 +1100
> > > Subject: [PATCH] driver core: fix root_device_register for not CONFIG_MODULES
> > >
> > > Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
> > > ---
> > > drivers/base/core.c | 2 ++
> > > 1 files changed, 2 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/drivers/base/core.c b/drivers/base/core.c
> > > index 6fbdd8b..aa93980 100644
> > > --- a/drivers/base/core.c
> > > +++ b/drivers/base/core.c
> > > @@ -1273,6 +1273,7 @@ struct device *__root_device_register(const char *name, struct module *owner)
> > > return ERR_PTR(err);
> > > }
> > >
> > > +#ifdef CONFIG_MODULE
> > > if (owner) {
> > > struct module_kobject *mk = &owner->mkobj;
> > >
> > > @@ -1283,6 +1284,7 @@ struct device *__root_device_register(const char *name, struct module *owner)
> > > }
> > > root->owner = owner;
> > > }
> > > +#endif
> >
> > Yep, looks correct to me ...
>
> Ick, I hate ifdefs... I'll go fix this up.
Its still there today. Lucky for you I didn't notice early enough to
drop the driver-core tree :-). I will reapply my patch.
--
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: Pull request for FS-Cache, including NFS patches
From: Stephen Rothwell @ 2008-12-29 5:26 UTC (permalink / raw)
To: Andrew Morton
Cc: Bernd Schubert, nfsv4, steved, linux-kernel, dhowells, linux-next,
linux-fsdevel, rwheeler
In-Reply-To: <20081228200726.7b7078b4.akpm@linux-foundation.org>
[-- Attachment #1.1: Type: text/plain, Size: 599 bytes --]
Hi Andrew, Trond,
On Sun, 28 Dec 2008 20:07:26 -0800 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> And that of course means that many many 2.6.28 patches which I am
> maintaining will need significant rework to apply on top of linux-next,
> and then they won't apply to mainline. Or that linux-next will not apply
> on top of those patches. Mainly memory management.
>
> Please drop the NFS tree until after -rc1.
OK, it is dropped for now (including today's tree).
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #1.2: Type: application/pgp-signature, Size: 197 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
NFSv4 mailing list
NFSv4@linux-nfs.org
http://linux-nfs.org/cgi-bin/mailman/listinfo/nfsv4
^ permalink raw reply
* Re: linux-next: kvm tree build failure
From: Stephen Rothwell @ 2008-12-29 5:17 UTC (permalink / raw)
To: Avi Kivity; +Cc: linux-next, Jan Kiszka, Hollis Blanchard
In-Reply-To: <20081223002514.6fbcfe4f.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]
Hi Avi,
On Tue, 23 Dec 2008 00:25:14 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next build (powerpc ppc44x_config) failed like this:
>
> arch/powerpc/kvm/44x.c: In function 'kvmppc_core_load_guest_debugstate':
> arch/powerpc/kvm/44x.c:58: warning: initialization from incompatible pointer type
> arch/powerpc/kvm/44x.c:75: error: 'struct kvm_guest_debug' has no member named 'bp'
> arch/powerpc/kvm/44x.c:76: error: 'struct kvm_guest_debug' has no member named 'bp'
> arch/powerpc/kvm/44x.c:79: error: 'struct kvm_guest_debug' has no member named 'bp'
> arch/powerpc/kvm/44x.c:80: error: 'struct kvm_guest_debug' has no member named 'bp'
> arch/powerpc/kvm/44x.c:83: error: 'struct kvm_guest_debug' has no member named 'bp'
> arch/powerpc/kvm/44x.c:84: error: 'struct kvm_guest_debug' has no member named 'bp'
> arch/powerpc/kvm/44x.c:87: error: 'struct kvm_guest_debug' has no member named 'bp'
> arch/powerpc/kvm/44x.c:88: error: 'struct kvm_guest_debug' has no member named 'bp'
>
> Probably caused by commit 6968f31a2163f8fcf26ea8775c44d7e5be54d622 ("KVM:
> Remove old kvm_guest_debug structs") so I have reverted the kvm tree for
> today.
This error is still there, so I have dropped the kvm tree again 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
* linux-next: manual merge of the kvm tree
From: Stephen Rothwell @ 2008-12-29 5:11 UTC (permalink / raw)
To: Avi Kivity
Cc: linux-next, Hollis Blanchard, Benjamin Herrenschmidt,
Paul Mackerras
[-- Attachment #1: Type: text/plain, Size: 764 bytes --]
Hi Avi,
Today's linux-next merge of the kvm tree got a conflict in
arch/powerpc/kvm/powerpc.c between commits
2a4aca1144394653269720ffbb5a325a77abd5fa ("powerpc/mm: Split low level
tlb invalidate for nohash processors") and
fad7b9b51e21a97e9e2662f1b51869ed2d209097 ("powerpc: Fix KVM build on
ppc440") from the powerpc tree (already merged into Linus' tree) and
commits 48e5562f7278782ae5d1772b7baa1ff76f035285 ("KVM: ppc: Refactor
powerpc.c to relocate 440-specific code") and
408e29020273079445b5a9161a80d6ce07ab6b1c ("KVM: ppc: Implement in-kernel
exit timing statistics") from the kvm tree.
I just used the kvm tree version of the file.
--
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: origin tree build warnings
From: David Miller @ 2008-12-29 4:21 UTC (permalink / raw)
To: sfr; +Cc: nhorman, linux-next, linux-kernel, netdev
In-Reply-To: <20081229151749.8dd82c02.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 29 Dec 2008 15:17:49 +1100
> On Sun, 28 Dec 2008 20:01:45 -0800 (PST) David Miller <davem@davemloft.net> wrote:
> >
> > I'll take care of all of these issues, along with the
>
> Thanks.
>
> > ibmveth et al. ones you reported seperately.
>
> Linus already took my patches for cifs, ibmveth and ehea (probably
> assuming that they were trivial).
Yep I noticed that, thanks a lot Stephen.
^ permalink raw reply
* Re: linux-next: origin tree build warnings
From: Stephen Rothwell @ 2008-12-29 4:17 UTC (permalink / raw)
To: David Miller; +Cc: nhorman, linux-next, linux-kernel, netdev
In-Reply-To: <20081228.200145.33502228.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 431 bytes --]
Hi Dave,
On Sun, 28 Dec 2008 20:01:45 -0800 (PST) David Miller <davem@davemloft.net> wrote:
>
> I'll take care of all of these issues, along with the
Thanks.
> ibmveth et al. ones you reported seperately.
Linus already took my patches for cifs, ibmveth and ehea (probably
assuming that they were trivial).
--
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: manual merge of the net tree
From: Stephen Rothwell @ 2008-12-29 4:14 UTC (permalink / raw)
To: David Miller; +Cc: linux-next, johannes, sam
In-Reply-To: <20081228.200055.170405541.davem@davemloft.net>
[-- Attachment #1: Type: text/plain, Size: 298 bytes --]
Hi Dave,
On Sun, 28 Dec 2008 20:00:55 -0800 (PST) David Miller <davem@davemloft.net> wrote:
>
> I'll take care of this as I prepare the sparc-next-2.6 tree for
> merging.
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
* Re: Pull request for FS-Cache, including NFS patches
From: Andrew Morton @ 2008-12-29 4:07 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Bernd Schubert, nfsv4, steved, linux-kernel, dhowells, linux-next,
linux-fsdevel, rwheeler
In-Reply-To: <20081229144533.4a0ab696.sfr@canb.auug.org.au>
On Mon, 29 Dec 2008 14:45:33 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> I ask because it
> reappeared in linux-next today via the nfs tree (merged into that on Dec
> 24 and 25) ...
And that of course means that many many 2.6.28 patches which I am
maintaining will need significant rework to apply on top of linux-next,
and then they won't apply to mainline. Or that linux-next will not apply
on top of those patches. Mainly memory management.
Please drop the NFS tree until after -rc1.
Guys, this: http://lkml.org/lkml/2008/12/27/173
^ permalink raw reply
* Re: linux-next: manual merge of the creds tree
From: Stephen Rothwell @ 2008-12-29 4:06 UTC (permalink / raw)
To: David Chinner, Lachlan McIlroy
Cc: linux-next, Christoph Hellwig, David Howells, James Morris
In-Reply-To: <20081030154741.2651e779.sfr@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]
Hi David,
On Thu, 30 Oct 2008 15:47:41 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Today's linux-next merge of the creds tree got conflicts in
> fs/xfs/linux-2.6/xfs_cred.h, fs/xfs/linux-2.6/xfs_globals.h and
> fs/xfs/xfs_vnodeops.h between commit
> 959f0f5b48d25a478694e04d024cd1ca681ea4bf ("[XFS] kill sys_cred") from the
> xfs tree and commit 3634a8a33b2cd7296e265d01d606b58c22b6a557 ("CRED:
> Separate task security context from task_struct") from the creds tree.
>
> The former mostly removed what the latter changed. I fixed it up (see
> below - I just removed the "extern cred_t *sys_cred;" from xfs_globals.h
> and the cred_t arguments to xfs_setattr and xfs_change_file_space in
> xfs_vnodeops.h) and can carry the fix.
These conflicts are now between the xfs tree and Linus' tree and so could
be sorted out by merging Linus' tree into the xfs tree before asking
Linus to pull the xfs tree.
--
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: origin tree build warnings
From: David Miller @ 2008-12-29 4:01 UTC (permalink / raw)
To: sfr; +Cc: nhorman, linux-next, linux-kernel, netdev
In-Reply-To: <20081229113525.89450db7.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 29 Dec 2008 11:35:25 +1100
> Hi Neil,
>
> Today's linux-next build (powerpc ppc64_defconfig) produced these new
> warnings:
>
> drivers/net/pasemi_mac.c: In function 'pasemi_mac_rx_intr':
> drivers/net/pasemi_mac.c:957: warning: unused variable 'dev'
> drivers/net/pasemi_mac.c: In function 'pasemi_mac_poll':
> drivers/net/pasemi_mac.c:1637: warning: unused variable 'dev'
> drivers/net/spider_net.c: In function 'spider_net_poll':
> drivers/net/spider_net.c:1280: warning: unused variable 'netdev'
>
> Probably caused by commit 908a7a16b852ffd618a9127be8d62432182d81b4 ("net:
> Remove unused netdev arg from some NAPI interfaces").
>
> Please fix these up.
I'll take care of all of these issues, along with the
ibmveth et al. ones you reported seperately.
Thanks Stephen.
^ permalink raw reply
* Re: Pull request for FS-Cache, including NFS patches
From: Andrew Morton @ 2008-12-29 4:01 UTC (permalink / raw)
To: Stephen Rothwell
Cc: Bernd Schubert, nfsv4, steved, linux-kernel, dhowells, linux-next,
linux-fsdevel, rwheeler
In-Reply-To: <20081229144533.4a0ab696.sfr@canb.auug.org.au>
On Mon, 29 Dec 2008 14:45:33 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi David,
>
> On Fri, 19 Dec 2008 11:05:39 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Given the ongoing discussions around FS-Cache, I have removed it from
> > linux-next. Please ask me to include it again (if sensible) once some
> > decision has been reached about its future.
>
> What was the result of discussions around FS-Cache?
There was none.
Dan Muntz's question:
Solaris has had CacheFS since ~1995, HPUX had a port of it since
~1997. I'd be interested in evidence of even a small fraction of
Solaris and/or HPUX shops using CacheFS. I am aware of customers who
thought it sounded like a good idea, but ended up ditching it for
various reasons (e.g., CacheFS just adds overhead if you almost
always hit your local mem cache).
was an very very good one.
Seems that instead of answering it, we've decided to investigate the
fate of those who do not learn from history.
> I ask because it
> reappeared in linux-next today via the nfs tree (merged into that on Dec
> 24 and 25) ...
oh.
^ permalink raw reply
* Re: linux-next: manual merge of the net tree
From: David Miller @ 2008-12-29 4:00 UTC (permalink / raw)
To: sfr; +Cc: linux-next, johannes, sam
In-Reply-To: <20081229145300.0a86e1de.sfr@canb.auug.org.au>
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 29 Dec 2008 14:53:00 +1100
> Hi Dave,
>
> On Sun, 07 Dec 2008 23:26:58 -0800 (PST) David Miller <davem@davemloft.net> wrote:
> >
> > From: Stephen Rothwell <sfr@canb.auug.org.au>
> > Date: Mon, 8 Dec 2008 14:48:51 +1100
> >
> > > Today's linux-next merge of the net tree got a conflict in
> > > arch/sparc64/kernel/idprom.c between commit
> > > a88b5ba8bd8ac18aad65ee6c6a254e2e74876db3 (sparc,sparc64: unify kernel/"")
> > > from the sparc tree and commit 7c510e4b730a92cecf94ada45c989d8be0200d47
> > > ("net: convert more to %pM") from the net tree.
> >
> > Thanks for reporting this.
> >
> > > The former renamed the file while the latter modified it. I just deleted
> > > the renamed file for now, the %pM conversion can be done later.
> >
> > Yes it's probably the best way to handle this for now.
>
> This conflict is now between the sparc tree and Linus' tree ...
I'll take care of this as I prepare the sparc-next-2.6 tree for
merging.
^ 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