From: Sukadev Bhattiprolu <sukadev@us.ibm.com>
To: Christoph Hellwig <hch@infradead.org>,
akpm@osdl.org, achirica@users.sourceforge.net,
"David C. Hansen" <haveblue@us.ibm.com>,
serue@us.ibm.com, clg@fr.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] kthread: airo.c
Date: Thu, 13 Jul 2006 16:00:18 -0700 [thread overview]
Message-ID: <20060713230018.GA24359@us.ibm.com> (raw)
In-Reply-To: <20060713212824.GA14729@infradead.org>
Christoph Hellwig [hch@infradead.org] wrote:
| On Thu, Jul 13, 2006 at 01:53:19PM -0700, Sukadev Bhattiprolu wrote:
| > Andrew,
| >
| > Javier Achirica, one of the major contributors to drivers/net/wireless/airo.c
| > took a look at this patch, and doesn't have any problems with it. It doesn't
| > fix any bugs and is just a cleanup, so it certainly isn't a candidate
| > for this mainline cycle
|
| I'm not sure it's that easy. I think it needs some more love:
|
| - switch to wake_uo_process
| - kill JOB_DIE
| - cleanup a the convoluted mess in airo_thread a bit
|
| Note that it's still reimplementing the single threaded workqueue
| functionality quite badly. So if someone could switch it over and while
| we're at it try to kill the idiociy of doing the trylock in the calling
| context and only then calling the thread by always calling the thread
| (which also solves the synchronization problem).
|
| Anywhy, here's a small incremental patch ontop of yours to implement my
| above items:
I had a quick look at your patch and looks fine to me. I agree we could
do more to clean up the driver.
My inital goal was to replace kernel_thread() with kthread_*(). So can I
assume you are ok with my patch and that it can go in as is ?
Suka
next prev parent reply other threads:[~2006-07-13 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-13 20:53 [PATCH] kthread: airo.c Sukadev Bhattiprolu
2006-07-13 21:28 ` Christoph Hellwig
2006-07-13 23:00 ` Sukadev Bhattiprolu [this message]
2006-07-14 14:35 ` John W. Linville
2006-07-24 18:13 ` Sukadev Bhattiprolu
2006-07-26 6:18 ` Andrew Morton
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=20060713230018.GA24359@us.ibm.com \
--to=sukadev@us.ibm.com \
--cc=achirica@users.sourceforge.net \
--cc=akpm@osdl.org \
--cc=clg@fr.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
/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