Linux-Next discussions
 help / color / mirror / Atom feed
* linux-next: build failure after merge of the final tree (net tree related)
From: Stephen Rothwell @ 2012-01-09  5:38 UTC (permalink / raw)
  To: David Miller, netdev; +Cc: linux-next, linux-kernel, Glauber Costa

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

Hi ,

After merging the final tree, today's linux-next build (powerpc
allnoconfig) failed like this:

In file included from include/linux/tcp.h:211:0,
                 from include/linux/ipv6.h:221,
                 from include/net/ipv6.h:16,
                 from include/linux/sunrpc/clnt.h:26,
                 from include/linux/nfs_fs.h:50,
                 from init/do_mounts.c:20:
include/net/sock.h: In function 'sk_update_clone':
include/net/sock.h:1109:3: error: implicit declaration of function 'sock_update_memcg' [-Werror=implicit-function-declaration]

Caused by commit f3f511e1ce6f ("net: fix sock_clone reference mismatch
with tcp memcontrol") from the net tree.  In this build, CONFIG_INET is not set.

I applied the following patch for today:

From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 9 Jan 2012 16:33:16 +1100
Subject: [PATCH] net: sk_update_clone is only used in net/core/sock.c

so move it there.  Fixes build errors when CONFIG_INET is not defeined:

In file included from include/linux/tcp.h:211:0,
                 from include/linux/ipv6.h:221,
                 from include/net/ipv6.h:16,
                 from include/linux/sunrpc/clnt.h:26,
                 from include/linux/nfs_fs.h:50,
                 from init/do_mounts.c:20:
include/net/sock.h: In function 'sk_update_clone':
include/net/sock.h:1109:3: error: implicit declaration of function 'sock_update_memcg' [-Werror=implicit-function-declaration]

Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
 include/net/sock.h |    6 ------
 net/core/sock.c    |    6 ++++++
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/include/net/sock.h b/include/net/sock.h
index 0ed65e3..bb972d2 100644
--- a/include/net/sock.h
+++ b/include/net/sock.h
@@ -1103,12 +1103,6 @@ sk_sockets_allocated_read_positive(struct sock *sk)
 	return percpu_counter_sum_positive(prot->sockets_allocated);
 }
 
-static inline void sk_update_clone(const struct sock *sk, struct sock *newsk)
-{
-	if (mem_cgroup_sockets_enabled && sk->sk_cgrp)
-		sock_update_memcg(newsk);
-}
-
 static inline int
 proto_sockets_allocated_sum_positive(struct proto *prot)
 {
diff --git a/net/core/sock.c b/net/core/sock.c
index e80b64f..c3ae73d 100644
--- a/net/core/sock.c
+++ b/net/core/sock.c
@@ -1272,6 +1272,12 @@ void sk_release_kernel(struct sock *sk)
 }
 EXPORT_SYMBOL(sk_release_kernel);
 
