linux-kernel - Re: [PATCH v6 RESEND 0/5] ARM/ARM64 architected timer updates

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:	Thu, 26 Sep 2013 10:49:57 +0100
From:	Sudeep KarkadaNagesha <Sudeep.KarkadaNagesha@....com>
To:	Arnd Bergmann <arnd@...db.de>
CC:	Daniel Lezcano <daniel.lezcano@...aro.org>,
	"arm@...nel.org" <arm@...nel.org>,
	"linux-arm-kernel@...ts.infradead.org" 
	<linux-arm-kernel@...ts.infradead.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Kevin Hilman <khilman@...aro.org>,
	Olof Johansson <olof@...om.net>
Subject: Re: [PATCH v6 RESEND 0/5] ARM/ARM64 architected timer updates

On 26/09/13 10:43, Arnd Bergmann wrote:
> On Wednesday 25 September 2013, Sudeep KarkadaNagesha wrote:
>> On 25/09/13 16:06, Daniel Lezcano wrote:
>>> On 09/18/2013 01:05 PM, Sudeep KarkadaNagesha wrote:
>>>> From: Sudeep KarkadaNagesha <sudeep.karkadanagesha@....com>
>>>>
>>>> Hi Olof/Kevin,
>>>
>>> Added Olof and Kevin in Cc.
>>>
>> Thanks Daniel, sorry I assumed mailing list alias(arm@...nel.org) was preferred way.
>>
> 
> The alias is mainly for when you are sending a pull request or a patch to
> be applied directly. For any review it makes more sense to Cc the ones you
> want involved directly.
> 
Thanks Arnd for clarification. I came across the same info yesterday from one of
the mails from Olof a while ago. I had a wrong assumption, sorry for that.

Regards,
Sudeep


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