Linux wireless drivers development
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Holger Schurig <hs4233@mail.mn-solutions.de>
Cc: libertas-dev@lists.infradead.org, linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH] libertas: rename thread names
Date: Wed, 30 Apr 2008 16:30:01 -0400	[thread overview]
Message-ID: <1209587401.16194.20.camel@localhost.localdomain> (raw)
In-Reply-To: <200804301051.47028.hs4233@mail.mn-solutions.de>

On Wed, 2008-04-30 at 10:51 +0200, Holger Schurig wrote:
> * Most thread names start with "k", so we can do the same
> * the module is named "libertas", so a "klibertas_XXX" thread
>   name more self-describing
> * one thread is a "struct task_struct", the other a workqueue,
>   let this be reflected in the name

It appears that of the other drivers that do something like this:

airo: uses device name
ipw2200: uses driver name (ipw2200)
iwlwifi: uses driver name (iwl3945)

I guess I'd rather go with those, seems odd to put a 'k' in front when
it's a driver thread and not too many other drivers put a 'k' in front.

Dan

> Signed-off-by: Holger Schurig <hs4233@mail.mn-solutions.de>
> 
> Index: wireless-testing/drivers/net/wireless/libertas/main.c
> ===================================================================
> --- wireless-testing.orig/drivers/net/wireless/libertas/main.c	2008-04-30 08:48:04.000000000 +0200
> +++ wireless-testing/drivers/net/wireless/libertas/main.c	2008-04-30 09:01:22.000000000 +0200
> @@ -1122,15 +1122,14 @@ struct lbs_private *lbs_add_card(void *c
>  
>  	priv->rtap_net_dev = NULL;
>  
> -	lbs_deb_thread("Starting main thread...\n");
>  	init_waitqueue_head(&priv->waitq);
> -	priv->main_thread = kthread_run(lbs_thread, dev, "lbs_main");
> +	priv->main_thread = kthread_run(lbs_thread, dev, "klibertasd");
>  	if (IS_ERR(priv->main_thread)) {
>  		lbs_deb_thread("Error creating main thread.\n");
>  		goto err_init_adapter;
>  	}
>  
> -	priv->work_thread = create_singlethread_workqueue("lbs_worker");
> +	priv->work_thread = create_singlethread_workqueue("klibertasq");
>  	INIT_DELAYED_WORK(&priv->assoc_work, lbs_association_worker);
>  	INIT_DELAYED_WORK(&priv->scan_work, lbs_scan_worker);
>  	INIT_WORK(&priv->sync_channel, lbs_sync_channel_worker);


  reply	other threads:[~2008-04-30 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30  8:51 [PATCH] libertas: rename thread names Holger Schurig
2008-04-30 20:30 ` Dan Williams [this message]
2008-05-01 21:12   ` Holger Schurig

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=1209587401.16194.20.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=hs4233@mail.mn-solutions.de \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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