From: Luciano Coelho <luciano.coelho@nokia.com>
To: ext Eliad Peller <eliad@wizery.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] wl1271: avoid redundant memcpy of rx_status
Date: Sun, 19 Sep 2010 22:46:12 +0300 [thread overview]
Message-ID: <1284925572.10001.4.camel@powerslave> (raw)
In-Reply-To: <1284915309-999-1-git-send-email-eliad@wizery.com>
On Sun, 2010-09-19 at 18:55 +0200, ext Eliad Peller wrote:
> copy the rx_status directly to skb->cb (control buffer) instead of copying
> it to a local struct and then copying it again (for each rx packet)
>
> Signed-off-by: Eliad Peller <eliad@wizery.com>
> ---
Acked-by: Luciano Coelho <luciano.coelho@nokia.com>
Thanks, Eliad!
--
Cheers,
Luca.
prev parent reply other threads:[~2010-09-19 19:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-19 16:55 [PATCH 1/2] wl1271: avoid redundant memcpy of rx_status Eliad Peller
2010-09-19 16:55 ` [PATCH 2/2] wl1271: bugfix: use bitwise-AND instead of logical-AND Eliad Peller
2010-09-19 19:47 ` Luciano Coelho
2010-09-19 19:46 ` Luciano Coelho [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=1284925572.10001.4.camel@powerslave \
--to=luciano.coelho@nokia.com \
--cc=eliad@wizery.com \
--cc=linux-wireless@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).