Hi all,
[The mirroring on kernel.org is running slowly]
Changes since 20101227:
The ux500-core tree still has its build failure for which I reverted a
commit.
The net tree lost a conflict.
The sound-asoc tree still has its build failure, so I used the version
from next-20101221.
The sound tree still has its build failure, so I used the version that
would have been in next-20101223.
The trivial tree gained conflicts against the v4l-dvb tree.
The tty tree still has its build failure so I reverted a commit.
The bkl-config tree gained a conflict against the v4l-dvb tree.
----------------------------------------------------------------------------
I have created today's linux-next tree at
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
(patches at http://www.kernel.org/pub/linux/kernel/v2.6/next/ ). If you
are tracking the linux-next tree using git, you should not use "git pull"
to do so as that will try to merge the new linux-next release with the
old one. You should use "git fetch" as mentioned in the FAQ on the wiki
(see below).
You can see which trees have been included by looking in the Next/Trees
file in the source. There are also quilt-import.log and merge.log files
in the Next directory. Between each merge, the tree was built with
a ppc64_defconfig for powerpc and an allmodconfig for x86_64. After the
final fixups (if any), it is also built with powerpc allnoconfig (32 and
64 bit), ppc44x_defconfig and allyesconfig (minus
CONFIG_PROFILE_ALL_BRANCHES - this fails its final link) and i386, sparc
and sparc64 defconfig. These builds also have
CONFIG_ENABLE_WARN_DEPRECATED, CONFIG_ENABLE_MUST_CHECK and
CONFIG_DEBUG_INFO disabled when necessary.
Below is a summary of the state of the merge.
We are up to 183 trees (counting Linus' and 26 trees of patches pending
for Linus' tree), more are welcome (even if they are currently empty).
Thanks to those who have contributed, and to those who haven't, please do.
Status of my local build tests will be at
http://kisskb.ellerman.id.au/linux-next . If maintainers want to give
advice about cross compilers/configs that work, we are always open to add
more builds.
Thanks to Randy Dunlap for doing many randconfig builds.
There is a wiki covering stuff to do with linux-next at
http://linux.f-seidel.de/linux-next/pmwiki/ . Thanks to Frank Seidel.
--
Cheers,
Stephen Rothwell [email protected]
$ git checkout master
$ git reset --hard stable
Merging origin/master
Merging fixes/fixes
Merging arm-current/master
Merging m68k-current/for-linus
Merging powerpc-merge/merge
Merging sparc-current/master
Merging scsi-rc-fixes/master
Merging net-current/master
Merging sound-current/for-linus
Merging pci-current/for-linus
Merging wireless-current/master
Merging kbuild-current/rc-fixes
Merging driver-core.current/driver-core-linus
Merging tty.current/tty-linus
Merging usb.current/usb-linus
Merging staging.current/staging-linus
Merging cpufreq-current/fixes
Merging input-current/for-linus
Merging md-current/for-linus
Merging audit-current/for-linus
Merging crypto-current/master
Merging ide-curent/master
Merging dwmw2/master
Merging sh-current/sh-fixes-for-linus
Merging rmobile-current/rmobile-fixes-for-linus
Merging fbdev-current/fbdev-fixes-for-linus
Merging gcl-current/merge
Merging arm/devel
Merging davinci/davinci-next
Merging i.MX/for-next
Merging linux-spec/for-next
Merging msm/for-next
Merging omap/for-next
CONFLICT (content): Merge conflict in arch/arm/plat-omap/Kconfig
Merging pxa/for-next
Merging samsung/next-samsung
Merging s5p/for-next
Merging tegra/for-next
CONFLICT (content): Merge conflict in arch/arm/mach-tegra/timer.c
Merging ux500-core/ux500-core
Merging avr32/avr32-arch
Merging blackfin/for-linus
Merging cris/for-next
Merging ia64/test
Merging m68k/for-next
Merging m68knommu/for-next
Merging microblaze/next
Merging mips/mips-for-linux-next
Merging parisc/next
Merging powerpc/next
Merging 4xx/next
Merging 52xx-and-virtex/next
Merging galak/next
Merging s390/features
Merging sh/sh-latest
CONFLICT (content): Merge conflict in arch/sh/kernel/cpu/sh2a/clock-sh7201.c
Merging rmobile/rmobile-latest
CONFLICT (content): Merge conflict in arch/arm/mach-shmobile/Kconfig
Applying: rmobile: merge fixup for clkdev changes
Merging sparc/master
Merging tile/master
Merging xtensa/master
CONFLICT (content): Merge conflict in arch/xtensa/configs/iss_defconfig
Merging ceph/for-next
Merging cifs/master
Merging configfs/linux-next
Merging ecryptfs/next
Merging ext3/for_next
Merging ext4/next
Merging fatfs/master
Merging fuse/for-next
Merging gfs2/master
Merging hfsplus/for-next
Merging jfs/next
Merging logfs/master
CONFLICT (content): Merge conflict in fs/logfs/logfs.h
Merging nfs/linux-next
Merging nfsd/nfsd-next
Merging nilfs2/for-next
Merging ocfs2/linux-next
Merging omfs/for-next
Merging squashfs/master
Merging udf/for_next
Merging v9fs/for-next
Merging ubifs/linux-next
Merging xfs/master
Merging vfs/for-next
Merging vfs-scale/vfs-scale-working
CONFLICT (content): Merge conflict in fs/cifs/dir.c
CONFLICT (content): Merge conflict in fs/fuse/inode.c
CONFLICT (content): Merge conflict in fs/hfsplus/hfsplus_fs.h
CONFLICT (content): Merge conflict in fs/hfsplus/unicode.c
Merging pci/linux-next
Merging hid/for-next
Merging quilt/i2c
Merging bjdooks-i2c/next-i2c
Merging quilt/jdelvare-hwmon
Merging hwmon-staging/hwmon-next
Merging quilt/kernel-doc
Merging v4l-dvb/master
Merging kbuild/for-next
Merging kconfig/for-next
Merging ide/master
Merging libata/NEXT
Merging infiniband/for-next
Merging acpi/test
Merging idle-test/idle-test
Merging ieee1394/for-next
Merging ubi/linux-next
Merging kvm/linux-next
Merging dlm/next
Merging swiotlb/master
Merging ibft/master
Merging scsi/master
Merging async_tx/next
Merging net/master
CONFLICT (content): Merge conflict in net/9p/protocol.c
Merging wireless/master
Merging bluetooth/master
CONFLICT (content): Merge conflict in net/bluetooth/Makefile
Merging mtd/master
Merging crypto/master
Merging sound-asoc/for-next
CONFLICT (rename/modify): Merge conflict in sound/soc/samsung/smdk_wm8580.c
CONFLICT (rename/modify): Merge conflict in sound/soc/samsung/smdk_wm9713.c
CONFLICT (add/add): Merge conflict in arch/arm/plat-samsung/dev-asocdma.c
$ git reset --hard HEAD^
Merging refs/next/20101221/sound-asoc
CONFLICT (rename/modify): Merge conflict in sound/soc/samsung/smdk_wm8580.c
CONFLICT (rename/modify): Merge conflict in sound/soc/samsung/smdk_wm9713.c
CONFLICT (add/add): Merge conflict in arch/arm/plat-samsung/dev-asocdma.c
[master c491f55] Merge commit 'refs/next/20101221/sound-asoc'
Merging sound/for-next
$ git reset --hard HEAD^
Merging refs/next/20101223/sound
Merging cpufreq/next
Merging quilt/rr
Merging input/next
CONFLICT (content): Merge conflict in drivers/input/keyboard/Kconfig
CONFLICT (content): Merge conflict in include/linux/input.h
Merging lsm/for-next
Merging block/for-next
Merging quilt/device-mapper
Merging embedded/master
Merging firmware/master
Merging pcmcia/master
Merging battery/master
Merging leds/for-mm
CONFLICT (content): Merge conflict in drivers/leds/Kconfig
Merging backlight/for-mm
Merging mmc/mmc-next
Merging kgdb/kgdb-next
Merging slab/for-next
Merging uclinux/for-next
Merging md/for-next
Merging mfd/for-next
CONFLICT (content): Merge conflict in drivers/mfd/Makefile
CONFLICT (content): Merge conflict in drivers/mfd/wm8994-core.c
Merging hdlc/hdlc-next
Merging drm/drm-next
Merging fbdev/master
CONFLICT (content): Merge conflict in drivers/video/sh_mobile_lcdcfb.c
Merging viafb/viafb-next
Merging omap_dss2/for-next
Merging voltage/for-next
CONFLICT (content): Merge conflict in drivers/regulator/core.c
CONFLICT (content): Merge conflict in drivers/regulator/mc13783-regulator.c
Merging security-testing/next
Merging selinux/master
Merging lblnet/master
Merging agp/agp-next
Merging watchdog/master
Merging bdev/master
Merging dwmw2-iommu/master
Merging cputime/cputime
Merging osd/linux-next
Merging jc_docs/docs-next
Merging nommu/master
Merging trivial/for-next
CONFLICT (content): Merge conflict in drivers/media/video/zoran/zoran.h
CONFLICT (delete/modify): drivers/staging/stradis/stradis.c deleted in HEAD and modified in trivial/for-next. Version trivial/for-next of drivers/staging/stradis/stradis.c left in tree.
$ git rm -f drivers/staging/stradis/stradis.c
Merging audit/for-next
Merging suspend/linux-next
Merging fsnotify/for-next
Merging irda/for-next
Merging catalin/for-next
Merging alacrity/linux-next
CONFLICT (content): Merge conflict in drivers/Makefile
CONFLICT (content): Merge conflict in include/linux/Kbuild
CONFLICT (content): Merge conflict in lib/Kconfig
Merging i7core_edac/linux_next
Merging i7300_edac/linux_next
Merging devicetree/next-devicetree
Merging spi/next-spi
Merging tip/auto-latest
Merging rcu/rcu/next
Merging oprofile/for-next
Merging xen/upstream/xen
Merging swiotlb-xen/master
CONFLICT (content): Merge conflict in drivers/xen/Kconfig
CONFLICT (content): Merge conflict in drivers/xen/Makefile
Merging xen-pvhvm/linux-next
Merging edac-amd/for-next
Merging percpu/for-next
Merging workqueues/for-next
CONFLICT (content): Merge conflict in Documentation/feature-removal-schedule.txt
CONFLICT (content): Merge conflict in drivers/media/video/bt8xx/bttv-input.c
CONFLICT (content): Merge conflict in drivers/rtc/rtc-dev.c
Merging sfi/sfi-test
Merging asm-generic/next
Merging drivers-x86/linux-next
Merging hwpoison/hwpoison
Merging sysctl/master
Merging driver-core/driver-core-next
Merging tty/tty-next
[master 8b6becf] Revert "drivers: serial: apbuart: Handle OF failures gracefully"
Merging usb/usb-next
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/Kconfig
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/clock3xxx_data.c
CONFLICT (content): Merge conflict in arch/arm/mach-omap2/clock44xx_data.c
CONFLICT (content): Merge conflict in arch/sh/Kconfig
Merging staging/staging-next
Merging slabh/slabh
Merging bkl-trivial/trivial
Merging bkl-llseek/llseek
Merging bkl-vfs/vfs
Merging bkl-config/config
CONFLICT (content): Merge conflict in arch/powerpc/kernel/setup_64.c
CONFLICT (delete/modify): drivers/staging/stradis/Kconfig deleted in HEAD and modified in bkl-config/config. Version bkl-config/config of drivers/staging/stradis/Kconfig left in tree.
CONFLICT (content): Merge conflict in include/linux/hardirq.h
CONFLICT (content): Merge conflict in include/linux/smp_lock.h
$ git rm -f drivers/staging/stradis/Kconfig
Merging irqflags/master
Merging cleancache/linux-next
CONFLICT (content): Merge conflict in fs/ocfs2/super.c
CONFLICT (content): Merge conflict in fs/super.c
CONFLICT (content): Merge conflict in include/linux/fs.h
CONFLICT (content): Merge conflict in mm/Kconfig
Merging scsi-post-merge/merge-base:master
$ git checkout scsi-post-merge/master
Applying: [SCSI] target: Add LIO target core v4.0.0-rc6
Applying: [SCSI] sd: implement sd_check_events()
[master eb46944] Revert "input/tc3589x: add tc3589x keypad support"
On Tue, 28 Dec 2010 17:30:49 +1100 Stephen Rothwell wrote:
> Hi all,
>
> [The mirroring on kernel.org is running slowly]
>
> Changes since 20101227:
warning: (TARGET_CORE && GFS2_FS) selects CONFIGFS_FS which has unmet direct dependencies (SYSFS)
from:
menuconfig TARGET_CORE
tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure"
select CONFIGFS_FS
but CONFIGFS_FS depends on SYSFS, so TARGET_CORE should either depend on SYSFS
or (eek) it should select SYSFS.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
On Tue, 2010-12-28 at 08:29 -0800, Randy Dunlap wrote:
> On Tue, 28 Dec 2010 17:30:49 +1100 Stephen Rothwell wrote:
>
> > Hi all,
> >
> > [The mirroring on kernel.org is running slowly]
> >
> > Changes since 20101227:
>
>
> warning: (TARGET_CORE && GFS2_FS) selects CONFIGFS_FS which has unmet direct dependencies (SYSFS)
>
> from:
>
> menuconfig TARGET_CORE
> tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure"
> select CONFIGFS_FS
>
> but CONFIGFS_FS depends on SYSFS, so TARGET_CORE should either depend on SYSFS
> or (eek) it should select SYSFS.
The latter, I think (and actually, configfs should select sysfs). All
these unmet dependencies are a minefield.
James
On Tue, 28 Dec 2010 10:39:14 -0600 James Bottomley wrote:
> On Tue, 2010-12-28 at 08:29 -0800, Randy Dunlap wrote:
> > On Tue, 28 Dec 2010 17:30:49 +1100 Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > [The mirroring on kernel.org is running slowly]
> > >
> > > Changes since 20101227:
> >
> >
> > warning: (TARGET_CORE && GFS2_FS) selects CONFIGFS_FS which has unmet direct dependencies (SYSFS)
> >
> > from:
> >
> > menuconfig TARGET_CORE
> > tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure"
> > select CONFIGFS_FS
> >
> > but CONFIGFS_FS depends on SYSFS, so TARGET_CORE should either depend on SYSFS
> > or (eek) it should select SYSFS.
>
> The latter, I think (and actually, configfs should select sysfs). All
> these unmet dependencies are a minefield.
It's just another language to deal with. Not a big deal, except for the
twists that EXPERIMENTAL injects into it.
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
On Tue, 2010-12-28 at 08:50 -0800, Randy Dunlap wrote:
> On Tue, 28 Dec 2010 10:39:14 -0600 James Bottomley wrote:
>
> > On Tue, 2010-12-28 at 08:29 -0800, Randy Dunlap wrote:
> > > On Tue, 28 Dec 2010 17:30:49 +1100 Stephen Rothwell wrote:
> > >
> > > > Hi all,
> > > >
> > > > [The mirroring on kernel.org is running slowly]
> > > >
> > > > Changes since 20101227:
> > >
> > >
> > > warning: (TARGET_CORE && GFS2_FS) selects CONFIGFS_FS which has unmet direct dependencies (SYSFS)
> > >
> > > from:
> > >
> > > menuconfig TARGET_CORE
> > > tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure"
> > > select CONFIGFS_FS
> > >
> > > but CONFIGFS_FS depends on SYSFS, so TARGET_CORE should either depend on SYSFS
> > > or (eek) it should select SYSFS.
> >
> > The latter, I think (and actually, configfs should select sysfs). All
> > these unmet dependencies are a minefield.
>
> It's just another language to deal with. Not a big deal, except for the
> twists that EXPERIMENTAL injects into it.
I agree with James on this one.. Attached is a patch to select SYSFS
and fix up some extra whitespace breakage. (jlbec CC'ed)
Thanks,
--nab
diff --git a/fs/configfs/Kconfig b/fs/configfs/Kconfig
index 13587cc..6874d75 100644
--- a/fs/configfs/Kconfig
+++ b/fs/configfs/Kconfig
@@ -1,11 +1,11 @@
config CONFIGFS_FS
tristate "Userspace-driven configuration filesystem"
- depends on SYSFS
+ select SYSFS
help
- configfs is a ram-based filesystem that provides the converse
- of sysfs's functionality. Where sysfs is a filesystem-based
- view of kernel objects, configfs is a filesystem-based manager
- of kernel objects, or config_items.
+ configfs is a ram-based filesystem that provides the converse
+ of sysfs's functionality. Where sysfs is a filesystem-based
+ view of kernel objects, configfs is a filesystem-based manager
+ of kernel objects, or config_items.
- Both sysfs and configfs can and should exist together on the
- same system. One is not a replacement for the other.
+ Both sysfs and configfs can and should exist together on the
+ same system. One is not a replacement for the other.
On 12/28/10 11:38, Nicholas A. Bellinger wrote:
> On Tue, 2010-12-28 at 08:50 -0800, Randy Dunlap wrote:
>> On Tue, 28 Dec 2010 10:39:14 -0600 James Bottomley wrote:
>>
>>> On Tue, 2010-12-28 at 08:29 -0800, Randy Dunlap wrote:
>>>> On Tue, 28 Dec 2010 17:30:49 +1100 Stephen Rothwell wrote:
>>>>
>>>>> Hi all,
>>>>>
>>>>> [The mirroring on kernel.org is running slowly]
>>>>>
>>>>> Changes since 20101227:
>>>>
>>>>
>>>> warning: (TARGET_CORE && GFS2_FS) selects CONFIGFS_FS which has unmet direct dependencies (SYSFS)
>>>>
>>>> from:
>>>>
>>>> menuconfig TARGET_CORE
>>>> tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure"
>>>> select CONFIGFS_FS
>>>>
>>>> but CONFIGFS_FS depends on SYSFS, so TARGET_CORE should either depend on SYSFS
>>>> or (eek) it should select SYSFS.
>>>
>>> The latter, I think (and actually, configfs should select sysfs). All
>>> these unmet dependencies are a minefield.
>>
>> It's just another language to deal with. Not a big deal, except for the
>> twists that EXPERIMENTAL injects into it.
>
> I agree with James on this one.. Attached is a patch to select SYSFS
> and fix up some extra whitespace breakage. (jlbec CC'ed)
and I am not surprised. James is a more liberal 'select'or than I am.
> Thanks,
>
> --nab
>
> diff --git a/fs/configfs/Kconfig b/fs/configfs/Kconfig
> index 13587cc..6874d75 100644
> --- a/fs/configfs/Kconfig
> +++ b/fs/configfs/Kconfig
> @@ -1,11 +1,11 @@
> config CONFIGFS_FS
> tristate "Userspace-driven configuration filesystem"
> - depends on SYSFS
> + select SYSFS
> help
> - configfs is a ram-based filesystem that provides the converse
> - of sysfs's functionality. Where sysfs is a filesystem-based
> - view of kernel objects, configfs is a filesystem-based manager
> - of kernel objects, or config_items.
> + configfs is a ram-based filesystem that provides the converse
RAM-based
> + of sysfs's functionality. Where sysfs is a filesystem-based
> + view of kernel objects, configfs is a filesystem-based manager
> + of kernel objects, or config_items.
>
> - Both sysfs and configfs can and should exist together on the
> - same system. One is not a replacement for the other.
> + Both sysfs and configfs can and should exist together on the
> + same system. One is not a replacement for the other.
>
>
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
desserts: http://www.xenotime.net/linux/recipes/
On Tue, 2010-12-28 at 12:04 -0800, Randy Dunlap wrote:
> On 12/28/10 11:38, Nicholas A. Bellinger wrote:
> > On Tue, 2010-12-28 at 08:50 -0800, Randy Dunlap wrote:
> >> On Tue, 28 Dec 2010 10:39:14 -0600 James Bottomley wrote:
> >>
> >>> On Tue, 2010-12-28 at 08:29 -0800, Randy Dunlap wrote:
> >>>> On Tue, 28 Dec 2010 17:30:49 +1100 Stephen Rothwell wrote:
> >>>>
> >>>>> Hi all,
> >>>>>
> >>>>> [The mirroring on kernel.org is running slowly]
> >>>>>
> >>>>> Changes since 20101227:
> >>>>
> >>>>
> >>>> warning: (TARGET_CORE && GFS2_FS) selects CONFIGFS_FS which has unmet direct dependencies (SYSFS)
> >>>>
> >>>> from:
> >>>>
> >>>> menuconfig TARGET_CORE
> >>>> tristate "Generic Target Core Mod (TCM) and ConfigFS Infrastructure"
> >>>> select CONFIGFS_FS
> >>>>
> >>>> but CONFIGFS_FS depends on SYSFS, so TARGET_CORE should either depend on SYSFS
> >>>> or (eek) it should select SYSFS.
> >>>
> >>> The latter, I think (and actually, configfs should select sysfs). All
> >>> these unmet dependencies are a minefield.
> >>
> >> It's just another language to deal with. Not a big deal, except for the
> >> twists that EXPERIMENTAL injects into it.
> >
> > I agree with James on this one.. Attached is a patch to select SYSFS
> > and fix up some extra whitespace breakage. (jlbec CC'ed)
>
> and I am not surprised. James is a more liberal 'select'or than I am.
;)
>
> > Thanks,
> >
> > --nab
> >
> > diff --git a/fs/configfs/Kconfig b/fs/configfs/Kconfig
> > index 13587cc..6874d75 100644
> > --- a/fs/configfs/Kconfig
> > +++ b/fs/configfs/Kconfig
> > @@ -1,11 +1,11 @@
> > config CONFIGFS_FS
> > tristate "Userspace-driven configuration filesystem"
> > - depends on SYSFS
> > + select SYSFS
> > help
> > - configfs is a ram-based filesystem that provides the converse
> > - of sysfs's functionality. Where sysfs is a filesystem-based
> > - view of kernel objects, configfs is a filesystem-based manager
> > - of kernel objects, or config_items.
> > + configfs is a ram-based filesystem that provides the converse
>
> RAM-based
>
Fixed, and added as a single patch into the LIO tree tracking linux-next
here:
http://git.kernel.org/?p=linux/kernel/git/nab/linux-next.git;a=commitdiff;h=87b548329a29fbe54453f9ef47819ee39a32716d
Thanks!
--nab