Re: Please include modem_shm in linux-next

Hi Sjur,

On Tue, 31 Jan 2012 09:45:22 +0100 Sjur BRENDELAND <sjur.brandeland <at> stericsson.com> wrote:
>
> >> I would also like to hear from Linus Walleij ...
> > 
> > Please replace my repo with Sjurs (whenever it merges fine).
> > 
> > Sjur, I guess an option would be if you rebase your for-next
> > onto 3.3-rc1 as soon as it appears? 
> 
> I have rebased to v3.3-rc1. Please pull:
> git://github.com/sjurbren/modem-ipc.git for-next.
> 
> This replaces the previous branch "xshm-for-next" pulled from Linus Walleij.
> Please get back to me if you get any issues.

I have switched to this from today.

--

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

linux-next wiki: IncludedTrees

Hi Frank,

It looks like the IncludedTrees page on the linux-next wiki is broken
due to an incorrect URL for the linux-next tree:

http://linux.f-seidel.de/linux-next/pmwiki/pmwiki.php?n=Linux-next.IncludedTrees

Did the linux-next tree move? (Perhaps since the kernel.org hacking
fiasco?) And is the linux-next wiki maintained still?

Thanks,
Brian

linux-next: build failure after merge of the modem-shm tree

Hi all,

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

scripts/Makefile.headersinst:18: include/linux/shm/Kbuild: No such file or directory

Caused by commit fdefb6d63aa1 ("modem_shm: Channel config definitions for
ST-E M7400 driver").

I have used the xshm tree from next-20120131 instead for today.
--

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

linux-next: Tree for Feb 1

Hi all,

Changes since 20120131:

Renamed tree: xshm -> modem-shm

The wireless-next tree gained a conflicts against the net-next tree.

The modem-shm tree gained a build failure so I used the version from
next-20120131.

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

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/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

Re: Adding remoteproc/rpmsg to linux-next

Hi Arnd,

On Thu, Dec 22, 2011 at 5:22 PM, Arnd Bergmann <arnd <at> arndb.de> wrote:
> If you think you need more Acks or if there are other
> reasons to have it go through arm-soc, please tell me and I'll try harder
> to find the time for a proper review.

Any chance you could carve out some time for reviewing remoteproc and
rpmsg [1] ?

I hope we could either get your Acks on the patches or even have it go
through arm-soc for 3.4.

Thanks!
Ohad.

[1] git://git.kernel.org/pub/scm/linux/kernel/git/ohad/remoteproc.git
rpmsg-for-3.3

Re: Adding remoteproc/rpmsg to linux-next

On Wednesday 01 February 2012, Ohad Ben-Cohen wrote:
> On Thu, Dec 22, 2011 at 5:22 PM, Arnd Bergmann <arnd <at> arndb.de> wrote:
> > If you think you need more Acks or if there are other
> > reasons to have it go through arm-soc, please tell me and I'll try harder
> > to find the time for a proper review.
> 
> Any chance you could carve out some time for reviewing remoteproc and
> rpmsg [1] ?

I will.

> I hope we could either get your Acks on the patches or even have it go
> through arm-soc for 3.4.

Yes, I think it's best to have it merged through arm-soc, in case Linus
is more likely to take it from there than pull from your tree.

	Arnd

Re: Adding remoteproc/rpmsg to linux-next

On Wed, Feb 1, 2012 at 6:57 PM, Arnd Bergmann <arnd <at> arndb.de> wrote:
> I will.

Thanks.

> Yes, I think it's best to have it merged through arm-soc, in case Linus
> is more likely to take it from there than pull from your tree.

Great, thanks.

Ohad.

Re: linux-next: Tree for Feb 1 (media/dvb/dm1105)

On 01/31/2012 10:16 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20120131:

ERROR: "i2c_bit_add_bus" [drivers/media/dvb/dm1105/dm1105.ko] undefined!

Full randconfig file is attached.

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

#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 3.3.0-rc2 Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
# CONFIG_X86_64 is not set
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf32-i386"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/i386_defconfig"
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y
CONFIG_LOCKDEP_SUPPORT=y

Re: linux-next: Tree for Feb 1 (mce_amd.c)

On 01/31/2012 10:16 PM, Stephen Rothwell wrote:
> Hi all,
> 
> Changes since 20120131:

mce_amd.c:(.cpuinit.text+0x4723): undefined reference to `cpu_llc_shared_map'

Full randconfig file is attached.

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

#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.3.0-rc2 Kernel Configuration
#
CONFIG_64BIT=y
# CONFIG_X86_32 is not set
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT="elf64-x86-64"
CONFIG_ARCH_DEFCONFIG="arch/x86/configs/x86_64_defconfig"
CONFIG_GENERIC_CMOS_UPDATE=y
CONFIG_CLOCKSOURCE_WATCHDOG=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_ARCH_CLOCKSOURCE_DATA=y
CONFIG_GENERIC_CLOCKEVENTS_BROADCAST=y

linux-next: Tree for Feb 2

Hi all,

Changes since 20120201:

The logfs tree lost its conflicts.

The l2-mtd tree lost a conflict.

The modem-shm tree lost its build failure.

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

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/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.