Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Ron Rindjunsky" <rindjon@googlemail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linville@tuxdriver.com, linux-wireless@vger.kernel.org,
	flamingice@sourmilk.net, tomas.winkler@intel.com,
	yi.zhu@intel.com
Subject: Re: [PATCH 03/12] mac80211: A-MPDU Tx adding basic functionality
Date: Sun, 27 Jan 2008 19:25:47 +0200	[thread overview]
Message-ID: <c85cb4470801270925g49203959l7fd7b35f472d9e73@mail.gmail.com> (raw)
In-Reply-To: <1201167281.3454.65.camel@johannes.berg>

> > +     /* Will put all the packets in the new SW queue */
> > +     /* ieee80211_requeue(local, ieee802_1d_to_ac[tid]); */
> > +     spin_unlock_bh(&local->mdev->queue_lock);
> > +
> > +     /* We have most probably almost emptied the legacy queue */
> > +     /* ieee80211_wake_queue(local_to_hw(local), ieee802_1d_to_ac[tid]); */
>
>
> Can't you re-order the patches instead? Or, if it simply doesn't work,
> I'd much prefer them to go into the tree as a single patch. (You also
> introduced leading whitespace in the patches removing the comment marks)
>

No problems, i'll make patches 0003 and 0006 consequent, but i think
it is better they will stay a part for better reading, as they touch
different parts in the code, and patch 0003 is big enough as it is.
I'll remove the whitespaces.

> johannes
>
>

  reply	other threads:[~2008-01-27 17:25 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 11:52 [PATCH 0/12] mac80211/iwlwifi: A-MPDU Tx support Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 01/12] mac80211: A-MPDU Tx add session's and low level driver's API Ron Rindjunsky
2008-01-24  9:23   ` Johannes Berg
2008-01-27 17:24     ` Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 02/12] mac80211: A-MPDU Tx add MLME structures Ron Rindjunsky
2008-01-24  9:29   ` Johannes Berg
2008-01-27 17:25     ` Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 03/12] mac80211: A-MPDU Tx adding basic functionality Ron Rindjunsky
2008-01-24  9:30   ` Johannes Berg
2008-01-27 17:25     ` Ron Rindjunsky
2008-01-24  9:34   ` Johannes Berg
2008-01-27 17:25     ` Ron Rindjunsky [this message]
2008-01-21 11:52 ` [PATCH 04/12] mac80211: A-MPDU Tx MLME data initialization Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 05/12] mac80211: A-MPDU add debugfs support Ron Rindjunsky
2008-01-24  9:45   ` Johannes Berg
2008-01-21 11:52 ` [PATCH 06/12] mac80211: A-MPDU Tx adding qdisc support Ron Rindjunsky
2008-01-24  9:42   ` Johannes Berg
2008-01-27 17:26     ` Ron Rindjunsky
2008-01-29 16:12       ` Johannes Berg
2008-01-30  9:11         ` Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 07/12] mac80211: A-MPDU Tx change tx_status to support Block Ack data Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 08/12] mac80211: A-MPDU Tx add delBA from recipient support Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 09/12] iwlwifi: A-MPDU Tx conform API to mac80211 Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 10/12] iwlwifi: A-MPDU Tx conform flows " Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 11/12] iwlwifi: A-MPDU Tx conform block Ack rate scaling " Ron Rindjunsky
2008-01-21 11:52 ` [PATCH 12/12] wlwifi: A-MPDU Tx activation by load measures Ron Rindjunsky

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=c85cb4470801270925g49203959l7fd7b35f472d9e73@mail.gmail.com \
    --to=rindjon@googlemail.com \
    --cc=flamingice@sourmilk.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=tomas.winkler@intel.com \
    --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