From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 1/2] ath10k: introduce struct ath10k_skb_rxcb
Date: Tue, 27 Jan 2015 15:57:54 +0200 [thread overview]
Message-ID: <877fw8com5.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1421407029-23967-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 16 Jan 2015 12:17:08 +0100")
Michal Kazior <michal.kazior@tieto.com> writes:
> It doesn't make much sense to share the
> ath10k_skb_cb with Rx path. The Rx path doesn't
> need to keep any mac80211's data.
>
> Signed-off-by: Michal Kazior <michal.kazior@tieto.com>
Thanks, both patches applied to ath.git.
--
Kalle Valo
prev parent reply other threads:[~2015-01-27 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 11:17 [PATCH 1/2] ath10k: introduce struct ath10k_skb_rxcb Michal Kazior
2015-01-16 11:17 ` [PATCH 2/2] ath10k: implement rx reorder support Michal Kazior
2015-01-27 13:57 ` Kalle Valo [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=877fw8com5.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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).