From: reinette chatre <reinette.chatre@intel.com>
To: Norbert Preining <preining@logic.at>
Cc: "Zhu, Yi" <yi.zhu@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>
Subject: Re: [ipw3945-devel] hang on 2.6.33-rc4
Date: Thu, 28 Jan 2010 08:23:59 -0800 [thread overview]
Message-ID: <1264695839.32142.35.camel@rchatre-DESK> (raw)
In-Reply-To: <20100128084150.GI1148@gamma.logic.tuwien.ac.at>
On Thu, 2010-01-28 at 00:41 -0800, Norbert Preining wrote:
> Done that,
> http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2155
Thank you.
>
> Should that be a bug in the kernel bugzilla as regression, too?
> I mean 2.6.32.N does not suffer from that.
It is easier for our team to track bugs in our bugzilla. That is where
we will be working on resolving this issue. If you would like to submit
a kernel bugzilla for the purpose of tracking a regression you are
welcome to, please then just use it for that purpose and point people to
our bugzilla for the details and latest status of this issue.
Thank you
Reinette
prev parent reply other threads:[~2010-01-28 16:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 15:22 Norbert Preining
2010-01-15 17:29 ` [ipw3945-devel] " reinette chatre
2010-01-16 2:30 ` Norbert Preining
2010-01-16 18:30 ` Norbert Preining
2010-01-18 17:06 ` reinette chatre
2010-01-18 17:19 ` Norbert Preining
2010-01-19 5:47 ` Norbert Preining
2010-01-19 17:01 ` reinette chatre
2010-01-19 17:59 ` Johannes Berg
2010-01-20 0:36 ` Norbert Preining
2010-01-20 9:52 ` Johannes Berg
2010-01-20 9:32 ` Zhu Yi
2010-01-21 0:28 ` Norbert Preining
2010-01-21 18:18 ` John Ranson
2010-01-27 15:37 ` Norbert Preining
2010-01-27 16:54 ` reinette chatre
2010-01-28 8:41 ` Norbert Preining
2010-01-28 16:23 ` reinette chatre [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=1264695839.32142.35.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=preining@logic.at \
--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
all inboxes | Powered by JetHome®