From: "John W. Linville" <linville@tuxdriver.com>
To: Tomas Winkler <tomasw@gmail.com>
Cc: Zhu Yi <yi.zhu@intel.com>, Ian Schram <ischram@telenet.be>,
linux-wireless@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2008-09-02
Date: Tue, 2 Sep 2008 20:00:22 -0400 [thread overview]
Message-ID: <20080903000022.GB2964@tuxdriver.com> (raw)
In-Reply-To: <1ba2fa240809021607s6855d3d3p411f13a940271f07@mail.gmail.com>
On Wed, Sep 03, 2008 at 02:07:27AM +0300, Tomas Winkler wrote:
> > John W. Linville (1):
> > iwlwifi: do not use GFP_DMA in iwl_tx_queue_init
> This one should be already in Yi's queue.The patch also address the
> allocation error path. It's coauthored with Ian (out of Intel) so we
> send it out just for record ... not sure what's the protocol.
Either rebase it or send it as-is -- I'm sure I can resolve the
conflict. I just don't see much point in waiting to resolve such a
simple issue.
John
next prev parent reply other threads:[~2008-09-03 0:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-02 22:15 pull request: wireless-2.6 2008-09-02 John W. Linville
2008-09-02 23:07 ` Tomas Winkler
2008-09-03 0:00 ` John W. Linville [this message]
2008-09-03 0:17 ` David Miller
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=20080903000022.GB2964@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ischram@telenet.be \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.com \
--cc=yi.zhu@intel.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