From: Pavel Machek <pavel@ucw.cz>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "Zhu, Yi" <yi.zhu@intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: iwl3945 in 2.6.31-rc0: ad-hoc mode broken?
Date: Mon, 22 Jun 2009 19:40:02 +0200 [thread overview]
Message-ID: <20090622174002.GD21299@elf.ucw.cz> (raw)
In-Reply-To: <1245692380.24303.494.camel@rc-desk>
On Mon 2009-06-22 10:39:40, reinette chatre wrote:
> Hi Pavel,
>
> On Fri, 2009-06-19 at 15:24 -0700, Pavel Machek wrote:
> > Hi!
> >
> > I tried using ad-hoc mode (against t-mobile G1) on -rc0, and was
> > unsuccessful -- never got dhcp. I had to reboot back to
> > 2.6.30... Should I try it few more times or is something broken?
> >
> > (Also wifi LED stopped working on x60, but that's older issue).
> >
>
> Are you testing Linus's repo here? Should we not maybe wait with testing
> until -rc1 is released?
WTF? Yes, I am testing Linus' tree (hence 2.6.31-rc0). I thought
2.6. stable series is expected to work at all times, and it is bug if
it does not (otherwise git bisect is useless). Did you intentionally
break the tree or what? Or do you have fixes pending?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2009-06-22 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-19 22:24 iwl3945 in 2.6.31-rc0: ad-hoc mode broken? Pavel Machek
2009-06-22 17:39 ` reinette chatre
2009-06-22 17:40 ` Pavel Machek [this message]
2009-06-22 18:01 ` reinette chatre
2009-06-29 18:08 ` reinette chatre
[not found] ` <20090709093859.GA10001@elf.ucw.cz>
[not found] ` <1247153986.17896.1233.camel@rc-desk>
2009-07-18 10:20 ` iwl3945: fix LED config option Pavel Machek
2009-07-20 20:45 ` reinette chatre
2009-07-20 22:19 ` Pavel Machek
2009-07-21 3:02 ` reinette chatre
2009-07-21 7:58 ` Pavel Machek
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=20090622174002.GD21299@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@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.