From: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH -iwlwifi] iwlwifi: make tx_cmd_pool kmem cache global
Date: Mon, 27 Feb 2012 09:48:48 -0800 [thread overview]
Message-ID: <1330364928.12612.15.camel@wwguy-huron> (raw)
In-Reply-To: <CANUX_P2Xia4HgF_ooUCTRN0+EqX8dx9Wc1rFiDbiNBdgzu9k5Q@mail.gmail.com>
On Mon, 2012-02-27 at 19:55 +0200, Emmanuel Grumbach wrote:
> I guess that Sanislaw patch is defining one single pool for all the
> devices, which means that we won't try to allocate a few pools with
> the same name, which leads to this warning.
>
That I got it, but is really the "only" way to do it, I am really not a
fan of global variable.
Wey
next prev parent reply other threads:[~2012-02-27 19:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 13:52 [PATCH -iwlwifi] iwlwifi: make tx_cmd_pool kmem cache global Stanislaw Gruszka
2012-02-27 14:30 ` Guy, Wey-Yi
2012-02-27 17:55 ` Emmanuel Grumbach
2012-02-27 17:48 ` Guy, Wey-Yi [this message]
2012-02-27 20:20 ` Emmanuel Grumbach
2012-02-27 22:14 ` Guy, Wey-Yi
2012-02-29 9:00 ` Johannes Berg
2012-02-29 15:00 ` Guy, Wey-Yi
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=1330364928.12612.15.camel@wwguy-huron \
--to=wey-yi.w.guy@intel.com \
--cc=egrumbach@gmail.com \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.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;
as well as URLs for NNTP newsgroup(s).