netdev - Re: [patch net-next RFC 0/2] ipv6: allow temporary address management for user-created addresses

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]

Date:	Mon, 11 Nov 2013 22:04:04 +0100
From:	Jiri Pirko <jiri@...nulli.us>
To:	David Miller <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, kuznet@....inr.ac.ru, jmorris@...ei.org,
	yoshfuji@...ux-ipv6.org, kaber@...sh.net, thaller@...hat.com,
	stephen@...workplumber.org, hannes@...essinduktion.org,
	vyasevich@...il.com, dcbw@...hat.com
Subject: Re: [patch net-next RFC 0/2] ipv6: allow temporary address
 management for user-created addresses

Mon, Nov 11, 2013 at 09:01:52PM CET, davem@...emloft.net wrote:
>From: Jiri Pirko <jiri@...nulli.us>
>Date: Mon, 11 Nov 2013 20:49:01 +0100
>
>> Mon, Nov 11, 2013 at 07:42:43PM CET, davem@...emloft.net wrote:
>>>
>>>I'm not really going to read patches not properly at least CC:'d to
>>>netdev, sorry Jiri.
>> 
>> netdev is in "To:"
>> 
>> I marked the patches as "RFC" on patchwork. Maybe I should not do it
>> next time, right?
>
>I think you sent this multiple times, once without netdev in the CC: and
>then again with it present.
>
>In any event you did the right thing in the end, sorry about that :)

Nope, I sent this only once.

Anyway, should I touch the state in netdev patchwork or should I always
leave that to you?

I'm used to set "changes requested" before I send another patch version
and "RFC" when I send RFC patch.

Thanks.

Jiri

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html