Randy Dunlap | 1 Mar 01:00 2011
Picon

Re: [PATCH upstream build breakage] acpi: several drivers depend on NET

On 02/28/11 14:42, Rafael J. Wysocki wrote:
> On Monday, February 28, 2011, Rafael J. Wysocki wrote:
>> On Monday, February 28, 2011, Randy Dunlap wrote:
>>> On Tue, 1 Feb 2011 13:03:23 +0100 Ingo Molnar wrote:
>>>
>>>> * Ingo Molnar <mingo <at> elte.hu> wrote:
>>>>
>>>>> * Randy Dunlap <randy.dunlap <at> oracle.com> wrote:
>>>>>
>>>>>> On Mon, 20 Dec 2010 20:00:13 +1100 Stephen Rothwell wrote:
>>>>>>
>>>>>>> Hi all,
>>>>>>>
>>>>>>> [The mirroring on kernel.org is running slowly]
>>>>>>>
>>>>>>> Changes since 20101217:
>>>>>>
>>>>>> ERROR: "thermal_cooling_device_register" [drivers/acpi/video.ko] undefined!
>>>>>> ERROR: "thermal_cooling_device_unregister" [drivers/acpi/video.ko] undefined!
>>>>>
>>>>> This bug has been reported two months ago, one month ago, it has been ignored twice 
>>>>> and now the bug has been pushed upstream and it's triggering there as well.
>>>>>
>>>>> What's going on?
>>>>
>>>> *Tap*, *tap*, is this thing on? :)
>>>>
>>>> acpi-video is still build-broken upstream, as of .38-rc3:
>>>>
>>>>    MODPOST 651 modules
(Continue reading)

Rafael J. Wysocki | 1 Mar 01:12 2011
Picon

Re: [PATCH upstream build breakage] acpi: several drivers depend on NET

On Tuesday, March 01, 2011, Randy Dunlap wrote:
> On 02/28/11 14:42, Rafael J. Wysocki wrote:
> > On Monday, February 28, 2011, Rafael J. Wysocki wrote:
> >> On Monday, February 28, 2011, Randy Dunlap wrote:
> >>> On Tue, 1 Feb 2011 13:03:23 +0100 Ingo Molnar wrote:
> >>>
> >>>> * Ingo Molnar <mingo <at> elte.hu> wrote:
> >>>>
> >>>>> * Randy Dunlap <randy.dunlap <at> oracle.com> wrote:
> >>>>>
> >>>>>> On Mon, 20 Dec 2010 20:00:13 +1100 Stephen Rothwell wrote:
> >>>>>>
> >>>>>>> Hi all,
> >>>>>>>
> >>>>>>> [The mirroring on kernel.org is running slowly]
> >>>>>>>
> >>>>>>> Changes since 20101217:
> >>>>>>
> >>>>>> ERROR: "thermal_cooling_device_register" [drivers/acpi/video.ko] undefined!
> >>>>>> ERROR: "thermal_cooling_device_unregister" [drivers/acpi/video.ko] undefined!
> >>>>>
> >>>>> This bug has been reported two months ago, one month ago, it has been ignored twice 
> >>>>> and now the bug has been pushed upstream and it's triggering there as well.
> >>>>>
> >>>>> What's going on?
> >>>>
> >>>> *Tap*, *tap*, is this thing on? :)
> >>>>
> >>>> acpi-video is still build-broken upstream, as of .38-rc3:
> >>>>
(Continue reading)

Stephen Rothwell | 1 Mar 04:54 2011
Picon
Picon

linux-next: manual merge of the mfd tree with the i.MX tree

Hi Samuel,

