linux-kernel - Re: [PATCH V3 2/2] of: add vendor prefix for Microchip Technology Inc

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: <CACRpkdbRWH+ZyFiGH-7C+UKJQLJtQjnhoojznuwoCKqjVfssHw@mail.gmail.com>
Date:	Thu, 29 Aug 2013 20:11:49 +0200
From:	Linus Walleij <linus.walleij@...aro.org>
To:	Lars Poeschel <larsi@....tu-dresden.de>
Cc:	Lars Poeschel <poeschel@...onage.de>,
	Grant Likely <grant.likely@...aro.org>,
	Rob Herring <rob.herring@...xeda.com>,
	Pawel Moll <pawel.moll@....com>,
	Mark Rutland <mark.rutland@....com>,
	Stephen Warren <swarren@...dotorg.org>,
	Ian Campbell <ian.campbell@...rix.com>,
	Rob Landley <rob@...dley.net>, Arnd Bergmann <arnd@...db.de>,
	"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-gpio@...r.kernel.org" <linux-gpio@...r.kernel.org>
Subject: Re: [PATCH V3 2/2] of: add vendor prefix for Microchip Technology Inc

On Wed, Aug 28, 2013 at 10:38 AM, Lars Poeschel <larsi@....tu-dresden.de> wrote:

> From: Lars Poeschel <poeschel@...onage.de>
>
> Trivial patch to add Microchip Technology Inc. to the list
> of devicetree vendor prefixes.
>
> Acked-by: Mark Rutland <mark.rutland@....com>
> Signed-off-by: Lars Poeschel <poeschel@...onage.de>

Applied this as well. Tell me if it sneaked in someplace else.

Yours,
Linus Walleij
--
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/