linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: linville@tuxdriver.com
Cc: netdev@vger.kernel.org, linux-wireless@vger.kernel.org,
	kune@deine-taler.de
Subject: Re: [PATCH] zd1211rw: changed GFP_NOFS to GFP_KERNEL
Date: Sun, 18 Feb 2007 15:58:15 -0500	[thread overview]
Message-ID: <45D8BDE7.10001@gentoo.org> (raw)
In-Reply-To: <20070218202823.9C4A07B409F@zog.reactivated.net>

Daniel Drake wrote:
> From: Ulrich Kunitz <kune@deine-taler.de>
> 
> Michael Buesch commented that GFP_NOFS should not be used in a
> network driver. This patch implements it for zd1211rw-d80211.

Forgot to update the description. As you might have figured, this 
version of the patch is for wireless-2.6, and the earlier one was for
wireless-dev.

Daniel

           reply	other threads:[~2007-02-18 20:57 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20070218202823.9C4A07B409F@zog.reactivated.net>]

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=45D8BDE7.10001@gentoo.org \
    --to=dsd@gentoo.org \
    --cc=kune@deine-taler.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=netdev@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).