From: "Masalkhi, Abd Alrhman" <abd.masalkhi@gatech.edu>
To: Mariusz Tkaczyk <mtkaczyk@kernel.org>
Cc: "song@kernel.org" <song@kernel.org>,
"yukuai@fygo.io" <yukuai@fygo.io>,
"chengzhihao1@huawei.com" <chengzhihao1@huawei.com>,
"magiclinan@didiglobal.com" <magiclinan@didiglobal.com>,
"xiao@kernel.org" <xiao@kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH v4 0/4] md: add a control device for array management
Date: Wed, 28 Oct 2026 12:31:50 +0000 [thread overview]
Message-ID: <m28q3i2eh6.fsf@gmail.com> (raw)
In-Reply-To: <20261028101352.272d7d37@kernel.org>
Hi,
On Wed, Oct 28, 2026 at 10:13 +0100, Mariusz Tkaczyk wrote:
> On Thu, 15 Oct 2026 20:47:51 +0000
> "Masalkhi, Abd Alrhman" <abd.masalkhi@gatech.edu> wrote:
>
>> A warning is emitted when it is used to recommend upgrading mdadm to
>> use the new control interface.
>
>
> Definitely you should not refer to mdadm from kernel context, user can
> send ioctls from the own applications which would be misleading.
>
Thank you for the feedback. I will update this in the next version.
> Mariusz
--
Best Regards,
Abd-Alrhman
prev parent reply other threads:[~2026-10-28 12:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-15 20:47 Masalkhi, Abd Alrhman
2026-10-15 20:48 ` [RFC PATCH v4 1/4] md: add uapi definitions for the md control device Masalkhi, Abd Alrhman
2026-10-15 20:48 ` [RFC PATCH v4 2/4] md: pass struct mdu_disk_info64 to md_add_new_disk() Masalkhi, Abd Alrhman
2026-10-15 20:48 ` [RFC PATCH v4 3/4] md: use struct mdu_array_info64 for SET_ARRAY_INFO Masalkhi, Abd Alrhman
2026-10-15 20:48 ` [RFC PATCH v4 4/4] md: add a control device for array management Masalkhi, Abd Alrhman
2026-10-28 9:13 ` [RFC PATCH v4 0/4] " Mariusz Tkaczyk
2026-10-28 12:31 ` Masalkhi, Abd Alrhman [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=m28q3i2eh6.fsf@gmail.com \
--to=abd.masalkhi@gatech.edu \
--cc=chengzhihao1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=magiclinan@didiglobal.com \
--cc=mtkaczyk@kernel.org \
--cc=song@kernel.org \
--cc=xiao@kernel.org \
--cc=yukuai@fygo.io \
/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®