From: reinette chatre <reinette.chatre@intel.com>
To: "sedat.dilek@gmail.com" <sedat.dilek@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Zheng, Jiajia" <jiajia.zheng@intel.com>,
"Kolekar, Abhijeet" <abhijeet.kolekar@intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: pull request: wireless-2.6 2010-05-28
Date: Tue, 01 Jun 2010 09:22:41 -0700 [thread overview]
Message-ID: <1275409361.2091.27208.camel@rchatre-DESK> (raw)
In-Reply-To: <AANLkTil8SLseSeq1M_Xg7P4AqMy3V_0jxc7by2Xuaqnb@mail.gmail.com>
Hi Sedat,
On Sat, 2010-05-29 at 06:34 -0700, Sedat Dilek wrote:
> Two people confirmed the patch in [2] fixes:
> 1. iwlwifi-2.6 GIT master (commit f10a237c95abd6d64a3a24553bd1d3bcddd9108b)
> 2. compat-wireless (2010-05-21)
>
> And it fixes also the above mentionned combination.
We are working on getting this patch upstream. The version tested
contains a significant amount of duplicated code as well as some cleanup
code mixed in. It is thus not appropriate for an upstream submission at
this time.
> As a suggestion:
> What about "copying" bug-reports (incl. its history) from IWL-BTS into
> linux-wireless ML?
> For example (dri-devel related) bug-reports from
> bugzilla.freedesktop.org are "copied" into dri-devel ML.
Pointing people to the bug report seems to work ok. What benefit does
the above have?
Reinette
next prev parent reply other threads:[~2010-06-01 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-28 18:09 pull request: wireless-2.6 2010-05-28 John W. Linville
[not found] ` <20100528180952.GC2405-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2010-05-29 6:01 ` David Miller
2010-05-29 13:34 ` Sedat Dilek
2010-06-01 16:22 ` reinette chatre [this message]
2010-06-02 8:42 ` Sedat Dilek
2010-06-02 16:01 ` reinette chatre
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=1275409361.2091.27208.camel@rchatre-DESK \
--to=reinette.chatre@intel.com \
--cc=abhijeet.kolekar@intel.com \
--cc=davem@davemloft.net \
--cc=jiajia.zheng@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sedat.dilek@gmail.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