linux-kernel - Re: [PATCH] MAINTAINERS: Update Grant's email address and maintainership

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]

Message-ID: <CACxGe6uao632OopSdWaxifanH0t2iG2gQb902L+0PW0kmG3UdQ@mail.gmail.com>
Date:	Wed, 17 Apr 2013 08:16:17 +0100
From:	Grant Likely <grant.likely@...retlab.ca>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Mark Brown <broonie@...nsource.wolfsonmicro.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Rob Herring <rob.herring@...xeda.com>
Subject: Re: [PATCH] MAINTAINERS: Update Grant's email address and maintainership

On Wed, Apr 17, 2013 at 12:52 AM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Grant,
>
> On Tue, 16 Apr 2013 11:43:36 +0100 grant.likely@...aro.org wrote:
>>
>> From: Grant Likely <grant.likely@...retlab.ca>
>>
>> I've taken a full time position with Linaro and so I'll be using my
>> Linaro email address from this point on. It has also been many years
>> since I've touched any of the Xilinx related code so mark those items as
>> unmaintained.
>>
>> In addition, Mark Brown is taking the lead on SPI maintainership now, so
>> I've reversed the order of our names for that entry.
>
> Does this have any implications for linux-next included trees or their
> contacts?

No. My old email address still works, and I'm not changing my git
trees anytime soon.

g.
--
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/