From: Dan Carpenter <dan.carpenter@linaro.org>
To: Markus Elfring <Markus.Elfring@web.de>
Cc: Demi Marie Obenour <demi@invisiblethingslab.com>,
dm-devel@redhat.com, kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Alasdair Kergon <agk@redhat.com>,
Mike Snitzer <snitzer@kernel.org>
Subject: Re: [PATCH v2 2/4] dm ioctl: Allow userspace to provide expected diskseq
Date: Tue, 27 Jun 2023 09:14:53 +0300 [thread overview]
Message-ID: <ab9f1618-5dde-4c70-a88e-c65f33abdb73@kadam.mountain> (raw)
In-Reply-To: <1c1cd489-6d59-00ed-a1f5-497ca532c08d@web.de>
On Mon, Jun 26, 2023 at 06:20:14PM +0200, Markus Elfring wrote:
> > …, stop bothering people about trivial nonsense. …
>
> See also another bit of background information once more:
> [PATCH v2] certs/extract-cert: Fix checkpatch issues
> 2023-06-09
> https://lore.kernel.org/kernel-janitors/c464c4ee-038c-47bf-857a-b11a89680e82@kadam.mountain/
> https://lkml.org/lkml/2023/6/9/879
Markus, it's not about imperative tense. It's about you wasting
people's time.
Read the subject again. "Allow userspace to provide expected diskseq".
That is imperative tense. I have not pointed it out to you because it
just doesn't matter at all. If it's in imperative tense or if it's not
in imperative tense, it doesn't matter.
You're sending out a lot of messages and quite a few times it looks like
your targeting newbies. One new developer sent me an email privately
who was over the top grateful when I told him he could ignore you. The
guy was like, "I was so puzzled, because it's my first patch and I
didn't know how to respond." This was an experienced programmer who we
want, but he was new to the kernel community so he didn't know if we had
bizarre rules or whatever.
I've looked through your patches that have recently been merged. Some
of those maintainers know that you are banned and that your patches are
not getting any review from the mailing list. We are really trying to
be nice and to work around your situation. But don't start bothering
newbies who don't know what the situation is.
regards,
dan carpenter
next prev parent reply other threads:[~2023-06-27 6:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-24 23:09 [PATCH v2 0/4] Diskseq support in device-mapper Demi Marie Obenour
2023-06-24 23:09 ` [PATCH v2 1/4] dm ioctl: Allow userspace to opt-in to strict parameter checks Demi Marie Obenour
2023-06-24 23:09 ` [PATCH v2 2/4] dm ioctl: Allow userspace to provide expected diskseq Demi Marie Obenour
[not found] ` <3241078c-2318-fe1b-33cc-7c33db71b1a6@web.de>
2023-06-25 17:39 ` Demi Marie Obenour
2023-06-26 12:59 ` Dan Carpenter
[not found] ` <c1b84520-94d2-2c5c-6eed-2a0697c086a4@web.de>
2023-06-26 14:51 ` [v2 " Dan Carpenter
[not found] ` <1c1cd489-6d59-00ed-a1f5-497ca532c08d@web.de>
2023-06-27 6:14 ` Dan Carpenter [this message]
2023-06-24 23:09 ` [PATCH v2 3/4] dm ioctl: Allow userspace to suppress uevent generation Demi Marie Obenour
2023-06-25 13:25 ` [dm-devel] " Milan Broz
2023-06-25 16:02 ` Demi Marie Obenour
2023-06-25 16:33 ` Milan Broz
2023-06-25 16:43 ` Demi Marie Obenour
2023-06-25 17:13 ` Milan Broz
2023-06-24 23:09 ` [PATCH v2 4/4] dm ioctl: inform caller about already-existing device Demi Marie Obenour
2024-01-15 17:56 ` [dm-devel] [PATCH v2 0/4] Diskseq support in device-mapper Martin Wilck
2024-01-15 21:44 ` Demi Marie Obenour
2024-01-16 8:00 ` Martin Wilck
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=ab9f1618-5dde-4c70-a88e-c65f33abdb73@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=Markus.Elfring@web.de \
--cc=agk@redhat.com \
--cc=demi@invisiblethingslab.com \
--cc=dm-devel@redhat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=snitzer@kernel.org \
/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®