From: "Steve French (smfltc)" <smfltc@us.ibm.com>
To: "Q (Igor Mammedov)" <qwerty0987654321@mail.ru>
Cc: linux-cifs-client@lists.samba.org,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [linux-cifs-client] Re: cifs and kthread_run / kernel_thread
Date: Mon, 02 Apr 2007 10:12:38 -0500 [thread overview]
Message-ID: <46111D66.8060208@us.ibm.com> (raw)
In-Reply-To: <4610B80F.9020102@mail.ru>
Q (Igor Mammedov) wrote:
> Steve French (smfltc) wrote:
>
>> No - IIRC the original patch (for the switch of cifs from
>> kernel_thread to kthread) had a
>> minor implementation problem in handling the cifs_demultiplex thread,
>> so this one small
>> area was left with the old style.
>>
>>> iii) Is it difficult to switch to the new interface?
>>>
>>>
>> No, I don't think so, but I have not investigated it. We would be happy
>> to review and test a patch for this though.
>>
>>> ***************************
>>
>
> It seems to me that I rewrote cifs_demultiplex_thread to use
> kthread_run in DFS patch.
>
Yes - Q's patch has the final change to kthread (as part of a larger
DFS change). The original
patch which switched to kthread was done long before this.
I have not broken all the large dfs patch into small pieces but will
look to see if just this part
can be done easily
next prev parent reply other threads:[~2007-04-02 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070331120030.BE6A916387F@lists.samba.org>
2007-04-01 19:12 ` cifs and kthread_run / kernel_thread Steve French (smfltc)
2007-04-02 8:00 ` [linux-cifs-client] " Q (Igor Mammedov)
2007-04-02 8:58 ` Wilhelm Meier
2007-04-02 15:40 ` Wilhelm Meier
2007-04-02 15:55 ` Steve French (smfltc)
2007-04-02 15:12 ` Steve French (smfltc) [this message]
2007-04-03 19:17 Steve French
2007-04-03 19:18 ` [linux-cifs-client] " Jeremy Allison
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=46111D66.8060208@us.ibm.com \
--to=smfltc@us.ibm.com \
--cc=linux-cifs-client@lists.samba.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qwerty0987654321@mail.ru \
/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.