From: Dan Carpenter <dan.carpenter@linaro.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Lin Ma <linma@zju.edu.cn>,
netdev@vger.kernel.org, kernel-janitors@vger.kernel.org,
Alexander Duyck <alexander.h.duyck@intel.com>,
Daniel Machon <daniel.machon@microchip.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Jeff Kirsher <jeffrey.t.kirsher@intel.com>,
Paolo Abeni <pabeni@redhat.com>,
Peter P Waskiewicz Jr <peter.p.waskiewicz.jr@intel.com>,
Petr Machata <petrm@nvidia.com>, Simon Horman <horms@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: net: dcb: Communication challenges for patch reviews?
Date: Tue, 1 Aug 2023 13:28:37 +0300 [thread overview]
Message-ID: <a03f4f45-08c7-4b7d-8f9a-328dbfbe721c@kadam.mountain> (raw)
In-Reply-To: <ed7020cb-cee5-16af-55f1-f1adac08f1b6@web.de>
I'm not trying to be mean. I don't go out looking for Markus's emails,
but he often adds kernel-janitors to the CC list. Kernel janitors is a
vger list so he's banned but we still see the responses to his emails.
In recent months probably seven maintainers have asked him over and over
(maybe 20 times?) to stop with this nonsense. So he knew he shouldn't
have asked Lin Ma to redo the patch.
regards,
dan carpenter
prev parent reply other threads:[~2023-08-01 10:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 4:52 [PATCH net v1] net: dcb: choose correct policy to parse DCB_ATTR_BCN Lin Ma
2023-07-31 10:00 ` Simon Horman
[not found] ` <fbda76a9-e1f3-d483-ab3d-3c904c54a5db@web.de>
2023-08-01 1:34 ` [PATCH net] " Lin Ma
2023-08-01 5:46 ` Dan Carpenter
2023-08-01 6:01 ` Lin Ma
[not found] ` <ed7020cb-cee5-16af-55f1-f1adac08f1b6@web.de>
2023-08-01 10:28 ` Dan Carpenter [this message]
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=a03f4f45-08c7-4b7d-8f9a-328dbfbe721c@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=Markus.Elfring@web.de \
--cc=alexander.h.duyck@intel.com \
--cc=daniel.machon@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jeffrey.t.kirsher@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=linma@zju.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=petrm@nvidia.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
all inboxes | Powered by JetHome®