From: Andreas Kemnade <andreas@kemnade.info>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Rob Herring <robh@kernel.org>,
sebastian.reichel@collabora.com, hns@goldelico.com,
devicetree@vger.kernel.org,
Johan Hedberg <johan.hedberg@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-bluetooth@vger.kernel.org, letux-kernel@openphoenux.org
Subject: Re: [Letux-kernel] [PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree
Date: Fri, 16 Nov 2018 20:46:01 +0100 [thread overview]
Message-ID: <20181116204601.4e1aa0de@kemnade.info> (raw)
In-Reply-To: <86A3A2E6-FC89-42FE-8410-9C8273EC9CF7@holtmann.org>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
Hi Marcel,
On Wed, 14 Nov 2018 08:51:17 +0100
Marcel Holtmann <marcel@holtmann.org> wrote:
[...[
> Btw. I see nothing standing in the way of merging btuart.c driver and then go from there. Either I dig this out and submit or someone else does.
>
Do you mean this?
https://patchwork.kernel.org/patch/10490651/
Regards,
Andreas
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2018-11-16 19:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-10 23:20 [PATCH RFC] bluetooth: add uart h4 devices via serdev/devicetree Andreas Kemnade
2018-11-11 2:46 ` Sebastian Reichel
2018-11-12 20:59 ` Andreas Kemnade
2018-11-12 21:19 ` [Letux-kernel] " H. Nikolaus Schaller
2018-11-12 22:27 ` Sebastian Reichel
2018-11-13 0:17 ` Rob Herring
2018-11-13 16:01 ` Andreas Kemnade
2018-11-14 7:51 ` Marcel Holtmann
2018-11-14 11:13 ` Andreas Kemnade
2018-11-16 19:46 ` Andreas Kemnade [this message]
2018-11-16 19:58 ` Marcel Holtmann
2019-01-04 5:44 ` Andreas Kemnade
2019-01-04 9:07 ` Marcel Holtmann
2019-01-04 19:57 ` Andreas Kemnade
2019-01-12 11:16 ` Jon Nettleton
2019-01-12 12:15 ` H. Nikolaus Schaller
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=20181116204601.4e1aa0de@kemnade.info \
--to=andreas@kemnade.info \
--cc=devicetree@vger.kernel.org \
--cc=hns@goldelico.com \
--cc=johan.hedberg@gmail.com \
--cc=letux-kernel@openphoenux.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
/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).