linux-kernel - [GIT PULL] AVR32 fixes

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>] [day] [month] [year] [list]

Message-ID: <20081218163849.5e6a07d9@hskinnemoen-d830>
Date:	Thu, 18 Dec 2008 16:38:49 +0100
From:	Haavard Skinnemoen <haavard.skinnemoen@...el.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	AVR32 Linux Kernel <kernel@...32linux.org>
Subject: [GIT PULL] AVR32 fixes

Hi Linus,

Please pull

  git://git.kernel.org/pub/scm/linux/kernel/git/hskinnemoen/avr32-2.6.git fixes

to get the following last-minute fixes for AVR32. Most of it is a
defconfig update for ATSTK1006 enabling JFFS2 write buffering support,
without which it can't boot from a JFFS2 file system stored in NAND
flash.

There's also a fix/workaround for a new "feature" in binutils 2.18
which causes it to build unbootable kernel images.

Anders Blomdell (1):
      avr32: Enable pullup on USART TX lines

Haavard Skinnemoen (2):
      ATSTK1006: Fix boot from NAND flash
      avr32: favr-32 build fix

Hans-Christian Egtvedt (1):
      avr32: remove .note.gnu.build-id section when making vmlinux.bin

 arch/avr32/boards/favr-32/flash.c      |    2 +-
 arch/avr32/boards/favr-32/setup.c      |    8 +-
 arch/avr32/boot/images/Makefile        |    2 +-
 arch/avr32/configs/atstk1006_defconfig |  134 +++++++++++++++++++++++---------
 arch/avr32/mach-at32ap/at32ap700x.c    |    8 +-
 5 files changed, 107 insertions(+), 47 deletions(-)
--
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/