From: Prarit Bhargava <prarit@redhat.com>
To: linux-wireless@vger.kernel.org
Cc: "John W. Linville" <linville@tuxdriver.com>
Subject: wireless-next-2.6 compile broken
Date: Thu, 17 Jun 2010 18:50:36 -0400 [thread overview]
Message-ID: <4C1AA6BC.8000702@redhat.com> (raw)
John, as I mentioned in my previous email, the wireless-next-2.6 kernel
tree is not compiling.
This is because the wireless-next-2.6 tree is missing linux-2.6 commit
6c1f716e8154ee9315534782b9b1eedea0559a24, but has wireless-next-2.6
commit 832c10fd733893f86c63bde1c65b005d5a2fe346 ... which explicitly
depends on the linux-2.6 commit.
FYI,
P.
reply other threads:[~2010-06-17 22:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4C1AA6BC.8000702@redhat.com \
--to=prarit@redhat.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.