netdev - Re: [v2] can: Use common error handling code in vxcan

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:   Wed, 1 Nov 2017 20:37:11 +0100
From:   SF Markus Elfring <elfring@...rs.sourceforge.net>
To:     Oliver Hartkopp <socketcan@...tkopp.net>,
        Marc Kleine-Budde <mkl@...gutronix.de>,
        Wolfgang Grandegger <wg@...ndegger.com>,
        linux-can@...r.kernel.org,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        kernel-janitors@...r.kernel.org
Subject: Re: [v2] can: Use common error handling code in vxcan_newlink()

> Acked-by: Oliver Hartkopp <socketcan@...tkopp.net>

Thanks for another positive feedback.

> Again: Posting such a patch on linux-can@...r.kernel.org is ENOUGH!

I was informed in an other way for Linux software patches.

> No need to cross post such a patch additionally on
> 
> netdev@...r.kernel.org
> linux-kernel@...r.kernel.org

These addresses were suggested (or recommended?) by the script “get_maintainer.pl”.

> kernel-janitors@...r.kernel.org

I tend to add this address also for my update suggestions.

> and to each of the maintainers
…
> We all subscribed the mailing list and listen to it.

This is generally fine. - But I do not know how long such subscriptions
will be active.

> That's the intention of a mailing list ...

I know …

> Cross posting is not appreciated in the community.

How does this view fit to the information in the section “5) Select
the recipients for your patch” from the document “submitting-patches.rst”?

Regards,
Markus