From: Markus Elfring <Markus.Elfring@web.de>
To: Matthew Wilcox <willy@infradead.org>,
Kaitao Cheng <pilgrimtao@gmail.com>,
linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Alexey Dobriyan <adobriyan@gmail.com>,
Colin Ian King <colin.king@canonical.com>,
Muchun Song <songmuchun@bytedance.com>
Subject: Re: [v2] proc/fd: Remove unnecessary variable initialisations in seq_show()
Date: Fri, 12 Jun 2020 18:43:41 +0000 [thread overview]
Message-ID: <d3d13ca7-754d-cf52-8f2c-9b82b8cc301f@web.de> (raw)
In-Reply-To: <20200612182811.GH8681@bombadil.infradead.org>
>> The presented suggestions trigger different views by involved contributors.
>
> Most of the views I've heard are "Markus, go away".
> Do you not hear these views?
I notice also this kind of feedback.
The clarification is still evolving for these concerns and communication difficulties.
I suggest to take another look at published software development activities.
>> In which directions can the desired clarification evolve?
>
> You could try communicating in a way that the rest of us do.
I got also used to some communication styles.
I am curious to find the differences out which hinder to achieve a better
common understanding.
> For example, instead of saying something weird about "collateral evolution"
> you could say "I think there's a similar bug here".
* Why do you repeat this topic here?
* Do try to distract from implementation details which were pointed out
by two developers for this patch?
>> How do you think about further function design alternatives?
>
> Could you repeat that in German? I don't know what you mean.
I imagine that you could know affected software aspects better.
Regards,
Markus
next prev parent reply other threads:[~2020-06-12 18:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-12 16:09 [PATCH v2] proc/fd: Remove unnecessary {files, f_flags, file} initialization in seq_show() Kaitao Cheng
2020-06-12 16:45 ` [PATCH v2] proc/fd: Remove unnecessary variable initialisations " Markus Elfring
2020-06-12 17:00 ` Matthew Wilcox
2020-06-12 17:03 ` Markus Elfring
2020-06-12 17:03 ` Markus Elfring
2020-06-12 17:04 ` Matthew Wilcox
2020-06-12 18:22 ` [v2] " Markus Elfring
2020-06-12 18:28 ` Matthew Wilcox
2020-06-12 18:43 ` Markus Elfring [this message]
2020-06-12 18:47 ` Matthew Wilcox
2020-06-12 19:00 ` Markus Elfring
2020-06-12 19:00 ` Markus Elfring
2020-06-12 19:02 ` Matthew Wilcox
2020-06-12 19:49 ` Al Viro
2020-06-14 7:12 ` [PATCH v2] " Greg KH
2020-07-07 7:23 ` [PATCH v2] proc/fd: Adjust " Markus Elfring
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=d3d13ca7-754d-cf52-8f2c-9b82b8cc301f@web.de \
--to=markus.elfring@web.de \
--cc=adobriyan@gmail.com \
--cc=colin.king@canonical.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pilgrimtao@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).