linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Imran Khan <imran.f.khan@oracle.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: tj@kernel.org, jiangshanlai@gmail.com, jirislaby@kernel.org,
	rafael@kernel.org, pavel@ucw.cz, len.brown@intel.com,
	linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: Re: [RFC PATCH v4] workqueue: Introduce show_one_worker_pool and show_one_workqueue.
Date: Wed, 20 Oct 2021 18:59:03 +1100	[thread overview]
Message-ID: <e3bd151d-4658-c5ff-36ce-42e3155f7c2d@oracle.com> (raw)
In-Reply-To: <YW+wagIij7zUbfsZ@kroah.com>

Hi Greg,

On 20/10/21 5:00 pm, Greg KH wrote:
> On Wed, Oct 20, 2021 at 02:09:00PM +1100, Imran Khan wrote:
[...]
>>
>> Signed-off-by: Imran Khan <imran.f.khan@oracle.com>
>> ---
>> Changes in v4:
>>    - Rebase on git://git.kernel.org/pub/scm/linux/kernel/git/tj/wq.git
>>      for-5.16
> 
> "RFC" means "I am not sure about this patch, please do not apply it."
> 
Thanks for clarifying this.

> Yet a v4 is very odd, why not be sure about this?

I have not got any negative feedback about the change so far, so I am 
fairly sure about it now. There was a mistake in my understanding where 
I thought that something that starts as an RFC remains like that in 
subsequent revisions. I will definitely be mindful about it in future.
Could you please let me know if I should send a "PATCH v5", removing RFC 
from the subject.

Thanks,
Imran
> 
> thanks,
> 
> greg k-h
> 

  reply	other threads:[~2021-10-20  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-20  3:09 [RFC PATCH v4] workqueue: Introduce show_one_worker_pool and show_one_workqueue Imran Khan
2021-10-20  6:00 ` Greg KH
2021-10-20  7:59   ` Imran Khan [this message]
2021-10-20 16:19 ` Tejun Heo

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=e3bd151d-4658-c5ff-36ce-42e3155f7c2d@oracle.com \
    --to=imran.f.khan@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiangshanlai@gmail.com \
    --cc=jirislaby@kernel.org \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=rafael@kernel.org \
    --cc=tj@kernel.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).