From: Michael Buesch <mb@bu3sch.de>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Jiri Benc <jbenc@suse.cz>, netdev@vger.kernel.org
Subject: Re: [PATCH 5/5] bcm43xx-d80211: fix sending of fragments
Date: Thu, 15 Jun 2006 18:55:11 +0200 [thread overview]
Message-ID: <200606151855.11953.mb@bu3sch.de> (raw)
In-Reply-To: <200606122135.17198.mb@bu3sch.de>
On Monday 12 June 2006 21:35, Michael Buesch wrote:
> On Monday 12 June 2006 21:16, Jiri Benc wrote:
> > This makes fragmentation work with bcm43xx.
> >
> > Signed-off-by: Jiri Benc <jbenc@suse.cz>
>
> Signed-off-by: Michael Buesch <mb@bu3sch.de>
>
> The other patch will get my sign-off tomorrow (I think modified, though).
> I don't have time to look at it more close, now.
Please also merge the other patch. It is too hard to figure out
the dependencies for me now. So simply merge it and I will submit
a fixup patch later, after you pushed it out.
The Subject was:
[incomplete 2/5] bcm43xx-d80211: per-queue TX flow control
It's not so much of trouble, if we break wireless-dev for one or
two days, so this is easiest.
Please notify me after you pushed the stuff to public repository,
so I can pull and fix it.
--
Greetings Michael.
next prev parent reply other threads:[~2006-06-15 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 19:16 [PATCH 0/5] d80211: better fragmentation handling Jiri Benc
2006-06-12 19:16 ` [PATCH 1/5] d80211: per-queue TX flow control Jiri Benc
2006-06-12 19:16 ` [incomplete 2/5] bcm43xx-d80211: " Jiri Benc
2006-06-12 19:16 ` [PATCH 3/5] d80211: handle full queue when sending fragments Jiri Benc
2006-06-12 19:16 ` [PATCH 4/5] d80211: add first_fragment flag to ieee80211_tx_control Jiri Benc
2006-06-12 19:16 ` [PATCH 5/5] bcm43xx-d80211: fix sending of fragments Jiri Benc
2006-06-12 19:35 ` Michael Buesch
2006-06-15 16:55 ` Michael Buesch [this message]
2006-06-15 20:27 ` Jiri Benc
2006-06-15 20:35 ` Michael Buesch
2006-06-14 16:36 ` [PATCH 6/5] rt2x00: per-queue TX flow control Jiri Benc
2006-06-14 18:35 ` Ivo van Doorn
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=200606151855.11953.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).