On 02/18/2016 01:34 PM, zopieux wrote:
Fix the MRF24J40 handling of security-enabled frames so it does not block upon receiving such frames. Signed-off-by: Alexander Aring <aar@xxxxxxxxxxxxxx> Reported-by: Alexandre Macabies <web+oss@xxxxxxxxxxx> Tested-by: Alexandre Macabies <web+oss@xxxxxxxxxxx> --- 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. ---
The "From" field of the email needs to have your real name in it. This will be where the "Author" field in git comes from.
It looks like there are a few separate things happening in this patch. Maybe they should be broken out in to separate patches. I see:
1. The ieee802154.h part, 2. The TX part, 3. The RX part. The patch description only really describes the RX part. Other than that, the actual code seems OK to me. Alan. -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
