All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: dragoran <drago01@gmail.com>
Cc: Jes Sorensen <jes@sgi.com>, Dan Williams <dcbw@redhat.com>,
	yi.zhu@intel.com, linux-wireless@vger.kernel.org,
	Tomas Winkler <tomas.winkler@intel.com>
Subject: Re: iwl4965 detection problem
Date: Fri, 26 Oct 2007 12:50:12 -0400	[thread overview]
Message-ID: <20071026165012.GE23415@tuxdriver.com> (raw)
In-Reply-To: <f6ca9fed0710260823u302cc2cco6dab40100870dbf8@mail.gmail.com>

On Fri, Oct 26, 2007 at 05:23:50PM +0200, dragoran wrote:
> On 10/26/07, Jes Sorensen <jes@sgi.com> wrote:
> > Jes Sorensen wrote:
> > > I haven't had a chance to build the driver with this change, ie. it's
> > > untested, but I have a suspicion that this patch might do the job.
> >
> > So, tested a kernel with this patch applied, and voila! My wireless
> > now works on first boot!
> >
> > Should I post it to linux-kernel or Andrew or will someone on this list
> > collect it and push it upstream?
> 
> posting it here is enough.
> you should add 3945 repost it in a new thread.

I've got the patch, duped for 3945 as well.

Thanks,

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2007-10-26 16:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 13:37 iwl4965 detection problem Jes Sorensen
2007-10-25 13:45 ` Dan Williams
2007-10-25 14:15   ` Jes Sorensen
2007-10-25 17:32     ` Dan Williams
2007-10-26  8:05       ` Jes Sorensen
2007-10-26 12:30         ` John W. Linville
2007-10-26 12:45           ` Jes Sorensen
2007-10-26 14:10             ` Jes Sorensen
2007-10-26 14:41               ` John W. Linville
2007-10-26 14:43                 ` Jes Sorensen
2007-10-26 15:17               ` Jes Sorensen
2007-10-26 15:23                 ` dragoran
2007-10-26 16:50                   ` John W. Linville [this message]
2007-10-29  1:14               ` Zhu Yi

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=20071026165012.GE23415@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dcbw@redhat.com \
    --cc=drago01@gmail.com \
    --cc=jes@sgi.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    --cc=yi.zhu@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.