From: SF Markus Elfring <elfring@users.sourceforge.net>
To: Oliver Hartkopp <socketcan@hartkopp.net>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Wolfgang Grandegger <wg@grandegger.com>,
linux-can@vger.kernel.org,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, kernel-janitors@vger.kernel.org
Subject: Re: [v2] can: Use common error handling code in vxcan_newlink()
Date: Wed, 1 Nov 2017 20:37:11 +0100 [thread overview]
Message-ID: <2346609d-85f6-6eec-e492-d15ba1b6489a@users.sourceforge.net> (raw)
In-Reply-To: <08fd31d5-8677-81e7-65d6-40d501017db6@hartkopp.net>
> Acked-by: Oliver Hartkopp <socketcan@hartkopp.net>
Thanks for another positive feedback.
> Again: Posting such a patch on linux-can@vger.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@vger.kernel.org
> linux-kernel@vger.kernel.org
These addresses were suggested (or recommended?) by the script “get_maintainer.pl”.
> kernel-janitors@vger.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
next prev parent reply other threads:[~2017-11-01 19:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 20:30 [PATCH] can: Use common error handling code in vxcan_newlink() SF Markus Elfring
2017-10-28 6:48 ` Oliver Hartkopp
2017-10-28 8:23 ` SF Markus Elfring
2017-10-28 17:40 ` Oliver Hartkopp
2017-10-28 18:33 ` SF Markus Elfring
2017-10-28 19:04 ` Oliver Hartkopp
2017-10-28 19:18 ` SF Markus Elfring
2017-10-28 19:54 ` Oliver Hartkopp
2017-10-28 20:13 ` SF Markus Elfring
2017-10-29 10:51 ` Oliver Hartkopp
2017-11-01 14:16 ` [PATCH v2] " SF Markus Elfring
2017-11-01 19:09 ` Oliver Hartkopp
2017-11-01 19:37 ` SF Markus Elfring [this message]
2017-11-02 8:22 ` [v2] " Oliver Hartkopp
2017-11-07 8:21 ` [PATCH v2] " Marc Kleine-Budde
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2346609d-85f6-6eec-e492-d15ba1b6489a@users.sourceforge.net \
--to=elfring@users.sourceforge.net \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=socketcan@hartkopp.net \
--cc=wg@grandegger.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).