From: GregKH <greg@kroah.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: Evgeniy Polyakov <zbr@ioremap.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] w1: w1_process() is not freezable kthread
Date: Thu, 19 Nov 2015 08:15:43 -0800 [thread overview]
Message-ID: <20151119161543.GA10832@kroah.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1511191645550.20111@pobox.suse.cz>
On Thu, Nov 19, 2015 at 04:49:41PM +0100, Jiri Kosina wrote:
> On Thu, 5 Nov 2015, Evgeniy Polyakov wrote:
>
> > > I fail to see why this kthread should be freezable at all. There is no way
> > > for w1 device to generate new I/O requests that should be written out to
> > > filesystem, is it?
> >
> > w1 doesn't generate such requests, but it was more to make this thread
> > consistent with majority of other threads in the kernel.
>
> Most of which actually don't need freezer at all, and only contribute to
> the overall confusion regarding what kthread freezer is actually for.
>
> It's my long-term goal to fix this situation (and this patch is part of
> some preparatory steps :) ).
>
> > Ok, I'm not against it, Greg please pull this patch into your tree.
> >
> > Acked-by: Evgeniy Polyakov <zbr@ioremap.net>
>
> Greg, do you plan to take this please? I don't seem to see it in
> linux-next as of today.
Give me a chance to catch up on things, the merge window was just over
and I just returned from another conference...
thanks,
greg k-h
next prev parent reply other threads:[~2015-11-19 16:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 5:53 [PATCH] w1: w1_process() is not freezable kthread Jiri Kosina
2015-10-27 14:30 ` Evgeniy Polyakov
2015-10-28 5:26 ` Jiri Kosina
2015-11-05 13:33 ` Evgeniy Polyakov
2015-11-19 15:49 ` Jiri Kosina
2015-11-19 16:15 ` GregKH [this message]
2016-02-08 5:31 ` GregKH
2016-02-10 10:41 ` Jiri Kosina
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=20151119161543.GA10832@kroah.com \
--to=greg@kroah.com \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=zbr@ioremap.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.