linux-kernel - Re: [PATCH v2 1/2] watchdog: bcm281xx: Watchdog Driver

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]

Date:	Mon, 18 Nov 2013 15:49:16 -0800
From:	Markus Mayer <markus.mayer@...aro.org>
To:	Guenter Roeck <linux@...ck-us.net>
Cc:	Wim Van Sebroeck <wim@...ana.be>,
	Christian Daudt <bcm@...thebug.org>,
	Linaro Patches <patches@...aro.org>,
	Matt Porter <matt.porter@...aro.org>,
	Linux Watchdog List <linux-watchdog@...r.kernel.org>,
	ARM Kernel List <linux-arm-kernel@...ts.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2 1/2] watchdog: bcm281xx: Watchdog Driver

On 15 November 2013 20:27, Guenter Roeck <linux@...ck-us.net> wrote:
> On 11/15/2013 12:58 PM, Markus Mayer wrote:
>>
>> This commit adds support for the watchdog timer used on the BCM281xx
>> family of SoCs.
>>
>> Signed-off-by: Markus Mayer <markus.mayer@...aro.org>
>
>
> You are using two different e-mail addresses, the one here and the one in
> MODULE_AUTHOR.
> Any chance to use only one ? Of course, there may be a reason, so maybe it
> is ok.

There is indeed reason behind the madness. I am wearing two hats of
sorts. I work for Broadcom, but I am assigned to Linaro, hence the
somewhat adventurous construction with two e-mail addresses.

I addressed your remaining comments and will be sending out v3 of the
patch shortly.

Thanks,
-Markus

-- 
Markus Mayer
Broadcom Landing Team
--
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/