From: Gabor Juhos <juhosg@openwrt.org>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
rt2x00 Users List <users@rt2x00.serialmonkey.com>
Subject: Re: [PATCH 0/7] rt2x00: avoid a few superfluous pointer dereferences
Date: Wed, 01 May 2013 22:41:52 +0200 [thread overview]
Message-ID: <51817E10.2000906@openwrt.org> (raw)
In-Reply-To: <CAL1gcdNQc1-vrxv5LGp3rtcLDPhNRqnCqedYRZdt+V4PSc71rg@mail.gmail.com>
Hi Gertjan,
> On Wed, May 1, 2013 at 5:17 PM, Gabor Juhos <juhosg@openwrt.org> wrote:
>> Gabor Juhos (7):
>> rt2x00: rt2x00dev: use rt2x00dev->tx->limit
>> rt2x00: rt61pci: use rt2x00dev->tx->limit
>> rt2x00: rt2800pci: use rt2x00dev->tx->limit
>> rt2x00: rt2800usb: use rt2x00dev->rx->limit
>> rt2x00: rt2800lib: use rt2x00dev->bcn->winfo_size
>> rt2x00: rt2x00dev: defer operational mode detection
>> rt2x00: rt2x00dev: use rt2x00dev->bcn->limit
>>
>> drivers/net/wireless/rt2x00/rt2800lib.c | 2 +-
>> drivers/net/wireless/rt2x00/rt2800pci.c | 2 +-
>> drivers/net/wireless/rt2x00/rt2800usb.c | 2 +-
>> drivers/net/wireless/rt2x00/rt2x00dev.c | 36 +++++++++++++++----------------
>> drivers/net/wireless/rt2x00/rt61pci.c | 2 +-
>> 5 files changed, 22 insertions(+), 22 deletions(-)
>>
>
> Thanks for these. Although they are micro optimizations, I guess it is
> cleaner to use the actual queue data rather than the queue description data.
To be honest, I made these patches in preparation of queue descriptor data
removal. However these changes are not strictly related to that, so I posted the
patches as a separate series.
> I've acked all patches,
Thanks!
> but I'm afraid they may have come just too late to be included in
> the 3.10 timeframe, but I leave it up to John to decide.
No problem, the patches can wait for 3.11.
-Gabor
prev parent reply other threads:[~2013-05-01 20:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 15:17 [PATCH 0/7] rt2x00: avoid a few superfluous pointer dereferences Gabor Juhos
2013-05-01 15:17 ` [PATCH 1/7] rt2x00: rt2x00dev: use rt2x00dev->tx->limit Gabor Juhos
2013-05-01 20:05 ` Gertjan van Wingerde
2013-06-03 17:09 ` [rt2x00-users] " Jakub Kicinski
2013-06-03 20:32 ` Gabor Juhos
2013-05-01 15:17 ` [PATCH 2/7] rt2x00: rt61pci: " Gabor Juhos
2013-05-01 20:06 ` Gertjan van Wingerde
2013-05-01 15:17 ` [PATCH 3/7] rt2x00: rt2800pci: " Gabor Juhos
2013-05-01 20:06 ` Gertjan van Wingerde
2013-05-01 15:17 ` [PATCH 4/7] rt2x00: rt2800usb: use rt2x00dev->rx->limit Gabor Juhos
2013-05-01 20:07 ` Gertjan van Wingerde
2013-05-01 15:17 ` [PATCH 5/7] rt2x00: rt2800lib: use rt2x00dev->bcn->winfo_size Gabor Juhos
2013-05-01 20:07 ` Gertjan van Wingerde
2013-05-01 15:17 ` [PATCH 6/7] rt2x00: rt2x00dev: defer operational mode detection Gabor Juhos
2013-05-01 20:08 ` Gertjan van Wingerde
2013-05-01 15:17 ` [PATCH 7/7] rt2x00: rt2x00dev: use rt2x00dev->bcn->limit Gabor Juhos
2013-05-01 20:08 ` Gertjan van Wingerde
2013-05-02 7:36 ` Gabor Juhos
2013-05-22 18:53 ` John W. Linville
2013-05-01 20:10 ` [PATCH 0/7] rt2x00: avoid a few superfluous pointer dereferences Gertjan van Wingerde
2013-05-01 20:41 ` Gabor Juhos [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=51817E10.2000906@openwrt.org \
--to=juhosg@openwrt.org \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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).