From: Alexander Aring <alex.aring@gmail.com>
To: Lennert Buytenhek <buytenh@wantstofly.org>
Cc: linux-wpan@vger.kernel.org
Subject: Re: [PATCHv2 bluetooth-next 6/6] mac802154: mac802154_mlme_start_req() optimisation.
Date: Tue, 26 May 2015 20:17:14 +0200 [thread overview]
Message-ID: <20150526181712.GA2954@omega> (raw)
In-Reply-To: <20150525123851.GO11340@wantstofly.org>
On Mon, May 25, 2015 at 03:38:51PM +0300, Lennert Buytenhek wrote:
> mac802154_mlme_start_req() calls
> ieee802154_mlme_ops(dev)->llsec->set_params() on the net_device
> passed into it, however, this net_device will always be a mac802154
> net_device, so just call mac802154_set_params() directly instead.
>
> Signed-off-by: Lennert Buytenhek <buytenh@wantstofly.org>
Acked-by: Alexander Aring <alex.aring@gmail.com>
prev parent reply other threads:[~2015-05-26 18:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1432535597.git.buytenh@wantstofly.org>
2015-05-25 12:38 ` [PATCHv2 bluetooth-next 1/6] ieee802154 socket: Return EMSGSIZE from raw_sendmsg() if packet too big Lennert Buytenhek
2015-05-25 12:38 ` [PATCHv2 bluetooth-next 2/6] Documentation/networking/ieee802154.txt: fix various inaccuracies Lennert Buytenhek
2015-05-26 18:17 ` Alexander Aring
2015-05-25 12:38 ` [PATCHv2 bluetooth-next 3/6] ieee802154: Remove ieee802154_reduced_mlme_ops references Lennert Buytenhek
2015-05-25 12:38 ` [PATCHv2 bluetooth-next 4/6] ieee802154: Remove 802.15.4/6LoWPAN checks for interface MTU Lennert Buytenhek
2015-05-25 12:38 ` [PATCHv2 bluetooth-next 5/6] ieee802154 socket: No need to check for ARPHRD_IEEE802154 in raw_bind() Lennert Buytenhek
2015-05-25 12:38 ` [PATCHv2 bluetooth-next 6/6] mac802154: mac802154_mlme_start_req() optimisation Lennert Buytenhek
2015-05-26 18:17 ` Alexander Aring [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=20150526181712.GA2954@omega \
--to=alex.aring@gmail.com \
--cc=buytenh@wantstofly.org \
--cc=linux-wpan@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