netdev - Re: [PATCH v6] net/hsr: Add support for the High-availability Seamless Redundancy protocol (HSRv0)

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: <5277F6D6.9040807@xdin.com>
Date:	Mon, 4 Nov 2013 20:34:46 +0100
From:	Arvid Brodin <arvid.brodin@...n.com>
To:	Joe Perches <joe@...ches.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Stephen Hemminger <shemminger@...tta.com>,
	Javier Boticario <jboticario@...il.com>,
	"balferreira@...glemail.com" <balferreira@...glemail.com>,
	Elías Molina Muñoz <elias.molina@....es>
Subject: Re: [PATCH v6] net/hsr: Add support for the High-availability Seamless
 Redundancy protocol (HSRv0)

On 2013-10-30 21:15, Joe Perches wrote:
> On Wed, 2013-10-30 at 21:10 +0100, Arvid Brodin wrote:
>> High-availability Seamless Redundancy ("HSR") provides instant failover
>> redundancy for Ethernet networks. It requires a special network topology where
>> all nodes are connected in a ring (each node having two physical network
>> interfaces). It is suited for applications that demand high availability and
>> very short reaction time.
> 
> Thanks Arvid.  Maybe add a MAINTAINERS entry too?

Something like this?

 S:     Maintained
 F:     drivers/net/usb/hso.c
 
+HSR NETWORK PROTOCOL
+M:     Arvid Brodin <arvid.brodin@...n.com>
+L:     netdev@...r.kernel.org
+S:     Maintained
+F:     net/hsr/*
+
 HTCPEN TOUCHSCREEN DRIVER
 M:     Pau Oliva Fora <pof@...ack.org>
 L:     linux-input@...r.kernel.org

This would indicate that people should CC me when they send patches or find bugs, 
and that I should review the patch within a couple of weeks and get back to the
sender and the list with my comments, right? Just making sure I understand what 
would be expected of me.

And where should the MAINTAINERS patch go - to netdev or to lkml?


-- 
Arvid Brodin | Consultant (Linux)
XDIN AB | Knarrarnäsgatan 7 | SE-164 40 Kista | Sweden | xdin.com

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