From: Johannes Berg <johannes@sipsolutions.net>
To: sedat.dilek@gmail.com
Cc: LKML <linux-kernel@vger.kernel.org>,
wireless <linux-wireless@vger.kernel.org>,
sfr@canb.auug.org.au, Randy Dunlap <randy.dunlap@oracle.com>,
John Linville <linville@tuxdriver.com>,
Wey-Yi Guy <wey-yi.w.guy@intel.com>
Subject: Re: linux-next: Tree for November 24 (iwlwifi-fix)
Date: Wed, 24 Nov 2010 07:14:45 +0100 [thread overview]
Message-ID: <1290579285.3790.1.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <AANLkTinVUkgZKbAkQ3_27Jw3cXJ7qySxm1UMFSReujfp@mail.gmail.com>
On Wed, 2010-11-24 at 07:09 +0100, Sedat Dilek wrote:
> Is that fix still required? Fixed in wireless-next-2.6?
That patch was causing that problem, but I fixed the original problem
since.
johannes
next prev parent reply other threads:[~2010-11-24 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 6:09 linux-next: Tree for November 24 (iwlwifi-fix) Sedat Dilek
2010-11-24 6:14 ` Johannes Berg [this message]
2010-11-24 8:54 ` Sedat Dilek
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=1290579285.3790.1.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=randy.dunlap@oracle.com \
--cc=sedat.dilek@gmail.com \
--cc=sfr@canb.auug.org.au \
--cc=wey-yi.w.guy@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;
as well as URLs for NNTP newsgroup(s).