linux-kernel - Re: linux-next: Tree for July 27

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 27 Jul 2010 12:54:22 +0530
From:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
	Avi Kivity <avi@...hat.com>,
	Linux SCSI List <linux-scsi@...r.kernel.org>
Subject: Re: linux-next: Tree for July 27

Hello Stephen,

On Tue, Jul 27, 2010 at 11:37 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> Changes since 20100726:
>
> The arm tree lost its conflict.
>
> The microblaze tree lost its conflict.
>
> The mips tree gained a build failure so I used the version from
> next-20100726.
>
> The xfs tree still has its build failure so I used the version from
> next-20100723.
>
> The ieee2394 tree gained a build failure so I used the version from
> next-20100726.
>
> The kvm tree still has its build failure.
>
> The async_tx tree gained a conflict against the arm tree.
>
> The devicetree tree lost its conflict, but gained another against the
> microblaze tree.
>
> The xen tree lost its build problems but gained a conflict against Linus'
> tree.
>
> The tip tree gained a conflict against the cpufreq tree.
>
> The tty tree gained a conflict against the genesis tree and a build
> failure for which I reverted 4 patches.
>
> The usb tree lost its conflicts.
>
> ----------------------------------------------------------------------------
>
> 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 167 trees (counting Linus' and 22 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 Jan Dittmer for adding the linux-next tree to his build tests
> at http://l4x.org/k/ , the guys at http://test.kernel.org/ and 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.
>

I am getting following compilation warnings in linux-next 20100727:

  CC [M]  arch/x86/kvm/mmu.o
arch/x86/kvm/mmu.c: In function ‘kvm_mmu_pte_write’:
arch/x86/kvm/mmu.c:2908: warning: suggest parentheses around operand
of ‘!’ or change ‘&’ to ‘&&’ or ‘!’ to ‘~’

 CC      lib/decompress_bunzip2.o
lib/decompress_bunzip2.c: In function ‘get_next_block’:
lib/decompress_bunzip2.c:511: warning: the frame size of 1968 bytes is
larger than 1024 bytes

  CC      drivers/scsi/constants.o
drivers/scsi/constants.c: In function ‘scsi_print_sense’:
drivers/scsi/constants.c:1407: warning: zero-length gnu_printf format string
drivers/scsi/constants.c:1413: warning: zero-length gnu_printf format string
drivers/scsi/constants.c: In function ‘scsi_print_result’:
drivers/scsi/constants.c:1456: warning: zero-length gnu_printf format string


  CC      drivers/scsi/sd.o
drivers/scsi/sd.c: In function ‘sd_print_sense_hdr’:
drivers/scsi/sd.c:2617: warning: zero-length gnu_printf format string
drivers/scsi/sd.c:2619: warning: zero-length gnu_printf format string
drivers/scsi/sd.c: In function ‘sd_print_result’:
drivers/scsi/sd.c:2625: warning: zero-length gnu_printf format string

Thanks,
--
Jaswinder Singh.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/