public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Richard Kennedy <richard@rsk.demon.co.uk>,
	Karl Relton <karllinuxtest.relton@ntlworld.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	wlan-devel <linux-wlan-devel@lists.linux-wlan.com>
Subject: Re: [PATCH] staging/wlan-ng: block ioctls until card fully initialised
Date: Tue, 17 Feb 2009 18:21:17 -0800	[thread overview]
Message-ID: <20090218022117.GB32325@kroah.com> (raw)
In-Reply-To: <1234478293.17792.1.camel@dellpc> <1234873158.2891.29.camel@localhost.localdomain>

On Tue, Feb 17, 2009 at 12:19:18PM +0000, Richard Kennedy wrote:
> Add a mutex to block ioctls before the card is fully initialised and
> only allow one ioctl at a time.
> This stops udev trying to load the firmware before to card is fully up.
> 
> patch ported from wlan-ng-devel
> 
> Karl Relton <karllinuxtest.relton@ntlworld.com> spotted that this was
> missing from the staging version,
> http://lists.linux-wlan.com/pipermail/linux-wlan-devel/2009-February/003890.html 

Karl sent me a patch a few days before you that also added this
functionality.

Unfortunatly, both of your patches don't apply to the latest version of
the wlan-ng driver as it has had a lot of work done on it recently.

Could one of you grab the linux-next tree and make a patch up against
the version in it so that I can apply this?

thanks,

greg k-h

  reply	other threads:[~2009-02-18  2:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1234213202.6875.70.camel@dellpc>
     [not found] ` <20090209211700.GA10742@kroah.com>
     [not found]   ` <1234478293.17792.1.camel@dellpc>
2009-02-17 12:19     ` [PATCH] staging/wlan-ng: block ioctls until card fully initialised Richard Kennedy
2009-02-18  2:21       ` Greg KH [this message]
2009-02-18 18:14         ` Richard Kennedy
2009-02-20 12:09         ` [PATCH] linux-next/staging/wlan-ng: " Richard Kennedy

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=20090218022117.GB32325@kroah.com \
    --to=greg@kroah.com \
    --cc=karllinuxtest.relton@ntlworld.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wlan-devel@lists.linux-wlan.com \
    --cc=richard@rsk.demon.co.uk \
    /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