From: Greg KH <greg@kroah.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Sasha Levin <sashal@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment
Date: Sun, 23 Jun 2019 06:52:32 +0200 [thread overview]
Message-ID: <20190623045232.GA30005@kroah.com> (raw)
In-Reply-To: <F46C65F2-411F-4B24-BD3C-ED9F39F5E65E@holtmann.org>
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
prev parent reply other threads:[~2019-06-23 4:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 13:47 [PATCH v5.2-rc5] Bluetooth: Fix regression with minimum encryption key size alignment Marcel Holtmann
2019-06-22 18:13 ` Sasha Levin
2019-06-22 18:21 ` Marcel Holtmann
2019-06-23 4:52 ` Greg KH [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=20190623045232.GA30005@kroah.com \
--to=greg@kroah.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.