From: Johannes Berg <johannes@sipsolutions.net>
To: Tomas Winkler <tomasw@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Zhu Yi <yi.zhu@intel.com>
Subject: Re: iwlwifi sparse warnings with __CHECK_ENDIAN__
Date: Sat, 08 Sep 2007 11:38:19 +0200 [thread overview]
Message-ID: <1189244299.4506.19.camel@johannes.berg> (raw)
In-Reply-To: <1ba2fa240709080120j1c67dbc8m14c91529085cc19a@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 396 bytes --]
On Sat, 2007-09-08 at 11:20 +0300, Tomas Winkler wrote:
> The version in wireless-dev is 0.1.8 and we are 0.1.15 on stable and
> 1.1.0 on the development branch. Looks like Yi's patches weren't
> synced for a while.
Huh ok. John is at KS anyhow, but we really need a better plan how to
continue developing stuff. No wonder if I've been looking at ancient
code all along...
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
prev parent reply other threads:[~2007-09-08 9:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 17:33 iwlwifi sparse warnings with __CHECK_ENDIAN__ Johannes Berg
2007-09-08 7:37 ` Tomas Winkler
2007-09-08 7:41 ` Johannes Berg
2007-09-08 8:20 ` Tomas Winkler
2007-09-08 9:38 ` Johannes Berg [this message]
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=1189244299.4506.19.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=tomasw@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox