From: Christoph Hellwig <hch@lst.de>
To: John Meneghini <jmeneghi@redhat.com>
Cc: Christoph Hellwig <hch@lst.de>,
Mikulas Patocka <mpatocka@redhat.com>,
linux-block@vger.kernel.org, dm-devel@lists.linux.dev,
linux-scsi@vger.kernel.org, Chris Leech <cleech@redhat.com>,
Hannes Reinecke <hare@suse.de>,
snitzer@kernel.org, Ming Lei <minlei@redhat.com>,
Benjamin Marzinski <bmarzins@redhat.com>,
Jonathan Brassow <jbrassow@redhat.com>,
Ewan Milne <emilne@redhat.com>,
bmarson@redhat.com, Jeff Moyer <jmoyer@redhat.com>,
"spetrovi@redhat.com" <spetrovi@redhat.com>,
Rob Evers <revers@redhat.com>
Subject: Re: DMMP request-queue vs. BiO
Date: Mon, 18 Nov 2024 14:05:40 +0100 [thread overview]
Message-ID: <20241118130540.GA29045@lst.de> (raw)
In-Reply-To: <e48b533d-c28a-4e92-b459-74820957ec7d@redhat.com>
On Fri, Nov 15, 2024 at 03:28:03PM -0500, John Meneghini wrote:
>> And, as pointed out in the private mail that John forwarded to the list
>> without my permission if we really have a workload that cares md could
>
> Ah come on. I deleted most of the private thread....
As a rule of thumb forwarding private mail to a public list is never
valid without previous permission. I'm not worried about any actual
information in this one, but it is still a breach of trust and privacy
expectations.
next prev parent reply other threads:[~2024-11-18 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2d5fe016-2941-43a4-8b7c-850b8ee1d6ce@redhat.com>
[not found] ` <20241104073547.GA20614@lst.de>
[not found] ` <d9733713-eb7b-4efa-ad6b-e6b41d1df93b@suse.de>
[not found] ` <20241105103307.GA1385@lst.de>
2024-11-07 18:35 ` DMMP request-queue vs. BiO John Meneghini
2024-11-15 14:05 ` Mikulas Patocka
2024-11-15 17:09 ` Christoph Hellwig
2024-11-15 20:28 ` John Meneghini
2024-11-18 13:05 ` Christoph Hellwig [this message]
2024-11-15 20:24 ` John Meneghini
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=20241118130540.GA29045@lst.de \
--to=hch@lst.de \
--cc=bmarson@redhat.com \
--cc=bmarzins@redhat.com \
--cc=cleech@redhat.com \
--cc=dm-devel@lists.linux.dev \
--cc=emilne@redhat.com \
--cc=hare@suse.de \
--cc=jbrassow@redhat.com \
--cc=jmeneghi@redhat.com \
--cc=jmoyer@redhat.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=minlei@redhat.com \
--cc=mpatocka@redhat.com \
--cc=revers@redhat.com \
--cc=snitzer@kernel.org \
--cc=spetrovi@redhat.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).