From: Jens Axboe <axboe@kernel.dk>
To: Kent Overstreet <kent.overstreet@linux.dev>,
Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
willy@infradead.org
Subject: Re: [PATCH 0/2] bio iter improvements
Date: Tue, 4 Apr 2023 10:01:58 -0600 [thread overview]
Message-ID: <2bbdb38b-a3ac-5127-23c0-56badd113538@kernel.dk> (raw)
In-Reply-To: <ZCxGdj3JKl2RPUJW@moria.home.lan>
>> Starting to get personal instead tends to not help to convince your
>> reviewers that it's really useful in general.
>
> I know you and others like to talk a lot about what you want as
> maintainers and reviewers - but I find that the people who are the
> loudest and the most authoritarian in that respect tend not to be the
> people who drive discussions forward in productive ways.
One issue is certainly that nobody wants to engage with people that
instantly try and make this personal, or just uncomfortable in general.
Then it's better to focus on other things that are more rewarding and
pleasant, nobody needs extra drama in their life. I sure as hell don't.
And unfortunately I find that your postings most often degenerate to
that. Which is a shame, because there's good stuff in a lot of these
patches, but it's often not worth the time/energy investment because of
it.
--
Jens Axboe
next prev parent reply other threads:[~2023-04-04 16:02 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-27 17:44 [PATCH 0/2] bio iter improvements Kent Overstreet
2023-03-27 17:44 ` [PATCH 1/2] block: Rework bio_for_each_segment_all() Kent Overstreet
2023-03-29 16:50 ` Phillip Lougher
2023-03-30 17:55 ` Kent Overstreet
2023-03-30 18:59 ` Phillip Lougher
2023-03-31 1:10 ` Phillip Lougher
2023-04-01 2:28 ` Kent Overstreet
2023-04-03 13:57 ` Phillip Lougher
2023-03-30 11:49 ` Ming Lei
2023-03-30 16:20 ` Kent Overstreet
2023-03-27 17:44 ` [PATCH 2/2] block: Rework bio_for_each_folio_all() Kent Overstreet
2023-04-03 15:13 ` Christoph Hellwig
2023-04-03 15:51 ` Kent Overstreet
2023-03-27 22:14 ` [PATCH 0/2] bio iter improvements Christoph Hellwig
2023-03-28 20:28 ` Kent Overstreet
2023-04-03 15:10 ` Christoph Hellwig
2023-04-03 16:36 ` Kent Overstreet
2023-04-04 15:20 ` Christoph Hellwig
2023-04-04 15:47 ` Kent Overstreet
2023-04-04 15:59 ` Christoph Hellwig
2023-04-04 16:08 ` Kent Overstreet
2023-04-04 16:01 ` Jens Axboe [this message]
2023-04-04 16:06 ` Kent Overstreet
2023-04-04 16:14 ` Jens Axboe
2023-04-04 17:11 ` Kent Overstreet
2023-03-28 13:42 ` Phillip Lougher
2023-03-28 16:57 ` Kent Overstreet
2023-03-29 16:41 ` Phillip Lougher
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=2bbdb38b-a3ac-5127-23c0-56badd113538@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kent.overstreet@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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