From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: gregor kowski <gregor.kowski@gmail.com>,
bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [RESEND] [PATCH] b43 : remove old kidx API
Date: Thu, 20 Aug 2009 19:15:13 +0200 [thread overview]
Message-ID: <200908201915.13498.mb@bu3sch.de> (raw)
In-Reply-To: <20090820145213.GB2657@tuxdriver.com>
On Thursday 20 August 2009 16:52:13 John W. Linville wrote:
> On Mon, Jul 27, 2009 at 10:43:36PM +0200, gregor kowski wrote:
> > Remove old kidx API.
> > This simplify the code, and fix a potential key overflow.
> >
> > Signed-off-by: Gregor Kowski <gregor.kowski@gmail.com>
>
> Is this patch still relevant?
no
--
Greetings, Michael.
prev parent reply other threads:[~2009-08-20 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 20:43 [RESEND] [PATCH] b43 : remove old kidx API gregor kowski
2009-08-20 14:52 ` John W. Linville
2009-08-20 17:15 ` Michael Buesch [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=200908201915.13498.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=gregor.kowski@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).