public inbox for rust-for-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Hamza Mahfooz <hamzamahfooz@linux.microsoft.com>
Cc: rust-for-linux@vger.kernel.org, "Miguel Ojeda" <ojeda@kernel.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <lossin@kernel.org>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Alice Ryhl" <aliceryhl@google.com>,
	"Trevor Gross" <tmgross@umich.edu>,
	"Danilo Krummrich" <dakr@kernel.org>, "Tejun Heo" <tj@kernel.org>,
	"Tamir Duberstein" <tamird@gmail.com>,
	"Alban Kurti" <kurti@invicto.ai>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] workqueue: rust: add work item runtime modification support
Date: Wed, 4 Feb 2026 06:24:18 +0100	[thread overview]
Message-ID: <2026020440-herbs-tranquil-d0a5@gregkh> (raw)
In-Reply-To: <20260203215555.832171-1-hamzamahfooz@linux.microsoft.com>

On Tue, Feb 03, 2026 at 01:55:55PM -0800, Hamza Mahfooz wrote:
> This feature is required for our Hyper-V VMBus reimplementation effort.
> As it provides the ability to modify the running state of work items at
> runtime.

This is great, BUT we need to see the user of this new code at the same
time before adding it to the kernel tree.  Why not just submit this as
part of your patch series for the rust hyperv stuff?

thanks,

greg k-h

  parent reply	other threads:[~2026-02-04  5:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-03 21:55 [PATCH] workqueue: rust: add work item runtime modification support Hamza Mahfooz
2026-02-04  4:54 ` kernel test robot
2026-02-04  5:24 ` Greg KH [this message]
2026-02-06 21:07   ` Hamza Mahfooz
2026-02-07  7:55     ` Greg KH

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=2026020440-herbs-tranquil-d0a5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=a.hindborg@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=dakr@kernel.org \
    --cc=gary@garyguo.net \
    --cc=hamzamahfooz@linux.microsoft.com \
    --cc=kurti@invicto.ai \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lossin@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=tamird@gmail.com \
    --cc=tj@kernel.org \
    --cc=tmgross@umich.edu \
    /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