From: Jeff Garzik <jgarzik@pobox.com>
To: abonilla@linuxwireless.org
Cc: netdev@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
ieee80211-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Git broken for IPW2200
Date: Wed, 07 Sep 2005 22:18:29 -0400 [thread overview]
Message-ID: <431F9F75.9020704@pobox.com> (raw)
In-Reply-To: <1126143695.5402.11.camel@localhost.localdomain>
Alejandro Bonilla Beeche wrote:
> Hi,
>
> Where does one report this? I was building Linus Git tree as per I
> updated it at 09/07/2005 7:00PM PDT and got this while compiling.
>
> Where do I report this?
>
> Debian unstable updated at same time.
>
> it looks like ipw2200 is thinking that ieee80211 is not compiled in, but
> I did select it as a module?
Wanna post a URL to your .config?
Jeff
next prev parent reply other threads:[~2005-09-08 2:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 1:41 Git broken for IPW2200 Alejandro Bonilla Beeche
2005-09-08 2:18 ` Jeff Garzik [this message]
2005-09-08 5:14 ` Alejandro Bonilla Beeche
2005-09-08 15:25 ` Joe Bob Spamtest
2005-09-08 15:45 ` Alejandro Bonilla
2005-09-12 18:54 ` Jeff Garzik
2005-09-12 19:04 ` Alejandro Bonilla
2005-09-12 19:08 ` Alejandro Bonilla
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=431F9F75.9020704@pobox.com \
--to=jgarzik@pobox.com \
--cc=abonilla@linuxwireless.org \
--cc=ieee80211-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@osdl.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).