Today's linux-next merge of the mfd tree got a conflict in
arch/arm/mach-imx/mach-mx27_3ds.c arch/arm/mach-imx/mach-pcm038.c
arch/arm/mach-mx3/mach-mx31_3ds.c arch/arm/mach-mx3/mach-mx31moboard.c
between commit 5836372e8a0ba5cc633f61bc0484ee20c86f4b36 ("ARM: imx+mx3:
convert to mc13xxx MFD") from the i.MX tree and commit
e84e545d47d26644275a79fe5ebc1797bcb80910 ("mfd: mfd_cell is now
implicitly available to mc13xxx drivers") from the mfd tree.

I fixed it up (I think - see below) and can carry the fix as necessary.
--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au

diff --cc arch/arm/mach-imx/mach-mx27_3ds.c
index ba88417,4bf1962..0000000
--- a/arch/arm/mach-imx/mach-mx27_3ds.c
+++ b/arch/arm/mach-imx/mach-mx27_3ds.c
 <at>  <at>  <at>  -231,10 -227,13 +231,13  <at>  <at>  <at>  static struct mc13xxx_regulator_init_da
  };

  /* MC13783 */
 -static struct mc13783_platform_data mc13783_pdata = {
 +static struct mc13xxx_platform_data mc13783_pdata __initdata = {
- 	.regulators = mx27_3ds_regulators,
- 	.num_regulators = ARRAY_SIZE(mx27_3ds_regulators),
+ 	.regulators = {
+ 		.regulators = mx27_3ds_regulators,
+ 		.num_regulators = ARRAY_SIZE(mx27_3ds_regulators),
(Continue reading)

Stephen Rothwell | 1 Mar 05:42 2011
Picon
Picon

linux-next: build warnings after merge of the mfd tree

Hi Samuel,

After merging the mfd tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:

drivers/video/tmiofb.c: In function 'tmiofb_hw_init':
drivers/video/tmiofb.c:270: warning: initialization discards qualifiers from pointer target type
drivers/video/tmiofb.c: In function 'tmiofb_hw_mode':
drivers/video/tmiofb.c:314: warning: initialization discards qualifiers from pointer target type
drivers/video/tmiofb.c:314: warning: unused variable 'cell'
drivers/video/tmiofb.c: In function 'tmiofb_probe':
drivers/video/tmiofb.c:683: warning: initialization discards qualifiers from pointer target type
drivers/video/tmiofb.c: In function 'tmiofb_remove':
drivers/video/tmiofb.c:811: warning: initialization discards qualifiers from pointer target type
drivers/video/tmiofb.c: In function 'tmiofb_suspend':
drivers/video/tmiofb.c:941: warning: initialization discards qualifiers from pointer target type
drivers/video/tmiofb.c: In function 'tmiofb_resume':
drivers/video/tmiofb.c:973: warning: initialization discards qualifiers from pointer target type

Introduced by commits 2a79bb1d72f5ac22dff96de340d90d512f852ecb ("mfd:
mfd_cell is now implicitly available to tc6393xb drivers") and
b6361637190e6cb7acb84509499942ada69e7136 ("fb: Use mfd_data instead of
driver_data for tmio-fb").

--

-- 
Cheers,
Stephen Rothwell                    sfr <at> canb.auug.org.au
http://www.canb.auug.org.au/~sfr/
Ingo Molnar | 1 Mar 07:17 2011
Picon
Picon

[build fix] ACPI: Fix build for CONFIG_NET unset


* Rafael J. Wysocki <rjw <at> sisk.pl> wrote:

> From: Rafael J. Wysocki <rjw <at> sisk.pl>
> Subject: ACPI: Fix build for CONFIG_NET unset

Acked-by: Ingo Molnar <mingo <at> elte.hu>

(I also changed the subject line to signal that a patch has been submitted.)

Thanks,

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Stephen Rothwell | 1 Mar 07:54 2011
Picon
Picon

linux-next: build failure after merge of the final tree (devicetree tree related)

Hi Grant,

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

drivers/mtd/nand/pasemi_nand.c:221: error: variable 'pasemi_nand_driver' has initializer but
incomplete type
drivers/mtd/nand/pasemi_nand.c:223: error: unknown field 'driver' specified in initializer
drivers/mtd/nand/pasemi_nand.c:223: error: extra brace group at end of initializer
drivers/mtd/nand/pasemi_nand.c:223: error: (near initialization for 'pasemi_nand_driver')
drivers/mtd/nand/pasemi_nand.c:227: warning: excess elements in struct initializer
drivers/mtd/nand/pasemi_nand.c:227: warning: (near initialization for 'pasemi_nand_driver')
drivers/mtd/nand/pasemi_nand.c:228: error: unknown field 'probe' specified in initializer
drivers/mtd/nand/pasemi_nand.c:228: warning: excess elements in struct initializer
drivers/mtd/nand/pasemi_nand.c:228: warning: (near initialization for 'pasemi_nand_driver')
drivers/mtd/nand/pasemi_nand.c:229: error: unknown field 'remove' specified in initializer
drivers/mtd/nand/pasemi_nand.c:229: warning: excess elements in struct initializer
drivers/mtd/nand/pasemi_nand.c:229: warning: (near initialization for 'pasemi_nand_driver')
drivers/mtd/nand/pasemi_nand.c: In function 'pasemi_nand_init':
drivers/mtd/nand/pasemi_nand.c:234: warning: passing argument 1 of 'platform_driver_register'
from incompatible pointer type
include/linux/platform_device.h:124: note: expected 'struct platform_driver *' but argument is of
type 'struct latform_driver *'
drivers/mtd/nand/pasemi_nand.c: In function 'pasemi_nand_exit':
drivers/mtd/nand/pasemi_nand.c:240: warning: passing argument 1 of 'platform_driver_unregister'
from incompatible pointer type
include/linux/platform_device.h:125: note: expected 'struct platform_driver *' but argument is of
type 'struct latform_driver *'

Caused by commit ac677e82cd5c031a010458304821bb8b1e47cf24 ("dt: Eliminate
(Continue reading)

Stephen Rothwell | 1 Mar 08:11 2011
Picon
Picon

linux-next: Tree for March 1

Hi all,

Changes since 20110228:

Dropped tree: xen

The ext4 tree lost its conflict.

The v4l-dvb tree still has its build failure so I used the version from
next-20110225.

The kvm tree lost its build failure.

The sound and sound-asoc trees lost their build failure.

The mfd tree gained conflicts against the i.MX tree.

The devicetree tree lost its conflict but gained a build failure for
which I applied a patch.

The powerpc allyesconfig build is still broken by some obscure bloating
of the low memory code.

----------------------------------------------------------------------------

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
(Continue reading)

David Jander | 1 Mar 09:35 2011
Picon

Re: linux-next: manual merge of the mfd tree with the i.MX tree


Hi Stephen,

On Tue, 1 Mar 2011 14:54:36 +1100
Stephen Rothwell <sfr <at> canb.auug.org.au> wrote:
> Today's linux-next merge of the mfd tree got a conflict in
> arch/arm/mach-imx/mach-mx27_3ds.c arch/arm/mach-imx/mach-pcm038.c
> arch/arm/mach-mx3/mach-mx31_3ds.c arch/arm/mach-mx3/mach-mx31moboard.c
> between commit 5836372e8a0ba5cc633f61bc0484ee20c86f4b36 ("ARM: imx+mx3:
> convert to mc13xxx MFD") from the i.MX tree and commit
> e84e545d47d26644275a79fe5ebc1797bcb80910 ("mfd: mfd_cell is now
> implicitly available to mc13xxx drivers") from the mfd tree.
> 
> I fixed it up (I think - see below) and can carry the fix as necessary.

Your fix seems correct, although I fear I am too dumb to understand why commit
e84e545d47d26644275a79fe5ebc1797bcb80910 introduces this extra struct
nesting.... AFAICS gcc will end up doing the same as without the extra nest.

Btw, include/linux/mfd/mc13783.h should end up disappearing after you're done
merging... I hope so.

Best regards,

--

-- 
David Jander
Protonic Holland.
Mauro Carvalho Chehab | 1 Mar 12:21 2011

Re: linux-next: build failure after merge of the v4l-dvb tree

Em 28-02-2011 04:28, Hans Verkuil escreveu:
> On Monday, February 28, 2011 02:05:01 Stephen Rothwell wrote:
>> Hi Mauro,
>>
>> After merging the v4l-dvb tree, today's linux-next build (powerpc
>> ppc64_defconfig) failed like this:
>>
>> drivers/video/matrox/matroxfb_base.c: In function 'matroxfb_ioctl':
>> drivers/video/matrox/matroxfb_base.c:1155: error: 'VIDIOC_S_CTRL_OLD' undeclared (first use in
this function)
>>
>> Caused by commit 0ff69fe7cebb65856eba7feb3fd76fb4ba365bf8 ("[media] v4l:
>> removal of old, obsolete ioctls"). grep is your friend ...
>>
>> I have used the v4l-dvb tree from next-20110225 for today.
>>
> 
> Mauro,
> 
> Here is the trivial fix for this. Must remember next time that matrox borrows
> some of the V4L2 API.

Yes, patch is trivial, but your patch is incomplete ;) The correct one is attached.
Btw, videodev2.h still have the definitions for VIDIOC_*_OLD. So, I'm preparing a
more complete patch removing the docbook definitions for it.

---

matrox: Remove definition for the legacy VIDIOC_*_OLD ioctls

(Continue reading)

Grant Likely | 1 Mar 17:41 2011
Picon

Re: linux-next: build failure after merge of the final tree (devicetree tree related)

On Mon, Feb 28, 2011 at 11:54 PM, Stephen Rothwell <sfr <at> canb.auug.org.au> wrote:
> Hi Grant,
>
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
>
> drivers/mtd/nand/pasemi_nand.c:221: error: variable 'pasemi_nand_driver' has initializer but
incomplete type
> drivers/mtd/nand/pasemi_nand.c:223: error: unknown field 'driver' specified in initializer
> drivers/mtd/nand/pasemi_nand.c:223: error: extra brace group at end of initializer
> drivers/mtd/nand/pasemi_nand.c:223: error: (near initialization for 'pasemi_nand_driver')
> drivers/mtd/nand/pasemi_nand.c:227: warning: excess elements in struct initializer
> drivers/mtd/nand/pasemi_nand.c:227: warning: (near initialization for 'pasemi_nand_driver')
> drivers/mtd/nand/pasemi_nand.c:228: error: unknown field 'probe' specified in initializer
> drivers/mtd/nand/pasemi_nand.c:228: warning: excess elements in struct initializer
> drivers/mtd/nand/pasemi_nand.c:228: warning: (near initialization for 'pasemi_nand_driver')
> drivers/mtd/nand/pasemi_nand.c:229: error: unknown field 'remove' specified in initializer
> drivers/mtd/nand/pasemi_nand.c:229: warning: excess elements in struct initializer
> drivers/mtd/nand/pasemi_nand.c:229: warning: (near initialization for 'pasemi_nand_driver')
> drivers/mtd/nand/pasemi_nand.c: In function 'pasemi_nand_init':
> drivers/mtd/nand/pasemi_nand.c:234: warning: passing argument 1 of 'platform_driver_register'
from incompatible pointer type
> include/linux/platform_device.h:124: note: expected 'struct platform_driver *' but argument is of
type 'struct latform_driver *'
> drivers/mtd/nand/pasemi_nand.c: In function 'pasemi_nand_exit':
> drivers/mtd/nand/pasemi_nand.c:240: warning: passing argument 1 of 'platform_driver_unregister'
from incompatible pointer type
> include/linux/platform_device.h:125: note: expected 'struct platform_driver *' but argument is of
type 'struct latform_driver *'
>
(Continue reading)


Gmane