+static void sk_update_clone(const struct sock *sk, struct sock *newsk)
+{
+	if (mem_cgroup_sockets_enabled && sk->sk_cgrp)
+		sock_update_memcg(newsk);
+}
+
 /**
  *	sk_clone_lock - clone a socket, and lock its clone
  *	@sk: the socket to clone
-- 
1.7.8.197.g73c6b

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply related

* Re: linux-next: build warning after merge of the sound-asoc tree
From: Mark Brown @ 2012-01-09  3:10 UTC (permalink / raw)
  To: Axel Lin; +Cc: Stephen Rothwell, Liam Girdwood, linux-next, linux-kernel
In-Reply-To: <CAF+7xWktUYvz1UqNyYsgAwEeap6UefXz+YE1wrRydrCWiMKAAg@mail.gmail.com>

On Mon, Jan 09, 2012 at 11:03:35AM +0800, Axel Lin wrote:
> 2012/1/9 Stephen Rothwell <sfr@canb.auug.org.au>:

> I think this commit should be replaced by [PATCH] ASoC: Fix build
> dependency for SND_AT91_SOC_AFEB9260
> http://mailman.alsa-project.org/pipermail/alsa-devel/2012-January/047861.html

> Should I send a revert patch for commit 739be96ab837? Or you can do it
> by git-revert command directly?

Send an incremental patch to put things into the desired state.

^ permalink raw reply

* Re: linux-next: build warning after merge of the sound-asoc tree
From: Axel Lin @ 2012-01-09  3:03 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: Mark Brown, Liam Girdwood, linux-next, linux-kernel
In-Reply-To: <20120109125531.dbcac0481adb6376fb7e9ca1@canb.auug.org.au>

2012/1/9 Stephen Rothwell <sfr@canb.auug.org.au>:
> Hi all,
>
> After merging the sound-asoc tree, today's linux-next build (powerpc
> ppc64_defconfig and x86_64 allmodconfig) produced this warning:
>
> drivers/misc/Kconfig:212:error: recursive dependency detected!
> drivers/misc/Kconfig:212:       symbol ATMEL_SSC is selected by SND_ATMEL_SOC_SSC
> sound/soc/atmel/Kconfig:9:      symbol SND_ATMEL_SOC_SSC is selected by SND_AT91_SOC_SAM9G20_WM8731
> sound/soc/atmel/Kconfig:18:     symbol SND_AT91_SOC_SAM9G20_WM8731 depends on ATMEL_SSC
>
> Probably introduced by commit 739be96ab837 ("ASoC: Fix build dependency
> for SND_ATMEL_SOC_SSC").
Hi Mark,
I think this commit should be replaced by [PATCH] ASoC: Fix build
dependency for SND_AT91_SOC_AFEB9260
http://mailman.alsa-project.org/pipermail/alsa-devel/2012-January/047861.html

Should I send a revert patch for commit 739be96ab837? Or you can do it
by git-revert command directly?

Thanks,
Axel
>
> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/

^ permalink raw reply

* Re: linux-next: manual merge of the vfs tree with Linus' tree
From: Stephen Rothwell @ 2012-01-09  2:22 UTC (permalink / raw)
  To: Linus Torvalds; +Cc: Al Viro, linux-next, linux-kernel, Chris Mason
In-Reply-To: <CA+55aFyYR=66K721tVF3NgLg-MyFsVuy6kewJJBXaS1GVd+wXQ@mail.gmail.com>

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

On Sun, 8 Jan 2012 17:32:14 -0800 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Sun, Jan 8, 2012 at 5:11 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Then again ... it looks like the vfs tree has other changes to the btrfs
> > code so that I need the version from the vfs tree, not Linus' tree ...
> 
> The btrfs changes (at lest most of them) will come through the btrfs
> tree, that's one of the reasons the vfs tree got re-built, afaik.

That's fine, but maybe we should consider getting the btrfs tree into
linux-next ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply

* Re: linux-next: manual merge of the vfs tree with Linus' tree
From: Al Viro @ 2012-01-09  2:14 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: linux-next, linux-kernel, Linus
In-Reply-To: <20120109121133.76f5b7c4a4780954c4562244@canb.auug.org.au>

On Mon, Jan 09, 2012 at 12:11:33PM +1100, Stephen Rothwell wrote:
> Hi Al,
> 
> Today's linux-next merge of the vfs tree got a conflict in
> fs/btrfs/super.c between commit 34c80b1d93e6 ("vfs: switch ->show_options
> () to struct dentry *") from Linus' tree and commit 2ddeb2a58b11 ("vfs:
> switch ->show_options() to struct dentry *") from the vfs tree.
> 
> I assume that you sent the correct version to Linus, so I used that.
> Please, if you do change stuff just before sending it to Linus also update
> your for-next branch.
> 
> Then again ... it looks like the vfs tree has other changes to the btrfs
> code so that I need the version from the vfs tree, not Linus' tree ...

btrfs stuff will (hopefully) get picked by Chris.  Until then I've got those
patches in #for-next, rebased on top of what Linus had picked...

^ permalink raw reply

* linux-next: build failure after merge of the battery tree
From: Stephen Rothwell @ 2012-01-09  2:11 UTC (permalink / raw)
  To: Anton Vorontsov; +Cc: linux-next, linux-kernel, Ashish Jangam, David Dajun Chen

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

Hi Anton,

After merging the battery tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/power/da9052-battery.c: In function 'da9052_bat_read_volt':
drivers/power/da9052-battery.c:293:2: error: implicit declaration of function 'da9052_adc_manual_read' [-Werror=implicit-function-declaration]
drivers/power/da9052-battery.c: In function 'da9052_bat_check_presence':
drivers/power/da9052-battery.c:306:2: error: implicit declaration of function 'da9052_adc_read_temp' [-Werror=implicit-function-declaration]
drivers/power/da9052-battery.c: In function 'da9052_determine_vc_tbl_index':
drivers/power/da9052-battery.c:348:1: warning: control reaches end of non-void function [-Wreturn-type]
cc1: some warnings being treated as errors

Caused by commit ded7fc7b0550 ("power_supply: Add DA9052 battery driver").

The commit message says "This driver depends on DA9052 MFD core dirver
for definitions and methods".  That core is presumably still pending
inclusion.

I have used the battery tree from next-20120104 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply

* linux-next: build warning after merge of the sound-asoc tree
From: Stephen Rothwell @ 2012-01-09  1:55 UTC (permalink / raw)
  To: Mark Brown, Liam Girdwood; +Cc: linux-next, linux-kernel, Axel Lin

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

Hi all,

After merging the sound-asoc tree, today's linux-next build (powerpc
ppc64_defconfig and x86_64 allmodconfig) produced this warning:

drivers/misc/Kconfig:212:error: recursive dependency detected!
drivers/misc/Kconfig:212:	symbol ATMEL_SSC is selected by SND_ATMEL_SOC_SSC
sound/soc/atmel/Kconfig:9:	symbol SND_ATMEL_SOC_SSC is selected by SND_AT91_SOC_SAM9G20_WM8731
sound/soc/atmel/Kconfig:18:	symbol SND_AT91_SOC_SAM9G20_WM8731 depends on ATMEL_SSC

Probably introduced by commit 739be96ab837 ("ASoC: Fix build dependency
for SND_ATMEL_SOC_SSC").

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply

* Re: linux-next: manual merge of the vfs tree with Linus' tree
From: Linus Torvalds @ 2012-01-09  1:32 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: Al Viro, linux-next, linux-kernel
In-Reply-To: <20120109121133.76f5b7c4a4780954c4562244@canb.auug.org.au>

On Sun, Jan 8, 2012 at 5:11 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Then again ... it looks like the vfs tree has other changes to the btrfs
> code so that I need the version from the vfs tree, not Linus' tree ...

The btrfs changes (at lest most of them) will come through the btrfs
tree, that's one of the reasons the vfs tree got re-built, afaik.

                      Linus

^ permalink raw reply

* linux-next: manual merge of the vfs tree with Linus' tree
From: Stephen Rothwell @ 2012-01-09  1:11 UTC (permalink / raw)
  To: Al Viro; +Cc: linux-next, linux-kernel, Linus

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

Hi Al,

Today's linux-next merge of the vfs tree got a conflict in
fs/btrfs/super.c between commit 34c80b1d93e6 ("vfs: switch ->show_options
() to struct dentry *") from Linus' tree and commit 2ddeb2a58b11 ("vfs:
switch ->show_options() to struct dentry *") from the vfs tree.

I assume that you sent the correct version to Linus, so I used that.
Please, if you do change stuff just before sending it to Linus also update
your for-next branch.

Then again ... it looks like the vfs tree has other changes to the btrfs
code so that I need the version from the vfs tree, not Linus' tree ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply

* linux-next: manual merge of the arm tree with Linus' tree
From: Stephen Rothwell @ 2012-01-08 23:53 UTC (permalink / raw)
  To: Russell King; +Cc: linux-next, linux-kernel, Nicolas Pitre

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

Hi Russell,

Today's linux-next merge of the arm tree got a conflict in
arch/arm/mach-exynos/common.c between commit 7affca3537d7 ("Merge branch
'driver-core-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core") from
Linus' tree and commit 53aa9b6a12dd ("ARM: mach-exynos: use standard
arch_idle()") from the arm tree.

I fixed it up (see below) and can carry the fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc arch/arm/mach-exynos/common.c
index b6ac6ee,8484019..0000000
--- a/arch/arm/mach-exynos/common.c
+++ b/arch/arm/mach-exynos/common.c
@@@ -468,10 -459,7 +460,7 @@@ int __init exynos_init(void
  {
  	printk(KERN_INFO "EXYNOS: Initializing architecture\n");
  
- 	/* set idle function */
- 	pm_idle = exynos_idle;
- 
 -	return sysdev_register(&exynos4_sysdev);
 +	return device_register(&exynos4_dev);
  }
  
  static struct s3c24xx_uart_clksrc exynos4_serial_clocks[] = {

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

^ permalink raw reply

* linux-next: manual merge of the arm tree with Linus tree
From: Stephen Rothwell @ 2012-01-08 23:53 UTC (permalink / raw)
  To: Russell King; +Cc: linux-next, linux-kernel, Nicolas Pitre

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

Hi Russell,

Today's linux-next merge of the arm tree got a conflict in
arch/arm/mach-s5pc100/common.c between commit 7affca3537d7 ("Merge branch
'driver-core-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core") from
Linus' tree and commit 109ac862f737 ("ARM: mach-s5pc100: use standard
arch_idle()") from the arm tree.

I fixed it up (see below) and can carry the fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc arch/arm/mach-s5pc100/common.c
index c909573,4659fb9..0000000
--- a/arch/arm/mach-s5pc100/common.c
+++ b/arch/arm/mach-s5pc100/common.c
@@@ -210,11 -201,7 +202,7 @@@ core_initcall(s5pc100_core_init)
  int __init s5pc100_init(void)
  {
  	printk(KERN_INFO "S5PC100: Initializing architecture\n");
- 
- 	/* set idle function */
- 	pm_idle = s5pc100_idle;
- 
 -	return sysdev_register(&s5pc100_sysdev);
 +	return device_register(&s5pc100_dev);
  }
  
  /* uart registration process */

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

^ permalink raw reply

* linux-next: manual merge of the arm tree with Linus' tree
From: Stephen Rothwell @ 2012-01-08 23:53 UTC (permalink / raw)
  To: Russell King; +Cc: linux-next, linux-kernel, Nicolas Pitre

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

Hi Russell,

Today's linux-next merge of the arm tree got a conflict in
arch/arm/mach-s5pv210/common.c between commit 7affca3537d7 ("Merge branch
'driver-core-next' of
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core") from
Linus' tree and commit 58329cb3171f ("ARM: mach-s5pv210: use standard
arch_idle()") from the arm tree.

I fixed it up (see below) and can carry the fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

diff --cc arch/arm/mach-s5pv210/common.c
index 0ec3933,2622b8a..0000000
--- a/arch/arm/mach-s5pv210/common.c
+++ b/arch/arm/mach-s5pv210/common.c
@@@ -247,11 -238,7 +239,7 @@@ core_initcall(s5pv210_core_init)
  int __init s5pv210_init(void)
  {
  	printk(KERN_INFO "S5PV210: Initializing architecture\n");
- 
- 	/* set idle function */
- 	pm_idle = s5pv210_idle;
- 
 -	return sysdev_register(&s5pv210_sysdev);
 +	return device_register(&s5pv210_dev);
  }
  
  static struct s3c24xx_uart_clksrc s5pv210_serial_clocks[] = {

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

^ permalink raw reply

* Re: linux-next: Tree for Jan 5 (exofs or nfs ?)
From: Boaz Harrosh @ 2012-01-08  8:36 UTC (permalink / raw)
  To: Randy Dunlap
  Cc: Stephen Rothwell, linux-next-u79uwXL29TY76Z2rM5mHXA, LKML, Linus,
	open-osd development, NFS list
In-Reply-To: <4F0644C1.6000405-/UHa2rfvQTnk1uMJSBkQmQ@public.gmane.org>

On 01/06/2012 02:48 AM, Randy Dunlap wrote:
> On 01/05/2012 12:12 AM, Stephen Rothwell wrote:
>> Hi all,
>>
>> Changes since 20120104:
> 
> 
> fs/built-in.o: In function `_write_done':
> objio_osd.c:(.text+0x134971): undefined reference to `ore_check_io'
> fs/built-in.o: In function `_read_done':
> objio_osd.c:(.text+0x134a11): undefined reference to `ore_check_io'
> fs/built-in.o: In function `objio_alloc_io_state':
> objio_osd.c:(.text+0x1353da): undefined reference to `ore_get_rw_state'
> fs/built-in.o: In function `objio_alloc_lseg':
> (.text+0x135724): undefined reference to `ore_verify_layout'
> fs/built-in.o: In function `objio_free_result':
> (.text+0x135966): undefined reference to `ore_put_io_state'
> fs/built-in.o: In function `objio_read_pagelist':
> (.text+0x135be5): undefined reference to `ore_read'
> fs/built-in.o: In function `objio_write_pagelist':
> (.text+0x135d46): undefined reference to `ore_write'
> 
> 
> Full randconfig file is attached.
> 
> 

I have a fix queued for this for linus to pull and Stable@. It should be
in linux-next. Though people reported problems with my git server, im
investigating. Next linux-next should have it.

http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=commit;h=831c2dc5f47c1dc79c32229d75065ada1dcc66e1

Thanks
Boaz
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

^ permalink raw reply

* Re: linux-next: net/smsc911x compile error on next-20120106
From: David Miller @ 2012-01-07 20:22 UTC (permalink / raw)
  To: shawn.guo; +Cc: sfr, linux-next, netdev, linux-arm-kernel
In-Reply-To: <CAAQ0ZWSRzUM2rdhfWDqang6Baat6x-gEso5hQGEkbOqFjM-sMQ@mail.gmail.com>

From: Shawn Guo <shawn.guo@linaro.org>
Date: Sat, 7 Jan 2012 13:55:41 +0800

> Hi Stephen, David,
> 
> I just ran into the following compile error when building
> next-20120106 with imx_v6_v7_defconfig.
> 

I just commited the following to fix this, thanks:

--------------------
smsc911x: Unconditionally include linux/smscphy.h in smsc911x.h

The energy detect enable/disable code in the driver uses some
register defines in this header unconditionally, so guarding
the smscphy.h header include with CONFIG_SMSC_PHY leads to
build failures in some configurations.

Reported-by: Shawn Guo <shawn.guo@linaro.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
---
 drivers/net/ethernet/smsc/smsc911x.h |    2 --
 1 files changed, 0 insertions(+), 2 deletions(-)

diff --git a/drivers/net/ethernet/smsc/smsc911x.h b/drivers/net/ethernet/smsc/smsc911x.h
index 938ecf2..9ad5e5d 100644
--- a/drivers/net/ethernet/smsc/smsc911x.h
+++ b/drivers/net/ethernet/smsc/smsc911x.h
@@ -401,8 +401,6 @@
 #include <asm/smsc911x.h>
 #endif
 
-#ifdef CONFIG_SMSC_PHY
 #include <linux/smscphy.h>
-#endif
 
 #endif				/* __SMSC911X_H__ */
-- 
1.7.6.5

^ permalink raw reply related

* Re: [PATCH -next] fs: fix fs/fs-writeback.c build error
From: Randy Dunlap @ 2012-01-07 18:17 UTC (permalink / raw)
  To: Wu Fengguang
  Cc: Linus Torvalds, Stephen Rothwell, linux-next, LKML, Al Viro,
	Andrew Morton
In-Reply-To: <20120107133008.GA21128@localhost>

On 01/07/2012 05:30 AM, Wu Fengguang wrote:
> On Fri, Jan 06, 2012 at 03:01:09PM -0800, Linus Torvalds wrote:
>> On Thu, Jan 5, 2012 at 4:18 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
>>>
>>> In linux-next, fs/fs-writeback.c no longer #includes <linux/buffer_head.h>,
>>> which #included <linux/pagemap.h>, so add that latter header file to
>>> <linux/writeback.h> to fix the build error:
>>>
>>> fs/fs-writeback.c:510:11: error: 'PAGE_CACHE_SHIFT' undeclared (first use in this function)
>>
>> I would actually suggest:
>>
>>  - move the whole MIN_WRITEBACK_PAGES #define from the header file to
>> fs/writeback.c
> 
> Done.
> 
>> (why expose such a random #define to outside users that
>> have nothing to do with it?)
>  
> Yeah, there were some early patches that reference MIN_WRITEBACK_PAGES
> from other files, which are dropped later..
> 
>>  - make sure that fs/fs-writeback.c has that pagemap.h #include.
> 
> Done. (otherwise it won't compile)
> 
>> There's no reason why <linux/writeback.h> should include filemap.h per
>> se, and there is no reason why it should expose some internal chunking
>> #define to anybody else.
> 
> Good point. I'll queue this patch to writeback-for-next:
> 
> Subject: writeback: move MIN_WRITEBACK_PAGES to fs-writeback.c
> Date: Sat Jan 07 20:41:55 CST 2012
> 
> Fix compile error
> 
>  fs/fs-writeback.c:515:33: error: ‘PAGE_CACHE_SHIFT’ undeclared (first use in this function)
> 
> Reported-by: Randy Dunlap <rdunlap@xenotime.net>
> Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>

Acked-by: Randy Dunlap <rdunlap@xenotime.net>

Thanks.

> ---
>  fs/fs-writeback.c         |    6 ++++++
>  include/linux/writeback.h |    5 -----
>  2 files changed, 6 insertions(+), 5 deletions(-)
> 
> --- next.orig/fs/fs-writeback.c	2012-01-07 21:01:34.552000061 +0800
> +++ next/fs/fs-writeback.c	2012-01-07 21:22:45.504000051 +0800
> @@ -20,6 +20,7 @@
>  #include <linux/sched.h>
>  #include <linux/fs.h>
>  #include <linux/mm.h>
> +#include <linux/pagemap.h>
>  #include <linux/kthread.h>
>  #include <linux/freezer.h>
>  #include <linux/writeback.h>
> @@ -29,6 +30,11 @@
>  #include "internal.h"
>  
>  /*
> + * 4MB minimal write chunk size
> + */
> +#define MIN_WRITEBACK_PAGES	(4096UL >> (PAGE_CACHE_SHIFT - 10))
> +
> +/*
>   * Passed into wb_writeback(), essentially a subset of writeback_control
>   */
>  struct wb_writeback_work {
> --- next.orig/include/linux/writeback.h	2012-01-07 21:01:34.544000059 +0800
> +++ next/include/linux/writeback.h	2012-01-07 21:13:09.008000026 +0800
> @@ -25,11 +25,6 @@ DECLARE_PER_CPU(int, dirty_throttle_leak
>  #define DIRTY_SCOPE		8
>  #define DIRTY_FULL_SCOPE	(DIRTY_SCOPE / 2)
>  
> -/*
> - * 4MB minimal write chunk size
> - */
> -#define MIN_WRITEBACK_PAGES	(4096UL >> (PAGE_CACHE_SHIFT - 10))
> -
>  struct backing_dev_info;
>  
>  /*


-- 
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

^ permalink raw reply

* Re: [PATCH -next] fs: fix fs/fs-writeback.c build error
From: Wu Fengguang @ 2012-01-07 13:30 UTC (permalink / raw)
  To: Linus Torvalds
  Cc: Randy Dunlap, Stephen Rothwell, linux-next, LKML, Al Viro,
	Andrew Morton
In-Reply-To: <CA+55aFx7vzez6C5M6EmZPDmkHig-mY=p64vZWWmWWe-nmxH4=w@mail.gmail.com>

On Fri, Jan 06, 2012 at 03:01:09PM -0800, Linus Torvalds wrote:
> On Thu, Jan 5, 2012 at 4:18 PM, Randy Dunlap <rdunlap@xenotime.net> wrote:
> >
> > In linux-next, fs/fs-writeback.c no longer #includes <linux/buffer_head.h>,
> > which #included <linux/pagemap.h>, so add that latter header file to
> > <linux/writeback.h> to fix the build error:
> >
> > fs/fs-writeback.c:510:11: error: 'PAGE_CACHE_SHIFT' undeclared (first use in this function)
> 
> I would actually suggest:
> 
>  - move the whole MIN_WRITEBACK_PAGES #define from the header file to
> fs/writeback.c

Done.

> (why expose such a random #define to outside users that
> have nothing to do with it?)
 
Yeah, there were some early patches that reference MIN_WRITEBACK_PAGES
from other files, which are dropped later..

>  - make sure that fs/fs-writeback.c has that pagemap.h #include.

Done. (otherwise it won't compile)

> There's no reason why <linux/writeback.h> should include filemap.h per
> se, and there is no reason why it should expose some internal chunking
> #define to anybody else.

Good point. I'll queue this patch to writeback-for-next:

Subject: writeback: move MIN_WRITEBACK_PAGES to fs-writeback.c
Date: Sat Jan 07 20:41:55 CST 2012

Fix compile error

 fs/fs-writeback.c:515:33: error: ‘PAGE_CACHE_SHIFT’ undeclared (first use in this function)

Reported-by: Randy Dunlap <rdunlap@xenotime.net>
Signed-off-by: Wu Fengguang <fengguang.wu@intel.com>
---
 fs/fs-writeback.c         |    6 ++++++
 include/linux/writeback.h |    5 -----
 2 files changed, 6 insertions(+), 5 deletions(-)

--- next.orig/fs/fs-writeback.c	2012-01-07 21:01:34.552000061 +0800
+++ next/fs/fs-writeback.c	2012-01-07 21:22:45.504000051 +0800
@@ -20,6 +20,7 @@
 #include <linux/sched.h>
 #include <linux/fs.h>
 #include <linux/mm.h>
+#include <linux/pagemap.h>
 #include <linux/kthread.h>
 #include <linux/freezer.h>
 #include <linux/writeback.h>
@@ -29,6 +30,11 @@
 #include "internal.h"
 
 /*
+ * 4MB minimal write chunk size
+ */
+#define MIN_WRITEBACK_PAGES	(4096UL >> (PAGE_CACHE_SHIFT - 10))
+
+/*
  * Passed into wb_writeback(), essentially a subset of writeback_control
  */
 struct wb_writeback_work {
--- next.orig/include/linux/writeback.h	2012-01-07 21:01:34.544000059 +0800
+++ next/include/linux/writeback.h	2012-01-07 21:13:09.008000026 +0800
@@ -25,11 +25,6 @@ DECLARE_PER_CPU(int, dirty_throttle_leak
 #define DIRTY_SCOPE		8
 #define DIRTY_FULL_SCOPE	(DIRTY_SCOPE / 2)
 
-/*
- * 4MB minimal write chunk size
- */
-#define MIN_WRITEBACK_PAGES	(4096UL >> (PAGE_CACHE_SHIFT - 10))
-
 struct backing_dev_info;
 
 /*

^ permalink raw reply

* Re: linux-next: Tree for Dec 28 (via_wdt)
From: Wim Van Sebroeck @ 2012-01-07 10:20 UTC (permalink / raw)
  To: Randy Dunlap
  Cc: Stephen Rothwell, linux-next, LKML, Marc Vertes, linux-watchdog
In-Reply-To: <4F07B291.4040608@xenotime.net>

Hi Randy,

> >> via_wdt needs a MODULE_LICENSE():
> >>
> >> WARNING: modpost: missing MODULE_LICENSE() in drivers/watchdog/via_wdt.o
> >> see include/linux/module.h for more information
> > 
> > Fixed.
> 
> Not yet in linux-next ??

I noticed it yesterday afternoon also. So I "re-fixed" (and double-checked) it yesterday in the afternoon.
So will be in linux-next with the next pull.

Kind regards,
Wim.

^ permalink raw reply

* Re: linux-next: build failure after merge of the battery tree
From: Jeremy Fitzhardinge @ 2012-01-07  9:00 UTC (permalink / raw)
  To: Anton Vorontsov; +Cc: Stephen Rothwell, linux-next, linux-kernel
In-Reply-To: <20120105152536.GB28629@oksana.dev.rtsoft.ru>

On 01/06/2012 02:25 AM, Anton Vorontsov wrote:
> On Thu, Jan 05, 2012 at 02:40:42PM +1100, Stephen Rothwell wrote:
>> Hi Anton,
>>
>> After merging the battery tree, today's linux-next build (x86_64
>> allmodconfig) failed like this:
>>
>> ERROR: "sysfs_create_link_nowarn" [drivers/power/power_supply.ko] undefined!
>>
>> Caused by commit 8351665195ce ("power_supply: allow a power supply to
>> explicitly point to powered device").  That symbol is not exported to
>> modules.
>>
>> I have used the battery tree from next-20120104 for today.
> Thanks for catching this, Stephen!
>
> I wonder why do we need to use _nowarn variant?..
>
> Something tells me that we actually want a warning.
>
> Jeremy, are you OK with the patch down below?

Yep, that's fine.

    J

>
> - - - -
> From: Anton Vorontsov <cbouatmailru@gmail.com>
> Subject: power_supply: Drop usage of nowarn variant of sysfs_create_link()
>
> The function is not exported to modules, plus we do want to catch anyone
> who tries to create complex hierarchy (in that case we'd need to change
> 'powers' symlink to a directory, probably under a different name to not
> break ABI).
>
> This patch fixes the following build error:
>
>  ERROR: "sysfs_create_link_nowarn" [drivers/power/power_supply.ko] undefined!
>
> Reported-by: Stephen Rothwell <sfr@canb.auug.org.au>
> Signed-off-by: Anton Vorontsov <cbouatmailru@gmail.com>
> ---
>  drivers/power/power_supply_core.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/power/power_supply_core.c b/drivers/power/power_supply_core.c
> index b10c121..47f4e11 100644
> --- a/drivers/power/power_supply_core.c
> +++ b/drivers/power/power_supply_core.c
> @@ -149,7 +149,7 @@ EXPORT_SYMBOL_GPL(power_supply_get_by_name);
>  
>  int power_supply_powers(struct power_supply *psy, struct device *dev)
>  {
> -	return sysfs_create_link_nowarn(&psy->dev->kobj, &dev->kobj, "powers");
> +	return sysfs_create_link(&psy->dev->kobj, &dev->kobj, "powers");
>  }
>  EXPORT_SYMBOL_GPL(power_supply_powers);
>  

^ permalink raw reply

* Re: linux-next: manual merge of the arm-soc tree with the arm tree
From: Stephen Rothwell @ 2012-01-07  6:53 UTC (permalink / raw)
  To: Shawn Guo
  Cc: Nicolas Pitre, Hui Wang, Arnd Bergmann, linux-kernel, linux-next,
	Russell King, Olof Johansson, linux-arm-kernel
In-Reply-To: <20120107044439.GE4790@S2101-09.ap.freescale.net>


[-- Attachment #1.1: Type: text/plain, Size: 1841 bytes --]

Hi Shawn,

On Sat, 7 Jan 2012 12:44:42 +0800 Shawn Guo <shawn.guo@linaro.org> wrote:
>
> On Fri, Jan 06, 2012 at 12:03:45PM +1100, Stephen Rothwell wrote:
> > diff --cc arch/arm/mach-imx/mm-imx5.c
> > index 65139a6,bc17dfe..0000000
> > --- a/arch/arm/mach-imx/mm-imx5.c
> > +++ b/arch/arm/mach-imx/mm-imx5.c
> > @@@ -21,9 -22,27 +22,24 @@@
> >   #include <mach/devices-common.h>
> >   #include <mach/iomux-v3.h>
> >   
> > + static struct clk *gpc_dvfs_clk;
> > + 
> >   static void imx5_idle(void)
> >   {
> >  -	if (!need_resched()) {
> >  -		/* gpc clock is needed for SRPG */
> >  -		if (gpc_dvfs_clk == NULL) {
> >  -			gpc_dvfs_clk = clk_get(NULL, "gpc_dvfs");
> >  -			if (IS_ERR(gpc_dvfs_clk))
> >  -				goto err0;
> >  -		}
> >  -		clk_enable(gpc_dvfs_clk);
> >  -		mx5_cpu_lp_set(WAIT_UNCLOCKED_POWER_OFF);
> >  -		if (tzic_enable_wake())
> >  -			goto err1;
> >  -		cpu_do_idle();
> >  -err1:
> >  -		clk_disable(gpc_dvfs_clk);
> > ++	/* gpc clock is needed for SRPG */
> > ++	if (gpc_dvfs_clk == NULL) {
> > ++		gpc_dvfs_clk = clk_get(NULL, "gpc_dvfs");
> > ++		if (IS_ERR(gpc_dvfs_clk))
> > ++			goto err0;
> > + 	}
> > ++	clk_enable(gpc_dvfs_clk);
> >  +	mx5_cpu_lp_set(WAIT_UNCLOCKED_POWER_OFF);
> > ++	if (tzic_enable_wake())
> > ++		goto err1;
> > ++	cpu_do_idle();
> > ++err1:
> > ++	clk_disable(gpc_dvfs_clk);
> > + err0:
> >  -	local_irq_enable();
> 
> This results in a compile error.
> 
>   CC      arch/arm/mach-imx/mm-imx5.o
> arch/arm/mach-imx/mm-imx5.c: In function ‘imx5_idle’:
> arch/arm/mach-imx/mm-imx5.c:42:1: error: label at end of compound statement

Ooops.  Sorry about that.  Just remove the label and turn the "goto err0"
into "return".

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #1.2: Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 176 bytes --]

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

^ permalink raw reply

* Re: linux-next: manual merge of the arm-soc tree with the arm tree
From: Stephen Rothwell @ 2012-01-07  6:48 UTC (permalink / raw)
  To: Shawn Guo
  Cc: Olof Johansson, Arnd Bergmann, linux-arm-kernel, linux-next,
	linux-kernel, Hui Wang, Russell King, Nicolas Pitre
In-Reply-To: <20120107054829.GF4790@S2101-09.ap.freescale.net>

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

Hi Shawn,

On Sat, 7 Jan 2012 13:48:31 +0800 Shawn Guo <shawn.guo@linaro.org> wrote:
>
> On Fri, Jan 06, 2012 at 12:03:45PM +1100, Stephen Rothwell wrote:
> > 
> > Today's linux-next merge of the arm-soc tree got a conflict in
> > arch/arm/mach-imx/mm-imx5.c between commit 9bdd46257ab3 ("ARM: plat-mxc:
> > hook special idle handlers to arm_pm_idle") from the arm tree and commit
> > 010dc8af8f28 ("ARM: mx5: use generic irq chip pm interface for pm
> > functions on") from the arm-soc tree.
> > 
> > I fixed it up (I think - see below) and can carry the fix as necessary.
> 
> When I was testing this fix on next-20120106, I spotted another compile
> error from this file.
> 
>   CC      arch/arm/mach-imx/mm-imx5.o
> arch/arm/mach-imx/mm-imx5.c:58:24: error: redefinition of ‘mx50_io_desc’
> arch/arm/mach-imx/mm-imx5.c:48:24: note: previous definition of ‘mx50_io_desc’ was here
> arch/arm/mach-imx/mm-imx5.c:48:24: warning: ‘mx50_io_desc’ defined but not used
> 
> The fix could just be removing the duplication.

Yeah, sometimes (I think it has happened to me about 3 times over the
last 2.5 years) both sides of a merge will insert the same function and
git does not notice (they are to far apart or the context is not unique)
and inserts them both as part of the automatic merge.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply

* Re: linux-next: manual merge of the vfs tree with the v9fs tree
From: Stephen Rothwell @ 2012-01-07  6:44 UTC (permalink / raw)
  To: Eric Van Hensbergen; +Cc: Al Viro, linux-next, linux-kernel, Joe Perches
In-Reply-To: <CAFkjPTndww2mu16gCa9cn7V=0t0wvYgPQ1wQGz0q0B=Fk6xQbA@mail.gmail.com>

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

Hi Eric,

On Fri, 6 Jan 2012 22:38:57 -0600 Eric Van Hensbergen <ericvh@gmail.com> wrote:
>
> What's typically the right process for me to prep the merge for Linus?
> Should I pull Al's patchset and then apply mine on top of it so I can
> merge your merge fix or just have my for-linus tree based on his
> current working merge (which I assume has Al's by now).  Just a bit
> confused because rebasing was discouraged last merge window -- but not
> sure how to deal with the conflict without a rebase....

Just warn Linus that there will be a conflict with Al's stuff.  You could
supply him with the patch I gave you just for good measure, but he is
good (better then me) at fixing merge conflicts and will ping you if he
has doubts.

i.e. don't rebase or even bother doing the merge yourself.  Just ask him
to pull what was in linux-next.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply

* linux-next: net/smsc911x compile error on next-20120106
From: Shawn Guo @ 2012-01-07  5:55 UTC (permalink / raw)
  To: Stephen Rothwell, David Miller; +Cc: netdev, linux-next, linux-arm-kernel

Hi Stephen, David,

I just ran into the following compile error when building
next-20120106 with imx_v6_v7_defconfig.

  CC      drivers/net/ethernet/smsc/smsc911x.o
drivers/net/ethernet/smsc/smsc911x.c: In function
‘smsc911x_phy_disable_energy_detect’:
drivers/net/ethernet/smsc/smsc911x.c:1329:32: error:
‘MII_LAN83C185_CTRL_STATUS’ undeclared (first use in this function)
drivers/net/ethernet/smsc/smsc911x.c:1329:32: note: each undeclared
identifier is reported only once for each function it appears in
drivers/net/ethernet/smsc/smsc911x.c:1340:12: error:
‘MII_LAN83C185_EDPWRDOWN’ undeclared (first use in this function)
drivers/net/ethernet/smsc/smsc911x.c:1341:13: error:
‘MII_LAN83C185_ENERGYON’ undeclared (first use in this function)
drivers/net/ethernet/smsc/smsc911x.c: In function
‘smsc911x_phy_enable_energy_detect’:
drivers/net/ethernet/smsc/smsc911x.c:1364:32: error:
‘MII_LAN83C185_CTRL_STATUS’ undeclared (first use in this function)
drivers/net/ethernet/smsc/smsc911x.c:1372:13: error:
‘MII_LAN83C185_EDPWRDOWN’ undeclared (first use in this function)

-- 
Regards,
Shawn

^ permalink raw reply

* Re: linux-next: manual merge of the arm-soc tree with the arm tree
From: Shawn Guo @ 2012-01-07  5:48 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Olof Johansson, Arnd Bergmann, linux-arm-kernel, linux-next,
	linux-kernel, Hui Wang, Russell King, Nicolas Pitre
In-Reply-To: <20120106120345.8157a839b1c924315d728eea@canb.auug.org.au>

On Fri, Jan 06, 2012 at 12:03:45PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/mach-imx/mm-imx5.c between commit 9bdd46257ab3 ("ARM: plat-mxc:
> hook special idle handlers to arm_pm_idle") from the arm tree and commit
> 010dc8af8f28 ("ARM: mx5: use generic irq chip pm interface for pm
> functions on") from the arm-soc tree.
> 
> I fixed it up (I think - see below) and can carry the fix as necessary.

Hi Stephen,

When I was testing this fix on next-20120106, I spotted another compile
error from this file.

  CC      arch/arm/mach-imx/mm-imx5.o
arch/arm/mach-imx/mm-imx5.c:58:24: error: redefinition of ‘mx50_io_desc’
arch/arm/mach-imx/mm-imx5.c:48:24: note: previous definition of ‘mx50_io_desc’ was here
arch/arm/mach-imx/mm-imx5.c:48:24: warning: ‘mx50_io_desc’ defined but not used

The fix could just be removing the duplication.

-- 
Regards,
Shawn


8<----
@@ -53,16 +54,6 @@ static struct map_desc mx50_io_desc[] __initdata = {
 };

 /*
- * Define the MX50 memory map.
- */
-static struct map_desc mx50_io_desc[] __initdata = {
-       imx_map_entry(MX50, TZIC, MT_DEVICE),
-       imx_map_entry(MX50, SPBA0, MT_DEVICE),
-       imx_map_entry(MX50, AIPS1, MT_DEVICE),
-       imx_map_entry(MX50, AIPS2, MT_DEVICE),
-};
-
-/*

^ permalink raw reply

* Re: linux-next: manual merge of the vfs tree with the v9fs tree
From: Eric Van Hensbergen @ 2012-01-07  4:38 UTC (permalink / raw)
  To: Stephen Rothwell; +Cc: Al Viro, linux-next, linux-kernel, Joe Perches
In-Reply-To: <20120106134658.7589dec177541808dad20eb9@canb.auug.org.au>

What's typically the right process for me to prep the merge for Linus?
Should I pull Al's patchset and then apply mine on top of it so I can
merge your merge fix or just have my for-linus tree based on his
current working merge (which I assume has Al's by now).  Just a bit
confused because rebasing was discouraged last merge window -- but not
sure how to deal with the conflict without a rebase....

         -eric

On Thu, Jan 5, 2012 at 8:46 PM, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Al,
>
> Today's linux-next merge of the vfs tree got conflicts in
> fs/9p/vfs_inode.c and fs/9p/vfs_inode_dotl.c between commit 5d3851530d6d
> ("9p: Reduce object size with CONFIG_NET_9P_DEBUG") from the v9fs tree
> and commits c2837de73e80 ("9p: don't bother with unixmode2p9mode() for
> link() and symlink()") and 3eda0de677b5 ("9p: propagate umode_t") from
> the vfs tree.
>
> I fixed it up (see below) and can carry the fix as necessary.
> --
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
>
> diff --cc fs/9p/vfs_inode.c
> index c8fe480,e0f20de..0000000
> --- a/fs/9p/vfs_inode.c
> +++ b/fs/9p/vfs_inode.c
> @@@ -127,14 -94,14 +122,14 @@@ static int p9mode2perm(struct v9fs_sess
>   * @rdev: major number, minor number in case of device files.
>   *
>   */
> - static int p9mode2unixmode(struct v9fs_session_info *v9ses,
> -                          struct p9_wstat *stat, dev_t *rdev)
> + static umode_t p9mode2unixmode(struct v9fs_session_info *v9ses,
> +                              struct p9_wstat *stat, dev_t *rdev)
>  {
>        int res;
> -       int mode = stat->mode;
> +       u32 mode = stat->mode;
>
>  -      res = mode & S_IALLUGO;
>        *rdev = 0;
>  +      res = p9mode2perm(v9ses, stat);
>
>        if ((mode & P9_DMDIR) == P9_DMDIR)
>                res |= S_IFDIR;
> @@@ -352,8 -329,8 +346,8 @@@ int v9fs_init_inode(struct v9fs_session
>
>                break;
>        default:
> -               p9_debug(P9_DEBUG_ERROR, "BAD mode 0x%x S_IFMT 0x%x\n",
>  -              P9_DPRINTK(P9_DEBUG_ERROR, "BAD mode 0x%hx S_IFMT 0x%x\n",
>  -                         mode, mode & S_IFMT);
> ++              p9_debug(P9_DEBUG_ERROR, "BAD mode 0x%hx S_IFMT 0x%x\n",
>  +                       mode, mode & S_IFMT);
>                err = -EINVAL;
>                goto error;
>        }
> @@@ -375,7 -352,7 +369,7 @@@ struct inode *v9fs_get_inode(struct sup
>        struct inode *inode;
>        struct v9fs_session_info *v9ses = sb->s_fs_info;
>
> -       p9_debug(P9_DEBUG_VFS, "super block: %p mode: %o\n", sb, mode);
>  -      P9_DPRINTK(P9_DEBUG_VFS, "super block: %p mode: %ho\n", sb, mode);
> ++      p9_debug(P9_DEBUG_VFS, "super block: %p mode: %ho\n", sb, mode);
>
>        inode = new_inode(sb);
>        if (!inode) {
> @@@ -1362,10 -1333,10 +1355,10 @@@ static int v9fs_vfs_mkspecial(struct in
>  static int
>  v9fs_vfs_symlink(struct inode *dir, struct dentry *dentry, const char *symname)
>  {
>  -      P9_DPRINTK(P9_DEBUG_VFS, " %lu,%s,%s\n", dir->i_ino,
>  -                                      dentry->d_name.name, symname);
>  +      p9_debug(P9_DEBUG_VFS, " %lu,%s,%s\n",
>  +               dir->i_ino, dentry->d_name.name, symname);
>
> -       return v9fs_vfs_mkspecial(dir, dentry, S_IFLNK, symname);
> +       return v9fs_vfs_mkspecial(dir, dentry, P9_DMSYMLINK, symname);
>  }
>
>  /**
> @@@ -1419,14 -1391,16 +1412,16 @@@ clunk_fid
>   */
>
>  static int
> - v9fs_vfs_mknod(struct inode *dir, struct dentry *dentry, int mode, dev_t rdev)
> + v9fs_vfs_mknod(struct inode *dir, struct dentry *dentry, umode_t mode, dev_t rdev)
>  {
> +       struct v9fs_session_info *v9ses = v9fs_inode2v9ses(dir);
>        int retval;
>        char *name;
> +       u32 perm;
>
> -       p9_debug(P9_DEBUG_VFS, " %lu,%s mode: %x MAJOR: %u MINOR: %u\n",
>  -      P9_DPRINTK(P9_DEBUG_VFS,
>  -              " %lu,%s mode: %hx MAJOR: %u MINOR: %u\n", dir->i_ino,
>  -              dentry->d_name.name, mode, MAJOR(rdev), MINOR(rdev));
> ++      p9_debug(P9_DEBUG_VFS, " %lu,%s mode: %hx MAJOR: %u MINOR: %u\n",
>  +               dir->i_ino, dentry->d_name.name, mode,
>  +               MAJOR(rdev), MINOR(rdev));
>
>        if (!new_valid_dev(rdev))
>                return -EINVAL;
> diff --cc fs/9p/vfs_inode_dotl.c
> index 73488fb,8ef152a..0000000
> --- a/fs/9p/vfs_inode_dotl.c
> +++ b/fs/9p/vfs_inode_dotl.c
> @@@ -283,8 -283,8 +283,8 @@@ v9fs_vfs_create_dotl(struct inode *dir
>        }
>
>        name = (char *) dentry->d_name.name;
> -       p9_debug(P9_DEBUG_VFS, "name:%s flags:0x%x mode:0x%x\n",
> -                name, flags, omode);
>  -      P9_DPRINTK(P9_DEBUG_VFS, "v9fs_vfs_create_dotl: name:%s flags:0x%x "
> ++      p9_debug(P9_DEBUG_VFS, "v9fs_vfs_create_dotl: name:%s flags:0x%x "
> +                       "mode:0x%hx\n", name, flags, omode);
>
>        dfid = v9fs_fid_lookup(dentry->d_parent);
>        if (IS_ERR(dfid)) {
> @@@ -810,9 -813,9 +810,9 @@@ v9fs_vfs_mknod_dotl(struct inode *dir,
>        struct dentry *dir_dentry;
>        struct posix_acl *dacl = NULL, *pacl = NULL;
>
> -       p9_debug(P9_DEBUG_VFS, " %lu,%s mode: %x MAJOR: %u MINOR: %u\n",
>  -      P9_DPRINTK(P9_DEBUG_VFS,
>  -              " %lu,%s mode: %hx MAJOR: %u MINOR: %u\n", dir->i_ino,
>  -              dentry->d_name.name, omode, MAJOR(rdev), MINOR(rdev));
> ++      p9_debug(P9_DEBUG_VFS, " %lu,%s mode: %hx MAJOR: %u MINOR: %u\n",
>  +               dir->i_ino, dentry->d_name.name, omode,
>  +               MAJOR(rdev), MINOR(rdev));
>
>        if (!new_valid_dev(rdev))
>                return -EINVAL;

^ permalink raw reply

* Re: linux-next: manual merge of the arm-soc tree with the arm tree
From: Shawn Guo @ 2012-01-07  4:44 UTC (permalink / raw)
  To: Stephen Rothwell
  Cc: Olof Johansson, Arnd Bergmann, linux-arm-kernel, linux-next,
	linux-kernel, Hui Wang, Russell King, Nicolas Pitre
In-Reply-To: <20120106120345.8157a839b1c924315d728eea@canb.auug.org.au>

Hi Stephen,

On Fri, Jan 06, 2012 at 12:03:45PM +1100, Stephen Rothwell wrote:
> diff --cc arch/arm/mach-imx/mm-imx5.c
> index 65139a6,bc17dfe..0000000
> --- a/arch/arm/mach-imx/mm-imx5.c
> +++ b/arch/arm/mach-imx/mm-imx5.c
> @@@ -21,9 -22,27 +22,24 @@@
>   #include <mach/devices-common.h>
>   #include <mach/iomux-v3.h>
>   
> + static struct clk *gpc_dvfs_clk;
> + 
>   static void imx5_idle(void)
>   {
>  -	if (!need_resched()) {
>  -		/* gpc clock is needed for SRPG */
>  -		if (gpc_dvfs_clk == NULL) {
>  -			gpc_dvfs_clk = clk_get(NULL, "gpc_dvfs");
>  -			if (IS_ERR(gpc_dvfs_clk))
>  -				goto err0;
>  -		}
>  -		clk_enable(gpc_dvfs_clk);
>  -		mx5_cpu_lp_set(WAIT_UNCLOCKED_POWER_OFF);
>  -		if (tzic_enable_wake())
>  -			goto err1;
>  -		cpu_do_idle();
>  -err1:
>  -		clk_disable(gpc_dvfs_clk);
> ++	/* gpc clock is needed for SRPG */
> ++	if (gpc_dvfs_clk == NULL) {
> ++		gpc_dvfs_clk = clk_get(NULL, "gpc_dvfs");
> ++		if (IS_ERR(gpc_dvfs_clk))
> ++			goto err0;
> + 	}
> ++	clk_enable(gpc_dvfs_clk);
>  +	mx5_cpu_lp_set(WAIT_UNCLOCKED_POWER_OFF);
> ++	if (tzic_enable_wake())
> ++		goto err1;
> ++	cpu_do_idle();
> ++err1:
> ++	clk_disable(gpc_dvfs_clk);
> + err0:
>  -	local_irq_enable();

This results in a compile error.

  CC      arch/arm/mach-imx/mm-imx5.o
arch/arm/mach-imx/mm-imx5.c: In function ‘imx5_idle’:
arch/arm/mach-imx/mm-imx5.c:42:1: error: label at end of compound statement

Regards,
Shawn

>   }
>   
>   /*

^ permalink raw reply


This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox