From: "John W. Linville" <linville@tuxdriver.com>
To: Jason Riedy <jason@acm.org>
Cc: "Chatre, Reinette" <reinette.chatre@intel.com>,
ipw3945-devel@lists.sourceforge.net,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] Make IWLCORE a silent option not to confuse iwl3945 users.
Date: Tue, 8 Apr 2008 19:38:58 -0400 [thread overview]
Message-ID: <20080408233858.GA23670@tuxdriver.com> (raw)
In-Reply-To: <877if8m5zx.fsf@sparse.dyndns.org>
On Tue, Apr 08, 2008 at 01:44:18PM -0700, Jason Riedy wrote:
> And John W. Linville writes:
> > I think it makes sense to make IWLCORE invisible, but this patch
> > seems not quite right. I'm dropping it -- feel free to repost a
> > revised version.
>
> I would love to, but I have no idea what the current base is.
> The net-2.6.26 branch of jgarzik/netdev-2.6.git, master of
> davem/net-2.6.26.git, and master of your 2.6.26 repo all still
> have the iwl3945 that won't compile without iwl4965. And
> rchatre/iwlwifi-2.6.git won't merge into those without irrelevant
> conflicts.
Is there some reason you wouldn't use the wireless-testing tree?
> This is a mess. I hope y'all can sort it out before the window
> opens. The blinky lights are fun.
Ah, pessimism...so refreshing...
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2008-04-09 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 6:28 [PATCH] Make IWLCORE a silent option not to confuse iwl3945 users Jason Riedy
2008-04-03 16:14 ` Chatre, Reinette
2008-04-08 18:04 ` John W. Linville
2008-04-08 20:44 ` Jason Riedy
2008-04-08 22:45 ` Chatre, Reinette
2008-04-08 23:38 ` John W. Linville [this message]
2008-04-09 8:30 ` Christoph Hellwig
2008-04-09 15:38 ` [ipw3945-devel] [PATCH] Make IWLCORE a silent option not toconfuse " Chatre, Reinette
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=20080408233858.GA23670@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=jason@acm.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@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 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.