From: Pavel Roskin <proski@gnu.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-wireless@vger.kernel.org, ipw3945-devel@lists.sourceforge.net
Subject: Re: iwlwifi warnings
Date: Fri, 23 Feb 2007 00:44:58 -0500 [thread overview]
Message-ID: <1172209498.20817.54.camel@dv> (raw)
In-Reply-To: <20070221193836.GC3732@elf.ucw.cz>
On Wed, 2007-02-21 at 20:38 +0100, Pavel Machek wrote:
> "Normal" installation procedure has too many steps in my eyes, and
> combined git tree is not available, so I was waiting for merge at
> least into -wirelessdev tree.
"make patch_kernel" would patch the kernel from wireless-dev.git. If
the Linux source tree is not configured, just run "make distclean" after
that (or apply my patch from the previous post in the ipw3945-devel
list).
You can use StGIT for convert the changes made by "make patch_kernel" to
a local patch so that updating from the upstream git repository is still
possible with "stg pull".
No need to wait for anything.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2007-02-23 5:45 UTC|newest]
Thread overview: 78+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-09 21:12 [ANNOUNCE] d80211 based driver for Intel PRO/Wireless 3945ABG James Ketrenos
2007-02-09 21:12 ` James Ketrenos
2007-02-09 22:14 ` Alon Bar-Lev
2007-02-09 22:26 ` Neil Brown
2007-02-09 22:26 ` Neil Brown
2007-02-09 21:52 ` James Ketrenos
2007-02-09 21:52 ` James Ketrenos
2007-02-10 3:26 ` Nick Kossifidis
2007-02-09 22:37 ` Stefan Schmidt
2007-02-09 22:37 ` Stefan Schmidt
2007-02-09 22:43 ` Pavel Roskin
2007-02-09 22:43 ` Pavel Roskin
2007-02-09 22:18 ` James Ketrenos
2007-02-09 22:18 ` James Ketrenos
2007-02-09 23:17 ` Pavel Roskin
2007-02-09 23:17 ` Pavel Roskin
2007-02-09 22:45 ` James Ketrenos
2007-02-09 22:45 ` James Ketrenos
2007-02-09 22:48 ` dragoran dragoran
2007-02-10 0:46 ` [ipw3945-devel] " Norbert Preining
2007-02-10 0:46 ` Norbert Preining
2007-02-10 0:46 ` [ipw3945-devel] " Norbert Preining
2007-02-13 23:23 ` James Ketrenos
2007-02-13 23:23 ` James Ketrenos
2007-02-13 23:23 ` James Ketrenos
2007-02-10 13:23 ` Hesse, Christian
2007-02-10 13:23 ` Hesse, Christian
2007-02-10 14:25 ` Hesse, Christian
2007-02-12 16:32 ` [ipw3945-devel] " dragoran
2007-02-12 16:32 ` dragoran
2007-02-12 18:35 ` James Ketrenos
2007-02-12 18:35 ` James Ketrenos
2007-02-13 12:18 ` Hesse, Christian
2007-02-13 12:18 ` Hesse, Christian
2007-02-11 0:55 ` Pavel Roskin
2007-02-11 13:17 ` Hesse, Christian
2007-02-13 6:47 ` Pavel Roskin
2007-02-13 10:41 ` Hesse, Christian
2007-02-11 13:19 ` Johannes Berg
2007-02-10 16:22 ` Theodore Tso
2007-02-10 16:22 ` Theodore Tso
2007-02-10 16:39 ` John W. Linville
2007-02-10 16:39 ` John W. Linville
2007-02-10 17:53 ` [ipw3945-devel] " Pavel Roskin
2007-02-10 17:53 ` Pavel Roskin
2007-02-10 17:53 ` [ipw3945-devel] " Pavel Roskin
2007-02-10 22:41 ` John W. Linville
2007-02-10 22:41 ` John W. Linville
2007-02-10 18:42 ` Michael Buesch
2007-02-13 13:58 ` Ismail Dönmez
2007-02-13 13:58 ` Ismail Dönmez
2007-02-13 15:10 ` Jeff Chua
2007-02-13 15:10 ` Jeff Chua
2007-02-13 16:57 ` Ismail Dönmez
2007-02-13 16:57 ` Ismail Dönmez
2007-02-13 16:57 ` Ismail Dönmez
2007-02-13 22:55 ` James Ketrenos
2007-02-13 22:55 ` James Ketrenos
2007-02-13 18:13 ` Pavel Machek
2007-02-13 18:36 ` Johannes Berg
2007-02-13 23:18 ` James Ketrenos
2007-02-13 23:18 ` James Ketrenos
2007-02-14 0:16 ` [ipw3945-devel] " James Ketrenos
2007-02-14 0:16 ` James Ketrenos
2007-02-14 0:16 ` James Ketrenos
2007-02-19 22:44 ` Pavel Machek
2007-02-19 22:44 ` Pavel Machek
2007-02-19 22:44 ` Pavel Machek
2007-02-21 6:23 ` iwlwifi warnings Stephen Hemminger
2007-02-21 6:23 ` Stephen Hemminger
2007-02-21 7:32 ` Randy Dunlap
2007-02-21 7:32 ` Randy Dunlap
2007-02-21 19:38 ` Pavel Machek
2007-02-21 19:38 ` Pavel Machek
2007-02-23 5:44 ` Pavel Roskin [this message]
2009-01-27 9:15 Johannes Berg
2009-01-27 9:34 ` Tomas Winkler
2009-01-27 9:38 ` Johannes Berg
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=1172209498.20817.54.camel@dv \
--to=proski@gnu.org \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pavel@ucw.cz \
/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.