linux-kernel - Re: [GIT PULL] arch/tile changes for v3.12

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

Message-ID: <CA+55aFzpmUtiw7OB54XS=PbZci3FZFpFc=5K8rViFqmW-D1qkw@mail.gmail.com>
Date:	Fri, 6 Sep 2013 11:16:01 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Chris Metcalf <cmetcalf@...era.com>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] arch/tile changes for v3.12

On Fri, Sep 6, 2013 at 10:51 AM, Chris Metcalf <cmetcalf@...era.com> wrote:
>
> These changes bring in a bunch of new functionality that has been
> maintained internally at Tilera over the last year, plus other stray
> bits of work that I've taken into the tile tree from other folks.
> The changes include some PCI root complex work, interrupt-driven console
> support, support for performing fast-path unaligned data fixups by
> kernel-based JIT code generation, CONFIG_PREEMPT support, vDSO support
> for gettimeofday(), a serial driver for the tilegx on-chip UART,
> KGDB support, more optimized string routines, support for ftrace and
> kprobes, improved ASLR, and many bug fixes.  We also remove support for
> the old TILE64 chip, which is no longer buildable.

Your new tilegx on-chip uart ended up conflicting with the equally new
ST ASC serial driver..

Which had gotten the ID 105 already.

So I bumped you to 106. Yay! You're now one more.

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