lkml.org 
[lkml]   [2019]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRe: [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment
From
Date
Hi Sasha,

> [This is an automated email]
>
> This commit has been processed because it contains a "Fixes:" tag,
> fixing commit: d5bb334a8e17 Bluetooth: Align minimum encryption key size for LE and BR/EDR connections.
>
> The bot has tested the following trees: v5.1.12, v4.19.53, v4.14.128, v4.9.182, v4.4.182.
>
> v5.1.12: Build failed! Errors:
> net/bluetooth/l2cap_core.c:1356:24: error: ‘HCI_MIN_ENC_KEY_SIZE’ undeclared (first use in this function); did you mean ‘SMP_MIN_ENC_KEY_SIZE’?
>
> v4.19.53: Build failed! Errors:
> net/bluetooth/l2cap_core.c:1355:24: error: ‘HCI_MIN_ENC_KEY_SIZE’ undeclared (first use in this function); did you mean ‘SMP_MIN_ENC_KEY_SIZE’?
>
> v4.14.128: Build failed! Errors:
> net/bluetooth/l2cap_core.c:1355:24: error: ‘HCI_MIN_ENC_KEY_SIZE’ undeclared (first use in this function); did you mean ‘SMP_MIN_ENC_KEY_SIZE’?
>
> v4.9.182: Build OK!
> v4.4.182: Build OK!
>
> How should we proceed with this patch?

either you reapply commit d5bb334a8e17 first or I have to send a version that combines both into a single commit for easy applying.

Regards

Marcel

\
 
 \ /
  Last update: 2019-06-22 20:22    [W:0.035 / U:0.416 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site