From: Marcel Holtmann <marcel@holtmann.org>
To: Alexandre Macabies <web+oss@zopieux.com>
Cc: linux-wpan@vger.kernel.org, Alexander Aring <aar@pengutronix.de>
Subject: Re: [PATCH v3 2/3] mrf24j40: fix security-enabled processing on inbound frames
Date: Wed, 13 Apr 2016 09:44:06 +0100 [thread overview]
Message-ID: <76BE7A9B-0C8F-406C-9846-6A584DD2304B@holtmann.org> (raw)
In-Reply-To: <1460479982-4955-2-git-send-email-web+oss@zopieux.com>
Hi Alexandre,
> When receiving a security-enabled IEEE 802.15.4 frame, the MRF24J40
> triggers a SECIF interrupt that needs to be handled for RX processing
> to keep functioning properly.
>
> This patch enables the SECIF interrupt and makes the MRF ignores all
> hardware processing of security-enabled frames, that is handled by the
> ieee802154 stack instead.
>
> Signed-off-by: Alexander Aring <aar@pengutronix.de>
> Signed-off-by: Alexandre Macabies <web+oss@zopieux.com>
> Reviewed-by: Stefan Schmidt <stefan@osg.samsung.com>
> Acked-by: Alan Ott <alan@signal11.us>
> ---
> drivers/net/ieee802154/mrf24j40.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
patch has been applied to bluetooth-next tree.
Regards
Marcel
next prev parent reply other threads:[~2016-04-13 8:44 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 18:14 [PATCH 1/3] ieee802154: add security bit check function web+oss
2016-03-10 18:14 ` [PATCH 2/3] mrf24j40: fix security-enabled processing on inbound frames web+oss
2016-03-14 11:05 ` Stefan Schmidt
2016-03-10 18:14 ` [PATCH 3/3] mrf24j40: apply the security-enabled bit on secured outbound frames web+oss
2016-03-14 11:06 ` Stefan Schmidt
2016-03-14 11:03 ` [PATCH 1/3] ieee802154: add security bit check function Stefan Schmidt
2016-04-08 17:37 ` Marcel Holtmann
2016-03-14 20:46 ` [PATCH v2 " Alexandre Macabies
2016-03-14 20:46 ` [PATCH v2 2/3] mrf24j40: fix security-enabled processing on inbound frames Alexandre Macabies
2016-03-30 8:45 ` Stefan Schmidt
2016-03-14 20:46 ` [PATCH v2 3/3] mrf24j40: apply the security-enabled bit on secured outbound frames Alexandre Macabies
2016-03-30 8:45 ` Stefan Schmidt
2016-03-30 8:45 ` [PATCH v2 1/3] ieee802154: add security bit check function Stefan Schmidt
2016-03-30 14:05 ` Alan Ott
2016-03-30 16:43 ` Stefan Schmidt
2016-04-08 17:35 ` Marcel Holtmann
2016-04-12 16:53 ` [PATCH v3 " Alexandre Macabies
2016-04-12 16:53 ` [PATCH v3 2/3] mrf24j40: fix security-enabled processing on inbound frames Alexandre Macabies
2016-04-13 8:44 ` Marcel Holtmann [this message]
2016-04-12 16:53 ` [PATCH v3 3/3] mrf24j40: apply the security-enabled bit on secured outbound frames Alexandre Macabies
2016-04-13 8:44 ` Marcel Holtmann
2016-04-13 8:44 ` [PATCH v3 1/3] ieee802154: add security bit check function Marcel Holtmann
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=76BE7A9B-0C8F-406C-9846-6A584DD2304B@holtmann.org \
--to=marcel@holtmann.org \
--cc=aar@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=web+oss@zopieux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.