From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Dad <ccmcphe@verizon.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Compatibility Issues with compat-wireless-2008-05-22
Date: Sun, 8 Jun 2008 09:12:54 -0700 [thread overview]
Message-ID: <43e72e890806080912o7d186120r8ce70c46ca3526de@mail.gmail.com> (raw)
In-Reply-To: <483D99DC.4020909@verizon.net>
On Wed, May 28, 2008 at 10:43 AM, Dad <ccmcphe@verizon.net> wrote:
> I am building with kernel 2.6.22-14 and I have some build problems with any
> compat-wireless build past 05-21. The builds show a problem with the
> function skb_get_queue_mapping not being defined and a define
> NETIF_F_MULTI_QUEUE not being defined. Complete list is below. I have
> checked my linux source and includes for theses references and cannot find
> them anywhere. Is there a way to make the builds compatable?
This required backport support of MQ, please try now.
Luis
prev parent reply other threads:[~2008-06-08 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-28 17:43 Compatibility Issues with compat-wireless-2008-05-22 Dad
2008-06-08 16:12 ` Luis R. Rodriguez [this message]
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=43e72e890806080912o7d186120r8ce70c46ca3526de@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=ccmcphe@verizon.net \
--cc=linux-wireless@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).