* Re: [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment
[not found] <20190622134701.7088-1-marcel@holtmann.org>
@ 2019-06-22 18:13 ` Sasha Levin
2019-06-22 18:21 ` Marcel Holtmann
0 siblings, 1 reply; 3+ messages in thread
From: Sasha Levin @ 2019-06-22 18:13 UTC (permalink / raw)
To: Sasha Levin, Marcel Holtmann, torvalds
Cc: linux-kernel, linux-bluetooth, stable, stable
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 963 bytes --]
Hi,
[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?
--
Thanks,
Sasha
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment
2019-06-22 18:13 ` [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment Sasha Levin
@ 2019-06-22 18:21 ` Marcel Holtmann
2019-06-23 4:52 ` Greg KH
0 siblings, 1 reply; 3+ messages in thread
From: Marcel Holtmann @ 2019-06-22 18:21 UTC (permalink / raw)
To: Sasha Levin
Cc: Linus Torvalds, Linux Kernel Mailing List,
open list:BLUETOOTH DRIVERS, stable
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment
2019-06-22 18:21 ` Marcel Holtmann
@ 2019-06-23 4:52 ` Greg KH
0 siblings, 0 replies; 3+ messages in thread
From: Greg KH @ 2019-06-23 4:52 UTC (permalink / raw)
To: Marcel Holtmann
Cc: Sasha Levin, Linus Torvalds, Linux Kernel Mailing List,
open list:BLUETOOTH DRIVERS, stable
On Sat, Jun 22, 2019 at 08:21:07PM +0200, Marcel Holtmann wrote:
> 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.
I can reapply it...
thanks,
greg k-h
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-06-23 4:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <20190622134701.7088-1-marcel@holtmann.org>
2019-06-22 18:13 ` [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment Sasha Levin
2019-06-22 18:21 ` Marcel Holtmann
2019-06-23 4:52 ` Greg KH
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).