From: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
To: johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: pull request: bluetooth-next 2017-04-30
Date: Mon, 01 May 2017 14:50:19 -0400 (EDT) [thread overview]
Message-ID: <20170501.145019.1619484787513762409.davem@davemloft.net> (raw)
In-Reply-To: <20170501184221.GA2093@x1c>
From: Johan Hedberg <johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Date: Mon, 1 May 2017 21:42:21 +0300
> Hi Dave,
>
> On Sun, Apr 30, 2017, David Miller wrote:
>> From: Johan Hedberg <johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
>> Date: Sun, 30 Apr 2017 17:09:28 +0300
>>
>> > Here's one last batch of Bluetooth patches in the bluetooth-next tree
>> > targeting the 4.12 kernel.
>> >
>> > - Remove custom ECDH implementation and use new KPP API instead
>> > - Add protocol checks to hci_ldisc
>> > - Add module license to HCI UART Nokia H4+ driver
>> > - Minor fix for 32bit user space - 64 bit kernel combination
>> >
>> > Please let me know if there are any issues pulling. Thanks.
>>
>> Pulled, thanks Johan.
>
> Thanks, however I don't see the patches in net-next yet. I have seen
> other patches go in there since your response though. Cause for concern?
Shuld be there now.
next prev parent reply other threads:[~2017-05-01 18:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-30 14:09 pull request: bluetooth-next 2017-04-30 Johan Hedberg
2017-05-01 3:03 ` David Miller
2017-05-01 18:42 ` Johan Hedberg
2017-05-01 18:50 ` David Miller [this message]
2017-05-01 19:21 ` Johan Hedberg
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=20170501.145019.1619484787513762409.davem@davemloft.net \
--to=davem-ft/pcqaiutieiz0/mpfg9q@public.gmane.org \
--cc=johan.hedberg-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-bluetooth-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.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 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).