From: David Kimdon <david.kimdon@devicescape.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: netdev@vger.kernel.org, Jiri Benc <jbenc@suse.cz>,
"John W. Linville" <linville@tuxdriver.com>,
Jean Tourrilhes <jt@hpl.hp.com>
Subject: Re: [RFC] [PATCH 3/3] Kconfig update for regulatory domain
Date: Mon, 23 Oct 2006 18:04:55 -0700 [thread overview]
Message-ID: <20061024010455.GB3552@devicescape.com> (raw)
In-Reply-To: <43e72e890610231551w5f5e947ena6d9a5d6f9a70ad9@mail.gmail.com>
This last chunk is broken:
. . .
Hunk #2 FAILED at 90.
> --- wireless-dev-old/net/d80211/Kconfig 2006-10-23 13:56:11.000000000 -0400
> +++ wireless-dev/net/d80211/Kconfig 2006-10-23 17:04:12.000000000 -0400
> @@ -16,8 +90,6 @@ config D80211_LEDS
> This option enables a few LED triggers for different
> packet receive/transmit events.
>
> -config D80211_
> -
> config D80211_DEBUG
> bool "Enable debugging output"
> depends on D80211
next prev parent reply other threads:[~2006-10-24 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 22:51 [RFC] [PATCH 3/3] Kconfig update for regulatory domain Luis R. Rodriguez
2006-10-24 1:04 ` David Kimdon [this message]
2006-10-24 5:09 ` Luis R. Rodriguez
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=20061024010455.GB3552@devicescape.com \
--to=david.kimdon@devicescape.com \
--cc=jbenc@suse.cz \
--cc=jt@hpl.hp.com \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
--cc=netdev@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).